[Mailman-Users] wrapper issue

[Mark Sapiro]

Mark Sapiro wrote:
>
>The list-name in the message you sent me ends in -admin. This is the
>problem.
>
>
>Your Mailman router in Exim doesn't work with list names that end with
>'-admin' or probably any of the other suffixes '-bounces', '-confirm',
>'-join', '-leave', '-owner', '-request', '-subscribe' or
>'-unsubscribe'.
>
>Does the router definition look like this:
>
>mailman_router:
>  driver = accept
>  domains = +mm_domains
>  require_files = MAILMAN_HOME/lists/$local_part/config.pck
>  local_part_suffix_optional
>  local_part_suffix = -bounces : -bounces+* : \
>                      -confirm : -confirm+* : \
>                      -join : -leave : \
>                      -subscribe : -unsubscribe : \
>                      -owner : -request : -admin
>  transport = mailman_transport
>
>
>If so, i think you can just delete the " : -admin" from the next to
>last line as this suffix is a deprecated synonym for the -bounces
>address and isn't actually used in Mailman 2.1.x.
>
>That should solve the problem for lists named *-admin, but not the
>others.
>
>I'm not an Exim wizard, but I'll try to come up with a more robust
>router definition.


The following is not too elegant, but you can just add a second router
so you have two as follows (order is important):

mailman_router:
  driver = accept
  domains = +mm_domains
  require_files = MAILMAN_HOME/lists/$local_part/config.pck
  local_part_suffix_optional
  local_part_suffix = -bounces : -bounces+* : \
                      -confirm : -confirm+* : \
                      -join : -leave : \
                      -subscribe : -unsubscribe : \
                      -owner : -request : -admin
  transport = mailman_transport

mailman__backup_router:
  driver = accept
  domains = +mm_domains
  require_files = MAILMAN_HOME/lists/$local_part/config.pck
  transport = mailman_transport

The first router will be invoked for addresses like 'list',
'list-admin', 'list-bounces', etc where 'list' is a valid list name.

Should there be a list with a name like 'xxx-admin', as long as there
also is not a list named 'xxx', the first router will fail to match on
list posts and the second router will match. Addresses like
'xxx-admin-bounces' etc. (even 'xxx-admin-admin') will match the first
router.

The only restriction is you can't have two lists, one named 'xxx' and
another named 'xxx-admin' or 'xxx-bounces', etc., but that's a problem
with other delivery methods too.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan