The mailing list for listmasters using Sympa

[CSS <address@concealed>]

On Sep 7, 2011, at 2:51 PM, Elwyn Davies wrote:

> Hi, Charles.
> 
> I am glad you found my stuff useful!
> 
> As far as I can see, you are pretty much done.
> 
> You seem to think you have a problem here in that you have to paste this in 
> manually..
> 
>>> And finally, the hack that I stick in the top of that same file to handle 
>>> the
>>> bounces, posts, etc.:
>>> 
>>> # this seems to be necessary, probably belongs somewhere else
>>> /^(sympa)\@lists\.hostcompanion\.com$/
>>> $1+lists.hostcompanion.com@sympalist.
>>> /^(listmaster)\@lists\.hostcompanion\.com$/
>>> $1+lists.hostcompanion.com@sympalist.
>>> 
> Well you could do some extra stuff to generate this automatically with
> the first instance of the list, but I didn't.

I think what happened here is that after looking at all the various docs on 
integrating with postfix and not really finding a canonical reference in the 
sympa docs that outlined exactly what each inbound address might be, I just 
relied on your doc as a reference guide.  But then I couldn't find any 
mention of the sympa/listmaster addresses in your guide, so I assumed I must 
have missed something somewhere.

I was also reminded that I know less about address rewriting in Postfix than 
I thought I did. :)

