>>>>> "Jeremy" == Jeremy Howard <[EMAIL PROTECTED]> writes:
Jeremy> Doing it in a content_filter lets you add headers that you
Jeremy> can then handle in Sieve scripts on a per-user basis,
Jeremy> which is faster and cleaner.
Would it really be faster?
I haven't played with Postfix content_filters much yet, but
FILTER_README says "You can expect to lose about a factor of two in
Postfix performance for transit mail that arrives and leaves via SMTP,
provided that you create no temporary files". From the diagram, it
appears that mail passes through Postfix twice, so it looks like the
message will be written into the Postfix queue twice as well.
By the time the sieve extension gets called, lmtpengine has already
written the message to a temporary file. All I have to do is to read
the file and pass it to spamd...
-- Bob
