"Jesse D. Guardiani" <[EMAIL PROTECTED]> writes: > One thing I noticed is that when a message is released (and > maybe when a message is deleted too), tmda-pending actually > pipes the message through the sendmail interface instead of > doing the work directly.
[...] > Would anyone object to the abstraction of this functionality > (release and delete) into a different class or having > tmda-pending call tmda-filter directly? The reason TMDA "re-injects" a message to get it delivered is so that it doesn't have to re-invent the behavior of the MTA's local delivery agent. For example, what if my final delivery instruction looks like this: DELIVERY="| /home/jason/bin/myprog" `myprog' may relay on one or more of the environment variables setup by qmail-local (see qmail-command(8). By re-injecting the message and allowing qmail-local to deliver it, TMDA doesn't need to have any knowledge of those environment variables. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