> 
> Its a once per virtual host operation, so I just left it for manual
> config.  I only really cared about making extra lists (I only had one
> host to worry about so it wasn't a big deal).  You will have to do it
> for each virtual host.
> 
> This line is *NOT* required (and will probably screw things up)
> /^(.*+owner\@lists\.hostcompanion\.com$/
>>> $1+lists.hostcompanion.com@sympaowner.
>>> 
> 
> The aliases already cope with address@concealed etc

I saw docs somewhere that suggested there was a "bounce-*@virtdomain" alias 
needed, and then others that claimed a "owner+*" was needed.  To be honest, 
I've not yet looked at how bounce processing works.  Nor have I looked at 
VERP.  Those will probably be in my next post to this list...

> 
> One point which is not clear form your mail is that it is essential that
> there are no extra newlines in the added lines.. if they are really like
> this in the virtual host aliases file, then they won't work.  You need
> something like:
> /^(root|postmaster)\@lists\.hostcompanion\.com$/      
> address@concealed
> /^(sympa|listmaster)\@lists\.hostcompanion\.com$/     
> $1+lists.hostcompanion.com@sympalist.
> 
> where there is no newline after .com$/

Yep, I posted that message via the sympa web interface, and I think it got 
cut up there.

I'm now going back and trying to understand just *how* all these mappings 
work.

> 
> BTW
> If you are willing to send me the updated conf.pm etc files, I'll add
> them to the description so that people can use them with the latest
> version.  I haven't had occasion to upversion my installation yet as it
> does everything we needed (very simple requirements) and the password
> improvement was not essential.  For our purposes the shared documents
> folders were really helpful!

Sure.  I'll tar up a bunch of stuff so that you've got the 6.1 version, my 
changes, and some diffs.

Thanks so much for your help and the excellent tutorial,

Charles

> 
> Regards,
> Elwyn Davies
> 
> On Wed, 2011-09-07 at 09:14 +0200, address@concealed wrote:
>> Hello,
>> 
>> I'm having a tough time getting this setup properly for a non-profit I'm
>> working with.
>> 
>> I read up on Sympa's features and it looks like the right choice - it 
>> covers
>> three things they need - web-based posting, discussion lists, and announce
>> lists.  And it covers things I need like a decent permissions system and
>> bounce processing.
>> 
>> After reading about the various Postfix integration methods, this one 
>> seemed
>> like it was the best in that it would not make me a backscatter source (the
>> other options for virtual setups do rejects after the message enters the 
>> queue
>> due to their greedy regex matching):
>> 
>> http://www.folly.org.uk/sympa/sympa_config_03.html
>> 
>> It's a nice setup, but the changes to Sympa since that was released left me
>> having to patch up Conf.pm, alias_manage.pl, and confdefs.pm.
>> 
>> This seems to work however - all my address@concealed mappings work,
>> those aliases are generated automatically by the patched alias manager.  
>> The
>> Conf.pm changes are working fine (set flags in each virthost robot.conf).
>> 
>> What I seem to be missing since I'm looking at so many Postfix tutorials, 
>> many
>> of which are now outdated, is how to handle my address@concealed 
>> mappings.
>> I can't find a decent reference for that.  Below is my current postfix 
>> setup,
>> which seems to work, but I need to add a mapping manually for each host as
>> noted in the config.
>> 
>> Let's start with main.cf:
>> 
>> #
>> # SYMPA STUFF
>> #
>> transport_maps = regexp:/usr/local/etc/postfix/transport_sympa
>> 
>> # Set the concurrency for delivery to Sympa
>> sympalist_destination_recipient_limit = 1
>> symparequest_destination_recipient_limit = 1
>> sympaeditor_destination_recipient_limit = 1
>> sympasubscribe_destination_recipient_limit = 1
>> sympaunsubscribe_destination_recipient_limit = 1
>> sympabounce_destination_recipient_limit = 1
>> 
>> # Specify the virtual alias domain(s)
>> virtual_alias_domains = lists.hostcompanion.com,lists.o4onyc.org
>> 
>> # Specify the virtual alias file(s) - this is the only per virthost config
>> virtual_alias_maps = regexp:/usr/local/etc/sympa/postfix/
>> lists.hostcompanion.com,regexp:/usr/local/etc/sympa/postfix/lists.o4onyc.org
>> 
>> Then the transport maps:
>> 
>> # Transport map for Sympa virtual domain transports
>> /^.*\@sympalist$/         sympalist:
>> /^.*\@symparequest$/      symparequest:
>> /^.*\@sympaeditor$/       sympaeditor:
>> /^.*\@sympasubscribe$/    sympasubscribe:
>> /^.*\@sympaunsubscribe$/  sympaunsubscribe:
>> /^.*\@sympaowner$/       sympabounce:
>> 
>> And master.cf:
>> 
>> # Sympa mailing list manager transports
>> sympalist     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/queue 
>> ${user}@${extension}
>> symparequest     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/queue ${user}-request@
>> ${extension}
>> sympaeditor     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/queue ${user}-editor@
>> ${extension}
>> sympasubscribe     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/queue ${user}-subscribe@
>> ${extension}
>> sympaunsubscribe     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/queue 
>> ${user}-unsubscribe@
>> ${extension}
>> sympabounce     unix  -       n       n       -       -       pipe
>>  flags=RF user=sympa argv=/usr/local/libexec/sympa/bouncequeue ${user}
>> 
>> And now the aliases that are autogenerated for one virthost:
>> 
>> ## This virtual aliases file for domain lists.hostcompanion.com is 
>> dedicated
>> to Sympa Mailing List Manager
>> ## You should edit your Postfix main.cf file to declare it
>> ##
>> /^lists\.hostcompanion\.com$/            xxx
>> ##
>> #------------------------------ test1: list alias created 06 Sep 2011
>> /^(test1)-(request|editor|owner|subscribe|unsubscribe)\@lists\.hostcompanion
>> \.com$/    $1+lists.hostcompanion.com@sympa$2.
>> /^(test1)\@lists\.hostcompanion\.com$/
>> $1+lists.hostcompanion.com@sympalist.
>> 
>> And finally, the hack that I stick in the top of that same file to handle 
>> the
>> bounces, posts, etc.:
>> 
>> # this seems to be necessary, probably belongs somewhere else
>> /^(sympa)\@lists\.hostcompanion\.com$/
>> $1+lists.hostcompanion.com@sympalist.
>> /^(listmaster)\@lists\.hostcompanion\.com$/
>> $1+lists.hostcompanion.com@sympalist.
>> /^(.*+owner\@lists\.hostcompanion\.com$/
>> $1+lists.hostcompanion.com@sympaowner.
>> 
>> I'm pretty lost here - any input is appreciated.
>> 
>> Thanks,
>> 
>> Charles
>