× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Hi Doug,

Why would they do that?  I thought the purpose of ISP's blocks on port 25
were to help isolate machines running rogue compromised bots spewing out
spam and sending it directly to other recipient mail servers.

I don't know why they did it.

They didn't tell me that they were going to do it, but all connections on that port number stopped working (including using telnet to test it) as if blocked by a firewall. Switching it to a different port immediately solved the problem, but I didn't want to keep doing that over and over.

They wouldn't normally be listening on anything other than port 25, so why block 2525 and 8025. Did you ISP actually detect you had email traffic on those ports and shut them off?

That's my guess -- though I don't really understand why it'd matter to them that I was sending it.

I've never had trouble using port 2525 with either of my ISP's in getting
mail to smtp.com's servers.

That's good, I'm glad it has worked for you. But, I'm not making this up -- they really blocked those ports for me!

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.