Mail from Mweb servers being marked as spam

F

fritzm

Well-Known Member
Joined
Dec 4, 2007
Messages
159
Reaction score
33
I've been trying to track down why much of the email that we send from our MWeb address does not get through. One clue I have is that people with gmail report that Gmail is flagging the emails as "Suspect because Google could not verify that mweb.co.za is the sender"; in some cases it appears with this warning in the inbox, in other cases it goes into spam.

I have reported this to Mweb and they gave me the following reply :

"There are no known issues with the outgoing mail-server platform.

Gmail might be giving the verification notification because MWEB’s mail service has moved to a cloud server platform, Securemail. All incoming and outgoing e-mail to and from our subscribers is being relayed through Securemail servers and no longer our own relay servers which have been decommissioned.

There should not be any issue however as using a Cloud server platform is quite common these days and many large companies are using Securemail."

My point is that if Gmail is going to the trouble of giving people warnings about these messages, then there quite clearly is a problem, and saying that "there should not be any issue" is simply trying to ignore it. In order to support my case, is anyone else using Mweb email having similar problems ? My wife uses this account for her business, so it is a serious problem if her emails don't get through. :mad:
 
Had an issue over the weekend and seems my email was compromised. I was getting error 550 in outlook when trying to send. Called the call centre and they escalated the issue. Got a call back the next day saying that my account was compromised and I should change the password. All back up and running again now.
 
fritzm said:
I've been trying to track down why much of the email that we send from our MWeb address does not get through. One clue I have is that people with gmail report that Gmail is flagging the emails as "Suspect because Google could not verify that mweb.co.za is the sender"; in some cases it appears with this warning in the inbox, in other cases it goes into spam.

I have reported this to Mweb and they gave me the following reply :

"There are no known issues with the outgoing mail-server platform.

Gmail might be giving the verification notification because MWEB’s mail service has moved to a cloud server platform, Securemail. All incoming and outgoing e-mail to and from our subscribers is being relayed through Securemail servers and no longer our own relay servers which have been decommissioned.

There should not be any issue however as using a Cloud server platform is quite common these days and many large companies are using Securemail."

My point is that if Gmail is going to the trouble of giving people warnings about these messages, then there quite clearly is a problem, and saying that "there should not be any issue" is simply trying to ignore it. In order to support my case, is anyone else using Mweb email having similar problems ? My wife uses this account for her business, so it is a serious problem if her emails don't get through. :mad:
Click to expand...



Hi fritzm

Please provide me with your MWEB email address and I'll look into what was emailed to you and also speak with the relevant team.
 
Hey Mweb...I've noticed that gmail recently started marked mails from mweb as "the source of this could not be verified" or some such story. i.e. It shows a banner warning in gmail.

