Philon, > Jul 13 13:42:12 mail amavis[32260]: (32260-03) ESMTP: 504 5.5.4 RCPT > command parameter not implemented: NOTIFY=NEVER; PENALIZE: RCPT > TO:<[EMAIL PROTECTED]> > > I googled a bit and found http://rfc1891.x42.com/ and some description of > the RFC to delivery notification. It seems that our internal Exchange > server sets NOTIFY for the users requesting it and external Exchange > servers also do this.
As Gary properly guessed, you must have been using a pre-queue content filtering setup in Postfix. This setup requires a transparent smtp proxy, which amavisd-new is not. If/when it works in this setup, it relies on having its ESMTP options announced the same was as Postfix does, Now that Postfix supports and announces a DSN extension, you run into a problem, as amavisd-new does not yet support it (planned for 2.4.0). You have two choices: the best option is to switch to a post-queue setup, which is the recommended setup. Or you may dumb down Postfix and don't let it announce DSN in its EHLO options. > Now, how can I tell amavis to simply ignore this NOTIFY call, and continue > with his work? Possible, but I would not recommend it, as it breaks DSN requirements. Mark ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
