Anon00Premium
join:2001-09-25
USA
kudos:1 | reply to inTulsa
Re: Steps for Netscape 7 Good to hear that inTulsa. Kinda sucks that I pay Yahoo! for pop3 and smtp features and Cox blocks the SMTP port. I can understand there reasoning though. |
|
| Send Yahoo a request for SMTPS, they're very good at listening to what their cu$tomers want. The more requests they get the sooner it may happen.
mail-premium-support@yahoo-inc.com
I'm not sure they'd trust premium email from the Cox SMTP. You might have to send it via their webmail interface.
[text was edited by author 2003-07-09 00:09:05] |
|
|
|
FCKGW
join:2003-01-07
Eureka, CA | inTulsa: I'm not sure they'd trust premium email from the Cox SMTP. You might have to send it via their webmail interface.
Yahoo doesn't have to trust it; it doesn't go through them. Outgoing mail through Cox SMTP goes from your computer, to region.smtp.cox.net, to the destination mail server. All that identifies the message as being from a Yahoo account are the From and Reply-to header fields. All Yahoo will notice if you use Cox SMTP is that you have stopped sending mail (since your outgoing mail won't go through Yahoo), but still receive it.
I'm not trying to deter you from trying to get SMTPS support, though. The more you can encrypt, the better. More importantly, try to get POP3S support, since you send a username and password when checking mail.
--
Keyboard error or no keyboard present.
Press F1 to continue. |
|
| Good points, I guess you're right. But I'd still rather be able to use authenticated SMTP which is not available by going through Cox's forced use of their archaic SMTP facilities.
It's somewhat like US Postal mail. For most things sent by most people an anonymous stamp is just fine. But for some things it's better to use registered, certified, or FedEx.
But now Cox is forcing us to use their SMTP even though it's not right for everyone and not suitable for everything. People will at least occasionally want/need better alternatives.
Blocking Yahoo is silly anyway. Customer-originated spam & virus infections was stated as the reason for blocking port-25. But nobody could send through Yahoo's SMTP without authentication (and $ubscription) so it should be on the white-list of exceptions like the .edu & other sites.
But this side-trip strays from the main topic which is to identify and highlight alternatives for overcoming the port block. |
|
