Hi Mark!
In simple terms, it claims your mail server is not properly configured. I don't know what your Mailman server's domain name is, but it appears from the error message that its IP is 62.75.175.182 and that IP has an rDNS PTR record to euve51864.serverprofi24.de.
this is all pretty correct.
"euve51864.serverprofi24.de" is the natural name of the vServer, I am running. I don't have a real domain configured, since I mainly just use it for mailman. I configured all Mailman lists to use something like <list name>@rc-worms.de, where <rc-worms.de> is the www domain of my sports club, whose administrator I am. For better readability I named and configured all lists this way, to use < members@rc-worms.de>, <team1@rc-worms.de> as exlicity reply-to address and so on.
This worked pretty well for years. Did it now turn into a problem, that reply-to address and domain () bear a different IP/rDNS result? Is there something you could suggest in this case?
Should I maybe configure a subdomain on my vServer, like <lists.rc-worms.de>, from which the mails will be send from and can bear own DNS config?
Kind regards, Sascha.
2016-01-26 0:11 GMT+01:00 Mark Sapiro <mark@msapiro.net>:
On 01/25/2016 02:48 PM, Sascha Rissel wrote:
thanks for your answer. I just checked the bounce log.
And I discovered a lot of entries like:
Jan 25 18:33:24 2016 (2741) <BounceRunner at 12019976> processing 9
queued
bounces Jan 25 18:33:24 2016 (2741) <my-list-name>: <some mail address> already scored a bounce for date 25-Jan-2016 ... where all mail addresses are from German Web.de and GMX. Both providers belong to the same company. Thinking about this, I remembered a bounce notification I received last week, where some of these addresses were set to disabled by Mailman, with the notification below.
Did GMX/Web.de maybe change their mail processing policies with the start of the new year?
Possibly. See below.
Below follows an excerpt from the bounce notification.
Bounce Mail:
<some_user@web.de>: host mx-ha02.web.de[212.227.17.8] refused to talk to me: 554-web.de (mxweb107) Nemesis ESMTP Service not available 554-No SMTP service 554-Bad DNS PTR resource record. 554 For explanation visit http://postmaster.web.de/error-messages?ip=62.75.175.182&c=rdns
OK. The recipient's mail exchange server is refusing your mail. web.de's explanation of this is at <http://postmaster.web.de/error-messages?ip=62.75.175.182&c=rdns#nordns>.
In simple terms, it claims your mail server is not properly configured. I don't know what your Mailman server's domain name is, but it appears from the error message that its IP is 62.75.175.182 and that IP has an rDNS PTR record to euve51864.serverprofi24.de.
In any case you need to ensure the IP address your server sends from has a rDNS (PTR) record pointing to its host name and that host name in turn needs an A record with the same IP address. Also, it should identify itself with this same name in the SMTP HELO or EHLO command.
,
According to the tool at < http://mxtoolbox.com/SuperTool.aspx?action=smtp%3a62.75.175.182&run=toolpage this is all OK, so I don't know why web.de is complaining. I suggest you use the form at <http://postmaster.web.de/en/contact/?ip=62.75.175.182&c=rdns> to ask them.
-- 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/mailman%40rissel.it