> > Has anyone found a general solution to keeping the list cluttered
> > with these (short of filtering messages that start with
> > "Confirmation of Reading" )
>
> I have modified several MLMs to solve this problem at one time or
> another. Basically, you want to remove the headers 'X-Pmrqc' and
> 'X-Confirm-Reading-To' (not sure on the capitalisation, I kill all
> capitalisations) from the messages going to the list. That way,
> Pegasus won't try to respond to a request for confirmation of
> reading.
>
> Under Majordomo, I changed the 'resend' program around line 194 to add
> the following lines to the "list of headers to skip":
>
> || /^x-pmrqc:/i
> || /^x-confirm-reading-to:/i
>
> This problem is not specific to majordomo, but other MLMs (perhaps
> listproc) may solve the problem as shipped.
I've found a couple of other headers to cause problems as well. Here's
some of the lines from the rules file I use on Primate-Talk to discard the
offending headers from messages before sending them out.
# Discard the following headers
match /^X-Ack:/i drop
match /^X-Pmrqc:/i drop
match /^X-Confirm-Reading-To:/i drop
match /^Return-Receipt-To:/i drop
I also try to detect replies to these types of worthless messages and
bounce them to myself:
match /^Subject:.*Delivery Confirmation/i bounce primate-talk-owner
match /^Subject:.*Receipt Confirmation/i bounce primate-talk-owner
match /^Subject:.*RCPT:/i bounce primate-talk-owner
match /^Subject:.*ACK:/i bounce primate-talk-owner
match /^Subject:.*Receipt Confirmation/i bounce primate-talk-owner
These rules are read by a perl script I use to preprocess incoming messages.
Since I started using them, this type of problem has pretty much gone away.
When I find a new header that causes problems, I just add a line to the
rules file.
Paul DuBois
dubois@primate.wisc.edu
Follow-Ups:
References:
|
|
