The mailing list for listmasters using Sympa

[Thomas Berry <address@concealed>]

  On an enterprise level, list admins who chose to prevent duplicates 
messages to members across lists are made aware of the risks associated. 
 But, this feature has--for the reasons you've indicated--caused some 
confusion.

  Bottom line, for us, it's a "desired" feature, but not a required 
feature--at least not yet.  We'll be doing a larger roll out to the 
organization in mid-May.  Then, we'll have a better feel for what Lyris 
features our users sorely missed.

Thomas


Olivier Salaün wrote:
> We've had requests for this feature for quite a long time but did not 
> implement it because there were details to sort :
>
>    * a message distributed via 2 lists might change on the way (custom
>      subject, footer,...). If the 'no_duplicate' mode is used, how
>      could decide which message should be sent ? First in wins ?
>    * How about users that have filters/triggers configured in their
>      mail client. Eg: I am subscribed to both important-list and
>      less-important-list. I carefully check all messages that were
>      received through important-list, but one day a message is sent to
>      both ; I only it through my less-important-list subscription. I
>      miss this important message...
>
> Thomas, could you describe how the feature is implemented in Lyris ? How 
> do they cope with this problem ? Is it a global parameter or something 
> per list ? per group of lists ?
>
> Thomas Berry wrote:z
>
> > Having recently switched from Lyris to Sympa [for its LDAP support], 
> > this is a Lyris feature that we miss.
> >
> > Miles Fidelman wrote:
> >
> > > Someone just asked me if I could set up a group of 7 lists for them, 
> > > with an interesting property: the lists have overlapping membership, 
> > > and they'd like to set things up so that a message sent to multiple 
> > > lists doesn't show up multiple times, if someone is on more than one 
> > > of the lists. (Think sports teams - a parent has kids on more than 
> > > one team - an announcement about field use goes out to parents of 
> > > kids on 3 of the teams.)
> > >
> > > To be more concrete:
> > > - 7 lists, a-g
> > > - John is on lists a, c, e
> > > - a message is sent to lists a, b, c
> > > - is there a way to set things up so John only gets one copy, instead 
> > > of 2?
> > >
> > > Any thoughts?