Tony, > I've discovered the amavisd-release command and if I use it, the mail gets > released ok, but is then rescanned and banned all over again - not exactly > the behaviour I was expecting!
This is not what normally happens. > Doe's anyone know if this is what is supposed to happen, or have I > configured something incorrectly? The 'amavisd-release' causes mail to be sent over $release_method, which specifies an IP address and a port number of a MTA to which a message should be sent. If $release_method is undefined it defaults to $notify_method, which in turn defaults to 'smtp:[127.0.0.1]:10025'. It is expected that a MTA at a specified port number does not invoke a content filter again, otherwise notifications and quarantine releases would be re-scanned. There is also a complementary utility (actually/usually just a soft link) called 'amavisd-requeue', which bahaves much like 'amavisd-release', except that it causes a message to be sent over a $requeue_method, which defaults to 'smtp:[127.0.0.1]:25', which typically causes a message to be re-scanned. > I'm using amavisd-new-2.5.4-1.el5.rf - so that's an rpm packaged version > from rpmforge. The o/s is Centos 5, and I'm also using sendmail and > cyrus-imapd on the same server. Are you invoking amavisd through a milter or through a dual-MTA setup? If you let things at their defaults, it seems that SMTP listener on port 10025 does not have a milter disabled, causing a message to be re-scanned. Using a dual-MTA setup is cleaner in this respect. Mark ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
