On 04/05/2014 06:40 PM, Curtis Maurand wrote:
> Sahil Tandon wrote:
>> On Fri, 2014-04-04 at 14:55:49 -0400, Curtis Maurand wrote:
>>
>>> I'm getting local user unknown errors when I try to send email to the
>>> list., but as far as I know, I shouldn't need local aliases with this
>>> configuration that anything destined for lists.delrc.org should go to
>>> mailman and that's that. I know that I'm missing a detail somewhere.
>>> I had all of this working prior to this, but I had a server meltdown
>>> the other day and my configs were blown away with it and for whatever
>>> reason, I can't find any backups. :-(
>>
>> Typically, you have to update the alias_maps definition, so that Postfix
>> is made aware of valid Mailman addresses. In your follow-up, include the
>> output of 'postconf -n' rather than snippets from main.cf. See:
>>
>>
>> http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html
>> http://www.postfix.org/postconf.5.html#alias_maps
>>
> I'll remember to do that. However, i was told of a way to configure it in
> such a way that using transport maps all you had to do was to create the
> list and there would be no alias management.
In the end, with the transport method, which I use, along with
postfix-to-mailman.py, you're still better off using aliases. (I don't
remember the reason why, possibly bounce/spam related) These can be
auto-generated by Mailman though.
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.
- Ron
