The mailing list for listmasters using Sympa

[address@concealed]

Allen, Pat wrote:
> Good morning –
>
> Excuse me if this is a basic question but I’ve just started working 
> with Sympa.
>
> We are currently using Lyris as our mail server and are looking to 
> migrate to Sympa. We’re an oceanographic research organization and 
> many of our lists are restricted to staff while many are open to 
> public subscription. I notice that when creating a list, I can 
> configure it so that the field “Who can subscribe to the list 
> (subscribe)” is set to “restricted to local domain users (intranet)”. 
> This would seem to be what I want but the problem is that the Sympa 
> server is in a tertiary DNS zone (shore.mbari.org) and users will be 
> logging in with their normal email addresses of address@concealed 
> <mailto:address@concealed>. It seems that the software doesn’t recognize 
> this as being the same DNS zone.
>
> Does anyone have any suggestions to get around this?
Access control are define in "authorization scenario". Scenario are 
small config files that allow to decide if a service must be accepted, 
refused or controled by list owner. The scenario named 
"subscribe.intranet" is minly a exemple because the definition of 
"intranet" is something with many deferences depending on local 
consideration.

You should define your own intranet scenari for subscribtion and 
probably also for some other services. You can do it by copying 
~sympa/bin/etc/scenari/subscribe.intranet to 
~sympa/etc/scenari/subscribe.intranet and edit the new file changing the 
rule :

match([sender],/[conf->host]$/) smtp,smime,md5 -> do_it

to

match([sender],/mbari\.org/) smtp,smime,md5 -> do_it


Then touch file config foreach list that use this scenario (the config 
will be updated if the mdate is changed) or remove all file confg.bin 
and restart both httpd and sympa.pl.

more information in tips and howto page : 
http://www.sympa.org/wiki/faq/tips_and_howto#how_to_restrict_some_pages_to_local_intranet_users

regards
Serge Aumont