Thats for an mweb email that is definitely legit & there was no way gmail flagged that addr for spam (its my old man's addr). So something is def dodge with the mweb/gmail interactions & its new.
 
HavocXphere said:
Hey Mweb...I've noticed that gmail recently started marked mails from mweb as "the source of this could not be verified" or some such story. i.e. It shows a banner warning in gmail.

Thats for an mweb email that is definitely legit & there was no way gmail flagged that addr for spam (its my old man's addr). So something is def dodge with the mweb/gmail interactions & its new.
Click to expand...

Hi HavocXphere, PM me your dad's MWEB address and I will have a look into this for you
 
MWEB Guy said:
Hi HavocXphere, PM me your dad's MWEB address and I will have a look into this for you
Click to expand...
ai bru. Thanks for the polite template response but no you're not hearing me. I know my dad's address isn't the problem. Lets try this in a more direct fashion.

This is not an issue connected to individual addresses nor is it an isolated case judging by this thread. Please go tell your corporate overlords that Gmail has designated mweb as a risky/spamy source & I'd politely suggest they figure out why very fkin fast.

Cool?
 
HavocXphere said:
ai bru. Thanks for the polite template response but no you're not hearing me. I know my dad's address isn't the problem. Lets try this in a more direct fashion.

This is not an issue connected to individual addresses nor is it an isolated case judging by this thread. Please go tell your corporate overlords that Gmail has designated mweb as a risky/spamy source & I'd politely suggest they figure out why very fkin fast.

Cool?
Click to expand...

Just test and it is true

Mweb Guy , Gmail shows a banner above the message "Gmail couldn't verify that this message was sent by mweb.co.za" and under learn more leads to https://support.google.com/mail/answer/1366858?hl=en&expand=5
 
Fudzy said:
I've dealt with two companies in the past the months who use @mweb.co.za addresses as their primary addresses (I know) and they went to GMail's spam folder. If I had forwarded the mails to [email protected] will you action to have it removed from the spamlist?
Click to expand...

That's correct; notifying our Abuse and Security team will be the best course of action for these sort of queries.
 
HavocXphere said:
ai bru. Thanks for the polite template response but no you're not hearing me. I know my dad's address isn't the problem. Lets try this in a more direct fashion.

This is not an issue connected to individual addresses nor is it an isolated case judging by this thread. Please go tell your corporate overlords that Gmail has designated mweb as a risky/spamy source & I'd politely suggest they figure out why very fkin fast.

Cool?
Click to expand...

The more examples our Abuse team are able to attain, the quicker it'll be to diagnose the root cause and resolve accordingly. That said, please either PM me your MWEB email address, or you can also email our Abuse team to investigate further: [email protected]
 
MWEBHelp you are not helping at all. I am receiving mails in gmail from people with mweb adresses. This is what I get in the mail. "Gmail couldn't verify that this message was sent by mweb.co.za". What it looks like is that gmail does not trust your domain. Individual email addresses are not the issue.


http://www.emailandpushmarketing.com/2015/09/gmail-couldnt-verify-that-this-message.html
Why did it happen? Probably because they set up a new SMTP server and forgot to update SPF and DKIM configuration appropriately
Click to expand...
 
Last edited:
acidman1 said:
MWEBHelp you are not helping at all. I am receiving mails in gmail from people with mweb adresses. This is what I get in the mail. "Gmail couldn't verify that this message was sent by mweb.co.za". What it looks like is that gmail does not trust your domain. Individual email addresses are not the issue.


http://www.emailandpushmarketing.com/2015/09/gmail-couldnt-verify-that-this-message.html
Click to expand...

Hi acidman1

In the 2 page thread, I do provide advice on where to send such queries. Have have sent your query to our abuse team?
 
From a few tests I did with my MWEB email, it appears their mail servers do NOT have DKIM, or SPF set up. This is basic config that ANY host worth its salt "should know".

Once again, it is not for "us" the client to prove, or troubleshoot your network settings. This is a fundamental "setting" for email that MWEB "should know" :whistle:
 
cortexenslaver said:
From a few tests I did with my MWEB email, it appears their mail servers do NOT have DKIM, or SPF set up. This is basic config that ANY host worth its salt "should know".

Once again, it is not for "us" the client to prove, or troubleshoot your network settings. This is a fundamental "setting" for email that MWEB "should know" :whistle:
Click to expand...

Yup.

I deal with them occasionally (mweb) They're not too smart.
These days they appear to use synaq.com for their email services.

No SPF records.
No DKIM as you say.

No SPF is why google is complaining.

They also don't conform to RFC's either when sending -

Example -

@40000000567d8183318b384c.s:@40000000567c7f663136b394 tcpserver: ok 1626 mail.computersolutions.cn:::ffff:61.152.104.159:25 securemail-pl-omx9.synaq.com:196.35.198.76::50400
@40000000567d8183318b384c.s-@40000000567c7f66313cc25c jgreylist[1626]: 196.35.198.76: OK known
@40000000567d8183318b384c.s-@40000000567c7f6a10a94c04 qmail-smtpd[1626]: before greeting: [196.35.198.76] client disconnected


I have a greet delay of 30 seconds setup for new unseen incoming mail ip's, they ignore that, and try blat out mail regardless.
Thats in direct violation of mail RFC 2821

https://tools.ietf.org/html/rfc2821


So, clueless *and* incompetent. Great mix.
 
lsheed_cn said:
Yup.

I deal with them occasionally (mweb) They're not too smart.
These days they appear to use synaq.com for their email services.

No SPF records.
No DKIM as you say.

No SPF is why google is complaining.

They also don't conform to RFC's either when sending -

Example -

@40000000567d8183318b384c.s:@40000000567c7f663136b394 tcpserver: ok 1626 mail.computersolutions.cn:::ffff:61.152.104.159:25 securemail-pl-omx9.synaq.com:196.35.198.76::50400
@40000000567d8183318b384c.s-@40000000567c7f66313cc25c jgreylist[1626]: 196.35.198.76: OK known
@40000000567d8183318b384c.s-@40000000567c7f6a10a94c04 qmail-smtpd[1626]: before greeting: [196.35.198.76] client disconnected


I have a greet delay of 30 seconds setup for new unseen incoming mail ip's, they ignore that, and try blat out mail regardless.
Thats in direct violation of mail RFC 2821

https://tools.ietf.org/html/rfc2821


So, clueless *and* incompetent. Great mix.
Click to expand...

As long as you sent an email to the abuse department, just make sure you don't send it from your mweb address because that might bounce.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X