Re: timeout after DATA + lost connection after DATA | Jeroen Geilman | 6/17/10 9:57 AM | > I have a problem with receiving mail from yandex (large mail service). > > May 21 13:30:09 mx postfix/smtpd[77115]: timeout after DATA (47440 > bytes) from forward11.mail.yandex.net[95.108.130.93] > May 21 13:31:56 mx postfix/smtpd[76924]: lost connection after DATA > (33439 bytes) from forward3.mail.yandex.net[77.88.46.8] > May 21 13:32:39 mx postfix/smtpd[77207]: lost connection after DATA > (75160 bytes) from forward14.mail.yandex.net[95.108.130.92] > > I have no problem with receiving mail from other servers. > I have no problem when sending mail to any servers including yandex. > At different location I have another postfix mail server that > receiving mail from yandex. > > I tried to decrease MTU size to 1000. Also I tried switch to other > ISP. With no result in both cases. > Did you try... oh, I dunno, *asking* yandex ?
|
Re: timeout after DATA + lost connection after DATA | Alexander Moisseev | 6/17/10 11:07 AM | > Did you try... oh, I dunno, *asking* yandex ? Yes, I did. |
Re: timeout after DATA + lost connection after DATA | Wietse Venema | 6/17/10 12:25 PM | Alexander Moisseev: [ Charset KOI8-R unsupported, converting... ] > Postfix 2.7.0, FreeBSD 7.1-RELEASE > > Attached tcpdump files: > ts-dump.cap - from my postfix server > ya-dump.cap - from one of the yandex servers Here is a fragment from the second file. 05:01:10.500421 81.25.172.91.25 > 95.108.130.119.52679: . ack 30840 win 64400 (DF) At 05:01:10.500421 the client at 95.108.130.119 receives an ack This is typical for the remainder of the session. Each time the Your machine is announcing a large TCP window, but I suspect that The workaround then is don't announce a huge TCP window size. # postconf -e master_service_disable=inet If you run an older Postfix, you will have to tweak your Wietse |
Re: timeout after DATA + lost connection after DATA | tbro...@gmail.com | 4/6/14 9:55 AM | Just wanted to say thanks. although this is an old post it was still helpful in solving the same problem for latest build.
|