Skip to main content

FeedMail Support Outage

It was recently discovered that the FeedMail support address was rejecting messages. These support requests have not been received. This situation has now been resolved.

If you require support please re-send your request. There are no currently open requests awaiting responses. Any request sent in the past has been lost.

We are very sorry about this loss of support. FeedMail strives to respond to all requests within one business day. Typically we respond within a few hours.

We don't know the exact time that this started, but we noticed a configuration change that affected the intended email address. It is likely that this change occurred on 2024-04-02 as some other support settings were being adjusted at that time. This would mean that for the past 6 weeks support messages were being lost.

Our testing shows that users should have received a rejection message with the subject "[Rejected]" followed by the original subject. And the following body:

Unfortunately, your email message to GitLab could not be processed.

We couldn't find the project. Please check if there's any typo.

However at least one customer did not receive or did not notice this response.

If in the future you are unable to reach our usual support desk for any reason or don't get a response within two business days feel free to reach out to our security contact or any other contact listed in our FAQ.


Popular posts from this blog

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:*" as the rule and select " Never send it to Spam". If your notifications are delayed we are unaware of any action that you can take. However marking notifications that ended up in your spam folder as "Not Spam" may help avoid future delays.  It does appear that these emails are eventually being accepted but we are unsure if that means that they are actually ending up in users' mailboxes (or even their spam folder

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

Email Headers

FeedMail now sets some email headers that advanced users can use to filter the messages that FeedMail sends. For example you can filter notifications in a specific category into a different folder. The headers that we set are documented in the FAQ . These headers have been being set on notifications for a few months now so you can use past messages to test your filters. If you have any questions, or would like to see other headers set to help your filtering please let us know .