If you are using the client to check other email accounts, such as GMail, Yahoo etc, you must use the IDNet SMTP server to send messages from those accounts. However to collect mail from non-IDNet accounts you must set your email client to the names of their POP servers, eg pop.googlemail.com etc.
This is fairly common. Most ISPs restrict port 25 (which is used when sending
email) to prevent their network being used to send spam. The only connection they allow via port 25 is to their own email server which gives them control over what gets sent out.
However when collecting
email you always have to contact the actual server that holds your account because only that server normally has access to your mail box.
The only thing puzzles me about that statement is that I don't think IDNet do block port 25. I run my own mail server so I need port 25 unblocked (so that my mail server can send mail for me) and I'm pretty sure Support told me that it wasn't blocked in the first place. I've also found this article online:
"The Director of IDNet , Simon Davies , told ISPreview:
"That's a simplistic view and is also futile. It is the same argument that says that if you block P2P ports then you'll stop illegal music filesharing. No, you won't. The traffic will just move to other ports and/or SSL-encrypted channels.
Most SMTP servers accept incoming connections on port 587 and also 465 for TLS. Blocking port 25 wouldn't slow down the spammers for very long at all but it would inconvenience the very many, mostly business use, legitimate reasons for being able to reach port 25."
I would contact Support to clarify but to be honest IDNet just isn't the kind of 'Mickey Mouse' ISP that does stupid stuff. It provides an honest and traditional service that allows its customers to use the internet in whatever (legal) way they want to. It does not put blocks or obstacles in place to try and control us.
Edited by Andrue (Sun 23-Feb-20 10:36:01)