On Sun, 2011-07-17 at 23:33 +0200, Alexander Dalloz wrote:
> >> Organisation: British Telecommunications, EU
> >> HELO / EHLO: smtpe1.intersmtp.com
> >> HELO IP: 62.239.224.89
> >> MX IP: 62.239.224.234
> >> MX DNS A record: smtp61.intersmtp.com
> > BUT the IP address used for the mail server was, as the list shows,
> > 62.239.224.234 which, at the time, had a host name of
> > smtp61.intersmtp.com
> What do you mean by that? Was the connecting mailserver the one with IP
> 62.239.224.234? If you mean that the mailserver should have been the one
> listed as MX, you are simply wrong and you do not know what an MX is.
In the list there is limited space for explanations. There is no
abbreviation for 'receiving MTA' so I used 'MX'. I have changed it to
ACTUAL. Hope that helps. (You will probably need to refresh/reload the
web page)
> In DNS as well in mail addresses in the public zone the letter case does
> not matter.
I know. It was a joke about the COM and com :-)
> No, though there is no RFC which states that the HELO/EHLO name must be
> eqal to any MX record. In your example the greeting name resolves fine
> and is ok in this regard.
If the 'greeting name' (HELO/EHLO) does not resolve to the IP address
used by the sending server, then the mail is not accepted.
> Someone who does not want to receive mail from legitimate senders can
> just switch off his MTA ;-)
Legitimate senders should not use fake, false, misleading credentials.
Incidentally your own ISP is one of the worse users in England of 'fake'
HELO/EHLO names.
--
With best regards,
Paul.
England,
EU.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
