The mailing list for listmasters using Sympa

[Warren Anderson <address@concealed>]

Hi Christian,

I had the same problem. I created an LDAP filter in /etc/sympa/search_filters 
and used a scenario file to deal with it. For us, the email lists are defined 
as groups in LDAP to simplify authorization management (the groups are also 
used for web acls, for instance). From my notes, my filters are of the form:

> vi /etc/sympa/search_filters/MyGroup.ldap and add
>         host            my.ldap.edu:389
>         suffix          ou=people,dc=my,dc=org
>         filter          (&(mail = 
> [sender])(isMemberOf=Groups:MyGroupMembers))
>         scope           sub

You want whatever LDAP attributes will contain the email addresses in the 
first clause of the filter. We currently dump them all in mail, since it is a 
multivalued attribute, so mail = [sender] is sufficient. However, if you have 
them sprinkled in multiple attributes, it's not much harder, eg (&(|(mail = 
[sender])(mailalternateaddress = 
[sender]))(isMemberOf=Groups:MyGroupMembers)). Once you have defined this 
filter, you use it in a scenario.

> vi /etc/sympa/scenari/send.MyGroup
>         title.gettext MyGroup members allowed, moderated for non subscribers
>         search(MyGroup.ldap)               smtp,smime,md5    -> do_it
>         is_editor([listname],[sender])     smtp,smime,md5    -> do_it
>         true()                             smtp,smime,md5    -> editorkey

This scenario allows anything returned by the LDAP search defined in 
MyGroup.ldap to be accepted as send address. Make sure that all the new files 
are owned correctly (sympa:sympa) and restart sympa. Then go to the admin 
menu of the list you want to accept alternate email addresses to send to, and 
select "MyGroup members allowed, moderated for non subscribers" or whatever 
the title text you've put in your scenario file, and click the update button.

These instructions are based on sympa 5.4.x, so your mileage may vary by 
version.

Cheers,
Warren

On Feb 17, 2010, at 08:47 , Christian Dahlhausen wrote:

> Thanks for the hint. We have a similar constellation and people want to be 
> able to send to subscribed mailing lists from all their aliases. 
> 
> I managed to import their alternate aliases, but that also sends post to a 
> mailing list to all their aliases. How do you cope with that? Is there a 
> way to flag the alternate aliases and set them to nomail when they are 
> going to be imported?
> 
> Thanks, Christian
> 
> 
> 
> On Wed, Sep 16, 2009 at 3:55 PM, christopher pax <address@concealed> wrote:
> I am in the same boat as you are on this topic. My solution is to use ldap. 
> In our ldap, for each user, there is an attribute that holds all there 
> aliases (mailalternateaddresses). 
> 
> for subscribers:
> in the include_ldap_query paragraph, I use mailalternateaddress in the 
> 'extracted attribute'.
> 
> for owners and editors:
> this is more tricky. you need a include file with a ldap paragraph in it.
> navigate to
> /home/sympa/expl/ROBOT/LISTNAME/data_sources
> OR
> /home/sympa/data_sources/
> 
> create a file called, myincludefile.incl
> 
> and wrtie a sympa ldap paragraph that includes the owners and extracts 
> their alternateaddress, here is an example:
> include_ldap_query
>         attrs mailalternateaddress
>         ssl_ciphers ALL
>         filter (usetype=faculty)
>         name anyname
>         host ldap.njit.edu
>         user SOMEDN
>         passwd SOMEPW
>         suffix ou=base,o=org,c=us
> then edit the lists configuration file and add:
> owner_include
> profile normal
> reception mail
> source myincludefile
> visibility noconceal
> 
> * same thing for editor_include
> 
> 
> sync the list with its data sources, and now you have everyones aliases 
> added to the list.
> 
> reffer to 
> https://www.sympa.org/manual/list-parameters
> https://www.sympa.org/manual/parameters-definition#owner_include
> https://www.sympa.org/manual/list-definition#data_inclusion_file
> 
> 
> 
> 
> 
> On Wed, Sep 16, 2009 at 11:11 AM, Wendell Epps <address@concealed> wrote:
> Hello,
> 
>  
> Our institution allows for users to have multiple aliases for their email 
> accounts. That is a problem when working with Sympa because there are 
> several instances where a user logs in and cannot see a particular list 
> because they were subscribed with an address other than the default one 
> Sympa pulls from the system.
> 
>  
> Is there a way to get Sympa to gather all of the aliases for a user so that 
> it can pull all of the lists in which that subscriber is an 
> owner/subscriber/moderator is subscribed, no matter the valid alias that 
> that user is subscribed with? This would greatly cut down our support 
> issues regarding that problem.
> 
>  
> Thank you.
> 
>  
>  
> ----------------------------------------
> 
> Wendell Epps
> 
> Enterprise Messaging & Collaboration
> 
> IT@JH - Mt. Washington
> 
> e: address@concealed
> 
> p: 410.735.7353
> 
> ----------------------------------------
> 
> P Please consider the environment before printing this e-mail.
> 
>  
> 
> 
> 
> -- 
> Christopher Pax
> New Jersey Institute of Technology
> University Information Systems
> address@concealed
> 
> 
> 
> 
> -- 
> -----------------------------------------------------------
> Christian Dahlhausen, Network Systems Engineer
> University of Virginia - ITC Network Systems 
> PO Box 400324, 2015 Ivy Road, Charlottesville, VA 22904
>