Developers of Sympa

[Mark K <address@concealed>]

Well, I don't think there is a correct syntax.  I don't think one can
slice and dice the ${user} argument in the master.cf.  There would have
to be a custom version of bouncequeue to split the address.

That said, I don't think it is necessary to have that transport.  The
reason for the custom transports is to grab family lists that haven't
been created yet.  Why would we need an owner transport for a list that
does not yet exist?  And what good could it do if we did?  Once the
list has been used, the proper owner alias (and all the others the list
needs) will be created anyway.

On Thu, 14 Aug 2008 16:38:02 +0200
Olivier Sala__n <address@concealed> wrote:

> You're right Mark, the parameter to bouncequeue needs to be 
> 'list@robot', not 'list-owner'.
> What would be the correct syntax for the transpart then?
> 
> > Upon looking at it further yesterday, I think that the transport and
> > regexp for owners is unnecessary.  Normally, a 'list-owner' alias
> > points to /home/sympa/bin/bouncequeue with 'list@robot' as the
> > argument, not 'list-owner'.  Unless there is something else going
> > on under the hood, wouldn't the owner transport as described in the
> > automatic list setup not work?
> >
> > On Thu, 14 Aug 2008 09:23:10 +0200
> > Olivier Sala__n <address@concealed> wrote:
> >
> >   
> >> Hi Mark,
> >>
> >> Sylvain Amrani will be the right person to react on your changes,
> >> since he implemented the automatic lists feature and wrote this
> >> part of the documentation. I hope he is in the sympa-dev list.
> >>
> >> Anyhow, thanks for taking the time to update the manual.
> >>
> >> Mark K a __crit :
> >>     
> >>> After having done some work on my own site with this, I have
> >>> modified
> >>> https://www.sympa.org/manual/list-families#automatic_list_creation
> >>> to reflect some extra work that needs to be done.  Postfix will
> >>> reject email to unknown recipients by default, so you also need to
> >>> account for that when doing automatic list creation since you want
> >>> postfix to accept mail for aliases that do not yet exist.  So I
> >>> added this line to main.cf in the example on the wiki:
> >>> local_recipient_maps = pcre:/etc/postfix/local_recipient_regexp
> >>> unix:passwd.byname $alias_maps
> >>>
> >>> And then:
> >>> /etc/postfix/local_recipient_regexp
> >>>       /^.*-owner\@lists\.domain\.com$/  1
> >>>       /^auto-.*\@lists\.domain\.com$/   1
> >>>
> >>> Now, I also corrected what I think was an error.
> >>> The /etc/postfix/transport_regexp example had this line:
> >>>
> >>> /^.*+owner\@lists\.domain\.com$/      sympabounce:
> >>>
> >>> Which I think should be:
> >>>
> >>> /^.*-owner\@lists\.domain\.com$/      sympabounce:
> >>>
> >>> Notice the - instead of +.  Sympa does not use an extension for
> >>> owner emails.
> >>>
> >>> Also, I think that the 
> >>>
> >>> /^.*\@lists\.domain\.com$/            sympa:
> >>>
> >>> line in transport_regexp is unnecessary unless there is more going
> >>> on in this example than is mentioned (virtual domain or
> >>> something).  Not only is is not necessary, but it would be
> >>> destructive if lists.domain.com contains anything but sympa lists.
> >>>
> >>> Comments?
> >>>
> >>>   
> >>>       
> >
> >
> >   
> 


-- 
Mark K