Hi,
I caught the log of two of those high-CPU, hung processes. They had
almost the same output. The two ended in "451 Incomplete DATA".
Did a search on that:
SMTP.pm:696: $self->respond(451, "Incomplete DATA");
I looked at "sub respond" code in TcpServer.pm and doesn't seem like a
candidate for retrying the writes...
On the next line a $self->reset_transaction is issued. Can the tls
plugin not be handling that last reset_transaction very well?
So I THINK I've got a way to reproduce the behaviour:
- Connect to server
- Start TLS
- Send data (but don't send last .<CR><LF>)
- Cut client connection
Note that I only did '*' substitutions, I did not blank anything out.
-- LOG --
32125 Accepted connection 52/100 from 194.51.3.49 / bow.rain.fr
32125 Connection from bow.rain.fr [194.51.3.49]
32125 check_earlytalker plugin: remote host said nothing spontaneous,
proceeding
32125 220 ****** ESMTP
32125 dispatching EHLO bow.rain.fr
32125 250-************ Hi bow.rain.fr [194.51.3.49]
32125 250-PIPELINING
32125 250-8BITMIME
32125 250-SIZE 26214400
32125 250-STARTTLS
32125 250-AUTH=PLAIN LOGIN CRAM-MD5
32125 250 AUTH PLAIN LOGIN CRAM-MD5
32125 dispatching STARTTLS
32125 220 Go ahead with TLS
32125 tls plugin: TLS setup returning
32125 dispatching EHLO bow.rain.fr
32125 250-************ Hi bow.rain.fr [194.51.3.49]
32125 250-PIPELINING
32125 250-8BITMIME
32125 250-SIZE 26214400
32125 250-AUTH=PLAIN LOGIN CRAM-MD5
32125 250 AUTH PLAIN LOGIN CRAM-MD5
32125 dispatching MAIL From:<> SIZE=44160
32125 full from_parameter: From:<> SIZE=44160
32125 from email address : [<>]
32125 getting mail from <>
32125 250 <>, sender OK - how exciting to get mail from you!
32125 dispatching RCPT To:<[EMAIL PROTECTED]>
32125 to email address : [<[EMAIL PROTECTED]>]
32125 250 <[EMAIL PROTECTED]>, recipient ok
32125 dispatching DATA
32125 354 go ahead
32125 451 Incomplete DATA
-- END LOG --
Any ideas?
Jose Luis Martinez
CAPSiDE
[EMAIL PROTECTED]
