Re: [exim] SMTP timeouts

On Mon, Mar 14, 2022 at 06:59:44AM +, Mike Tubby via Exim-users wrote: > On 13/03/2022 22:30, Evgeniy Berdnikov via Exim-users wrote: > > On Sun, Mar 13, 2022 at 08:06:45PM +, Mike Tubby via Exim-users wrote: > > > 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com > > >

Re: [exim] SMTP timeouts

On 13/03/2022 22:30, Evgeniy Berdnikov via Exim-users wrote: On Sun, Mar 13, 2022 at 08:06:45PM +, Mike Tubby via Exim-users wrote: 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909 bytes written):

Re: [exim] SMTP timeouts

On 13/03/2022 20:33, Jeremy Harris via Exim-users wrote: On 13/03/2022 20:06, Mike Tubby via Exim-users wrote: 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909 bytes written): Connection timed out

Re: [exim] SMTP timeouts

On Sun, Mar 13, 2022 at 08:06:45PM +, Mike Tubby via Exim-users wrote: > 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com > [2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909 > bytes written): Connection timed out Looks like broken Path MTU discovery

Re: [exim] SMTP timeouts

On 13/03/2022 20:06, Mike Tubby via Exim-users wrote: 2022-03-13 19:47:53 1nTTGO-0001Jw-Tr H=alt2.gmail-smtp-in.l.google.com [2a00:1450:4025:c03::1a]: SMTP timeout after sending data block (476909 bytes written): Connection timed out Google doesn't want to talk to you, at least on that IP.

[exim] SMTP timeouts

I have started seeing odd timeouts from Exim when talking to Goolge gmail, email path:     MTA (Thunderbird/Win 10) --> mail.tubby.org (Linux/Exim) --> relay1.thorcom.net (Linux/Exim) --> Gmail My MTA is behind my firewall, it sends SMTP to my public mail server, which relays (smart host)

Re: [exim] smtp timeouts sending to google servers

On 04/02/2021 12:00, exim-users-requ...@exim.org wrote: 1) Is there any contact point within Google that I can use to try to get me unblocked? 2) Is there anything I can do to improve my reputation with Google? I am working through their bulk email sender guidelines? 3) Until I fix the underly

Re: [exim] smtp timeouts sending to google servers

On 03/02/2021 15:40, Jeremy Harris via Exim-users wrote: On 03/02/2021 15:12, Gary Stainburn via Exim-users wrote: 1) Is there any contact point within Google that I can use to try to get me unblocked? 2) Is there anything I can do to improve my reputation with Google? I am working through thei

Re: [exim] smtp timeouts sending to google servers

On 03/02/2021 16:01, Evgeniy Berdnikov via Exim-users wrote: On Wed, Feb 03, 2021 at 03:12:32PM +, Gary Stainburn via Exim-users wrote: 3) Until I fix the underlying problems, is it possible to route all emails destined to google servers through another of my Exim boxes? Yes, look for des

Re: [exim] smtp timeouts sending to google servers

On 03/02/2021 18:58, Bill Cole via Exim-users wrote: On 3 Feb 2021, at 10:12, Gary Stainburn via Exim-users wrote: I am experiencing problems when trying to deliver to Google's email servers. My emails are timing out while trying to send. The first thing to check before trying to persuade G

Re: [exim] smtp timeouts sending to google servers

On 3 Feb 2021, at 10:12, Gary Stainburn via Exim-users wrote: I am experiencing problems when trying to deliver to Google's email servers. My emails are timing out while trying to send.  The first thing to check before trying to persuade Google to change is to make sure you are NOT using an

Re: [exim] smtp timeouts sending to google servers

You should be able to contact them from here As far as I know they don't reply to you; they just to their checks, and eventually do a mitigation after a few days/weeks. Il 03/02/21 16:12, Gary Stainburn via Exim

Re: [exim] smtp timeouts sending to google servers

On Wed, Feb 03, 2021 at 03:12:32PM +, Gary Stainburn via Exim-users wrote: > 3) Until I fix the underlying problems, is it possible to route all emails > destined to google servers through another of my Exim boxes? Yes, look for description of "manualroute" router in Exim's documentation. --

