Somehow as a follow-up on this discussion, I notice that today Yahoo! started to 451 messages destined to their servers deffering them for some time.
2006-10-26 12:47:31 1Gd2Mh-000I76-Gz SMTP error from remote mail server after end of data: host mx1.mail.yahoo.com [67.28.113.73]: 451 Message temporarily deferred - [190] 2006-10-26 12:47:33 1Gd2Mh-000I76-Gz SMTP error from remote mail server after end of data: host mx1.mail.yahoo.com [4.79.181.14]: 451 Message temporarily deferred - [190] 2006-10-26 12:47:34 1Gd2Mh-000I76-Gz SMTP error from remote mail server after end of data: host mx1.mail.yahoo.com [67.28.113.19]: 451 Message temporarily deferred - [190] 2006-10-26 12:47:35 1Gd2Mh-000I76-Gz SMTP error from remote mail server after end of data: host mx3.mail.yahoo.com [67.28.113.71]: 451 Message temporarily deferred - [190] 2006-10-26 12:47:37 1Gd2Mh-000I76-Gz SMTP error from remote mail server after end of data: host mx3.mail.yahoo.com [4.79.181.134]: 451 Message temporarily deferred - [190] 2006-10-26 12:47:38 1Gd2Mh-000I76-Gz == [EMAIL PROTECTED] R=dnslookup T=remote_smtp defer (-46): SMTP error from remote mail server after end of data: host mta-v1.mail.vip.re3.yahoo.com [66.196.97.250]: 451 Message temporarily deferred What I am interested in is knowing why woud exim retry the same message every few seconds? Then it tries the next one, and so on. I thought it would try once, got the deferred status and wait a bit before trying again? I run exim with qq15m option. Thanks for your suggestions! Zbyszek On Sun, 22 Oct 2006, Peter Bowyer wrote: > On 21/10/06, Jörg Sommer <[EMAIL PROTECTED]> wrote: >> Hi, >> >> on a private mailing list, someone raised the claim Exim has a bad queue >> handling and relies on delivering the mail in the first attempt. The >> discussion was about greylisting and "using" the queue of the remote site. > > Is there a more detailed explanation of that problem? > > Philip often states that Exim's delivery model was designed for an > always-connected situation where most of the mail is deliverable on > the first attempt. There was certainly no concept of business-as-usual > deliberate deferral (of which greylisting is an example) around then. > > It's not trivial to tune Exim's retry mechanism to optimize delivery > under greylisting I guess. > >> Speaking accross the board, is it true that Exim has bad (it need more >> resources) queue handling? For Exim on the sender site, is greylisting a >> problem? > > Resources in what sense? > > Peter > > -- > Peter Bowyer > Email: [EMAIL PROTECTED] > > -- > ## List details at http://www.exim.org/mailman/listinfo/exim-users > ## Exim details at http://www.exim.org/ > ## Please use the Wiki with this list - http://www.exim.org/eximwiki/ > -- Zbigniew Szalbot -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
