Mail Server Conundrum

VaxPrime

Member
Joined
May 30, 2010
Messages
26
Reaction score
2
I am a happy MWEB Uncapped ADSL User....

Question: Since since I DO NOT use MWEB's Outgoing or Incoming Mail Servers at all, but only the MWEB ADSL Connection to my Domain Host's Mail Server, can and will MWEB block the Port 25 on my connection to that 3rd party Outgoing Mail Server?

My Domain Host claims it is happening and I'm having trouble buying it, I can see that MWEB can and will control spam for example on their own Outgoing Mail Servers, but interfering with web traffic in their ADSL Connection?

Asked MWEB guy and he either doesn't know or won't say, he refers me to abuse if I don't come right, but coming right is not the issue though, I want to know the answer to my question, have any of the group got an idea?
 
Yes, MWEB does block port 25 going beyond their network. This is to stop spam/viruses/mailbots.

They do allow port 587 (and others), and many mail servers can use that port as incoming. You will probably need to set up "outgoing mail authentication" as well.
 
Simple test.

Open a DOS box, "telnet mail.yourmailserver.co.za 25" and see what happens. It will probably respond with some reference to mweb.

Then try port 587.

If you are using Windows 7 you will have to enable Telnet under "turn windows features on or off". Just hit the windows key and start typing "turn wi"
 
I have clients who use mweb as their ADSL provider and I host their email.

Had a similar issue with port 25 and spoke to my hosting provider who has port 26 available. Seems that port 26 is used for blackberries although I cannot confirm this.

Switched my clients to using port 26 and no more issues.

Any reason why you don't use mwebs SMTP server ?
 
Let me just clarify the misconceptions here

an Mweb home ADSL account automatically redirects outgoing port25 traffic to it's own SMTP relays,so if you have authentication turned off and no spf/domainkeys configured your mail will relay successfully
If you are unwilling to live with this you can use the alternative SMTP ports as described or move to a business account which doesn't have this redirect active
 
Any reason why you don't use mwebs SMTP server ?

It initially happened when I changed from IS to MWEB and I jumped the gun slightly on the migration in some of my sites where the locals aren't all that tec savvy, my Domain host happened to provide the service and I could set up and get it over with so the transition between ISP's would be less painful.

When I thought of it again some time down the line I thought it was actually a nice touch enabling me to jump for ISP to ISP with much more ease as we are in a volatile time in the industry and I'm just about as loyal to my ISP's as I perceive they are to me.

I am however currently Using MWEB's Outgoing Mail Server.
 
Last edited:
Let me just clarify the misconceptions here

an Mweb home ADSL account automatically redirects outgoing port25 traffic to it's own SMTP relays,so if you have authentication turned off and no spf/domainkeys configured your mail will relay successfully
If you are unwilling to live with this you can use the alternative SMTP ports as described or move to a business account which doesn't have this redirect active

Authentication ON, Outgoing Port 578 as prescribed and successfully used for over 2 years, and the mail bounce occurred erratically for no longer than 2 days in a row, with a frequency of anywhere between 6 months and a year.
 
This conundrum is definitely a "woordraadsel' as the deo add says.

Setup seems to be the way it's supposed to be.

I can maybe accept that it happens on accasion, but for two days in a row? You will have a track it when it happens to see if the wrong mail server is reached, or that the right mail server is rejecting the email.

During the 'outage', is mail to the home domain also rejected?
 
This conundrum is definitely a "woordraadsel' as the deo add says.

During the 'outage', is mail to the home domain also rejected?

Negative on that question, no problem with the home domain.

I suspect it is simply some kind of glitch on the Host Server, and it is more important to them to deny this than finding and fixing the occasional glitch, it's the only valid argument that remains for me.
 
I would agree with you on that one.

The outage is equivalent to you turning off authentication. I think your Host provider is at fault.
 
Top
Sign up to the MyBroadband newsletter
X