From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.1) Gecko/20010607 BuildID: 2001060703 Reproducible: Always Steps to Reproduce: 1. Open Mail Client 2. Edit/ Mail/News Account Settings/ Outgoing Settings (SMTP) / Use secure connections (SSL) 3. Check "Use secure connections" to "Always". 4. Try to connect to server, where SSMTP mapped to port other than 25. 5. An error occured sending mail :-( When I try setup in Accaunt settings SMTP over SSL (Edit/ Mail/News Account Settings/ Outgoing Settings (SMTP) / Use secure connections (SSL)), then I cannot connect to my server, because it was setup to use a port number 465, like it described in my /etc/services. But Mozilla can use only port number 25, and impossible to change this. I think this is wrong. Moreover, I can setup port for IMAP over SSL automatically, but I cant do it for SMTP. Please help me! Good luck.

This appears to be fixed in one of the recent nightly builds. What build are you using? Marking this a duplicate of bug# 85304. *** This bug has been marked as a duplicate of 85304 ***

Reopening, my mistake. I thought it was about the recent Send problem using SSL but this bug addresses the need to change the SMTP port number.

PSM

This feature was not available in Nav. 4.X, and is not available in Eudora either.

Just to point out. When admins are setting up UNIX/Linux-based mail servers, a whole lot of the documentation out that tells you to put SSL-based SMTP on the reserved ssmtp port. Not allowing a user to access that port from Mozilla would seem to me to be a bug regardless of what other software fails to allow for it, no?

*** Bug 86805 has been marked as a duplicate of this bug. ***

*** Bug 87176 has been marked as a duplicate of this bug. ***

target 2.1 P2

to mailnews. The ability to let the user select which port to use when using smtp over ssl is not a psm issue.

SMTP -> Ninoschka

adding nsenterprise+

changing summary to reflect the real goal. SMTP over SSL works. You can't specify a custom port.

In Nav 4.x we got around this by putting an entry of the following form in the "Outgoing mail (SMPT) server:" option box. mail.server.com:898 However, I agree that an option box (default filled with the proper SSMTP entry) would be an excellent option.

the work for this will happen during .9.5 but it may land on the eMojo branch. Leaving nsEnterprise+ keyword alone.

Added bug 98372 to report recent nightly breakage of the smtp-server:smtps-port workaround (which I was relying on). Not really a duplicate of this bug, but I thought the note would be useful. Not really a blocker or dependancy, though.

nsenterpise-; not a stopper

Also nice to have this for cases like port-forwarding mail through SSH (when I work from home, for example).

triaging.

With 0.9.5 and 2001-10-12-21-trunk on linux, I cannot use any custom port with non-SSL connection. It worked well on 0.9.4.

moving to 0.9.7

Eudora is actually capable of using custom port settings - it's just not very user friendly... http://www.eudora.com/techsupport/kb/1501hq.html

With 0.9.5 and 2001102309-trunk on Windows NT 4, I cannot use any custom port with non-SSL connection. It worked well on 0.9.4.

This seems to have a fix in bug 106631

this is a dup of 106631 which does have a patch, so I'm going to mark this one as the dup. *** This bug has been marked as a duplicate of 106631 ***

Verified Duplicate.