Lloyd Zusman <[EMAIL PROTECTED]> writes: > Therefore, for any given piece of email that makes it through my > filters into my inbox, I'm not always sure which filtering steps > have actually "touched" it. > > Therefore, I'd like each step to add a custom header, so that I can > see the path that a given email has gone through before delivery.
[...] > So, what remains is TMDA, the only link in the chain that doesn't > add its own header. Sure, I see the value here, and think it would probably be good to add at some point. I've really got my hands full with other things at the moment though, so we should probably figure out another way to do this using other tools. TMDA's DELIVERY variable is pretty flexible, allowing you to forward messages or pipe them to a command. What is your DELIVERY variable currently set to? > If I set up TMDA to use tmda-ofmipd to deliver its email locally, I > think that I could then get it to use the ADDED_HEADERS_SERVER to > append an appropriate header (is that correct, or am I > misunderstanding something about tmda-ofmipd?). ADDED_HEADERS_SERVER is only for adding headers to tmda-filter generated auto-replies (bounces, confirmation requests, confirmation acceptance notices). _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
