When did MWEB start relaying all mail through their servers?

[Will@MWEB]

Glad to hear that Mark.
I understand your frustration regarding the redirection, however the need to combat spam and viruses is a very real one and this solution will ultimately be to the benefit of all our customers.

 

[racer]

@Mark the solution we are in the process of implementing is not outright blocking of port 25, its a redirect to ensure that the traffic passes through our relays so that normal virus and spam filtering can take place.

In this case, can you make it work so that your relays ignore any SMTP authentication attempts and just accept the mail anyway? I know of at least one ISP (in Dubai) who does it this way, so that laptops with SMTP authentication setup can still send mail via their redirected servers without breaking...

 

[Will@MWEB]

Hi racer You can still do this, just not on port 25. Port 587 should be supported on almost all smtp servers that accept auth - if you have a problem doing it this way let us know and we'll assist.

 

[racer]

Hi racer You can still do this, just not on port 25. Port 587 should be supported on almost all smtp servers that accept auth - if you have a problem doing it this way let us know and we'll assist.

i'm thinking more about the thousands of ppl already out there with laptops using SMTP Auth on port 25 who are suddenly gonna get stuck sending email when connecting to an Mweb network. Its really not feasible to have to call every client with a laptop and talk them thru changing SMTP settings just in case their gym has an Mweb connection. It should be simple enough to get your servers to "ignore" any SMTP Auth coming through, so that people with setups as described above can still be redirected through your servers when on your network and not have an Auth error...? I do know of at least one ISP (in Dubai though) who does it this way, ie. succesfully redirects all smtp port 25 traffic through their own relays, irrespective of whether the client has SMTP auth or not...

 

[Juggy]

i'm thinking more about the thousands of ppl already out there with laptops using SMTP Auth on port 25 who are suddenly gonna get stuck sending email when connecting to an Mweb network. Its really not feasible to have to call every client with a laptop and talk them thru changing SMTP settings just in case their gym has an Mweb connection. It should be simple enough to get your servers to "ignore" any SMTP Auth coming through, so that people with setups as described above can still be redirected through your servers when on your network and not have an Auth error...? I do know of at least one ISP (in Dubai though) who does it this way, ie. succesfully redirects all smtp port 25 traffic through their own relays, irrespective of whether the client has SMTP auth or not...

Yeah, your source IP is what authenticates you on MWebs network?

 

[daffy]

You should have been using port 587 all along.
Don't blame the ISP for breaking your already broken setup.

 

[7th day adventist church]

You should have been using port 587 all along.
Don't blame the ISP for breaking your already broken setup.

To be fair, Outlook and most other email clients default to port 25 for SMTP.

 

[Gordon_R]

To be fair, Outlook and most other email clients default to port 25 for SMTP.

+1

My Yahoo business website e-mail (which I don't use often) requires port 465 for SSL, not 587, so this change is not obvious, even for experienced users.

 

[Will@MWEB]

Hi Gordon

Port SSL over port 465 is unaffected, the only redirection that takes place is on Port 25.

 

[TonyA]

Will@mweb can you give more details? My SMTP is relay.mweb.co.za, when I use smtp.mweb.co.za I cant receive mail. Thanks

 

[MWEBHelp]

Will@mweb can you give more details? My SMTP is relay.mweb.co.za, when I use smtp.mweb.co.za I cant receive mail. Thanks

Hi TonyA

Changing your outgoing email server only, does not affect your incoming emails.

Regards
MWEB Operations

 

[racer]

You should have been using port 587 all along.
Don't blame the ISP for breaking your already broken setup.

please don't talk crap. how many joe public's out there even know what ports are, let alone SMTP ports. the FACT is that many. many people are using smtp auth on port 25, and have been doing so since noah's ark. its not MY broken setup, its just the way things are... my clients use many different ISP's and many different email setups (given to them by ISPs etc, not by me) - but I'm the one who gets the call when Johnny can't send email from his gym becasue Mweb decided to play this trick. My point is... if you're going to reroute port 25 traffic to a server that the client doesn't even know he's going to be using, then at least disable smtp auth from breaking. It can be done, as I've already stated.

 

[Juggy]

please don't talk crap. how many joe public's out there even know what ports are, let alone SMTP ports. the FACT is that many. many people are using smtp auth on port 25, and have been doing so since noah's ark. its not MY broken setup, its just the way things are... my clients use many different ISP's and many different email setups (given to them by ISPs etc, not by me) - but I'm the one who gets the call when Johnny can't send email from his gym becasue Mweb decided to play this trick. My point is... if you're going to reroute port 25 traffic to a server that the client doesn't even know he's going to be using, then at least disable smtp auth from breaking. It can be done, as I've already stated.

Like I stated in a previous post. It is a knee jerk reaction and doesn't appear to have been thought out properly