Nils Vogels <[EMAIL PROTECTED]> writes: Sorry, I've been busy and not keeping up with the lists....
> Tim Legant wrote: > > >The final recipe should only happen if tmda-filter returned something > >other than 0. It says that if tmda-filter returned 99 (because of a > >bounce, confirm or drop, for example), procmail's exit code should be > >reset to 0, since no MTA but qmail understands the 99. > > > > > Do you have any idea if tmda-filter will spit out the message on > stdout if it has decided to bounce/confirm/hold the message ? It will not. However!!! Procmail, upon seeing that the filter did not produce output, will continue processing using the message as it existed before you passed it to the filter. Procmail will log the following messages: procmail: Non-zero exitcode (99) from " /home/thl/projects/tmda/bin/tmda-filter -p" procmail: Rescue of unfiltered data succeeded Nice of it, huh? That's why you have to go through the nonsense to check return codes yourself. > If it does: Can I assume that X-TMDA-Action-Incoming is set > correctly,(ie. not OK) so that I can decide to ditch the message on > that header? Given that procmail will "rescue" the original message, there will be no X-TMDA-Action-Incoming header. You could then drop the message if the header doesn't exist. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
