Re: Limit rate/concurrency to a given domain

2009-02-23 Thread /dev/rob0
On Mon February 23 2009 09:52:26 Santiago Romero wrote: > > That's right, the logs show the program name (smtp) not the > > transport name; you can't tell which transport called smtp. > > > > You can add something like > > -o syslog_name=postfix-slow > > to the master.cf slow transport entry to d

Re: Limit rate/concurrency to a given domain

2009-02-23 Thread Santiago Romero
That's right, the logs show the program name (smtp) not the transport name; you can't tell which transport called smtp. You can add something like -o syslog_name=postfix-slow to the master.cf slow transport entry to differentiate the logging. That's it. Postfix is awesome and very well des

Re: Limit rate/concurrency to a given domain

2009-02-23 Thread Noel Jones
Santiago Romero wrote: mouss escribió: Is there any way to verify seeing the logfile if a given message is going throught a given transport (say "slow" in my master.cf) instead of standard "smtp" transport? I'm not sure or I don't know how to check if the messages are being delivered by the "sl

Re: Limit rate/concurrency to a given domain

2009-02-23 Thread Santiago Romero
mouss escribió: Is there any way to verify seeing the logfile if a given message is going throught a given transport (say "slow" in my master.cf) instead of standard "smtp" transport? I'm not sure or I don't know how to check if the messages are being delivered by the "slow" transport I defined

Re: Limit rate/concurrency to a given domain

2009-02-21 Thread mouss
Santiago Romero a écrit : > > Is there any way to verify seeing the logfile if a given message is > going throught a given transport (say "slow" in my master.cf) instead of > standard "smtp" transport? > > I'm not sure or I don't know how to check if the messages are being > delivered by the "slo

Re: Limit rate/concurrency to a given domain

2009-02-20 Thread Wietse Venema
Santiago Romero: > > > Therefore, "smtpd -o slow_destination_rate_delay" does not work, > > nor does "smtp -o slow_destination_rate_delay". > > > > So, how do I set an specific rate delay for a given "transport"? > > This way?: > > qmgr fifo n - n 300 1 qm

Re: Limit rate/concurrency to a given domain

2009-02-20 Thread Santiago Romero
Therefore, "smtpd -o slow_destination_rate_delay" does not work, nor does "smtp -o slow_destination_rate_delay". So, how do I set an specific rate delay for a given "transport"? This way?: qmgr fifo n - n 300 1 qmgr -o slow_destination_rate_delay =1 ?

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Santiago Romero
Is there any way to verify seeing the logfile if a given message is going throught a given transport (say "slow" in my master.cf) instead of standard "smtp" transport? I'm not sure or I don't know how to check if the messages are being delivered by the "slow" transport I defined :? (at least

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Wietse Venema
Santiago Romero: > Wietse Venema escribi?: > > default_destination_rate_delay (default: 0s) > >The default amount of delay that is inserted between individual > > deliv- > >eries to the same destination; with per-destination recipient > > limit > > >1, a destination is

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Santiago Romero
Wietse Venema escribió: default_destination_rate_delay (default: 0s) The default amount of delay that is inserted between individual deliv- eries to the same destination; with per-destination recipient limit > 1, a destination is a domain, otherwise it is a recipient. ..

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Wietse Venema
Santiago Romero: [ Charset ISO-8859-1 unsupported, converting... ] > > Sorry, I meant "smtp" instead of "smtpd" in the master.cf. > > > > /etc/postfix/master.cf: > > slow inet n - - - - smtp > > > > /etc/postfix/transports: > > domain1.comslow: > > domain2.

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Santiago Romero
Sorry, I meant "smtp" instead of "smtpd" in the master.cf. /etc/postfix/master.cf: slow inet n - - - - smtp /etc/postfix/transports: domain1.comslow: domain2.comslow: /etc/postfix/main.cf: slow_destination_concurrency_limit = 1 slow_destination_rate

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Santiago Romero
The destination_concurrency_limit and rate_delay parameters can be configured per transport. You could configure a transport map to route all mail destined to domain.com via the example: transport, which can be configured as a clone of the smtp transport in master.cf. Then, specify concur

Re: Limit rate/concurrency to a given domain

2009-02-19 Thread Sahil Tandon
On Feb 19, 2009, at 11:44 AM, Santiago Romero wrote: Hi. I have a postfix mailserver working as a secondary MX of a domain (let's call it "domain.com"). The primary MX is a qmail+antivir +antispam server that has serious memory/cpu problems to process all the email (the one which recei

Limit rate/concurrency to a given domain

2009-02-19 Thread Santiago Romero
Hi. I have a postfix mailserver working as a secondary MX of a domain (let's call it "domain.com"). The primary MX is a qmail+antivir+antispam server that has serious memory/cpu problems to process all the email (the one which receives by itself and the email that I sent to it). Is there an