 GeekNJPremium
join:2000-09-23
Waldwick, NJ | Bad move :-( So what happens next... a virus that figures out what your ISPs mail server is and sends out mail through that, just as it would any other email server? Any way to protect against that?
Blocking 25 is not the right solution and hurts those that do have legitimate needs for sending mail out through a mail server that doesn't belong to their ISP. I pay for web hosting which includes email from a company (my ISP doesn't provide hosting). I can't use that mail server that I pay for as an outgoing mail server? Sounds pretty dumb to me.
--
Have you tweaked your OOL connection? |
|
 lakinoPremium
join:2003-04-03
Campbell, CA | said by GeekNJ:
So what happens next... a virus that figures out what your ISPs mail server is and sends out mail through that, just as it would any other email server? Any way to protect against that?
Blocking 25 is not the right solution and hurts those that do have legitimate needs for sending mail out through a mail server that doesn't belong to their ISP. I pay for web hosting which includes email from a company (my ISP doesn't provide hosting). I can't use that mail server that I pay for as an outgoing mail server? Sounds pretty dumb to me.
Another problem is that many ISPs only allow a certain size limit to outgoing mail. Part of the reason I pay each month to host my own domain name and have mail routed through them is so that I have NO limits whatsoever on outgoing as well as incoming mail. I can send out 100 meg attachments or receive 100 meg attachments. I'd like to see someone try doing that via SBC/YAHOO.
--
Why do people like .sig files so much? Baffling to me... |
|
|
|
 crowdx
join:2001-10-12
Concord, CA | reply to GeekNJ
I really think you guys have this wrong. What the ports that they are blocking are doing is only preventing "email servers" from home being able to send and receive email. I own two domains and host each for $4.99 a month and this allows me 10 email addresses per domain name. I can send and receive exactly as if I was using my ISP's email, the only main difference for me apart from the fact that my emails use my domain name in the address, is that I also can send large emails which would normally be rejected by isp's normal email size limits.
So I agree it is a nuisance to those who want to run email servers locally from their home office or house, but for other users this will not affect them. |
|
 djrobx
join:2000-05-31
Valencia, CA
kudos:1
 ·Verizon Wireless..
 ·RoadRunner Cable
 ·AT&T U-Verse
 ·VOIPo
·PHONE POWER
1 edit | reply to GeekNJ
quote:
What the ports that they are blocking are doing is only preventing "email servers" from home being able to send and receive email.
No. Problem: "Servers" use the same SMTP port to send email as your e-mail client does to send emails to your ISP's mail server.
So if they institute a outgoing port 25 block, you MUST use your ISP's mail server to send outgoing e-mail, or use a mail service that can accept messages on a different port.
-- Rob
--
\\ROB - a part of the SCB local network |
|
crowdx
join:2001-10-12
Concord, CA | reply to GeekNJ
Yes, but if commercial companies that web host for us find that port 25 is blocked, they will have to switch so as to make their service still accessible.
ISP Mail servers suck, it is years since I have used their services. |
|
