We run fail2ban to update postscreen blacklist which is cidr file. To
make postscreen see the changes we have to reload postfix. Yesterday we
found postfix was reloaded more than 3000 times. Sure it is not acceptable.
What would be the best way to refresh postscreen blacklist (something
like kill
Daniel L. Miller:
>
> The above is a very rough draft - but something like this that exposes
> Postfix's thinking,
Actually showing the message way through Postfix looks like a good idea.
Best regards,
MU
smime.p7s
Description: Kryptograficzna sygnatura S/MIME
Wietse Venema:
> Don't turn on the "after 220 greeting" tests if you don't want to live
> with the consequences of doing so.
Actually we wanted to have "greylisting" active knowing the
consequences, which is mail delay. However, _infinite_ mail delay by
google.com showed up as a side effect...
We found the following in postfix log while expecting test mail delivery:
2012-03-29T13:32:41+02:00 services/192.168.10.210
postfix/postscreen[1697]: [ID 197553 mail.info] NOQUEUE: reject: RCPT
from [74.125.83.53]:56421: 450 4.3.2 Service currently unavailable;
from=mailto:uh...@gazeta.pl>>,
to=ma
