Read Error: Generic::failed_precondition: Read Error (0): Error

Several users have recently reported seeing bounce backs from Gmail that look like this:

Commitment to the following recipient failed permanently:

Technical details of permanent failure:
read error: generic::failed_precondition: read fault (0): fault

We've seen bounces like this for both regular Gmail users and Google Apps users using GMass. The error is a non-standard bounce message that is specific to sending via the Google platform. What causes the error? Nobody is certain for sure, but the Internet speculates that it's either i of the post-obit:

1. The remote server is rejecting the e-mail due to an SPF failure. This is applicable to Google Apps users that are sending from their own arrangement's domain, not from gmail.com or googlemail.com.
2. The remote server is rejecting the email because Gmail's sending IP is blacklisted, just Gmail doesn't desire the stop user to know that's the reason for the fail, and so this generic bulletin is delivered instead.

Regarding reason #2, generally we've seen that the deliverability through Gmail's servers is the world's best, but it seems that occasionally even Gmail'southward servers go blacklisted.

Regarding reason #1, if you lot're a Google Apps user, regardless of whether you lot're using GMass, ensure that you take SPF set upwards correctly for your domain. That means you need to configure the DNS for your domain to allow email to exist sent by Google'southward servers on behalf of your domain. You can check if your domain is configured permit Google to send electronic mail on its behalf via this easy-to-use tool. Just input your domain, and check the results. I merely checked my own domain, wordzen.com, which runs on Google Apps, and noticed an consequence, which I'g about to gear up:

The SPF tape for wordzen.com breaks the rules by requiring too many DNS lookups.

In the example of wordzen.com's SPF record, the tape includes permission for Google's servers to send email for wordzen.com, but here'due south an example of a domain of a GMass user where SPF doesn't include Google'due south servers at all:

If you still see this bounciness notification after ensuring correct SPF settings, or if y'all're non a Google Apps user, information technology could be issue #2 at play.

How is GMass treatment these bounces?

Since GMass categories all bounces and replies for you, and builds an internal Bounce List for your account in order to suppress futurity mailings to bounced addresses, we've added these bounces to our "Bounciness Exception" listing, meaning we won't count addresses that bounciness with this message every bit a true bounce. That means that future attempts to ship to these addresses volition nonetheless work.

Nosotros've also deleted all bounces that were on your business relationship's Bounce List in the past because of this effect.

References

Ajay is the founder of GMass and has been developing e-mail sending software for xx years.

poorequist1988.blogspot.com

Source: https://www.gmass.co/blog/how-to-handle-this-strange-gmail-bounce-read-error-genericfailed_precondition/

Share this post