ihug smtp problems

Forums › One New Zealand (including Vodafone, WxC, Farmside) › ihug smtp problems

1 | 2

jdbob

43 posts

Geek

#116747 15-Mar-2008 09:11

The last time I was in NZ I thought I was going to get around the port 25 blocking problem by using port 587. Not nearly clever enough. I could get to my web hosting company's SMTP server but it turns out that the IP address I was using (from my friend's orcon account) was listed in the SBL list at spamhaus. This is another trick that ISPs use, I had the same situation trying to use my neighbors DSL connection here in the evil empire.

wnelson

10 posts

Wannabe Geek

#116753 15-Mar-2008 09:44

jdbob: ....., I had the same situation trying to use my neighbors DSL connection here in the evil empire.

I'm amazed that people would put up with this from their ISP. I mean you are paying for Internet (Inter_Nework) connection not Web access. Does your phone company limit you what numbers you can call?

The ISPs that do this this should be exposed and shamed. They are simply trying to implement security on the cheap.
My advise to anyone with one of these ISPs is to vote with your feet (that is what hurts them the most)

Wayne

cokemaster

Exited
4930 posts

Uber Geek

Retired Mod

Trusted

Lifetime subscriber

#116757 15-Mar-2008 10:01

As previously stated, Xtra does allow you to opt out of port 25 filtering and there is no charge associated with it. Simply fill out of opt out form, restart connection and you are done. Compared to another providers, this is well documented and unlike a certain provider you don't have to pay $10 for a static IP just to get unfiltered..

The majority of the users won't need port 25 connectivity to the non ISP servers, so it slows down the ability for spam viruses to set up a SMTP server and spam like no tomorrow. Those users that need it can opt out easily enough and ensure that they don't get their ISP blacklisted (which affects everyone on that ISP) by spamming or getting infected.

Many email servers are starting to use 465 and 587.

webhosting

Loose lips may sink ships - Be smart - Don't post internal/commercially sensitive or confidential information!

wnelson

10 posts

Wannabe Geek

#116808 15-Mar-2008 13:34

cokemaster: .....The majority of the users won't need port 25 connectivity to the non ISP servers .....

Well maybe. Who knows? If you can retain your userbase implementing measures like this, good luck to you. I personally wouldn't stay with an ISP who did this.

There are many other methods to combat spam and trojans. They may not be as easy or cheap to implement but I guess that is the differentiator......

Wayne

freitasm

BDFL - Memuneh
79316 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#116812 15-Mar-2008 13:49

wnelson: Well maybe. Who knows? If you can retain your userbase implementing measures like this, good luck to you. I personally wouldn't stay with an ISP who did this.

You... But for each "geek" who knows what is port 25 and is (should be) very capable of visiting a webpage to simply opt out of filtering, there are many non-geeks who don't need about to know anything to the whole port 25, filtering, etc because they just use the ISP's provided email service and wouldn't need anything to be changed.

What it seems is needed is better help desk training around, so that when someone move from "I just use this from home" to "I need to send emails using my work server" or "I need to send emails from your smtp server but with another address" then a correct answer is provided.

PenultimateHop

637 posts

Ultimate Geek

Trusted

#116817 15-Mar-2008 14:18

Large numbers of ISPs block outgoing port 25 to destinations that aren't their own mail servers. UUNET started this at least 6 years ago (probably more) on their global dialup platform, at the time the largest in the world. Most hotel internet providers also do this.

It's very common for outgoing port 25 to be intercepted and forwarded to a local smtp server as well. It's a cheap and very effective spam containment solution.

You are quite incorrect about using From: <something@ihug.co.nz> and using a non ihug mailserver is going to cause issues, unless ihug are publishing strict SPF records (they're not) and the recipient mailserver is enforcing strict SPF behavior (which is stupid).

As far as ihug not requiring encryption - well, if you're using POP3 or IMAP you're almost certainly transmitting in the clear. But you can always use TLS, as you note from your own posting that they support STARTTLS.

As for your problem: frankly no idea, it does sound like an issue with ihug,

1 | 2