Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: crazybob on March 21, 2006, 04:14:56 PM
-
Not sure if this is a bug, or I don't have something set properly.
There are a number of remote users that receive and send email through my server, and this worked fine woth SME 6.01. I built a new server using 7rc1. I have configured the remote OE clients for ssl connection on pop3, and they can receive email fine, but can not send. I have set them to use port 2525 as their ISP's block port 25, aid I did a port forward on my server (and this used to work on the old server)
I have tried turnning off ssmtp, changing all possible settings in OE for smtp, and I continue to receive failure notices in OE. Either unexpected terminitation, or 550 invalid recipient.
Any thoughts or suggestions
Bob
-
Hello.
Secure SMTP uses port 465.
I don't use port forwarding so I cannot comment if you can fiddle with this port setting. I would try port 465 on your remote users as this encrypts it all, including login, from the outside. Once you establish that works, you can proceed to see if you can change the port.
I use Secure SMTP through a Juniper firewall to the SME and it works like a charrm.
I really don't know if you can change the port for your purposes? I also am not clear why you need to change it from 465 as it is encrypted?
regards,
patrick
-
idyll,
Thanks, I will give it a try. I was running SME 6.01 before, and I needed to have users use a different port because their isp's were blocking port 25. If this works, you are golden. I assume you are setting the ssl tick in advanced settings, and changing the port to 465.
Thanks
Bob
-
I assume you mean changing the port on the email client? Or what do you mean?
On the server it just works once you select the option since that is a standard port assignment for secure SMTP. The same is true (as it is an established port) for the client side. Select SSL for the "SMTP" option on whatever mail client you use and yes, it will work.
Or maybe I need to change that assertion - standards supporting email clients will use this port assignment. I use Thunderbird on Linux, Windows and OS-X, and they all work. I cannot speak for any other clients but I am sure most work as you would expect.
regards,
patrick
-
patrick,
yea, I was refering to the port on the client. Pardon me for not being clearer, it has been a rough few days with the server crashing and trying to get every thing fired back up. I do really appreciate the info. sorry if I appear a little thick.
Thanks again
Bob
ps. It worked Thanks much
Bob