On Tue, Mar 08, 2011 at 10:38:09AM -0300, M?rcio Luciano Donada wrote: > I understand perfectly that postfix has nothing to do with tmda, but I'm > so use it to transport, as follows, but so the tmda returns code 99 [2]. > Well, what I am now is much the same set up as a transport:
You can't use a policy service as a transport. They are completely different beasts. If you try to use your sneakers as a hat, you'll be disappointed. > # TMDA > tmda unix - n n - - spawn > user=nobody argv=/bin/bash /usr/local/tmda/contrib/tmda-postfix-policy.sh This is a policy service script. > In the main.cf > mailbox_transport_maps = hash:/etc/postfix/maps/transport-tmda > > smtpd_recipient_restrictions = ... > check_policy_service unix:private/tmda, This is a policy service call, which is likely fine. > # cat /etc/postfix/maps/transport-tmda > user tmda A pair of sneakers is not a hat, you can't use a policy service as a transport. > [1]. http://tmda.sourceforge.net/cgi-bin/moin.cgi/ServerConfiguration > [2]. Mar 7 17:17:48 mx postfix/local[6202]: 3F01F8480A1: > to=<mdon...@xxxx.com.br>, relay=local, delay=0.07, delays=0.01/0/0/0.06, > dsn=5.3.0, status=bounced (Command died with status 99: > "/usr/local/tmda/bin/tmda-filter") The exit status of "99" is I believe designed with qmail in mind. Also this message did not get routed to the transport you configured, it got handled by "local(8)", the command "tmda-filter" is not what you show above. You appear to be rather confused. -- Viktor.
