I've been doing it with postfix and dbmail for several years. It works very well. I also have it running amavisd-new/spamassassin, clam anti-virus as well as the fuzzyocr plugin for spamassassin. Along with additional rule set and bayes database in MySQL, it works well.



On 12/1/2010 4:02 PM, Robert Moskowitz wrote:
This is on Fedora 12.

I have been running Postfix with SQL, CourierMail, and Squirelmail for over a year. I did this using the setup from:

http://wiki.amahi.org/index.php/Amahi_Mail_System

That was created using the instructions at:

http://www.howtoforge.com/virtual-users-domains-postfix-courier-mysql-squirrelmail-fedora-12-x86_64

It works well. I have been running 4 virtual domains with a couple handful of users.

Now I want to add Mailman.

Amahi runs any new web app in a virtual host. So Squirrelmail is running as https://webmail.foo.com and Mailman will run as http://mailman.foo.com/mailman (supposedly I will be able to reduce this to mailman.foo.com, but one thing at a time).

Challenge is that Mailman runs all of its processes as commands via /etc/aliases (or so it seems). For example there are aliases now like:

mailman:    "|/usr/lib/mailman/mail/mailman post mailman"

For the main mailman list. A user subscribed to the list gets have that the user mail...@mailman.foo.com does not exist.

So I am trying to figure out how to work this integration. The SQL approach with a domains table overrides the 'standard' postfix virtual-domains approach:

cat /etc/postfix/mysql-virtual_domains.cf

user = mail_admin
password = mail_admin_password
dbname = mail
query = SELECT domain AS virtual FROM domains WHERE domain='%s'
hosts = 127.0.0.1

postconf -e 'virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf'

So how do I get the virtual mailman domain to work? I DO have to add mailman.foo.com to the domain table. Without this, postfix responds that mail...@mailman.foo.com loops back to itself. With it I get the domain table entry I get mail...@mailman.foo.com does not exist. And /etc/aliases can only have local addresses in it, I have learned. I have looked up the transport table, but I can't use that to run commands like what is in the aliases file. What about the forward table? Do I put some form of the command into it? I cannot find any manpage or other on how to work with the forwarding setup.

So help here would be greatly appreciated!



Reply via email to