Re: [exim] smtp timeouts sending to google servers

On 03/02/2021 15:12, Gary Stainburn via Exim-users wrote: 1) Is there any contact point within Google that I can use to try to get me unblocked? 2) Is there anything I can do to improve my reputation with Google? I am working through their bulk email sender guidelines? 3) Until I fix the underl

[exim] smtp timeouts sending to google servers

I am experiencing problems when trying to deliver to Google's email servers. My emails are timing out while trying to send.  The emails retry, but I'm seeing delivers times of 10+ hours for some emails. I suspect that Google are doing this on purpose to throttle the number of emails I'm sendi

Re: [exim] SMTP Timeouts

Ruairi Hickey wrote: > Hi, > > I am having problems receiving email from a particular client, > the connection looks to set up correctly > > SNIP > > 22066 ident connection to 212.36.164.100 failed: Connection refused This is the problem. I have already had this with stupid dyn

[exim] SMTP Timeouts

Hi, I am having problems receiving email from a particular client, the connection looks to set up correctly 22032 child 22041 ended: status=0x0 22032 0 SMTP accept processes now running 22032 Listening... 22032 Connection request from 212.36.164.100 port 9017 22032 search_tidyu

Re: [exim] smtp timeouts / what to look for

Hello, 2008/3/14, Peter Bowyer <[EMAIL PROTECTED]>: > On 14/03/2008, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: > > Thank you all very much. It seems that *open*transit company is > > blocking whole TP IP address range and the block is complete as I was > > unable to even access their website.

Re: [exim] smtp timeouts / what to look for

On 14/03/2008, Zbigniew Szalbot <[EMAIL PROTECTED]> wrote: > Thank you all very much. It seems that *open*transit company is > blocking whole TP IP address range and the block is complete as I was > unable to even access their website. opentransit.net is France Telecom's international transit and

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: > > Thank you all very much. It seems that *open*transit company is > blocking whole TP IP address range and the block is complete as I was > unable to even access their website. > I am also unable to even access their website. I tried from USA, Germany and 2 networks

Re: [exim] smtp timeouts / what to look for

Hi, 2008/3/14, Renaud Allard <[EMAIL PROTECTED]>: > > > Zbigniew Szalbot wrote: > >> > >> The "!A" means Administrative Prohibition; more precisely, ICMP 3, > >> "Destination Unreachable", Code 11, "Destination Network Unreachable for > >> Type of Service". > >> > >> Either regular trace

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: >> >> The "!A" means Administrative Prohibition; more precisely, ICMP 3, >> "Destination Unreachable", Code 11, "Destination Network Unreachable for >> Type of Service". >> >> Either regular traceroute was used, or tcptraceroute on a port which >> isn't open on a firew

Re: [exim] smtp timeouts / what to look for

On Fri, 14 Mar 2008 10:21:23 +0100, "Zbigniew Szalbot" <[EMAIL PROTECTED]> wrote: >10 so-3-0-0-0.dalcr2.Dallas.opentransit.net (193.251.241.18) 157.308 >ms !A 157.348 ms !A 156.995 ms !A Administratively prohibited. Right in the middle of some ISP's backbones: >10 so-4-0-0-0.dalcr2.Dallas.op

Re: [exim] smtp timeouts / what to look for

Hi there, 2008/3/14, Phil Pennock <[EMAIL PROTECTED]>: > On 2008-03-14 at 10:44 +0100, Renaud Allard wrote: > > > Zbigniew Szalbot wrote: > > > 9 pos0-0-2-0.daltr1.Dallas.opentransit.net (193.251.241.17) 158.566 > > > ms 158.634 ms 158.842 ms > > > 10 so-3-0-0-0.dalcr2.Dallas.opentransit.

Re: [exim] smtp timeouts / what to look for

On 2008-03-14 at 10:44 +0100, Renaud Allard wrote: > Zbigniew Szalbot wrote: > > 9 pos0-0-2-0.daltr1.Dallas.opentransit.net (193.251.241.17) 158.566 > > ms 158.634 ms 158.842 ms > > 10 so-3-0-0-0.dalcr2.Dallas.opentransit.net (193.251.241.18) 157.308 > > ms !A 157.348 ms !A 156.995 ms !A >

