It never fails to amaze me now many mail server admins ask for ways to
break the RFC's in the interest of "security". I do tech support on
mail servers, and get requests to configure out server for this kind of
thing weekly. . .
jay
Philip Prindeville wrote:
Well, I tried to contact some people responsible for
the servers below that what they were doing was broken,
including citing chapter and verse where in RFC-2822 in
syntax of the Received: lines was spec'd out:
Received: from Gate2-sandiego.nmci.navy.mil (gate2-sandiego.nmci.navy.mil
[138.163.0.42])
by mail.redfish-solutions.com (8.13.8/8.13.7) with ESMTP id
kAGNLZHp020689
for <[EMAIL PROTECTED]>; Thu, 16 Nov 2006 16:21:40 -0700
Received: from nawesdnims03.nmci.navy.mil by Gate2-sandiego.nmci.navy.mil
via smtpd (for mail.redfish-solutions.com [71.36.29.88]) with ESMTP;
Thu, 16 Nov 2006 23:21:40 +0000
Received: (private information removed)
Received: (private information removed)
Received: (private information removed)
Received: (private information removed)
Received: (private information removed)
and which fields it requires (like the semi-colon followed by the
timestamp coming after a comment field) [cf: RFC 2822, section 3.6.7:
received = "Received:" name-val-list ";" date-time CRLF
name-val-list = [CFWS <http://tools.ietf.org/html/rfc2822#ref-CFWS>]
[name-val-pair *(CFWS name-val-pair)]
including the definition of CFWS in 3.2.3.]
It just boggles my mind why anyone would go through that much trouble
to deliberately damage a header line, rather than just delete it.
Well, maybe they'll get a whiff of the errs of their ways in the
Hall of Spam Shame...
-Philip
