Author: Rick Ennis Date: To: Exim-users, Nico Erfurth Subject: Re: [Exim] more 4.11 problems :-/
> 2002-12-12 20:01:10 SMTP call from another.host [111.222.111.222] > dropped: too many nonmail commands
> Due to a line-problem at my provider today he spooled some mails for me.
Are you using TLS between your server and your backup? In the case of
multiple messages going down the same TLS connection, is exim still shutting
down TLS and reinitializing it for each message? Each STARTTLS command
counts as a non-mail command. So that might be the bug. I can't search the
archives at the moment (web server error) but I found this in my mailbox...
On Wed, 24 Apr 2002, Philip Hazel wrote: > Exim isn't designed to handle this gracefully. I didn't know about TLS
> back in 1995. When Exim has sent a message to a host and notices that it
> has another message for the same host that failed previously, it starts
> a new delivery process in order to deliver the second message, passing
> it the connected TCP/IP socket.[*] However, because it re-executes Exim, it > cannot pass on all the state needed for TLS. Therefore, it calls the
> appropriate OpenSSL function that closes down encryption beforehand. > In the new process, it will try to start up a new TLS session. If both
> ends of the connection are running Exim, this works. For other servers,
> it doesn't. I don't know if it is "permitted" - I don't think the RFC
> about STARTTLS says anything one way or another. However, OpenSSL does
> support it if you call it in the appropriate manner.
--
Rick Ennis
----- Original Message -----
From: "Nico Erfurth" <masta@???>
To: "Exim-users" <Exim-users@???>
Sent: Thursday, December 12, 2002 2:10 PM
Subject: [Exim] more 4.11 problems :-/
> Yesterday I installed exim 4.11, first we had the lookup-problem
> (nis/dbm (most probably ldap will be affected too)).
>
> Now I have this in my logs:
>
> 2002-12-12 20:01:10 SMTP call from another.host [111.222.111.222]
> dropped: too many nonmail commands
>
> another.host is a server of a friend of mine, running as backup-mx for
> some of my domains, the server runs exim 4.10.
>
> Due to a line-problem at my provider today he spooled some mails for me.
> When the line came back, and another.host tried to deliver, the above
> errors occured in the log, (counted 8 of these so far).
>
> Exim 4.11 is really a DON'T USE at the moment :-/