 NOYBSt. John 3.16Premium
join:2005-12-15
Forest Grove, OR
kudos:1 | Hosting RFC Compliant SMTP SystemsWhy is it so difficult for SMTP hosting operators to conform to the SMTP RFCs.
Portland Trail Blazers Email System Out of RFC Compliance
RFC 5321 section 4.1.1.1. Extended HELLO (EHLO) or HELLO (HELO) specifies that the helo or ehlo name is "the fully-qualified domain name of the SMTP client".
However the email system utilized by the Blazers message boards system provides an helo/ehlo name of "NEWRWN5" for client "rwn5.rosecitydigital.com". To be RFC compliant the helo/ehlo name should be "rwn5.rosecitydigital.com"
SMTP Server Log Entry:
connect from rwn5.rosecitydigital.com[66.178.131.105]
NOQUEUE: reject: EHLO from rwn5.rosecitydigital.com[66.178.131.105]: 504 5.5.2 : Helo command rejected: need fully-qualified hostname; proto=SMTP helo=
NOQUEUE: reject: HELO from rwn5.rosecitydigital.com[66.178.131.105]: 504 5.5.2 : Helo command rejected: need fully-qualified hostname; proto=SMTP helo=
disconnect from rwn5.rosecitydigital.com[66.178.131.105]
--
Be a Good Netizen - Read, Know & Complain About Overly Restrictive Tyrannical ISP ToS & AUP »comcast.net/terms/ »verizon.net/policies/
Say Thanks with a Tool Points Donation |
