"Julian Mehnle" <[EMAIL PROTECTED]> writes: > Anand Buddhdev [EMAIL PROTECTED] wrote: >> Sam once suggested that your filter could mark the current message as >> "done" ie. mark all recipients as delivered, and instead inject a new >> message into the queue, with the headers you want added in. This is >> still a kind of hack, but saves you from having to create additional >> directories, and having to add headers later with maildrop. > > IIRC, a courierfilter can't "mark all recipients as delivered", only a > delivery instruction (in a dot-courier file) can. > > 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)? > > What am I overlooking?
Nothing, except for the fact that I want to do SPF processing as early and efficiently as possible, and so I want to do it during a courierfilter (using, for example, courier-pythonfilter+SPF). But to add the SPF-Received header to the message, I would have to do that in a maildrop recipe, and so I would need to devise a way to communicate state information between the courierfilter step and the maildrop step. My earlier proposal involved storing this state information in a central repository, keyed by the Message-ID. -- Lloyd Zusman [EMAIL PROTECTED] ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
