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.
http://support.cox.com/sdccommon/asp/contentredirect.asp?sprt_cid=777985a9-df9d-40bd-ab18-e6bb14c4329f
I used to be on cox (not terribly found of them as a company, but
anyway...) and it worked for me.
Scott
On Oct 28, 2008, at 2:44 PM, Steve Tomporowski wrote:
I think I've got both problems sorted out now, not solved, have to
give one a shot.
AT&T doesn't support secure authentication, which was what I was
turning on. Really dumb for me on that one. Then apparently there is
an AT&T bug that keeps sending you emails despite the fact that you
are correctly set with SSL.
I'm trying to access the COX server from the AT&T network. Cox has
port 25 blocking, but I can't find an opt-out on their site. I'll
have to give them a call (and not tell them I'm using TB as they'll
just jump ship on me immediately).
Steve
On Tue, Oct 28, 2008 at 6:03 AM, maccrawj <[EMAIL PROTECTED]> wrote:
Problem 1:
That looks like a useless thread!
"Any firewall needs to include entries for the IP/Subnet for the
local
adapter/router and the IP of the Modem."
Sounds like the last guy is not using his modem in bridge mode,
irregardless
his problem came down to his router settings not TB.
Scott Sipe wrote:
Problem 1:
http://forums.mozillazine.org/viewtopic.php?f=39&t=866485&p=4755585
Seems at least others have the same problem...
