About postmasterMTA88-198-2-66

postmasterMTA88-198-2-66 · 03-09-2016

Hello I am running an normal MTA on 88.198.2.66, a few months ago i had problems delivering EMail from this MTA to Iron Port Mail systems running on mxX.dhl.iphmx.com. After lots of struggling with German zone-c management of the international domain...

postmasterMTA88-198-2-66 · 03-22-2016

Ok guys, support just replied: They say its To this end, we are seeing reports of HELO strings which do not match the PTR / rDNS of the IP. One of the HELO string we are seeing “static.88-198-2-66.clients.your-server.de” which is not exact mat...

postmasterMTA88-198-2-66 · 03-22-2016

Hello Mathew & exMSW4319,thank you for the reply, i submitted now a ticket to http://www.senderbase.org/support/#problem=other.IPs: 88.198.2.66Investigation: MTA 88.198.2.66 got blocked since 08/03 (no reason given), then unblocked since 10/03 (proba...

postmasterMTA88-198-2-66 · 03-22-2016

Back again. I understand, that it might be a problem that spammers are using parts of the main domain of a FQDN, and this is something i can control. So i changed it to cust.z59.org. 1-2 days later -without any notice or reason given mx1.dhl.iphmx.co...

postmasterMTA88-198-2-66 · 03-10-2016

Thats right, i used to use "static.88-198-2-66.clients.your-server.de" until web.de/gmx.de/einsundeins.de MTA servers started blocking me due to "wrong dns name used" the end of of last year. They said reverse resolution it is looking like dynamic en...

Member Since	‎03-09-2016 04:25 PM
Date Last Visited	‎08-18-2017 03:55 AM
Posts	5

User Statistics

User Activity

Sending MTA's poor reputation with no contact possibility from client side

Ok guys, support just replied

Hello Mathew & exMSW4319

Back again. I understand,

Thats right, i used to use