Anand Buddhdev <ar...@anand.org> writes:
On Tue, Feb 10, 2004 at 04:39:12PM +0100, Julian Mehnle wrote:
[ ... ]
IIRC, a courierfilter can't "mark all recipients as delivered", only
a delivery instruction (in a dot-courier file) can.
I think you're wrong. A filter *can* modify a control file.
But the courierfilter sees the TEMPORARY control file.
And that brings up the following question: is this temporary control
file a copy of the longer-lived one, or does the longer-lived control
file come into existence via a rename of this temporary control file?
In other words, is this temporary control file only good for read-only
information, or if I modify this temporary control file within a
courierfilter step, will the subsequent message-processing steps see
these control-file changes?
So, what significant difference is there between marking all
recipients as delivered plus resubmitting the message *in a delivery
instruction* (e.g. in a maildrop script) and just modifying the
message *in a delivery instruction* (e.g. in a maildrop script)?
Maildrop cannot modify the control file. And adding headers to a copy
of a message being delivered to multiple users uses more resources
than doing it once at message reception time.
It would be so nice if courier allowed adding,removing or modifying
message headers at filter-time.
Hear hear!
18 messages in net.sourceforge.lists.courier-users[courier-users] Re: Minor flaw in cou...
