hey all, >and the HELO command:
>b. must have a hostname, else reject >c. it must be valid characters, else reject >e. it must not contain IP address /a.b.c.d/ Is the above covered by RFC or is it just best practise? I'm seeing a few of our partner sites using a helo with IP address. I've whitelisted them but in doing so have minimised the checks for mail coming from them. I like them to clean up their act so any advise as to what I should convey to them (in terms of standards) would be greatly appreciated! >the end of your smtpd restrictions for a week or so, then study the=20 >warn_if_reject lines for ptr/to/from/protocol/helo to see what would have=20 >been rejected. For legit servers habitually contacting yours, try to=20 >contact abuse@ or postmaster@ to point that their server is "in danger of=20 >being blocked in the near future" (just a little FUD in their direction) by= =20 >your MX due to missing PTR and/or bad HELO hostname. Whitelist them if=20 >they won't cooperate, and then convert warn_if_reject to reject. I'm getting quite a few warnings since incorporating this and I suspect the majority of these are missing PTR records. -Peter ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been virus scanned and although no viruses were detected by the system, St Vincent's Hospital accepts no liability for any consequential damage resulting from email containing any computer viruses. **********************************************************************
