Hello,
On Sat, May 17, 2014, at 09:37 AM, [email protected] wrote:
> peaks of 100 rejected messages per minute is *nothing*
> frankly you can receive 100 messages per minute with no real load
>
> we have days with 1200000 rejected messages on a Barracuda appliance
> which in many cases even reveice and store the complete message for
> analyzes while reject at end-of-data, postfix usually don't receive
> a message it rejects and "hangs up" before message data
>
> 120000 in 24 hours = 120000 / 1440 = 833 per minute as average and
> you see peaks of 5000 rejected messages per minute on such days
Ok, it's pretty clear -- I should stop worrying. There's no 'problem'
here. Thanks!
> keep in mind restrictions are always processed in their
> order and so you should have the cheapest one at the begin
As I started looking I realize that I don't understand enough about
what's cheap, and wha't not so cheap. So I have to get back to some
reading.
As a first check with you, though, from this server I have from
postconf smtpd_recipient_restrictions
the following current order
check_recipient_access hash:/usr/local/etc/postfix/conf/traps
reject_non_fqdn_recipient
permit_sasl_authenticated
permit_mynetworks
reject_unlisted_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
reject_rbl_client b.barracudacentral.org
reject_rbl_client zen.spamhaus.org
check_policy_service unix:private/policy
permit
which I've tried to keep from server to server. I get that it's a naive
copy, and I'll do my homework.
Is there any GLARING problem in the order above?
Thanks.
Grant
