FeedMail Blog

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 " 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

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

FeedMail was offline for 26 minutes. During this period the website was unavailable and feed updates were not sent. This outage was caused by our CoreDNS resolver failing. While FeedMail continued operating normally for a while as most operations such as feed fetching and mail sending don't rely on the Kubernetes DNS server FeedMail does use the Kubernetes DNS server for a few operations such as connecting to it's own database. When database connections needed to be refreshed the DNS resolution failure caused FeedMail to become unhealthy and it was unable to continue operation. Timeline All times are in UTC . 13:28 Start FeedMail goes down. Website is offline and feeds are not being checked. 13:32 Detection Automated monitoring reported that the FeedMail website was unavailable. 13:38 Automated monitoring reported that feeds were not being fetched. 13:42 Kubernetes cluster update was started. 13:53 Mitigated FeedMail was restored to operation. The website was ag

FeedMail now has some options for bulk editing. You can edit the following attributes of multiple subscriptions at the same time: Target (which email or digest the subscription notifies). Notification body (feed content, scraped full-text or no content). We hope this is helpful, especially for users moving between email addresses or moving lots of subscriptions to digests.

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 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.

Hi, It's Kevin, the founder of FeedMail. Wow, time really flies. I missed FeedMail's birthday by a couple of days. On November 2nd 2021 I announced FeedMail publicly . At the beginning I was going to make FeedMail just for myself. An RSS-to-email service that fit my needs. However I also wanted a way to provide email-subscriptions to my blog. I decided to roll these together and make FeedMail publicly available. This necessitated some extra features such as signup and billing but I think it was the right choice. One year later I'm pretty happy with what FeedMail has become. Features I feel that FeedMail has all of the core features it needs. There are a few customer requests and some UX improvements in the queue but it seems that we now cover most features that someone would want out of a RSS-to-email service. The last big feature was releasing digests two months ago and with that our the door we are don't have any other major changes on the roadmap. Of course if were

Thanks everyone who has helped evaluate digests over the past weeks. All of the blocking issues are now resolved and we will be releasing them soon. Once digests are officially released there will be links to them from the FeedMail site and pricing information added to our homepage. Price Increase Part of the purpose of the beta was to evaluate the cost of providing digests and see how they would be used. We have decided upon final pricing which we hope will be sustainable for years to come. Digests issues will cost 1 credit per 5 feeds. Note that this is feeds included in an issue , not total feeds that target a particular digest. It also does not matter how many new items a feed has. So if you have a digest with 200 feeds configured but this morning's issue only has new items from 2 of them it will cost 1 credit. If 14 feeds update the next day that issue will cost 3 credits. If the day after has no updates it will cost nothing. This new pricing takes effect no earlier than 202