[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MessageIDs (Re: High Road)
On Mon, Oct 20, 2003 at 02:03:45PM -0400, Chuck Yerkes wrote:
> Message ID, if present, must be unique and *must* be in the form:
^^^^^^
> "Message-ID: " + "<" + LHS + "@" + RHS + ">"
I fail to see how you ensure uniqueness of the MID with an RHS of
"goldfinger.local". To make the example more drastic, imagine the
hundreds of thousands of boxes who deliver messages as being
localhost.local. Using those kind of RHSs does not need any kind of
destructive mind to make MIDs collide[1], it just requires some other
Netizens who do the same mistake like you and accidently send
mails/usenet-posts with the same RHS.
An unique MID can be ensured by using a FQDN which is unique on the
Net; for example the FQDN of an IP that resolves forward- and reverse
uniquely on non-RFC-1918 Space.
If you cannot ensure that or are on dynamic IPs, you might consider
letting your SmartHost setting the MID. This has atleast one drawback
though: Spamfilters like Spamassassin might put scores on
MID-set-by-MTA[\d] or similar.
On Mon, Oct 20, 2003 at 08:25:14PM +0200, Andreas Krennmair wrote:
> P.S.: the solution is that goldfinger.local is not a valid Internet
> domain name.
That, too.
1) MIDs are supposed to be unique exactly to prevent MID-collisions.
feel free to fup2p (headers set), since it was a sidenote only anyway
and possibly is OffT.
--
| Rico -mc- Gloeckner | mv ~/.signature `finger mc@ukeer.de` |
| gpg/mail: 3D67 D42F 2D50 4B68 1D62 E999 EFCB CDFF 61F0 5B8C |
| gpg/jabber: 7A1C D378 CAB7 C545 5E5D CC44 C44F 9657 3D9C 8389 |