Sorry for not changing the subject last time. This is a server using the Plesk 12 control panel.
The answer was: "Ensure that 'localhost' IP addresses is white listed in Plesk. Go to Tools & Settings > Mail Server Settings > White list To verity it open Tools & Settings > Mail Settings > White List and check whether it contain the following addresses: '::1/128' and '127.0.0.1'." Their knowledgebase article is at http://kb.odin.com/en/123649. Thank you! Dean -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+dean.collins=insightplanners....@python.org] On Behalf Of Mark Sapiro Sent: Friday, May 15, 2015 12:59 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7 On 05/15/2015 12:28 PM, Dean Collins wrote: > > Subscribers include m...@mydomain.com (the same domain the list is on) > and various addresses from other domains/servers (a couple of servers > I run, plus Gmail and AT&T.) > > Mail sent to myl...@mydomain.com from any subscriber gets archived -- > and distributed to m...@mydomain.com. But none of the other subscribers > receive the list mail. In order to be sure about anything, I'd need to see some logs like Mailman's smtp-failure log and the MTA logs, except I don't know anything about qmail. However, based on past experience I can say the following. 1) Mailman is delivering to the local MTA (qmail) and the mail is being delivered to local addresses but not being sent to remote domains. 2) Other locally generated mail is being sent to remote domains. When this happens it is probably an IPv4 vs. IPv6 issue. Here's one scenario. It may not be exactly this in your case, but you should be able to translate. The MTA has an idea of what addresses constitute the local network and will relay mail from those addresses to the outside. This includes say the IPv4 local host, something like 127.0.0.1, but not the IPv6 local host ::1. Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which is not in the MTA's notion of the local network, so the MTA refuses to relay the mail. This can be fixed in multiple ways. You can add the IPv6 local host to the MTA's local network. You can change /etc/hosts to associate 127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in mm_cfg.py to something that will work. E.g., SMTPHOST = '127.0.0.1' Note that since I haven't seen your logs, the above scenario may be off. Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail wants IPv6, but the idea is the same. -- Mark Sapiro <m...@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/dean.collins%40insight planners.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
