On Jul 19, 2006, at 03:52, Arno Garrels wrote:
> kaythorn wrote:
>>>> Is there something I can do to pacify X-Spam?
>>>
>>> Remove that space (the one between Roland and Couvela).
>>
>> Shall we modify function GenerateMessageID? Something like:
>>
I don't think we should modify the function. X-Spam is the one at
fault, as *it* does not conform to RFC. A Message-ID string's
requirement is that it be universally unique. To that extent, message
specific data (e.g. domain name, IP address, etc.) is appended to
locally unique strings such as timestamps, process IDs, etc; but this
is just convention. It may contain any character which is valid in the
Header values, as defined by RFC 822, which include spaces. The
angled-brackets defined the value's delimiter, so there is no need to
escape or remove spaces, nor any need to argue whether this field or
that should be the one included in the ID, as its all fair game as long
as we can guarantee uniqueness. A very common strategy is to do:
MessageID := '<'
+ Md5Checksum(ServerProcessID) + '$' +
Md5Checksum(EpochTimestamp)
+ '@' + SenderDomainName
+ '>'
dZ.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
