[policyd-users] rate limiting outgoing emails per domain.

[Roalt Zijlstra]

Hi there,

I am new to policyd v1 and v2. I see that the policyd is able to rate limit email. I am
using it with Postfix and don't understand how I can get it to rate limit outgoing mail,
which is send by the 'smtp' processes.

I added the smtpd_*_restrictions to my postfix config, but as I understand Postfix that
has only effect on the receiving email. I tried cluebringer-2.0.4 and I will be testing
it a little more, but I am curious how you might be able to rate limit outgoing mail.

Greetings,

Roalt Zijlstra

[Markus Quaritsch]

Roalt,

Post by Roalt Zijlstra
I added the smtpd_*_restrictions to my postfix config, but as I understand Postfix that
has only effect on the receiving email. I tried cluebringer-2.0.4 and I will be testing
it a little more, but I am curious how you might be able to rate limit outgoing mail.

That's also my understanding how rate-limits work. According to the
postfix documentation you can tune the queue management, but that was
not applicable in my case.

So my solution is to setup two postfix instances. The first one queues
all the outgoing mails without throttling, having the second instance as
relay-host. The second instance uses cbpolicyd quotas and defers mails
if over quota (smtpd_*_restrictions). Works pretty fine...

regards,
quam
--
Markus Quaritsch
E: quam at qwws.net
W: www.qwws.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 257 bytes
Desc: OpenPGP digital signature
Url : http://lists.policyd.org/pipermail/users/attachments/20080902/7268a7f0/attachment.asc

[Roalt Zijlstra]

Post by Markus Quaritsch
Roalt,

Post by Roalt Zijlstra
I added the smtpd_*_restrictions to my postfix config, but as I understand Postfix that
has only effect on the receiving email. I tried cluebringer-2.0.4 and I will be testing
it a little more, but I am curious how you might be able to rate limit outgoing mail.

That's also my understanding how rate-limits work. According to the
postfix documentation you can tune the queue management, but that was
not applicable in my case.
So my solution is to setup two postfix instances. The first one queues
all the outgoing mails without throttling, having the second instance as
relay-host. The second instance uses cbpolicyd quotas and defers mails
if over quota (smtpd_*_restrictions). Works pretty fine...

Hi Markus,

Thanks for your answer...

I am thinking if it is possible to come up with an after-queue filtering script using
cluebringer with postfix. Ie like an amavisd-new daemon is implemented, you could send
mail to a rate limiting daemon which allows or denies.. if denied it gets a soft-bounce.

postfix -> port: 10024 -> rate limit daemon -> port: 10025 -> postfix

This way you don't need two postfixes... I have per server several postfix instances and
am not getting cheery about having to double the number of the instances.

You have any clues how to use cluebringer in this?

Greetings,

Roalt

Post by Markus Quaritsch
regards,
quam
--
Markus Quaritsch
E: quam at qwws.net
W: www.qwws.net
_______________________________________________
Users mailing list
Users at lists.policyd.org
http://lists.policyd.org/mailman/listinfo/users