On 04/05/2014 10:38 PM, Curtis Maurand wrote:
> Ron Guerin wrote:
>>
>> In mm_cfg.py I have this to generate the aliases:
>> MTA='Postfix'
>>
>> In main.cf I use the aliases under:
>> alias_maps hash:/var/lib/mailman/data/aliases
>>
>> In in my master.cf for the mailman transport, I have ${user} where you
>> have ${mailbox} , don't know if that's got anything to do with it.
>>
>> If you want to use the autogenerated aliases, at this point, you're
>> going to need to generate them yourself first. This for me would look
>> like:
>> /usr/lib/mailman/bin/genaliases
>>
>> And of course, don't forget to restart Mailman if you change mm_cfg.py
>> (before running genaliases) and HUP Postfix if you change that.
>
> my setup is a bit different. I'm using dbmail and I have to add the
> aliases to the aliases table, there. I can do that, but was trying to
> avoid it. I was told about and I had an alternate configuration working
> where alias maintenance was completely unnecessary. It had to do with
> setting up the mailman_to_postfix.py script and transport_maps. I wish I
> could find the backups of my original configuration. It's driving me
> crazy. I missed a detail, but I can't remember exactly what it is. very
> annoying.
Why do the Mailman aliases need to be in dbmail? I use MySQL, but
there's absolutely no need for these to be in the database. If you
allow Mailman to autogenerate them, there is no alias maintenance. Just
set it up like you see above. Add, to the alias_maps in main.cf, rather
than replacing whatever you're doing with dbmail.
Aside, some Googling says "I'm doing it wrong" using both, and that
there's really no reason why anyone should be using
postfix-to-mailman.py. Take that under consideration along with what I
said about dbmail not needing to know about Mailman's aliases. Let
Mailman manage Mailman's aliases. They've got nothing to do with
anything else except Postfix.
- Ron
