On 2/20/2012 9:42 AM, Przemysław.Orzechowski wrote: > > On Mon, 20 Feb 2012 07:00:11 -0600, Stan Hoeppner <s...@hardwarefreak.com> > wrote: >> On 2/20/2012 5:45 AM, Przemysław.Orzechowski wrote: >> >> >>> Feb 19 10:47:27 panel2 postfix/smtp[10854]: 56F7A8ED0DC: >>> to=<timez...@poczta.onet.pl>, >>> relay=mx.poczta.onet.pl[213.180.147.146]:25, >>> conn_use=7, delay=24703, delays=22811/1887/0.02/5.3, dsn=4.7.1, >>> status=deferred (host mx.poczta.onet.pl[213.180.147.146] said: 450 > 4.7.1 >>> <timez...@poczta.onet.pl>: Recipient address rejected: Sender address >>> deferred by rule #CR-IN-DEF-2 (in reply to RCPT TO command)) >> >>> Feb 19 10:47:27 panel2 postfix/smtp[12360]: 560128EC302: >>> to=<timez...@poczta.onet.pl>, >>> relay=mx.poczta.onet.pl[213.180.147.146]:25, >>> conn_use=2, delay=3975, delays=2083/1887/0.02/5.3, dsn=4.7.1, >>> status=deferred (host mx.poczta.onet.pl[213.180.147.146] said: 450 > 4.7.1 >>> <timez...@poczta.onet.pl>: Recipient address rejected: Sender address >>> deferred by rule #CR-IN-DEF-2 (in reply to RCPT TO command)) >>> >>> as this state continues longer than four hours a notice Delay info is >>> generated wich is sent to external host wich generates another 450 > error >>> and so forth. >>> I cant disable Delivery Delay notifications globally as other clients > use >>> them so is there any way to disable them for this account or drop them >>> before they are sent out ? >>> >>> Hope this explanation is clear enough. >> >> Yes, it is. I'm not fluent in Polish--have you read this? >> > http://www.goldenline.pl/forum/2640244/ciekawostka-serwery-pocztowe-onetu >> >> It's the only relevant Google hit, out of 5 total, searching for >> "deferred by rule #CR-IN-DEF-2", and it's on a Polish forum. (2 of the >> first 3 hits are your own messages to this Postfix list). >> >> It appears this problem exists at a single receiving site in Poland. >> Most likely a custom rule some mail admin has created. >> >> What I would suggest is contacting the postmaster or responsible person >> at this receiving site to find out what "deferred by rule #CR-IN-DEF-2" >> means and how you can avoid triggering it. > > Actually they have quite restrictive incoming mail policy this is > Single ip can send up to 300 mails / hour > Single sender can send up to 200 mails/hour (FROM) > Single recipient can recive up to 100 mails/hour (TO) > > Now that i know what is happening i will have to somehow setup a delivery > route that will not exceed those limits. > Any hints on this would be welcome.
from http://www.postfix.org/QSHAPE_README.html#backlog In master.cf set up a dedicated clone of the "smtp" transport for the problem destination. In the example below we call it "slow". In main.cf configure a short delay between deliveries to the same destination. /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/transport slow_destination_rate_delay = 1 slow_destination_concurrency_failed_cohort_limit = 100 /etc/postfix/transport: example.com slow: /etc/postfix/master.cf: # service type private unpriv chroot wakeup maxproc command slow unix - - n - - smtp See also the documentation for default_destination_rate_delay. http://www.postfix.org/postconf.5.html#default_destination_rate_delay -- Noel Jones
