[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

not accepting mail despite proper A<->PTR setup



I just got a mail delivery error from another MTA:

  <xxxxx@xxxxxxx.xx>: host xxxx xxxxxxx.xx[123.12.123.12] refused to
  talk to me: 501-HELO requires a valid host name as operand:
  'albatross.madduck.net' 501-connection rejected from
  debian4.unizh.ch remote address [130.60.73.144]. 501-Reason given
  was: 501-  No reverse DNS PTR for the remote address
  [130.60.73.144] has a 501   hostname matching
  'albatross.madduck.net'

130.60.73.144 is my mailout server, which has a PTR record to
debian4.unizh.ch, which resolves back to that IP.

since this is a virtual setup, the same IP also services
albatross.madduck.net. in this case, the HELO name used was
albatross.madduck.net, which the other MTA refused. is it just me,
or is this overly paranoid, and possibly even wrong? is there
any document that specifies that I have to have a PTR record for
every A record? my belief is that multiple PTR records have little
purpose. am i wrong?

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
 
keyserver problems? http://keyserver.kjsl.com/~jharris/keyserver.html
get my key here: http://madduck.net/me/gpg/publickey
 
there's an old proverb that says just about whatever you want it to.

Attachment: pgp5zR0FVLAQM.pgp
Description: PGP signature


Reply to: