Noel, > reject_unauth_pipelining is ineffective under > smtpd_recipient_restrictions, and probably shouldn't > be used on a content_filter reinjection port.
I stand corrected. It's been some time since I visited that part of the docs for the last time. > You don't really intend to check amavisd-new for > pipelining violations, do you? Certainly not. > That seems quite pointless. > Seems like the goal is to prevent abuse of the > reinjection port (it's well protected with > permit_mynetworks,reject) Yes. > and disable other checks > that could either slow down reinjection or interfere > with legit amavisd-new traffic. Right. > reject_unauth_pipelining doesn't belong here. The reasoning was that it doesn't hurt if Postfix keeps an eye on potential protocol violations from amavisd, just in case if some bug creeps it, assuming that reject_unauth_pipelining doesn't cost anything. > BTW, recent versions of postfix will allow but > complain about: > -o smtpd_recipinet_restrictions=permit,reject > "warning: restriction `reject' after `permit' is > ignored" > so best to stick with "permit_mynetworks,reject". Agreed. So you think the: -o smtpd_client_restrictions=reject_unauth_pipelining,permit_mynetworks,reject would be quite useless and I should stick to: -o smtpd_client_restrictions=permit_mynetworks,reject ? Mark ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ 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/
