On 5/4/2010 2:51 PM, Nataraj wrote:
Charles Gregory wrote:
On Tue, 4 May 2010, Nataraj wrote:
Enclosed is a tcpdump of a telnet connection where nothing was typed,
i.e. I telnetted to the smtp server and 5 seconds later the server
closed the connection.
THIS IS NORMAL. As I said previously, type the MAIL FROM, RCPT TO, and
DATA commands, send a couple of ilnes, THEN wait and time the timeout.
How about those logs showing a complete mail 'life cycle'?
- C
I have attached tcpdump-with-commands.txt where I pasted with the mouse
helo mymail.com
mail from:<m...@mymail.com>
I then waited and it still timed out in 5 seconds.
I think the timeout should be whatever the smtpd_timout parameter is set
to (300s in my case), unless the stress code is enabled and operating,
in which case it should be set to the stress config timeout parameter).
5 seconds is not a normal timeout for my configuration. I am enclosing a
tcpdump of a telnet session to the mail server which serves this mailing
list (I hope it's not considered abusive to use it as a reference:-)),
which times out after 21 seconds (probably because it is configured that
way). 5 seconds is just too short, and it should change based on my
configuration, which it is not doing.
As I've mentioned, I can't type fast enough to my server to prevent
timeouts, but if I reenable pipelining, I can paste smtp commands and
submit messages, only if I paste them all at once (and pipelining is
enabled).
Also, please don't loose sight of the fact that all of my timeouts are
screwed up, i.e. inbound smtp, outbound smtp as well as transport and
policy. Maybe this is not a postfix problem, or postfix is having some
strange interaction with something going on in the OS (or a vmware
clocking problem or something).
Nataraj
You can try setting smtpd_timeout and smtp_connect_timeout to
riduclously high values (maybe 3000s for testing) to see if it
makes any difference. If it doesn't change anything, then
this problem is outside postfix somewhere and you'll need to
examine other parts of your system.
I suppose this could be some sort of a clock issue, but I've
never heard of one this extreme. Still, the problem and
solution would both be outside postfix.
-- Noel Jones
