On 2005-01-08 13:15:07 +0100, Peter J. Holzer wrote:
On 2005-01-07 20:02:31 -0500, Seth Breidbart wrote:
for a sufficiently large ISP (think AOL, or a cable modem business),
keeping track of the tuples of <sender, recipient> for any length of time
will require a _substantial_ database infrastructure.
Under 1K of data. Remembering stuff is doing it the hard way. Create
the lhs of the Message-ID signed with a private key that changes
daily.
That assumes that the Message-ID is created by the MTA. Many MUAs create
the Message-ID themselves, and the MTA should not (indeed must not, per
RFC 2476 and 2821, if it is syntactically correct) replace it, because
that would make the "In-Reply-To" and "References" headers useless.
However, the ENVID introduced in RFC 1891 (current version: RFC 3461)
may be generated in that way.
Would that be feasible?
* Do MUAs generate ENVIDs?
* Which percentage of bounces contains the ENVID?
Looks like I should do a bit of research on our mail server :-)
hp
--
_ | Peter J. Holzer | Je höher der Norden, desto weniger wird
|_|_) | Sysadmin WSR | überhaupt gesprochen, also auch kein Dialekt.
| | | hjp(_at_)hjp(_dot_)at | Hallig Gröde ist fast gänzlich
dialektfrei.
__/ | http://www.hjp.at/ | -- Hannes Petersen in desd
pgp6wwDsf7L8n.pgp
Description: PGP signature
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg