Re: [exim] retry timeout exceeded

2014-04-09 Thread Dennis Davis
On Wed, 9 Apr 2014, Jasen Betts wrote: > From: Jasen Betts > To: exim-users@exim.org > Newsgroups: gmane.mail.exim.user > Date: Wed, 9 Apr 2014 10:44:37 > Subject: Re: [exim] retry timeout exceeded > > On 2014-04-08, Jeremy McSpadden wrote: > > Jasen, > > > &

Re: [exim] retry timeout exceeded

2014-04-09 Thread Jasen Betts
On 2014-04-08, Jeremy McSpadden wrote: > Jasen, > > Are you using the community edition, or enterprise of baruwa 2? no. -- umop apisdn -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - htt

Re: [exim] retry timeout exceeded

2014-04-08 Thread Jeremy McSpadden
eremy=fluxlabs@exim.org [mailto:exim-users-bounces+jeremy=fluxlabs@exim.org] On Behalf Of Jasen Betts Sent: Tuesday, April 01, 2014 2:21 AM To: exim-users@exim.org Subject: Re: [exim] retry timeout exceeded On 2014-03-31, Jacco van Gent wrote: >> > > I am using Mailscanner togethe

Re: [exim] retry timeout exceeded

2014-04-08 Thread Jasen Betts
On 2014-03-31, Jacco van Gent wrote: >> > > I am using Mailscanner together with Baruwa 2.0, their setup suggest >deferring the message, so that Mailscanner can process it and write >message data to a postgresql database. If I am not mistaken, this is >the same approach Mailscanner suggests on the

Re: [exim] retry timeout exceeded

2014-04-08 Thread Dennis Davis
On Mon, 31 Mar 2014, Jacco van Gent wrote: > From: Jacco van Gent > To: Exim-users > Date: Mon, 31 Mar 2014 07:08:12 > Subject: Re: [exim] retry timeout exceeded ... > I am using Mailscanner together with Baruwa 2.0, their setup > suggest deferring the message, so that Mails

Re: [exim] retry timeout exceeded

2014-04-08 Thread Jacco van Gent
On 2014-03-31 08:05, Jeremy Harris wrote: > On 31/03/14 07:08, Jacco van Gent wrote: > > I am using Mailscanner together with Baruwa 2.0, their setup suggest > > deferring the message, so that Mailscanner can process it and write message > > data to a postgresql database. If I am not mistaken, th

Re: [exim] retry timeout exceeded

2014-03-31 Thread Jeremy Harris
On 31/03/14 07:08, Jacco van Gent wrote: I am using Mailscanner together with Baruwa 2.0, their setup suggest deferring the message, so that Mailscanner can process it and write message data to a postgresql database. If I am not mistaken, this is the same approach Mailscanner suggests on their

Re: [exim] retry timeout exceeded

2014-03-30 Thread Jacco van Gent
On 2014-03-30 17:29, Evgeniy Berdnikov wrote: > On Sun, Mar 30, 2014 at 11:05:08AM +, Jacco van Gent wrote: > > I am using exim (4.82) together with mailscanner. Exim is setup to > > defer messages so that mailscanner can scan the messages. After > > mailscanner has scanned the message and if t

Re: [exim] retry timeout exceeded

2014-03-30 Thread Evgeniy Berdnikov
On Sun, Mar 30, 2014 at 11:05:08AM +, Jacco van Gent wrote: > I am using exim (4.82) together with mailscanner. Exim is setup to > defer messages so that mailscanner can scan the messages. After > mailscanner has scanned the message and if the message passes as > clean, mailscanner calls exim t

[exim] retry timeout exceeded

2014-03-30 Thread Jacco van Gent
Hi, I am using exim (4.82) together with mailscanner. Exim is setup to defer messages so that mailscanner can scan the messages. After mailscanner has scanned the message and if the message passes as clean, mailscanner calls exim to sent the message to the backend smtp server (exchange). N

Re: [exim] retry timeout exceeded with greylisting

2013-03-05 Thread Jeremy Harris
On 03/05/2013 02:12 PM, Frank Elsner wrote: retry timeout exceeded Is it possible that the destination host has been not-accepting for some time? (also, what version Exim?) -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http:/

[exim] retry timeout exceeded with greylisting

2013-03-05 Thread Frank Elsner
Hallo, how can this happen that a message immediatly after "please come back later" gets a timeout as in this case?: 2013-02-21 21:43:28 1U8czG-XP-EG <= sen...@tu-berlin.de H=autodiscover.tu-berlin.de (exchange.tu-berlin.de) [130.149.7.70] P=esmtps X=TLSv1:AES128-SHA:128 S=4033116 id=7760

[exim] Retry timeout exceeded, but why exactly.

