×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi David -
On Mon, 16 Nov 2009 10:20:01 -0600, David Gibbs <david@xxxxxxxxxxxx>
wrote:
I'm of two minds about it ...
1. I could change my helo identifier to 'ip26.midrange.com', so that host will accept mail from me.
2. I could keep my helo identifier 'mail.midrange.com' so the users will complain to the mail admin and they remove the policy.
I suspect it's just a mater of time before they disable that policy ... they are probably rejecting far more legitimate mail than they are accepting.
I have the same situation. I originally had it because of having two
separate internet providers. I had separate rDNS with a matching host
(A) record for each so that there would be a 1-to-1 matchup. Neither
rDNS matched my mail server's identification.
I've since eliminated one internet provider. But I've left the rDNS
of the other provider as is because I can't change the rDNS myself and
so far I've never ran into a problem <knock on head>.
FYI, for incoming email to my server, I don't do any kind of
rejections based on rDNS. The software (postfix) logs if there is no
rDNS or if there is no matching host record or if the IP address of
the host record doesn't match the connecting IP address, but I have
the configuration set to not reject for that.
The software doesn't log anything if the HELO/EHLO doesn't match the
rDNS, and rightly so IMO.
Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
As an Amazon Associate we earn from qualifying purchases.