From: Alain Spineux (aspineuxgmail.com)
Date: Sun Jul 22 2007 - 07:52:49 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello

First, *_destination_recipient_limit=1 will do the opposite of what you want.
If you had an email to 10 recipients, using *recipient_limit=1, will split
the mail in 10 emails to 1 recipients.

If I had to do that quickly, I would take the sample script in Aftter
Queue content filtering
and add some sleep command in it, and limit the number of daemon to 1.

for the sleep something like

let now=`date +"%s"`
let delay=60-now%60
sleep $delay

will wait until the next minute, meaning if it is 14:49:47, this will
wait 13 sec.
That way if mail sending is less than 1min, it will send an email every minutes.

Regards

On 7/21/07, Juan Pablo Bagnon <jpbgrupo-netcom.com> wrote:
>
>
> Dear list members:
>
>
> i was in the need to catch all the overwelming tsunami of emails that my
> content filter server (CFS) is getting with a postfix server, then, sending
> with a controlled rate, tunning it untill the CFS works w/o colapsing.
>
> i did some sort of a solution that works but i dont have a fine control of
> the message rate feeding my lame CFS. the only thing i have in mind is set a
> IP traffic sharping.
> QoS can control the ammount of data passed to the CFS but is not efficient
> in the number of emails, mostly spam (~80%). these spam messages are mostly
> less than 1 kb so the real problem of my CFS is processing emails/minute
> than KB/minute.
>
>
> i have googled and found and implemented the solution above. im not happy
> with it... is there another tecnically more robust and better than this?
>
>
> from http://www.akadia.com/services/postfix_mx_backup.html
> i did:
>
>
>
>
> /etc/postfix/main.cf:
>
> relay_domains = $mydestination the.backed-up.domain.name
> smtpd_recipient_restrictions = permit_mynetworks
> check_relay_domains
>
> /etc/postfix/main.cf:
>
> transport_maps = hash:/etc/postfix/transport
>
> /etc/postfix/transport:
>
> the.backed-up.domain.name smtp:[their.mail.host.name]
>
> then from
> http://groups.google.com.ar/group/list.postfix.users/browse_thread/thread/cf0fe8258b1fedd/a07e91e50c693fe4?lnk=gst&q=rate+limiting&rnum=37&hl=es#a07e91e50c693fe4
>
>
> i have set to 1 all of this values:
>
> *_destination_recipient_limit
> *_destination_concurrency_limit
>
>
> from somewhere else i got a solution to hold for 5 secs every delivery
> setting a fake non functional transport and playing with
> smtp_connect_timeout, so the final setup is this:
>
>
>
> master.cf:
>
>
> brc unix - - n - 1 smtp
> -o fallback_relay=[dest.ip.1.ok]
> -o smtp_connect_timeout=5
> brc2 unix - - n - 1 smtp
> -o fallback_relay=[dest.ip.2.ok]
> -o smtp_connect_timeout=5
>
>
> main.cf
>
>
> initial_destination_concurrency =
> 1
> default_destination_concurrency_limit =
> 1
>
> transport_maps =
> hash:/etc/postfix/transport
> relay_domains =
> hash:/etc/postfix/relay_domains
>
> brc2_destination_concurrency_limit =
> 1
> brc2_destination_recipient_limit =
> 1
>
> brc_destination_concurrency_limit = 1
> brc_destination_recipient_limit = 1
>
>
>
> transport
>
>
> domain1.ltd smtp:[real.ip.addr.ok]
> domain2.ltd brc:[10.10.10.10]
> domain3.ltd brc2:[10.10.10.10]
>
>
> take in mind that i need to archive is the opposite of the developers have
> working on all this time: performance.
> i need to hold the emails with this server and slowly feed in a
> message/minute based rate with the finest control posible to set a proper
> rate for letting the CSF opperate efficiently.
>
> thanks in advance.
>

--
--
Alain Spineux
aspineux gmail com
May the sources be with you

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]