Re: postprox per recipient

2013-11-26 Thread Wietse Venema
Ian Baldwin: > Nov 24 07:01:13 aminoacid postfix/smtp[21274]: 80F96303AE7: > to=, relay=127.0.0.1[127.0.0.1]:10027, delay=303, > delays=1.9/0.02/301/0, dsn=5.5.0, status=bounced (host > 127.0.0.1[127.0.0.1] said: 354 End data with . (in > reply to MAIL FROM command)) Wietse: > You need a program t

Re: postprox per recipient

2013-11-26 Thread Ian Baldwin
Hi Wietse, all, I may see your point. Although postprox itself is an SMTP proxy, the script I'm forwarding its stdin to does nothing to acknowledge the SMTP protocol of the incoming data. Would that be the correct interpretation of your answer? Ian On Sat, Nov 23, 2013 at 10:09 PM, Wietse Venem

Re: postprox per recipient

2013-11-23 Thread Wietse Venema
Ian Baldwin: > localhost:10027 inet n n n - - spawn > user=vscan argv=/usr/local/sbin/postprox -v -c ... > Nov 24 07:01:13 aminoacid postfix/smtp[21274]: 80F96303AE7: > to=, relay=127.0.0.1[127.0.0.1]:10027, delay=303, > delays=1.9/0.02/301/0, dsn=5.5.0, status=

postprox per recipient

2013-11-23 Thread Ian Baldwin
Hi there, I am trying to setup a postprox based filter only for one recipient but it fails me altogether, no matter what I do. The last setup I have is routing messages by way of a transport map directive such as acco...@test.au postprox:[127.0.0.1]:10027 where in master.cf I have postprox un