On 02/08/13 11:15, Nigel Rantor wrote:
> On 01/08/13 13:56, Andy Bennett wrote:
>> Hi,
>>
>>> In my (albeit limited) experience of running a mail server this is
>>> something that is seen as a big issue (possibly just for newer domains)
>>> - having had a similar issue it was resolved almost immediately by
>>> fixing the PTR records - doing a reverse lookup on your mail server's
>>> address should match how it identifies itself (If it claims to be
>>> mail.a.com <http://mail.a.com> when connecting then the PTR for its IP
>>> address should be mail.a.com <http://mail.a.com>).
>>
>> That is relevant at the SMTP level. AIUI, Nigel was talking about what
>> appears in the MX record.
>
> Ah, I omitted this on my resolved update.
>
> I had
>
> A otter.wiggly.org -> IP
> A mail.wiggly.org -> IP
> MX mail.wiggly.org
> IP PTR otter.wiggly.org
AIUI, This arrangement is fine provided otter.wiggly.org appears in the
HELO repsonse at the SMTP level.
It's must be: think about how it might work if you had more than one
relay. Also, look at the DNS setup for cam.ac.uk: that's a relay that's
known to be well run.
> So when doing a full circle you found that the MX name didn't match the
> PTR record for the IP it resolves to.
>
> I fixed this before finding the problem with the SPF / IPv6 issue so I
> don't know if it was another problem that required fixing, it is better
> to have these the same though so I am leaving it that way and will have
> to live with my MX being called "otter" and not "mail".
Regards,
@ndy
--
andyjpb@???
http://www.ashurst.eu.org/
0x7EBA75FF
