Problems using Postfix with Mailman
Hello all,
I previously posted a message about a server "migration" of Mailman to a new CentOS 7 server. It actually is a rebuild and I will be trying to restore list info from backup.
Anyway, I have Mailman installed and can access web pages and create lists. I am using Postfix as the MTA and I restored the main.cf file from the old server. I have indicated MTA ="Postfix" in mm_cfg.py, which I also moved over frrom old server backup.
I restarted Postfix and Mailman. Now, when I post to a list, I get a variety of errors.
In my own mailbox, I get this:
mymailmanserver.com #<mymailmanserver.com#5.1.1 SMTP; 550 5.1.1 < osltest@mymailmanserver.com <osltest@listsmart.osl.state.or.us>>: Recipient address rejected: User unknown in local recipient table> #SMTP#
In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 4.71 <my.address@mydomain.com>: Relay access denied; from=< mylist-bounces@mymailmanserver.com>
In the Mailman smtp-failure log file, I get: "Relay access denied"
From all that I have read, it must be a Postfix configuration problem, but since I just moved the old main.cf to the new server, I am perplexed. Posts to the Postfix-Users list has not been productive.
If anyone uses Mailman and Postfix, maybe you can share your experiences.
Many thanks.
-- Christopher Adams adamsca@gmail.com
On 05/03/2016 04:50 PM, Christopher Adams wrote:
In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 4.71 <my.address@mydomain.com>: Relay access denied; from=< mylist-bounces@mymailmanserver.com>
In the Mailman smtp-failure log file, I get: "Relay access denied"
From all that I have read, it must be a Postfix configuration problem, but since I just moved the old main.cf to the new server, I am perplexed. Posts to the Postfix-Users list has not been productive.
Right, and the problem is you didn't change the postfix main.cf to match the RedHat/CentOS change in /etc/hosts.
The issue is that mailman is sending to 'localhost', /etc/hosts is defining localhost as the IPv6 address [::1], and this is not in mynetworks in main.cf. There are various ways to fix this including replacing the localhost entry in /etc/hosts - something like
::1 localhost
with
127.0.0.1 localhost
or adding [::1]/128 to mynetworks in main.cf.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Yes, you are so right. I did have an entry for 127.0.0.1 localhost in /etc/hosts, but also the entry for IPV6, which I didn't need and it apparently took preference.
So, this did help and I thank you. Additionally, there was some configuration in the Postfix main.cf that needed updating due to a change in the version of Postfix.
Many thanks, Mark. On May 3, 2016 5:56 PM, "Mark Sapiro" <mark@msapiro.net> wrote:
On 05/03/2016 04:50 PM, Christopher Adams wrote:
In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 4.71 <my.address@mydomain.com>: Relay access denied; from=< mylist-bounces@mymailmanserver.com>
In the Mailman smtp-failure log file, I get: "Relay access denied"
From all that I have read, it must be a Postfix configuration problem, but since I just moved the old main.cf to the new server, I am perplexed. Posts to the Postfix-Users list has not been productive.
Right, and the problem is you didn't change the postfix main.cf to match the RedHat/CentOS change in /etc/hosts.
The issue is that mailman is sending to 'localhost', /etc/hosts is defining localhost as the IPv6 address [::1], and this is not in mynetworks in main.cf. There are various ways to fix this including replacing the localhost entry in /etc/hosts - something like
::1 localhost
with
127.0.0.1 localhost
or adding [::1]/128 to mynetworks in main.cf.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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/adamsca%40gmail.com
Christopher Adams writes:
Yes, you are so right. I did have an entry for 127.0.0.1 localhost in /etc/hosts, but also the entry for IPV6, which I didn't need and it apparently took preference.
This is a general property of IPv6: where available it takes precedence. Unfortunately, the definition of "available" used by the low-level stack where this preference operates (ie, I can connect to the port and get a TCP/IP-level response, including rejection) often fails to conform to the human idea of "available" (ie, the resource content is delivered).
That's way over-simplified, of course, but it's worth being aware that enabling IPv6 may require configuration changes throughout your application stack. (And the way things are these days, with IPv6 being more and more important, you may get IPv6 without asking for it in an OS upgrade or something.)
participants (3)
-
Christopher Adams -
Mark Sapiro -
Stephen J. Turnbull