When did MWEB start relaying all mail through their servers?

[guest2013-1]

I run my own mail server. Today, for the first time in a few weeks (I think), tried sending a mail... which obviously prompts me to authenticate to my mail server. It kept failing so when I did a quick Telnet to debug I noticed that they're intercepting SMTP traffic via their own mail relay (which makes sense why my authentication would fail, since it's not my mail server answering the request)

Now, since I have SPF records on my DNS, assuming I could send email, it would immediately fail since the relay is now responsible for that mail being sent and not my own mail server.

This is somewhat gay. Even gay's would go "this is gay". I'm reconsidering this account altogether, since this is the primary reason why I don't use WISP's or any other ISP that does this bull****.

 

[7th day adventist church]

I wish all ISPs would do this since it makes them able to cut down on "zombie" computers sending out spam.

Besides, you shouldn't be using SPF records on a dynamic IP address. What you could do is just to add mweb's sending servers to your DNS spf records.

 

[guest2013-1]

I wish all ISPs would do this since it makes them able to cut down on "zombie" computers sending out spam.

Besides, you shouldn't be using SPF records on a dynamic IP address. What you could do is just to add mweb's sending servers to your DNS spf records.

Okay, n00b

Having your own email server = data center hosted machine with a static IP address. I'm not hosting my own mail server on a dynamic IP address or on my own network. That's just ****ing stupid. So having SPF records on my DNS to circumvent spammers and viruses from sending mail as me makes sense huh? (I wish banks would follow the same practice)

 

[7th day adventist church]

Good job pointing that out in your original post

So use that tiny brain of yours and send your mail over a non-standard SMTP port (hint: not port 25) and stop crying like a little baby about an issue you could have solved yourself.

regards, n00b

 

[guest2013-1]

Good job pointing that out in your original post

So use that tiny brain of yours and send your mail over a non-standard SMTP port (hint: not port 25) and stop crying like a little baby about an issue you could have solved yourself.

regards, n00b

"n00b" was in jest

FYI, port 25 is a non-standard port for SMTP since the RFC documents mention 2 others to be used and not 25. I got my mail to work within a few minutes, and you completely miss the point of the post:

When did MWEB start relaying all mail through their servers?

Since I didn't receive any kind of notification from them, I'm assuming it was sometime the last week, but I figured I would have wanted some kind of helpful response. Instead, troll's appear

 

[MusherSA]

@Acid Mine only started this morning sometime. And yes I agree, something like this should have been communicated to us.

 

[Valerion]

Just checked to a server hosted at Hetzner as well as an international SMTP relay (that requires a username from me). Both worked correctly.

Then again, I don't use MWEB for DNS.

 

[Gambit]

I don't have an mweb account but do remember reading about some security control panel thing they have to block ports etc which is now enabled by default. Maybe see if that is switched on for your account.

Just checked to a server hosted at Hetzner as well as an international SMTP relay (that requires a username from me). Both worked correctly.

Then again, I don't use MWEB for DNS.

Luckely DNS can't redirect ports, only ip addresses.

 

[SabreWolfy]

Deleted; missed the point about the mail server being hosted elsewhere.

 

[Gambit]

Are you on a business account?



(Don't shoot the messenger.)

He is not running the mail server on his ADSL account. He has stated that the mail server he wants to connect to is hosted in a data centre.

 

[milomak]

Deleted; missed the point about the mail server being hosted elsewhere.

then don't send messages that have nothing to do with the subject matter

 

[James]

I must say that I like the idea. In the USA the norm is for ISP's to just block port 25 outright. The fact that MWEB routes all SMTP through them where they might have some control over the huge amount of SPAM that is sent from there network is a good one. In Saying this, I would not want MY mail going through this route. I would just send all mail through port 2525 which is non-standard (but becoming more standard) and you have the problem solved.

 

[James]

FYI, port 25 is a non-standard port for SMTP since the RFC documents mention 2 others to be used and not 25

Just for the record, not starting an argument but port 25 is indeed standard and even if it were not it is by far the most widely used port.

Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (e-mail) transmission across Internet Protocol (IP) networks. SMTP was first defined in RFC 821 (STD 15) (1982),[1] and last updated by RFC 5321 (2008)[2] which includes the extended SMTP (ESMTP) additions, and is the protocol in widespread use today. SMTP is specified for outgoing mail transport and uses TCP port 25. The protocol for new submissions is effectively the same as SMTP, but it uses port 587 instead.

- Wikipedia

 

[bboy]

Good job pointing that out in your original post

So use that tiny brain of yours and send your mail over a non-standard SMTP port (hint: not port 25) and stop crying like a little baby about an issue you could have solved yourself.

regards, n00b

i nominate you for dumbass of the day

 

[Icarium]

If you have a problem or query about a specific service provider, why not contact said service provider?

 

[Lounger]

I wish all ISPs would do this since it makes them able to cut down on "zombie" computers sending out spam.

Besides, you shouldn't be using SPF records on a dynamic IP address. What you could do is just to add mweb's sending servers to your DNS spf records.

That would make sense if Mweb mail was spam reduced or even free - which is certainly isn't.

 

[SabreWolfy]

then don't send messages that have nothing to do with the subject matter

It's called a mistake; we all make them

 

[sin_x]

i nominate you for dumbass of the day

You nominate him/her for dumbass of the day for what?
He/she is entirely correct. MWEB would be intercepting on port 25. The correct thing to do would be to use SSL over port 465.

 

[guest2013-1]

If you have a problem or query about a specific service provider, why not contact said service provider?

Because I believe in open communication and freedom of speech. Companies like MWEB and Web Africa love to try and dull-down the actual outcry of users by forcing them on the phone or in private message state's. They pretend to give you a "personalized" service, when in fact all they're trying to do is shut you up and get the information that is out there buried as quickly as possible since they know how powerful the internet is these days when it comes to "reviews" by the general public.

Having said that, intercepting mails that I send or receive, according to me and as far as I know, is a direct infringement to my right to privacy. That is one of the reasons WHY I host my own email on a secure server I know no one has access to except myself and some support staff. (The nature of great service turning into ****ty service, especially on an ISP front, also made me choose this instead of just using @mweb/iafrica/webafrica/icon/afrihost email addresses and then bound to one specific ISP for life and fear of losing any important email)

Even though I agree that there are multiple idiots out there that get infected with trojan's turning their machine into spam-a-pa-looza, I must admit I was one of those idiots a few years back. However, I diagnosed and fixed the issue before it became critical and it only happened because of a fresh install of Windows without an antivirus (which I normally install first and foremost). There are better ways to approach this than what they've done. One of which could be a notification that there's quite a bit of traffic on port 25 constantly and/or shutting down their service temporarily so the person could phone in and inquire so they could help them through installing anti-virus and getting rid of the cause.

If MWEB wants to curb the spam being sent out from their network without impacting anyone else's stand-alone server, I'd suggest they do what Web Africa does and have the network scan without the need to intercept such emails (it can be done)

However, as I mentioned. MWEB didn't relay any kind of information to me via a newsletter or a press release via MyBroadband to inform me of the fact they changed their service (even though it probably does say so in the T&C that they can), but since this could possible infringe on my rights, I would've liked to be warned and give them permission to do so.

 

[7th day adventist church]

If MWEB wants to curb the spam being sent out from their network without impacting anyone else's stand-alone server, I'd suggest they do what Web Africa does and have the network scan without the need to intercept such emails (it can be done)

Please, do go on. I am interested in your views and would like to subscribe to your newsletter.