I have put a lot of time into this, and think I have as done as much
as I can do to rule out this being on my end. Something is happening
in ASSP, or the perl modules that handle SSL/TLS.
If port 25 on the far end MTA that ASSP will talk to offers STARTTLS,
ASSP will try to make a secure crypto connection to that far end MTA.
This feature only works some of the times. The dominant log line is:
SSL negotiation with MTA failed - problem with MTA's SSL configuration?
I have worked a little with J.R. and could not come an a solution. My
tests include sending emails, telnet, opensssl client.
I have tried ASSP version .3 to .5, and have downgraded each perl
module that is related to this issue. I have updated to each new
update of the perl module, and then tested. I then updated ASSP to
the next release, and repeat that process. All in all, I have
probably tested a good 50 different combinations.
Here are snips of the debug logs from an email that works, and one
that does not work. There may be a little overlap of other emails, I
had a hard time seeing where a transction began, and where it ended.
* Why do the date format differ on some lines?
I think around line 60 in the files, there are some clear differences;
one sends capabilities, the other omits them. There is an awful lot
of back and forth communication, which I am not entirely sure I
understand, but it is all in there.
I am more than happy to allow access to the web admin, and anyone can
point an MX at this and I will set it up.
Scott * If you contact me off list replace talklists@ with scott@ *