RE: [cobalt-users] OT: ISP's and Port 25 blocks

[Mike Smith <cobaltdude2002@xxxxxxxxx>]

> If their ISP
> is blocking that port they need to get a new ISP or pay for a
> professional level of service from their ISP that doesn't include the
> block. Alternatives for you may be difficult. I'm not sure if you can
> make SMTP listen on another port at the same time or if it requires
> running a second instance of Sendmail.

That's part of the main issue - one of our clients actually had to
switch to another ISP because their prior ISP wouldn't allow them to
relay through our servers because of the port 25 block. We have another
client that needs to send large files via email (3-5Mb) because his
clients are too dumb to figure out ftp - even with a browser - and his
ISP won't allow file attachments larger than 2Mb....thus, he is now
screwed because he can't use his domain's smtp capability.
Personally, I don't see how an ISP can *legally* block access to
someone else's equipment.
I can understand the reasoning behind the port 25 blocks - ISP's
draconian attempt to stop spam - but it is not a solution - apparently,
though, it is a way for the ISP's to cover their backsides to ensure no
one uses their network to send spam via another network - but it does
not spam on the ISP's network.
Perhaps a class action lawsuit is in order - understand my reasoning
behind that suggestion - an ISP is blocking my clients' access to *my*
equipment.

Mike



__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com