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 recordin
in mail's server queue with error: timeout exceeded (in reply to end of DATA
> command)).
> Some emails stay in queue untill timeout expires (3 days) and returns to a
> sender with error.
> There are emails which stay in queue for a few hours (with the same error)
> but after serv
ostfix ver 2.8.3-1
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
4A9409365 4130 Tue Jun 14 09:59:13 a...@aaa.aaa.aa
(host mailhub.aaa.aaa[NN.NN.N.NN] said: 421 4.4.2 mailhub.aaa.aaa Error: timeout exceeded (in reply to end of
DATA command))
postconf -n
alias_database =
Zitat von Wietse Venema :
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 t
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 on
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 packet
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
> [sinc
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 suppo
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
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:
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
17:30:44.954496 IP 145.222.14.10.25 > 213.207.90.2.48147: S
4148480248:4148480248(0) ack 50514821 win 5840
17:30:44.954519 IP 213.207.90.2.48147 > 145.222.14.10.25: . ac
; 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 ~8MB st
dam.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 ~8MB stuck in the queue. I don't think this is a postfix
>> issue on our site
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
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
.10] said: 421 enepmx02.amsterdam.nl
>> Error: timeout exceeded (in reply to end of DATA command)
I also found a mail in the queue to mx-cluster1.one.com with exactly the
same problem, this mail is also ~600kb.
>>
>> This error only seems to occur with 'large' mails. Curre
On Wed, 20 Jan 2010 10:56:39 +0100, Martijn de Munnik
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 comman
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
18 matches
Mail list logo
