At 08:50 AM 11/14/2005, Mark Martinec wrote:
> But it might be a good idea to add some of the
newer
> restrictions to your suggested list to prevent
> surprises. If they have an older postfix without
> these options, they will be ignored and not break
> anything.
> -o smtpd_data_restrictions=
> -o smtpd_end_of_data_restrictions=
Ok, so now we have:
-o
smtpd_recipient_restrictions=reject_unauth_pipelining,permit_mynetworks,reject
-o
smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
reject_unauth_pipelining is ineffective under
smtpd_recipient_restrictions, and probably shouldn't
be used on a content_filter reinjection port.
You don't really intend to check amavisd-new for
pipelining violations, do you? That seems quite
pointless.
Seems like the goal is to prevent abuse of the
reinjection port (it's well protected with
permit_mynetworks,reject) and disable other checks
that could either slow down reinjection or interfere
with legit amavisd-new
traffic. reject_unauth_pipelining doesn't belong
here.
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".
--
Noel Jones
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.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/