Re: [exim] smtp timeouts / what to look for

Hello again, 2008/3/14, Renaud Allard <[EMAIL PROTECTED]>: > > > Zbigniew Szalbot wrote: > > > > > I have eventually connected my box straight to the modem and: > > 1/ I am still getting timeouts to Yahoo (though they claim not to block us) > > 2/ I can at least use (tcp)traceroute and here a

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: > > I have eventually connected my box straight to the modem and: > 1/ I am still getting timeouts to Yahoo (though they claim not to block us) > 2/ I can at least use (tcp)traceroute and here are some logs. Can you > help me interpret them? Am I right in thinking that t

Re: [exim] smtp timeouts / what to look for

Hello again, 2008/3/13, Renaud Allard <[EMAIL PROTECTED]>: > > > Zbigniew Szalbot wrote: > > > > > I do seem to be having some basic problem with (tcp)traceroute: > > > > tcptraceroute 209.191.118.103 25 > > Selected device fxp0, address 192.168.16.4, port 56180 for outgoing packets > > Tra

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: > > I do seem to be having some basic problem with (tcp)traceroute: > > tcptraceroute 209.191.118.103 25 > Selected device fxp0, address 192.168.16.4, port 56180 for outgoing packets > Tracing the path to 209.191.118.103 on TCP port 25, 30 hops max SNIP > > tcptracerou

Re: [exim] smtp timeouts / what to look for

Hello, 2008/3/13, Renaud Allard <[EMAIL PROTECTED]>: > > > Zbigniew Szalbot wrote: > > >> > >> Can you try to make a tcptraceroute on port 25 for the IPs of the yahoo > >> MXes, it may give you a hint on where you are blocked. > > > > The issue is that no traceroute ever completes successfu

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: >> >> Can you try to make a tcptraceroute on port 25 for the IPs of the yahoo >> MXes, it may give you a hint on where you are blocked. > > The issue is that no traceroute ever completes successfully: > > traceroute 209.191.118.103 > traceroute to 209.191.118.103 (209.

Re: [exim] smtp timeouts / what to look for

Hi there, 2008/3/13, Renaud Allard <[EMAIL PROTECTED]>: > > > Zbigniew Szalbot wrote: > > Dear all, > > > > I have been getting smtp timeouts from certain domains (mostly Yahoo) > > and I at first I thought I had been blocked as mail to 90% of other > > domains is flowing well (gmail, aol, y

Re: [exim] smtp timeouts / what to look for

Zbigniew Szalbot wrote: > Dear all, > > I have been getting smtp timeouts from certain domains (mostly Yahoo) > and I at first I thought I had been blocked as mail to 90% of other > domains is flowing well (gmail, aol, you name it). It took a lot of > time to communicate with Yahoo but they have

[exim] smtp timeouts / what to look for

Dear all, I have been getting smtp timeouts from certain domains (mostly Yahoo) and I at first I thought I had been blocked as mail to 90% of other domains is flowing well (gmail, aol, you name it). It took a lot of time to communicate with Yahoo but they have eventually replied stating that they

Re: [exim] SMTP timeouts and retry database

Hi. On Wed, 19 Apr 2006 15:14:35 +0100 (BST), Philip Hazel wrote: > But if you are using 4.43, it should be fixed... I can not reliably reproduce this, it seems. I'll have to watch my mailqueues some more. Thanks. -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim

Re: [exim] SMTP timeouts and retry database

On Wed, 19 Apr 2006, Ralf Ertzinger wrote: > http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20040830/msg00135.html > > The exim version is the default RHEL4 version, so it's a little oldish > (based on 4.43). > > Has this bug been fixed in a more recent version? Looking through the > c

[exim] SMTP timeouts and retry database

Hi all. I have a problem regarding TCP timeouts on outgoing SMTP connections and the retry database. Looking around revealed this message from this list back in 2004 which describes the exact problem I am seeing: http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20040830/msg00135.html The