Skip to main content

Delivery Delays to Gmail

In the past 48 hours Google has started delaying the delivery of some FeedMail notifications. This is currently affecting about 10% of messages to Gmail users. These notifications will be resent with a delay. We also speculate that some notifications will be marked as spam.

 Update: As of 2023-05-09 this appears to be resolved.

If You Are Affected

If you use Gmail you may be affected by this. Notifications may be delayed or marked as spam.

  • If your notifications are marked as spam you can create a filter to avoid this. Use "from:*@feedmail.org" as the rule and select "

More Details

The temporary rejection we are seeing from Google is in the form of:

transient error (421): 4.7.28 [165.22.236.104 15] Our system has detected an unusual rate of
4.7.28 unsolicited mail originating from your IP address. To protect our
4.7.28 users from spam, mail sent from your IP address has been temporarily
4.7.28 rate limited. Please visit
4.7.28  https://support.google.com/mail/?p=UnsolicitedRateLimitError to
4.7.28 review our Bulk Email Senders Guidelines.

FeedMail does not send unsolicited mail so this is a false positive. However it is possible that it was triggered by a user marking FeedMail notifications as spam instead of unsubscribing which lead Google to believe that these messages were unsolicited.

Our email sending rate to Google users has not changed notably in the past couple of weeks so it is surprising to see this error occur.

We have submitted a Sender Contact Form but it does not suggest that we should expect a response.

Labels:

Comments

Post a Comment

Popular posts from this blog

Updates to HTML Processing

Since its inception FeedMail has done processing on HTML content in feeds to ensure that it renders as expected in email form. At first this was fairly simple things like rewriting URLs to point to the correct location (many feeds use non-absolute URLs that won't work in email) but over time more complex transformations were added such as adding fallback content to media embeds without any. The full-text scraping feature requires even more complex processing as it requires stripping away most of the page and handling content that was designed for full-featured browsers. What changed? Recently FeedMail has migrated all HTML rewriting to use new infrastructure. This provides more flexibility and enabled new features (such as showing controls on all media embeds) and made our processing much more reliable. What does this mean to me? As a user you shouldn't see much difference. Overall the emails you receive should be better formatted but the difference will be subtle. Full-text sc
Post a Comment
Read more

No body notification option.

Previously FeedMail provided two options for notification bodies: Content from the feed. Attempt to scrape content from the linked website. A third option is now available which includes no content in notifications. This can be useful to reduce email size or if you prefer reading articles in your browser anyways. This option is especially useful for digests. By setting subscriptions in a digest to "No Content" you can get a headlines-only digest. Or you can keep content for some short content like micro blogging but just get headlines for news sources with longer articles. Simply go to your subscription management page to change this setting. You can find a link at the bottom of each email notification.
Post a Comment
Read more