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.

Comments

Popular posts from this blog

Delay on YouTube Feeds

Most YouTube feeds have not sent new notifications since 2023-10-02 14:20 UTC. We will be triggering a manual YouTube feeds over the next hour and all missing notifications will be sent. If you have any missing notifications after 2023-10-05 14:00 UTC please reach out to support. Update 14:00 : All updates have been sent. If you believe that you are still missing updates feel free to reach out. The rest of this post is a technical analysis of the issue. Background This was caused due to recent emergency response to YouTube WebSub notifications. The emergency response was necessary is due to the following factors. YouTube WebSub posts are not spec compliant and do not contain the required information to send notifications. Therefore FeedMail uses these notifications as a "ping" to re-fetch the feed. YouTube often sends notifications before the entries appear in the feed. The exact reason is not known but sometimes entries do not appear for up to an hour after the WebSub push. ...

Invalid DKIM Signature for Some Mail

As of 2023-07-26 FeedMail messages sent via AWS SES have an invalid feedmail.org DKIM signature. This may result in messages ending up in your spam folder. This is an ongoing issue and updates will be posted here as they are available. 2023-09-25 We have issue an update that should avoid SES re-formatting signed fields. This is a workaround but should result in valid signatures. Who is affected? This is unlikely to affect most of our users for the following reasons: 97% of our mail is sent by us directly, not via AWS. This mail still has a SPF-verified sending IP. However this may still affect users because spam filters may consider these messages less "good" than they would have been with a valid DKIM signature. The most notable Inbox Providers affected by this are Apple and Microsoft. FeedMail uses AWS SES for these providers as they reject all messages from our network provider. However other smaller providers may also have a portion of their messages sent via AWS SES. ...

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.