RE: [courier-users] ESMTP over SSL (again)

[Bryan Ross]

Thanks Mike,   Outlook works alright with my esmtp server, as long as I tell it not to bother with SSL, so I think it can handle the multi-line greeting alright. Similarly, it can handle the secure connections thru pop3/imap, so I assume there’s not a problem there. I think its got something to do with my esmtp config. Pop3/imap over ssl have their own port, so I think that’s more straight forward.   Thanks for the offer of letting me try it with your server, but I think I would really need someone who has SSL running, just to prove that its my courier-mta config that’s broken.   Kind Regards,   Bryan.   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Michael J. Tubby B.Sc (Hons) G8TIC Sent: 03 February 2002 10:27 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [courier-users] ESMTP over SSL (again)   Bryan,   Is this as simple as Outlook is unable to support correctly formatted multi-line greeting messages in the form       250-line1     250-line2     250-line3     250 last line   NB. no continuation dash on the last line...  Sam's output looks fine to me.  I don't use outlook but you might try pointing it my mail relay which runs exim and also does multi-line output at start up:       bash$ telnet post.thorcom.com 25     Trying 212.172.148.70 (post.thorcom.com) ...     Connected to post.thorcom.com     220-post.thorcom.com ESMTP Exim 3.33 #2 Sun, 03 Feb 2002 10:20:29 +0000     220-Computer Misuse Act (1990) UK applies - Unauthorised access prohibited.     220-Unsolicited Commercial Email (UCE) or SPAM is not permitted here!     220-All connections are logged. Sending of UCE or SPAM via this system     220-constitutes unauthorised use and may result in blacklisting with ISPs     220 and/or criminal proceedings against the originators of such messages.   There's no SSL (STARTTLS not enabled) and its not an open relay but you could see just how early in the session starto Outlook barfs (if I recall there's a 'record a log file' option somewhere).   You should be able to attempt to relay via my box and get the usual "550 we do not relay" unless you're sending me a mail and you're a non- dialup internet connection.     Mike       ----- Original Message ----- From: Bryan Ross To: [EMAIL PROTECTED] Sent: Sunday, February 03, 2002 9:50 AM Subject: [courier-users] ESMTP over SSL (again)   Hi,   Posted this question a while ago, but didn’t get anything back. I know its lame to keep reposting, but hoping that at least one person has got this working. If im being stupid, just say so, and I’ll go away and do (yet more) reading…   Anyway, I’ve got pop3/imap running over SSL, using my thawte certificate, and everything works alright. My problem is with esmtp over ssl. I installed the relevant emstpd.cnf and esmtpd.pem file, using the same settings as I did for the outgoing protocols above. But, I cant seem to get Outlook to play nice with it.   From what I can understand, smtp over ssl is ‘normally’ done over port 465, but here we’re using the STARTTLS extension, so the clients just connects to port 25. If I telnet into port 25, I get the following advertised;   250-AUTH LOGIN 250-AUTH=LOGIN X-NETSCAPE-HAS-BUGS 250-STARTTLS 250-XVERP=Courier 250-XEXDATA 250-XSECURITY=NONE,STARTTLS 250-PIPELINING 250-8BITMIME 250-SIZE 250 DSN   Outlook barfs, telling me that my server reported an internal error, but I cant find anything in the server logs. All I see is the start of a smtp connection. I assume the problem is that Outlook isn’t starting the session properly, and therefore isn’t doing SSL, and hence, isn’t authenticating… but does anyone have any clues as to why? Or even if there’s some tests I can run to get a little bit more debug info.   Oh, and just to confirm, I don’t need a emtpd-ssl config file do I ?   Thanks,   Bryan.