On Sun, 21 Nov 2004, at 10:08pm, [EMAIL PROTECTED] wrote:
The HELO domain represents the mail provider used by the author of the
message and thus is more closely related to the author than any other
header within the message.
Eh...
HELO isn't even a header. It is an SMTP command
Sheesh. HELO is not a header. :-)
I quote from RFC-821, Section 4.1.1, Page 19:
HELLO (HELO)
This command is used to identify the sender-SMTP to the
receiver-SMTP. The argument field contains the host name of
the sender-SMTP.
The
Anybody agree with the following statement?
The HELO domain represents the mail provider used by the author of the
message and thus is more closely related to the author than any other
header within the message.
This is from the CSV doc to the FTC. Is is just mean, or does this
seem to ignore
Jeff Macdonald wrote:
Anybody agree with the following statement?
The HELO domain represents the mail provider used by the author of the
message and thus is more closely related to the author than any other
header within the message.
This is from the CSV doc to the FTC. Is is just mean, or does
Jeff Macdonald wrote:
Anybody agree with the following statement?
The HELO domain represents the mail provider used by the author of the
message and thus is more closely related to the author than any other
header within the message.
This is from the CSV doc to the FTC. Is is just mean, or does
I was a bit too quick on the reply, the HELO in the mail header is from
the first mail server which accepts the message. Subsequent hops don't
change the initial HELO. However, I do have mail servers which have to
rewrite headers and provide a specific domain in a HELO for mail to be
On Sun, 21 Nov 2004 23:18:20 -0500, Dan Jenkins wrote:
I was a bit too quick on the reply, the HELO in the mail header is from
the first mail server which accepts the message. Subsequent hops don't
change the initial HELO.
I must re-read the RFCs. I was not under the impression this was so.
