From: Mark M. <Mar...@ij...> - 2004-01-31 23:51:17
|
Thorild, | > You can do what you are used to, by using the Postfix smtpd 'proxy' | > (README_FILES/SMTPD_PROXY_README), but I do not recommend it | > for precisely the reasons explained by Klaus. | | Would this make a setup like this possible? | | * If proper action for all recipients of a message is REJECT, the | receiving MTA will reject the message. Yes. | * If proper action for at least one recipient is other than REJECT, | the receiving MTA will accept the message and then deliver and | bounce as appropriate, respecting per recipient configurations -- | including per recipient settings for header rewriting (this is a | requirement). Yes. | If this is possible, then I am likely to cheerfully abandon sendmail | RSN. Is it? Experience of using amavisd-new as a Postfix smtpd 'proxy' is scarce. It was reported that it works fine, but there might still be some hidden gochas, as amavisd-new is not exectly a 'transparent' proxy, which is what Postfix smtpd 'proxy' was intended for. One catch for example is when AUTH is being used in SMTP session. I have code now to make plain authentication be passed to the output side (in recent snapshots), but it can not work this way for more complex authentication schemes which involve a dialog. Try it out. I'll help if unexpectable happens. And there is always a possibility to switch to the content_filter setup. Mark |