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

Digests are now Supported for Owner-Paid Feeds

Owner-paid feeds allow feed publishers to provide FeedMail to their subscribers at no cost. For example the FeedMail Blog is an owner-paid feed. Up until now digest subscriptions were not covered by owner-paid plans. Subscribers could select a digest but they would have to pay for the subscriptions themselves. Digests are now fully supported under owner-paid plans. For users: The owner-paid feeds in your digests no longer count towards the cost of the digest. For publishers: Users will now be able to receive your feed as a digest or included in one of their existing digests. You will be charged one credit for each digest issue containing items from your feed (no matter how many items from your feed are in that issue). Notably this cost will never be more than real-time subscriptions would be.
Post a Comment
Read more

Changes to Billing for Multiple Simultaneous Updates

This change may result in increased credit usage for non-digest subscriptions. Am I Affected? Digest Subscriptions are unaffected . Owner-paid Feeds are unaffected . Frequently updating real-time subscriptions are affected . If you have questions regarding your specific subscriptions please contact FeedMail support . Background FeedMail pricing has always been 1 credit per email notification. However in practice FeedMail would charge at most 1 credit every time a feed was checked, even if there were multiple new items on that feed and multiple emails were sent. In other words FeedMail sometimes undercharged users. Going forward, this billing error will be corrected, which may result in higher credit usage for feeds that were previously undercharged. Correcting this issue is essential to preventing abuse, ensuring long-term sustainability, and maintaining fair pricing. Multiple updates are a rare occurrence. It usually happens on on feeds that update very often (faster than once every 5...
Post a Comment
Read more

Support for SMTP MTA Strict Transport Security

FeedMail now supports SMTP MTA Strict Transport Security (MTA-STS) . This standard provides receiving domains a way to attempt to indicate that incoming mail should only be delivered over a secure connection. When FeedMail receives this signal it will refuse to deliver over insecure connections (retrying mail as required). FeedMail does not currently support SMTP TLS Reporting (TLSRPT) . We will be reaching out to any existing customers who's mail may be rejected due to this change.
Post a Comment
Read more