Cox sucks Cock
 

bastards.

now that i'm not using their isp (but my parents are), i cant access my email thru smtp.

they've blocked this to prevent relaying and i'm left without a place to send email through.

i have other accounts, but i'm pissed off at them.


and they've warned me that it's a breach of contract to try to even to try to send the damn email.

anyone know a way past this?

Sorry I can't help, but I have the same problem.

I use Insightbb and now that i'm in college I can't access my email or FTP. It's really a pain because all my important mail goes there.

No, cox sure are bastards. I work a web hosting company in techsupport, and we got MANY complaints when they started this. I don't know a way around it unfortunately.... They don't block incoming just outgoing...so basically, all you can do is use whoever for incoming, but them for outgoing.

what is weak is the fact that i can access it using the web interface, but not using the smtp.

Hey, I like blowjobs, change your title! :p

Umm, correct me if I'm wrong, but doesn't every ISP do this, or shouldn't they? If relaying was allowed, Spam would be even worse (IMHO).

If you want to send mail, change the SMTP server for that account to the SMTP account of who you're using to connect right now (if you're at school, use their SMTP server to send mail from your Cox account).

Cox had to block port 25 to try and stop spammers. Your bitch is with spammers, not Cox.

Re: Cox sucks Cock
 

Are they not attempting to solve the problem?? And how can you breach a contract in sending an email using 'normal' protocols ?? Anyway, all a bit weird to me.

I use Cox, but they never gave me an email account...

Time to contact the BBB...

So you think it sucks that cox does not allow you to use their service when you aren't paying for it. (Your parents are). Gee imagine that, a company that doesn't want to give their services away for free.

Only allowing authenticated users to send mail cuts way down on open relay spams. Have your parents set up an email account for you on their account. They should have like 7 available email boxes. Then you can use it.

no no, i am authorized to use this account.

my parents are not well informed about te


h internet and i set up the accounts for them (and for me).

we have 3 free accounts avaliable and i have 2 of them (my parents use one, but it's prolly collecting dust right now).can you expand on that?

What email client are you using? If you have an email account w/ your school, what's the SMTP settings for it (mail.your.domain i.e. mail.tu.edu is usually a safe bet.. I don't know Texas colleges' domain names, sorry.? I can explain it better with this information.

Basically, I see this setup. You're using Outlook, Outlook Express, Eudora, whatever.. right? And you have two accounts. You have your Cox account (which uses the cox POP3 server to receive mail) and your school account (which uses the school mail server to receive mail). You modify your Cox account so that it still receives mail through the POP3 server, but it now sends mail through your schools SMTP server (not the Cox SMTP server you probably have it set to now). This will allow you to send mail from your Cox account (using you Cox email address). It just is going through another server, which is fine. Since you're on your school's network, they should allow you to send email... no matter what the address is (blahblah@cox.com).

Think of it this way.. you own two houses.. now usually.. you walk outside and talk to people out of one house. But for some reason you decide to go to the second house... you walk outside and talk to the same people the same way out of that house.. it's just a different house. They don't notice a difference, and once you make the switch, you don't either (unless you go home, then it's back to the "original house" for you).

I'm fairly drunk, so that example may not make sense, but the explentation does (I re-read it). If you set the SMTP server for your Cox account to send through the SMTP server for the school you're at.. you should be able to use your Cox account no worries. The SMTP server you use does not add/change the information of what your email address is.. so if it's set up to send from the blahblah@cox account.. it'll do that.. no matter what server it goes through.

----------
Side note about Spammers:
If ISP's left their SMTP server open to computers that weren't on their network (like the above case where someone from another domain is trying to send email, even though they're a legal user) spammers could use and abuse them. Anyone could send an email through that server with a fake username and address.. and they could send hundreds/thousands/millions of emails from that server, getting that server into trouble. "Why doesn't the SMTP server just validate that the username in the email is a valid account?" you ask? Because the spammer could easily set their email address to be soandso@domain.com and send the spams without any problem. SMTP does not require a password for a username, so it isn't possible to use the mail username's as a verification feature. You must use the IP, ensuring the user is on your network. Sure someone who is using you as an IP can spam people.. but at least you have record of who they are (they had to register to become a user, right?) and can take the correct action.

There IS secure SMTP, where you use your normal username and password to send mail. I imagine that this would do away with the "have to be on the network" restriction, but I've never tried it. I don't know for sure. Just a guess.

Once again, I'm fairly pissed as I write this. Your mileage may vary.

Hope this helps, let me know if you need more help.

thanks Latch! it worked!

That's pretty bad, considering that you are now sending mail as you@cox.com from your school's SMTP server. What's to keep me/your uncle/joe down the street from sending email as you@cox.com? One solution to this is to block relaying on the SMTP server, which I guess your school didn't do, or to use such other tricks that mail servers sometimes use, like waiting for you to authenticate to read mail before allowing you to send mail, or using extended protocols that allow for authentication such as ESMTP. Scary to think that someone could be sending email as someone else, and the only way to really be sure a message is from who it says it's from is to check the headers (something that most people on the internet don't know how to do)...