Hi Rick,

I think you're right--I at least don't disagree with anything you said :) I'm glad my current ISP does not block port 25 anymore. My last two--Cox and SBC--did.

Maybe I am misunderstanding something, but I was just saying that if you're connected to the internet via Cox, you can send any and all mail through the Cox SMTP servers--cox, att, etc (hmm..I wonder if that messes with SPF though). You cannot send mail to any other smtp server via port 25. On the other hand, if you're connected to AT&T (or SBC, etc), you have to specifically request they unblock port 25 if you want to send mail via a different server on port 25. Other ports (pair.com for instance allows port 2525 to their SMTP server), SSL etc should always work.

Scott


On Oct 29, 2008, at 9:37 AM, Rick Glazier wrote:

I admit I have not followed this thread,
but unless I'm missing something,
it seems to boil down to port 25 blocking. (IMHO)
I never have THAT problem and most of my e-mail is
sent to all different hosting services and THEIR "personal" servers
on higher port numbers. I send NO e-mail through my ISP
servers on their ports.
I doubt if I'm sending anything on port 25 anymore at all.

As an example, I use the free Gmail servers on a port in the 5XX
series. I do similar things many other places. The smarter ones
password protect their site configuration info to members only.

The best place to see public instructions on how to do this is
at Gmail, in the POP3/SMTP (ESMTP??) configuration section (free)...

This only works well (and continues to work with-out problems)
when the servers always authenticate sends so they are not accused
of being open relays.  Open replays are trouble, and WILL be banned
and black-listed eventually...

Hope this helps.                              Rick Glazier

--------------------------------------------------
From: "Scott Sipe" <[EMAIL PROTECTED]>
Sorry if I wasn't clearer in my earlier email--
If you're connecting through cox, there is no reason to use a different SMTP server. Just send your mail (regardless of whether it's @cox.net or @att.net or whatever) through the cox SMTP server.

Reply via email to