On 17 February, "Henry W. Miller" <henrym@sacto.mp.usbr.gov> wrote:
> > From: MX%"jerry@ora.com" 17-FEB-1996 09:28:05.11
> > Listproc 6.0 (and probably later versions) do a few things to stop
> > your problem of duplicate messages going to a list:
> >
> > - it keeps the last 500 (I think) Message-IDs sent to each list, and
> > also sent to listproc itself (administrative requests). ...
> >
> > - it computes a checksum of each message body sent to a list.
> > When a new message comes in, it compares the checksum to the last 500
> > checksums ...
>
> This would assume, of course, that the rogue mailer kept
> generating the same message-id for each message. If not, then there
> would still be trouble...
On 17 February, close@lunch.engr.sgi.com (Diane Barlow Close) wrote:
> You could always strip out the headers and do a body checksum...
Sorry if I wasn't clear. That's what listproc does when it computes
that checksum I mentioned. (I think it also strips trailing whitespace
from each line of the body before it calculates the checksum... in case
some gateway/etc. has added whitespace to the original message body.)
--Jerry, jerry@ora.com
Follow-Ups:
References:
|
|
