30 Jul
2013
30 Jul
'13
8:13 p.m.
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 when
connecting then the PTR for its IP address should be mail.a.com).
On 30 July 2013 21:05, Nigel Rantor <wiggly(a)wiggly.org> wrote:
Further to on-list discussions another sysadmin friend of mine suggested
that the fact that the A record for my MX doesn't match the PTR record
might be an issue but I feel it is a red herring.
I'm pretty sure multiple PTR records is not allowed (or at least
discouraged) anyway, which means I would need to start using the real name
of my machine for the MX record instead of the one I am using.
This isn't that much of a problem really, just means I don't have a nice
'mail.*' MX entry.
Thoughts?
n
______________________________**_________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…
--
Robert Gauld
http://www.robertgauld.co.uk