Hi All,
I manage a local intranet mail server which collects mails from our local users
and sends them all via our public mail hub server.
Everything was fine until few weeks ago. Some small part of our emails (about
10%) hangs
in mail's server queue with error: timeout exceeded (in reply to
Tomasz Iwanowski:
Hi All,
I manage a local intranet mail server which collects mails from our local
users
and sends them all via our public mail hub server.
Everything was fine until few weeks ago. Some small part of our emails (about
10%) hangs
in mail's server queue with error:
On Wed, Jun 15, 2011 at 10:38:44AM -0400, Wietse Venema wrote:
Command:
# tcpdump -s 0 -w /file/name host server-ip-address and port 25
After some time, kill -INT the tcpdump process.
Look in the logfile for a session that breaks, and find that session
in the tcpdump recording.
It's nice for a change to work with someone who provides actual
information, instead of that dork from last week who was just
venting his opinions and not giving people a chance to help.
In this case it looks like a Solaris TCP bug when sending data over
a connection that suffers from heavy
On Thu, 21 Jan 2010 10:30:54 -0500 (EST), wie...@porcupine.org (Wietse
Venema) wrote:
It's nice for a change to work with someone who provides actual
information, instead of that dork from last week who was just
venting his opinions and not giving people a chance to help.
I don't know how one
Zitat von Wietse Venema wie...@porcupine.org:
It's nice for a change to work with someone who provides actual
information, instead of that dork from last week who was just
venting his opinions and not giving people a chance to help.
In this case it looks like a Solaris TCP bug when sending
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error: timeout exceeded (in reply to end of DATA command)
This error only seems to occur with 'large' mails. Currently I have a mail
of ~600KB and
On Wed, 20 Jan 2010 10:56:39 +0100, Martijn de Munnik
mart...@youngguns.nl wrote:
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error: timeout exceeded (in reply to end of DATA command)
On Wed, 20 Jan 2010 11:10:50 +0100, Martijn de Munnik
mart...@youngguns.nl wrote:
On Wed, 20 Jan 2010 10:56:39 +0100, Martijn de Munnik
mart...@youngguns.nl wrote:
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421
On 2010-01-20 Martijn de Munnik wrote:
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error: timeout exceeded (in reply to end of DATA command)
This error only seems to occur with 'large' mails.
Martijn de Munnik:
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error: timeout exceeded (in reply to end of DATA command)
This error only seems to occur with 'large' mails. Currently I
On Wed, 20 Jan 2010 07:20:01 -0500 (EST), wie...@porcupine.org (Wietse
Venema) wrote:
Martijn de Munnik:
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error: timeout exceeded (in reply to
Martijn de Munnik:
On Wed, 20 Jan 2010 07:20:01 -0500 (EST), wie...@porcupine.org (Wietse
Venema) wrote:
Martijn de Munnik:
Hi list,
I have a problem with delivering mail to a host and get this error:
host mx2.amsterdam.nl[145.222.14.10] said: 421 enepmx02.amsterdam.nl
Error:
Here's the TCP initial handshake:
17:30:44.951789 IP 213.207.90.2.48147 145.222.14.10.25: S
50514820:50514820(0) win 49640 mss 1460,nop,wscale 0,nop,nop,sackOK
17:30:44.954496 IP 145.222.14.10.25 213.207.90.2.48147: S
4148480248:4148480248(0) ack 50514821 win 5840 mss 1380,nop,wscale 2
On Wed, Jan 20, 2010 at 03:22:56PM -0500, Wietse Venema wrote:
The broken router then throws away the bytes with higher sequence
numbers than 14233.
Workaround: turn off window scaling support on the sender's kernel.
This problem is sufficiently common, that on Linux MTAs I always add:
On Jan 20, 2010, at 9:28 PM, Victor Duchovni wrote:
On Wed, Jan 20, 2010 at 03:22:56PM -0500, Wietse Venema wrote:
The broken router then throws away the bytes with higher sequence
numbers than 14233.
Workaround: turn off window scaling support on the sender's kernel.
This problem is
Martijn de Munnik:
On Jan 20, 2010, at 9:28 PM, Victor Duchovni wrote:
On Wed, Jan 20, 2010 at 03:22:56PM -0500, Wietse Venema wrote:
The broken router then throws away the bytes with higher sequence
numbers than 14233.
Workaround: turn off window scaling support on the sender's
Wietse Venema:
You can do
ndd /dev/tcp \?
to find out what parameters are supported. On my Solaris9 and
Solaris10 test boxes it is called tcp_wscale_always.
According to Solaris10 documentation:
When this parameter is enabled, which is the default setting
[since
18 matches
Mail list logo
