At 06:42 AM 8/22/2005, Jochen Seifarth wrote:
I am currently setting up a Postfix dual-SMTPD configuration with AMaViS
in between in the SMTPDs. In this configuration I would like to implement
restrictions in the second SMTPD, based on spam scores calculated by
AMaViS via SpamAssassin, i.e. low spam score -> no restrictions, high spam
score -> restrictions. These restrictions obviously have to have to be
done in the the second SMTPD, therefore I would like to restrict in the
second SMPTD but also based on the orginal MTA's address (i.e. the one
that spoke to my first SMTPD) and not that of my AMaViS installation.
That's why I was looking at XCLIENT/XFORWARD... but then you can only
configure Postfix to automatically send an XFORWARD, not an XCLIENT...
arghh... so at the moment I have tweaked AMaViS to accept an XFORWARD and
send on the details as XCLIENT.
This is a bad idea. When the second postfix REJECTs mail, the first
postfix will have no choice but to generate a bounce to the envelope
sender. Your server will be sending bounces to innocent third
parties (called backscatter - you'll get blacklisted for this) and
your queue will be clogged with undeliverable bounces, slowing everything down.
Once you have accepted mail from the internet, your only reasonable
options are to deliver as is, tag & deliver, or discard it.
--
Noel Jones
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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/
