1

Topic: [SOLVED] bulk mail bottleneck

Hi,

   I have a customer that send bulk mails periodically, what collapse the postfix queue. As throttle doesn't work as expected:
http://www.iredmail.org/forum/topic2063 … ottle.html
, I wonder if I can bypass spamassassin and antivirii for authenticated users of for mails from a particular ip.

Regards,
   Lucas

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: [SOLVED] bulk mail bottleneck

landm wrote:

I wonder if I can bypass spamassassin and antivirii for authenticated users of for mails from a particular ip.

Reference:
http://www200.pair.com/mecham/spam/bypassing.html#5
http://www200.pair.com/mecham/spam/bypassing.html#6
http://www200.pair.com/mecham/spam/bypassing.html#7

3

Re: [SOLVED] bulk mail bottleneck

Hi ZhangHuangbin,

  I think I found the error. In the faq:
http://www.iredmail.org/wiki/index.php? … ian.Ubuntu
In the file: /etc/postfix-policyd_sender_throttle.conf
you suggest:

SENDERTHROTTLE=1
SENDER_THROTTLE_SASL=1
SENDER_THROTTLE_HOST=0
RECIPIENTTHROTTLE=1

But reading this link:
http://comments.gmane.org/gmane.mail.po … olicyd/826
this is the key:
----------------------------------------------------------------------

Yes, the problem arises as soon as there is a message with more than one
recipient. As far as I know, Postfix does not pass multiple recipient
addresses to policyd when it is invoked at
smtpd_end_of_data_restrictions. Therefore recipient throttle cannot work
at this point.
Now I put recipient throttle together with the greylisting stuff into
the first instance of policyd that is invoked with
smtpd_recipient_restrictions.
The second instance of policyd is invoked at
smtpd_end_of_data_restrictions and does only sender throttle but nothing
else.

This seems to work now. Thank you for the hint.

----------------------------------------------------------------------

So I changed
RECIPIENTTHROTTLE=0

  And it works!!!
Please double check it and correct the faq.

Regards,
   Lucas