With EXCESSIVE logging turned on, the SMTP session looks like this -- > 06/09/2011 16:59:09 LOG OUTPUT > EXCESSIVE(middleman()@spamdyke.c:2398): read 10 bytes from network > input file descriptor 0, buffer contains 10 bytes, current position is 0 > > 06/09/2011 16:59:09 FROM REMOTE TO CHILD: 10 bytes > STARTTLS > > 06/09/2011 16:59:09 FROM SPAMDYKE TO REMOTE: 14 bytes > 220 Proceed. > > 06/09/2011 16:59:09 LOG OUTPUT > EXCESSIVE(tls_start()@tls.c:317): setting socket to nonblocking mode: 0 > EXCESSIVE(tls_start()@tls.c:368): TLS operation did not complete, > already waited 0 seconds > EXCESSIVE(tls_start()@tls.c:368): TLS operation did not complete, > already waited 1 seconds > > 06/09/2011 16:59:10 - TLS negotiated and started > > 06/09/2011 16:59:10 LOG OUTPUT TLS > EXCESSIVE(middleman()@spamdyke.c:2398): read 33 bytes from network > input file descriptor 0, buffer contains 33 bytes, current position is 0 > > 06/09/2011 16:59:10 FROM REMOTE TO CHILD: 33 bytes TLS > EHLO mail-out-01.healthways.com > > 06/09/2011 16:59:10 LOG OUTPUT TLS > EXCESSIVE(smtp_filter()@spamdyke.c:1195): EHLO received; going to add > SMTP AUTH > EXCESSIVE(smtp_filter()@spamdyke.c:1209): EHLO received; going to > remove TLS > > 06/09/2011 16:59:10 LOG OUTPUT TLS > EXCESSIVE(middleman()@spamdyke.c:1984): read 48 bytes from child input > file descriptor 7, buffer contains 48 bytes, current position is 0 > > 06/09/2011 16:59:10 FROM CHILD TO REMOTE: 18 bytes TLS > 250-panoptic.com > > 06/09/2011 16:59:10 FROM CHILD TO REMOTE: 16 bytes TLS > 250-PIPELINING > > 06/09/2011 16:59:10 FROM CHILD TO REMOTE: 14 bytes TLS > 250-8BITMIME > > 06/09/2011 16:59:10 FROM SPAMDYKE TO REMOTE: 3 bytes TLS > 250 > 06/09/2011 16:59:10 FROM SPAMDYKE TO REMOTE: 1 bytes TLS > > 06/09/2011 16:59:10 FROM SPAMDYKE TO REMOTE: 27 bytes TLS > AUTH LOGIN PLAIN CRAM-MD5 > > 06/09/2011 17:04:10 LOG OUTPUT TLS > ERROR: unable to read from SSL/TLS stream: The operation failed due to > an I/O error, Unexpected EOF found > EXCESSIVE(middleman()@spamdyke.c:2418): network input file descriptor > 0 indicates EOF, buffer contains 0 bytes, current position is 0 > EXCESSIVE(middleman()@spamdyke.c:2598): child output file descriptor 6 > closed > EXCESSIVE(middleman()@spamdyke.c:2624): child process exited normally > with return value 1 > EXCESSIVE(middleman()@spamdyke.c:1993): child input file descriptor 7 > indicates EOF, buffer contains 0 bytes, current position is 0 > EXCESSIVE(middleman()@spamdyke.c:1994): child input file descriptor 7 > closed > > 06/09/2011 17:04:10 - TLS ended and closed > > 06/09/2011 17:04:10 CLOSED
Assuming we can't ask the remote client to look at their server's logs, I think I have a hypothesis. Looking at Ron's SMTP server, I see he's using the following SSL certificate: depth=0 /O=Qmail Toaster Server/OU=Test Certificate/CN=localhost verify error:num=27:certificate not trustedverify return:1 I suspect that the remote client's MX is configured to NOT send mail if the SSL certificate isn't verifiable/trusted. I also use a self-signed cert. for panoptic.com, and so that would explain why test messages sent to my server also fail in the exact same way. I just installed a GoDaddy SSL certificate - Ron, when you can, could you have another test email sent? On 6/9/11 4:07 PM, Dossy Shiobara wrote: > Just confirmed that the SSL interop problem that Ron's seeing is also > a problem in Spamdyke 4.1.0. > > Going to turn all knobs to 11 and see what's really going on, here ... -- Dossy Shiobara | "He realized the fastest way to change [email protected] | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on." (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
