 |
| Prev-20 | Home | Next-20 |
| Prev-20 | Home | Next-20 |
| Prev-Msg | Prev-Thread | Postfix-users | May-2008 | Next-Thread | Next-Msg |
| Subject: | Re: mailq lockups |
| Group: | Postfix-users |
| From: | Victor Duchovni |
| Date: | 6 May 2008 |
> OK first let me clarify that I am not saying postfix is to blame, I think it's exchange, but that???s not the point.
> I am looking to understand/learn what is going wrong and see how on the postfix side I can figure out whats going on.
> This is happening from 3 postfix servers, and happening to several clients, me being the common factor.
>
> These two links will show you the connections on the exchange side:
> http://www.web56.net/ebay/retries1.jpg
> http://www.web56.net/ebay/retries2.jpg
This is sadly useless. This would be a good time to report a complete
"postconf -n".
Look at *your* connection table with
# lsof tcp@remoteip:25
for each connection in an "ESTABLISHED" state, and a corresponding "smtp"
process id, find the process start time (ps -o pid,stime,comm -p $pid)
and check whether the process reported any previous deliveries between
the start time and the present. The age of the connection (if not cached)
is measured approximately from the later of the process start time and
the last completed delivery report.
If no long-lived connections exist on the Linux end, find out why Exchange
still believes there are unfinished connections (this is where packet
captures and verbose logging are handy).
> My question is 1st: Why does the postfix timeout not drop the connection
> on the postfix side ( which may or may not drop the exchange side it of
> course has no control of that ) This shows me the connection is active,
> and it's longer then the timeouts in postfix.
We have no evidence for the premise (Postfix keeping idle connections
alive for a long time), so it is to early to comment on the veracity
of the conclusion. Postfix will normally terminate a delivery after 5
hours even if the remote end avoids idle timeouts by gradually receiving
trickles of traffic. When you report connections are 12+ hours old
(not 10 days as before), the evidence is not entirely plausible.
> 3F18D2A08A6* 6389 Sat May 3 09:20:37 hocxpx
> sixo
>
>
> 2nd: with the settings I have is there something additional I should be setting to insure I drop my connection if their connection takes too long?
>
You are jumping to conclusions. First find the real facts of the situation.
> I think these are logical questions to ask and please understand I
> am not fully versed in all of the high level things that happen during
> normal and abnormal email communications. Hence why I am here asking....
The questions are only "logical" if you take major leaps of faith to
accept the ambiguous evidence from the Exchange connection table, and
also accept that the connections are still active on the Postfix side.
It is far more likely that the leaps are unjustified than that Postfix
is actually keeping SMTP connections alive for 12+ hours.
No further progress is possible until you substantiate your conjectures
with detailed research to uncover and report the actual events.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
| Prev-Msg | Prev-Thread | Postfix-users | May-2008 | Next-Thread | Next-Msg |