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.

Labels:

Comments

Post a Comment

Popular posts from this blog

DNS Outage

From 2024-08-26 19:46 to 2024-08-27 11:21 UTC FeedMail had an outage. Until 2024-06-26 20:34 FeedMail was completely down. For the remainder of the outage most emails not sent. It is expected that no feed updates were lost during this outage. Updates would only be lost if they were only present on the feed within the 50min of total outage. Most feeds ensure that updates are present for days so this would not be an issue. Notifications have been delayed and should be sent by 2024-08-27 12:31. This may take longer if your mail provider applies limits and FeedMail needs to retry delivery at a later time. Update : All delayed notifications have been sent successfully. Timeline All times are in UTC . 2024-08-26 19:46 Start FeedMail goes down.   19:53 Detection Automated monitoring reported that feeds were not being checked. 20:34 The Database IP was hardcoded, restoring most functionality. 2024-08-27 11:21 Resolution FeedMail was switched external DNS. 11:24 Schedule of ...
Post a Comment
Read more

Digests Now Respect Category Filters

Due to an oversight category filters did not apply to digests. This has been corrected and future digests will be filtered by your selected categories. If you do not want this filtering to occur please update your filters to "Ignore selected categories" and deselect all categories to inactivate the filter.
Post a Comment
Read more

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