Gus Wirth wrote: > Todd Walton wrote: >> On Fri, May 16, 2008 at 2:44 PM, Gregory K. Ruiz-Ade >> <[EMAIL PROTECTED]> wrote: >>> All my mail goes exclusively through Gmail. I even use their SMTP >>> services >>> to send my mail. I primarily do it all via IMAP, but on occasion use >>> the web >>> interface, and it all seems to work well enough. >> >> How does that work? What would I do to my email setup to funnel it >> all through Gmail? > > Set everything to go to smtp.gmail.com on port 25. However, most ISP's > block port 25 except to their own servers...
Hmmm, I didn't know that. Roadrunner doesn't. I wonder what proportion of ISPs block outgoing smtp? > So try port 587 with SSL > encryption instead. See > <http://mail.google.com/support/bin/answer.py?answer=86401#> Double-hmmm, port 587 is said to be the "preferred port" (at least on paper, at least as interpreted at http://www.pcmag.com/article2/0,2704,1838667,00.asp And so a couple of other google-hits seem to confirm the above, as well as the concept that 25 is (supposed to be) reserved for submission (only) by "local" clients. I wonder what the general stats are on availability of 587. Also I suppose the intention of 25/587 use would explain why ISPs might filter outgoing port 25 -- otherwise, I would wonder why ISPs filter anything outgoing anyway? - - - Some experimenting shows that both 25 and 587 works fine for a web-hosting service I have. I just might consider sending all my outgoing mail there because they support TLS and roadrunner doesn't seem to. Maybe I should consider dumping my rr email address altogether; then I'd be using TLS both directions. Hmmm, that might also be good preparation for switching ISP. Regards, ..jim (hmmm-ing a lot!) -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
