Re: non-ldap aliases lookup q

On Thu, 2 Dec 2004, Duane Powers wrote:

> I'm trying to add virtual mailman lists to my existing jamm install.
> I've created the lists and put them into an aliases file (lets call it
> mailman.aliases) 
> 
>  
> 
> When I send email to the new virtual list, it bounces with a user
> unknown error, Where can I learn what the different maps
> (virtual_aliases, virtual_transport, aliases, local_recipient_maps) do,
> so I can figure out where to add the hash:mailman.aliases line to my
> main.cf, or how do I get postfix to first check for an alias in ldap,
> then check the file before bouncing the inbound email?

You might want to look at this:
http://www.gurulabs.com/files/postfix-to-mailman-2.1.py

It is just a python script that takes care of the aliases for you.
The comments from the script say this:

# postfix-to-mailman-2.1.py (to be installed as postfix-to-mailman.py)
#
# Interface mailman to a postfix with a mailman transport. Does not require
# the creation of _any_ aliases to connect lists to your mail system.
#
# Dax Kelson, [email protected], Sept 2002.
# coverted from qmail to postfix interface
# Jan 2003: Fixes for Mailman 2.1
# Thanks to Simen E. Sandberg <[email protected]>
# Feb 2003: Change the suggested postfix transport to support VERP
# Thanks to Henrique de Moraes Holschuh <[email protected]>
#
# This script was originally qmail-to-mailman.py by:
# Bruce Perens, [email protected], March 1999.
# This is free software under the GNU General Public License.
#
# This script is meant to be called from ~mailman/postfix-to-mailman.py.
# It catches all mail to a virtual domain, eg "lists.example.com".
# It looks at the  recipient for each mail message and decides if the mail is
# addressed to a valid list or not, and bounces the message with a helpful
# suggestion if it's not addressed to a list. It decides if it is a posting,
# a list command, or mail to the list administrator, by checking for the
#  -admin, -owner, and -request addresses. It will recognize a list as soon
# as the list is created, there is no need to add _any_ aliases for any list.
# It recognizes mail to postmaster, mailman-owner, abuse, mailer-daemon, root,
# and owner, and routes those mails to MailmanOwner as defined in the
# configuration variables, above.

This is what I did. Works like a champ for me.

Regards,

Tom


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/