Art Alexion on 2 Jun 2010 05:33:08 -0700 |
On Tue, Jun 1, 2010 at 2:52 PM, JP Vossen <jp@jpsdomain.org> wrote: > I *think*... I did not fully test it, but as of last night/early this > morning, I was unable to connect to my hosted server on port 25. The > server was up and fine, sIMAP & SSH worked fine, and port 25 to that > server worked from elsewhere (Comcast in NJ, among others). Yep, same thing happened to me yesterday morning with FiOS in Glenside. A couple of mails went out, and suddenly, the rest were stuck in the outbox with "authentication" errors. I recalled getting something from google about this so I assumed it was Gmail which was refusing SMTP on 25, as opposed to Verizon blocking the port. Based on the error messages I got, I still think it was Gmail, but it is quite a coincidence if you started getting blocked around the same time and weren't using google apps. > 2) Change all the client configs to use port 587 in the GUI > (workstations) Yep. That fixed it for me. By the way, kmail does a nice job of detecting the port the server wants. -- artAlexion sent unsigned from webmail interface ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|