To come back to your problem : this is primarily an imap standards discussion list, not a support list for an implementation. From what you wrote you say that you cannot send mail via port 25; which is the standard port number of a smtp daemon such as sendmail etc. pp. imap listens on 143 and possibly on an ssl port. So the bottom line ist that even if you have sendmail compiled with ssl support I cannot imagine how this would trigger a problem at the imap side. One exception : you are running some sort of smtp authentication like POP-before-SMTP or so. I have no experience with such a setup in connection with a imap server, maybe somebody else has. But if your IMAP server is working well in SSL mode, I would suspect that the cause of your problems doas not lie in the imap server but in another package which tries to talk to it when imap doas not expect it or in the wrong format. We haver the uw imap server running with ssl in multiple places, we run sendmail and postfix on the same servers, also with SMTP authentication (but not POP-before-SMTP) and never have had such a problem.
Hope this helps, Jakob Curdes
Robert Benites wrote:
I've seldom had such an unpleasant experience as I have with you.
You repeated yourself twice, I got your message the first time. To save bandwidth, you didn't need to send it back to the list. But I guess you think I didn't get the message the first time.
I submitted the same problem definition to RedHat and Berkeley sendmail, they said it was imap. You say it's not imap. I guess this is just one of those situations where everyone is pointing fingers.
Mar 5 15:17:31 candler imapd[28491]: SSL error status: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong \ version number
The above message is coming from an imap process, but I guess you'd still say it wasn't imap. Oh well..
-- bb
