PowerMTA Support Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

PowerMTA 5.5r1 is out!!!!  Please contact support@port25.com for a license and download access.

Author Topic: Gmail deferrals  (Read 28112 times)

CaLViN

  • Hero Member
  • *****
  • Karma: +43/-2
  • Posts: 1233
  • Hasan Kurtoglu
    • PowerMTA Administration Service
Gmail deferrals
« on: April 25, 2014, 05:45:15 AM »

Hello dears,
One of our customer started to see below gmail error :


Error: "550 5.7.1 [5.10.xx.xx 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit
for more information. z8si5698994oex.20 - gsmtp"


This is a very specific error as you know.This would be seen when there are high bounce rates but there is no changes on the email statistics.
Did any of you encounter this error suddenly ?

Logged

Professional PowerMTA Administrator - Deliverability Expert

Contact me for Consultancy needs!

jobeck

  • Jr. Member
  • **
  • Karma: +3/-7
  • Posts: 16
Re: Gmail deferrals
« Reply #1 on: April 27, 2014, 12:41:37 PM »

CaLViN,

We've seen these when we send on behalf of a domain with a p=reject DMARC rule but we're not authorized to send as that domain. Both AOL and Yahoo just started publishing p=reject which caused our sends on behalf of these domains to bounce with the message you're seeing. We were also seeing equivalent bounces from other mailbox providers that check DMARC.
Logged

CaLViN

  • Hero Member
  • *****
  • Karma: +43/-2
  • Posts: 1233
  • Hasan Kurtoglu
    • PowerMTA Administration Service
Re: Gmail deferrals
« Reply #2 on: April 27, 2014, 07:04:43 PM »

Hey jo,
The related domains doesnt have any dmarc record setup.

Thanks for the help.
This should be related to something else. :(
Logged

Professional PowerMTA Administrator - Deliverability Expert

Contact me for Consultancy needs!

MK2021

  • Jr. Member
  • **
  • Karma: +0/-6
  • Posts: 12
Re: Gmail deferrals
« Reply #3 on: May 08, 2014, 10:16:27 AM »

Hey Calvin,

I have seen this error before. That is because of the domain you are using to send from or it the domain that is used in the body of your mail.

Just change and test it. It shud work!

Your domain would have been listed in blacklists. I think thats why it is blocked by gmail

Regards,

Kumar
Logged

CaLViN

  • Hero Member
  • *****
  • Karma: +43/-2
  • Posts: 1233
  • Hasan Kurtoglu
    • PowerMTA Administration Service
Re: Gmail deferrals
« Reply #4 on: May 09, 2014, 09:01:15 AM »

Hey Kumar,
both sender domains and domains used in bodies are not in any blacklists.
This is very strange.
Logged

Professional PowerMTA Administrator - Deliverability Expert

Contact me for Consultancy needs!

MK2021

  • Jr. Member
  • **
  • Karma: +0/-6
  • Posts: 12
Re: Gmail deferrals
« Reply #5 on: May 09, 2014, 11:21:33 AM »

Might be! But things are different in gmail.

One way to find it is, just put that domain in your personal gmail id and try sending it to another gmail id, if you receive a bounce message that means gmail has blocked your mail becoz of the domain.

Try if that helps

Regards

Kumar
Logged

CaLViN

  • Hero Member
  • *****
  • Karma: +43/-2
  • Posts: 1233
  • Hasan Kurtoglu
    • PowerMTA Administration Service
Re: Gmail deferrals
« Reply #6 on: May 10, 2014, 05:41:35 AM »

Hey kumar,
It was successfully sent.
:(((
Logged

Professional PowerMTA Administrator - Deliverability Expert

Contact me for Consultancy needs!

MK2021

  • Jr. Member
  • **
  • Karma: +0/-6
  • Posts: 12
Re: Gmail deferrals
« Reply #7 on: May 10, 2014, 08:57:47 AM »


It's strange Calvin!

Just curious to know what was the content used! If possible can you share it here, so that I will have a look at it.
Logged

VIN786

  • Full Member
  • ***
  • Karma: +4/-12
  • Posts: 236
Re: Gmail deferrals
« Reply #8 on: May 23, 2014, 09:29:35 AM »

Yes I have seen this error too, last I researched, this was for a client and the list had auto-generated gmail email aliases - once the client removed those aliases the problem was resolved.

aliases were similar to john.smith@gmail.com, joh.nsmith@gmail.com, jo.h.n.smit.h@gmail.com and so on plus these were bad aliases so a hard bounce.

This may or may not be the case for your client.
Logged