From: "mouss" <[EMAIL PROTECTED]>
> Eric A. Hall wrote:
>
> >>
> >> Huh? The helo= stuff is inside the parenthesis. Perhaps I am missing
> >> something but your point 3 seems to conflicewith your point 2.
> >
> >
> > comments are only allowed where whitespace occurs
> >
>
> can you give you me the line num in the rfc?
>
> and even then, the original thing was:
> Received: from ar39.lsanca2-4.16.241.28.lsanca2.elnk.dsl.genuity.net
> ([4.16.241.28] helo=watson1)
> and here helo=watson1 is inside parens, and with withespace (before and
> after the parens). or am I missing something?
It IS Microsoft. I know that for certain. That machine is sitting about
10' to the East of me at this moment. My Received: header is will be
a similar format with "kittycat" as the helo. These are the computer
names on the local network isolated from the outside network by a Linux
firewall.
I am *NOT* about to rename these machines by the incomprehensible,
impossible to type from memory, and changeable name assigned to the
firewall interface.
I do NOT run a mail server for sending mail to the Internet on the
firewall machine. I do not, at this time, intend to. If we get a static
IP I might consider firing up a suitably screwed down Postfix for direct
incoming and outgoing email rather than the fetchmail configuration in
use at the moment.
While I fully realize that Microsoft is well known to "embrace and
extend" otherwise known as screw-up common standards for their own
incomprehensible reasons. (Most often it's probably some jerk genius
programming it who might declare, "Gee, I didn't think of that!" An
example of that is the means by which I, were I a malware author,
could render your machine mysteriously unbootable in anything but
safe-mode simply because Microsoft did not think of the consequences
of a change they put into SP2. A product I make happened to trigger
this defect. I had to find a way around it.) Anyway, the point of
this is that denying that format will deny a very large proportion
of mail that is from Outlook Express users.
Personally, I don't give a fleeking furglemonk whether you do or not.
I'm simply telling you what the facts of the situation are so that
you can make your own determination whether you want to block email
from a VERY large segment of the legitimate email crossing the net
today. Then you can take responsibility for lost or rejected email
for yourself. (If you have customers involved be aware this may
constitute a liability situation for you personally and your
company.)
{^_^} Joanne
PS: The actual firewall machine is imaginatively named "it".
If you dig in the headers enough maybe you can even figure out
the internal network particulars. It is NOT going to change
because somebody is needlessly particular about header formats.
