Thanks for both your reply and Alexanders.
After disabling the windows firewall (eset smartsecurity) and a restart of both Outlook and qmail, I was able to send mail messages using port 587 with SSL enabled within Outlook (!) So very happy and sending test mail messages for about 5 minutes... that was yesterday..... This morning I tried sending a message again and it stopped working, the same error messages return in outlook... (disabled windows firewall again / restart qmail / outlook etc, no luck this time) Think I will go for your suggestion to use port 465, but it still bugs me that I had this working yesterday... It seems that the page you're referring to describes a copy of the smtp service using port 465 and extra parameter "export SMTPS=1" Isn't it more secure/neccesary to add "export REQUIRE_AUTH=1" ? Thanks again for your help John -----Original Message----- From: Eric Shubert <[email protected]> To: [email protected] Sent: Sat, Feb 20, 2010 4:18 pm Subject: [qmailtoaster] Re: Unable to send mail with Outlook - Submission/SSL [email protected] wrote: > Hi, > > I have just setup qmailtoaster and having some problems with outgoing > > > mail on SSL. > Using Outlook 2003, I am able to setup IMAP-SSL and connect and read my > > e-mail. > (installed the servercert.pem key within /var/qmail/control) > > I can't however send mail using port 587 with SSL enabled. > Outlook returns after some time with "error 0x800CCC7D - SMTP server > > doesn't accept SSL secured connection" > When I remove the SSL switch for outgoing mail in Outlook (still using > port > 587), mail goes out without problems. > > I've read the wiki article "SSL on submission" > > > (http://wiki.qmailtoaster.com/index.php/SSL_on_submission_port) > Has anybody used this 'workaround' on Outlook? (not OE) > > Thanks and regards, > > John Thanks go to Aleksander, but I don't think the page he referenced is going to help you. I don't believe that Outlook'03 can do STARTTLS, it only supports an SSL connection. (FWIW, Outlook'07 does support STARTTLS.) While both methods of encryption use SSL, they are initiated in different ways. I know it can be confusing. Let me try to explain. STARTTLS can use any unencrypted port. It is a method by which the session can change from unencrypted to encrypted on the fly. Traditional SSL, on the other hand, requires a dedicated port, the entire contents of which are encrypted. That's why you see a 2nd port for imap4-ssl, and pop3-ssl. There is (was at one time not so long ago) also an smtp-ssl port (ssmpt 465), but this has been deprecated in favor of STARTTLS. I expect that other SSL ports will also be deprecated in the future as STARTTLS capability becomes more commonplace, but that's just my opinion. I haven't seen the patch to which you refer, but I expect it would work. However, it would also require all clients using that port to use SSL (using STARTTLS on an SSL port would be redundant if it would work, which I expect it might). If you decide to try this, I would use a separate port if it, like 465. ;) After having written all that, I think I found your best solution here: http://wiki.qmailtoaster.com/index.php/SSL :) -- -Eric 'shubes' --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
