On Saturday, February 26, 2005, 01:56:48, Matt wrote:
> When using an IP address as a "domain-literal", the RFC specifies that
> it must be enclosed in square brackets.
No disagreement here but I didn't claim that 81.255.84.73 was a
domain-literal.
> While domain-literals in the Received lines are definitely supposed to
> appear with this construct, I could see the possibility that this was
> not intended or required for use in the Message-ID.
Correct, its purpose is to be a unique message identifier.
> The RFC specifies this as a "id-right" with possible values being
> "dot-atom-text / no-fold-literal / obs-id-right", no mention of
> "domain-literal".
That's cause domain-literal allows white space, no-fold-literal doesn't.
no-fold-literal = "[" *(dtext / quoted-pair) "]"
dtext = NO-WS-CTL / ; Non white space controls
%d33-90 / ; The rest of the US-ASCII
%d94-126 ; characters not including "[",
; "]", or "\"
> Note that I am not an RFC expert and it takes the
> tech equivalent of a lawyer to figure some of this stuff out.
Its not that hard once you get used to it :-)
> ... but in a broader sense you
> should understand that this is in fact indicative of spam and can be
> used effectively with a moderately low weight in your Declude setup, so
> whether or not it is valid behavior according to the RFC, the use of
> this identifier should be the same.
I'm not arguing about the merits of treating certain instances of msg-id
as spam indicating. I'm just claiming that the msg-id in question was
RFC compliant.
--
[EMAIL PROTECTED] "The avalanche has already started, it is too
Rod Dorman late for the pebbles to vote." � Ambassador Kosh
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
