Is it possible to change the retransmission time to the second max? El mié., 5 de ago. de 2020 a la(s) 10:41, SysAdmin EM (emaw...@gmail.com) escribió:
> Viktor, > > My problem is that I cannot deliver the mail because the greylist does not > allow it and in some cases I also receive the same error in the other MXs. > > # Example > > Jul 31 09:30:08 smarthost03-ded postfix/smtp[22475]: A88B418003D5B: > to=<ism...@ilaviola.com.ar>, relay=mx7.webfaction.com[185.20.49.162]:25, > delay=969, delays=962/0.01/6.8/0.34, dsn=4.2.0, status=deferred (host > mx7.webfaction.com[185.20.49.162] said: 450 4.2.0 > <ism...@ilaviola.com.ar>: Recipient address rejected: Greylisted for 300 > seconds (in reply to RCPT TO command)) > Jul 31 09:31:04 smarthost03-ded postfix/smtp[22767]: A88B418003D5B: host > mx9.webfaction.com[185.20.49.164] said: 450 4.2.0 > <ism...@ilaviola.com.ar>: Recipient address rejected: Greylisted for 300 > seconds (in reply to RCPT TO command) > > I am use PowerMTA and depending on the message I receive, I can perform an > action such as hold the queue waiting for a certain time and not in postfix. > > I understand that postfix retries on all MXs in the domain, can I > configure the retry time towards the second MX? I did not find it in the > documentation http://www.postfix.org/qmgr.8.html > > Can i automatically send the queue into hold when i get a greylist error? > > Regards, > > > > El mar., 4 de ago. de 2020 a la(s) 19:51, Viktor Dukhovni ( > postfix-us...@dukhovni.org) escribió: > >> On Tue, Aug 04, 2020 at 05:47:35PM -0300, SysAdmin EM wrote: >> >> > > If you do believe there's actually a problem, i.e. something actually >> > > goes wrong as a result of trying to delivery 4XX failures on a second >> MX >> > > host, please explain what it is that does not work the way it should. >> > >> > I think I understood what I need, is it possible to send an email defer >> > when I receive a greylist error? I thought that with the command >> > "queue_run_delay" I could solve this but not. >> >> No queue_run_delay has nothing to do with whether a second MX host is >> tried when the first responds with a 4XX error. It just controls how >> often qmgr(8) scans the deferred queue. >> >> Since you've not (yet?) explained what problem you're trying to solve, >> I'm not (yet) prepared to offer a (half-baked) solution. >> >> -- >> VIktor. >> >
