On Sat, 13 Sep 2003, Sam Varshavchik wrote:
Colin Dick writes:
> Hi all,
> Thanks again for all the help with optimization to try to reduce /
> speed up the processing of my mail queue which at one point contained over
> 200,000 messages. I am now at about 70,000 and still reducing.
> > In any event, one of the things I attempted to was to write a > program to parse the queue for specific deliveries and run:
> > /usr/lib/courier/bin/cancelmsg <qid>
> > for the specific id's. I thought this was a great step as I have > a whack of messages to a common address that don't need to be delivered. > However, I see now that bounces are being sent for every message I have > marked to delete.
> This has not helped to clean my queue as now, instead of the > initial message, I have a bunch of bounces being generated and populating > the queue. So I am no further ahead with that theory.
> Is there a way to cancelmsg immediately with no bounce? This
Nope. cancelmsg essentially marks the message as failed. Unless the message has DSNs turned off, this will result in a non-delivery report.
Sounds like a perfect time to add a switch to cancelmsg to prevent bouncing of canceled messages!
Is that possible?
Well, it'll take a little bit more work to do that. Cancelmsg, in addition to adding the record in the control file that essentially fails all recipients, also needs to add another record that turns off DSNs for the message. Additionally, the code that checks the DSNs for the message needs to be modified to pay attention to the last record in the control file that sets the message's DSN. There could be one in there already, the real DSN setting for the message.
pgp00000.pgp
Description: PGP signature
