Following on my last below post, I'd wish to report a small additional problem that I encountered after applying the '$alias_maps' fix to the 'local_recipient_maps' parameter.
Whereas it effectively solved the 'Undelivered Mail Returned to Sender' issue when using a mail account from say virtual 'domain.net' co-hosted with say virtual 'domain.org' on the same physical VPS, it didn't resolve it when using a mail account from the same domain attributed to Mailman (as declared in the 'mm_cf.py' file)... To illustrate this, here is the related case set-up : - domain.net and domain.org are co-resident on the same host VPS12345, - domain.org is the one we use for mailman lists - link : http://lists.domain.org/mailman/listinfo, - we get no mail rejection when using the account na...@domain.net with a list created on 'lists.domain.org' (after the previous fix), - we get an 'Unknown User' mail rejection when using the na...@domain.org with a list created on 'lists.domain.org' (new problem observed). The kind of rejection error notification we then get is depicted thereafter : ____________________________ *** POST SUBMISSION TO TESTLIST *** From : Admin Lists DomainORG [mailto:admin-li...@domain.org] Sent : tuesday 29 april 2014 20:11 To : testl...@domain.org Subject : < Some topic line... > < Some content to publication on the TestList list... > *** UNDELIVERED MAIL NOTIFICATION RESPONSE *** From : MAILER-DAEMON (Mail Delivery System) [mailto:MAILER-DAEMON (Mail Delivery System)] Sent : tuesday 29 april 2014 20:11 To : admin-li...@domain.org Subject : Undelivered Mail Returned to Sender This is the mail system at host vps12345.ovh.net. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system < testl...@domain.org > : user unknown _____________________________ Is there another Postfix parameter which govern the behavior of local 'unix:passwd.byname' versus 'virtual-mailman' type email accounts defined on the SAME DOMAIN as the one specifically used for Mailman ? If it turns out that there is a restriction on such particular usage, we could live with it by not using same domain-based email addresses as the one devoted to Mailman. Many thanks for any hint regarding such reported behavior... - - - Jacques Setton jset...@waycast.com -----Message d'origine----- De : Jacques Setton [mailto:jset...@waycast.com] Envoyé : dimanche 27 avril 2014 21:05 À : 'Mark Sapiro' Cc : 'mailman-users@python.org' Objet : RE: [Mailman-Users] 'Undelivered Mail Returned to Sender' error when using an e-mail from a domain co-hosted with the one used for Mailman lists >> By default, local_recipient_maps includes $alias_maps, and I *think* it should in your case. >> Why this lack would cause Postfix to use the virtual_transport rather >> than local in just this one case is really a question for >> postfix-us...@postfix.org or some other Postfix resource, but you >> might try local_recipient_maps = unix:passwd.byname $alias_maps Very well spotted ! This is indeed the source of the mail rejection behavior that I have reported on when using a locally-hosted mail accounts on the same VPS which also hosts Mailman. The 'postconf -d' command output shows the following default setting : alias_maps = hash:/etc/aliases, nis:mail.aliases local_recipient_maps = proxy:unix:passwd.byname $alias_maps The 'postconf -n' command output shows the following (re)specified setting : alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases local_recipient_maps = unix:passwd.byname For some unclear reason, in the distribution we are using the '$allias_maps' parameter had been removed from the 'local_recipient_maps' setting in the Postfix 'main.cf' configuration file. After redefining the line as "local_recipient_maps = unix:passwd.byname $alias_maps" and doing a few test, it appears that we can now successfully use local mail accounts in relation with Mailman. >> or simply removing that line from main.cf and see if that helps. No need to do that as the above corrective action did fully resolve the problem. Many thanks, Mark, for your very effective guidance on this issue ! - - - Jacques Setton jset...@waycast.com ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
