Further to my earlier post, and re-checking the SMTP connectivity (as suggested
by someone off-list).
Connecting to Amavis is OK
telnet 127.0.0.1 10024
Trying 127.0.0.1...
Connected to mx1.domain.com (127.0.0.1).
Escape character is '^]'.
If it arrives there is an extended delay in getting
Alan,
telnet 127.0.0.1 10024
Trying 127.0.0.1...
Connected to mx1.domain.com (127.0.0.1).
Escape character is '^]'.
If it arrives there is an extended delay in getting the 220 from amavis
220 [127.0.0.1] ESMTP amavisd-new service ready
However, most of the time there is no 220 coming from
If it arrives there is an extended delay in getting the 220 from amavis
220 [127.0.0.1] ESMTP amavisd-new service ready
However, most of the time there is no 220 coming from amavis.
maxproc (Postfix) larger then $max_servers ?
I would need to be more precise: if maxproc is the same as
Mark
telnet 127.0.0.1 10024
Trying 127.0.0.1...
Connected to mx1.domain.com (127.0.0.1).
Escape character is '^]'.
If it arrives there is an extended delay in getting the 220 from amavis
220 [127.0.0.1] ESMTP amavisd-new service ready
However, most of the time there is no 220 coming from
Alan Munday wrote the following on 05/05/2006 17:36:
Alan Munday wrote the following on 05/05/2006 15:20:
Mark
telnet 127.0.0.1 10024
Trying 127.0.0.1...
Connected to mx1.domain.com (127.0.0.1).
Escape character is '^]'.
If it arrives there is an extended delay in getting the 220 from amavis
Alan,
and I've just spotted another consistent difference, the FC5 box always
reports:
amavis[7445]: (07445-04) enforcing size limit 10485760 during DATA
Seems you have $smtpd_message_size_limit or @message_size_limit_maps
in your amavisd.conf. Defaults are not to enforce the size limit.
Alan,
Comparing with another system (FC4) which has the same application build
I can see that the FC5 system is never reporting that it sees the EOF
(ESMTP .CRLF). So either the data is never sent or the EOF is never
sent.
tcpdump/ethereal on a loopcback interface would tell.
Mark
I've upgraded a box to fedora 5 today. There were no application upgrades as
the core 4 was running Postfix 2.2.10, Amavisd-new 2.4, Spamassassin 3.1.1.
Things look like they are OK, but the Postfix queue is backing up.
Turning up the log level I can see the following time-out problem:
May