2010-01-25 Thread Sander Smeenk
Hi! I see mails fail to deliver with the message "retry time exceeded" but i can't really place why the retry time was exceeded in the first place. I think this has to do with hints databases, but what exactly can be done to prevent it is unclear. Scenario: We have a (mailman) mailinglist with >2

Re: [exim] Retry timeout exceeded - Connection timed out

2007-03-30 Thread David Fernández
d Fernández - Original Message - From: "Peter Bowyer" <[EMAIL PROTECTED]> To: "exim users" Sent: Friday, March 30, 2007 12:41 PM Subject: Re: [exim] Retry timeout exceeded - Connection timed out On 30/03/07, David Fernández <[EMAIL PROTECTED]> wrote:

Re: [exim] Retry timeout exceeded - Connection timed out

2007-03-30 Thread Peter Bowyer
On 30/03/07, David Fernández <[EMAIL PROTECTED]> wrote: > Hi, my first message to the list. > May someone tell me why machine 1 have this strange behaviour? This is a bit of an obvious answer, but is the retry configuration different between the 2 machines? > And (not > related to Exim), did som

[exim] Retry timeout exceeded - Connection timed out

2007-03-30 Thread David Fernández
Hi, my first message to the list. After searching the web for an answer, I write to the list looking for help. I have two machines, Exim 4.63. Message for machine 1 to [EMAIL PROTECTED] 2007-03-29 18:55:59 1HWxnW-0003HD-0d == [EMAIL PROTECTED] R=lookuphost T=remote_smtp defer (110): Connection

Re: [exim] retry timeout exceeded on 450 error

2007-02-27 Thread Alexander Shikoff
On Tue, Feb 27, 2007 at 08:48:58AM +0100, Renaud Allard wrote: > > > Alexander Shikoff wrote: > >Hello, > > > >I've got a strange behavior of exim: > > > >Feb 26 16:27:34 dragon exim[12094]: 2007-02-26 16:27:34 1HLgp2-000394-Tb > ><= [EMAIL PROTECTED] H=(xxx.ua) [212.40.35.6] P=esmtp S=1536458

Re: [exim] retry timeout exceeded on 450 error

2007-02-26 Thread Renaud Allard
Alexander Shikoff wrote: Hello, I've got a strange behavior of exim: Feb 26 16:27:34 dragon exim[12094]: 2007-02-26 16:27:34 1HLgp2-000394-Tb <= [EMAIL PROTECTED] H=(xxx.ua) [212.40.35.6] P=esmtp S=1536458 [EMAIL PROTECTED] Feb 26 16:27:44 dragon exim[12109]: 2007-02-26 16:27:44 1HLgp2-00039

[exim] retry timeout exceeded on 450 error

2007-02-26 Thread Alexander Shikoff
Hello, I've got a strange behavior of exim: Feb 26 16:27:34 dragon exim[12094]: 2007-02-26 16:27:34 1HLgp2-000394-Tb <= [EMAIL PROTECTED] H=(xxx.ua) [212.40.35.6] P=esmtp S=1536458 [EMAIL PROTECTED] Feb 26 16:27:44 dragon exim[12109]: 2007-02-26 16:27:44 1HLgp2-000394-Tb SMTP error from remote

Re: [exim] retry timeout exceeded

2006-04-04 Thread Jason Keltz
On Tue, 4 Apr 2006, Jeremy Harris wrote: Jason Keltz wrote: How can retry timeout be exceeded? Exim replied to the original sender with a message SMTP error from remote mail server after RCPT TO:<[EMAIL PROTECTED]>: host x.x.x [#.#.#.#]: 450 <[EMAIL PROTECTED]>: Recipient address

Re: [exim] retry timeout exceeded

2006-04-04 Thread Jeremy Harris
Jason Keltz wrote: How can retry timeout be exceeded? Exim replied to the original sender with a message SMTP error from remote mail server after RCPT TO:<[EMAIL PROTECTED]>: host x.x.x [#.#.#.#]: 450 <[EMAIL PROTECTED]>: Recipient address rejected: Greylisted: retry timeout exceed

[exim] retry timeout exceeded

2006-04-04 Thread Jason Keltz
Hi. We're running exim 4.52. One of our users sent a message to a site that is configured with greylisting, and I'm not sure that I understand the log details: The message went out: 2006-04-03 15:45:26 1FQUzO-0006Jo-4J <= [EMAIL PROTECTED] H=([8.9.10.11]) [8.9.10.11] P=esmtpsa X=TLSv1:AES25

[exim] retry timeout exceeded - config problem?

2005-06-01 Thread Mike Bacher
Here is my situation. Using exim 4.34 built from freebsd-ports to do antivirus/antispam scanning (via MailScanner) and sending all scanned mail to back-end mailhub via smart_route (manualroute). Anyway, this all works great when the mailhub that the mail is routed to is up and working. Howe