Skip to main content

One Year of FeedMail

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 out the door we are don't have any other major changes on the roadmap.

Of course if were are missing functionality that you would like to see please reach out to support. We are always open to new ideas.

Sustainability

One year later FeedMail is covering it's operating costs. That's a pretty significant milestone for sustainability of the service. When I first launched it I planned to cover most of the costs myself. However due to a handful of paying customers we have been able to cover our operating costs for the first year. Thank you!

It isn't the end of the journey though. Our costs were lower in the first year due to some introductory discounts and free trials. At this point I expect our costs to be steady however we are slowly burning savings.

Not only that but many of our users' purchases will last them multiple years. This means that new customers are critical to sustainability. It will likely be another 1-2 years before we start seeing significant recurring income.

But that is expected! We were aiming to provide a low-cost service so per-user revenue will be small. It will take more users to cover the minimum cost of operating the service and hopefully we can get there in a couple more years. In the meantime I am happy to cover the difference as I want the service for myself anyways.

Of course if you know someone who would like FeedMail it is always appreciated if you spread the word. If you do feel free to use our Referral Program to get a small reward for yourself and a longer trial for your referee.

Abuse

Abuse and Reputation were my biggest concerns launching the service. Sending email can be tricky business since reputation is everything. Not only that but we were sending user-controlled content which may be likely to set off automated filters. However we took care. Most of all ensuring that all emails were validated before sending them user-controlled content of any type as well as some rate limits and other protections.

In fact the only abuse that we identified was free-trial abuse. We saw a chain of accounts each with the same subscription list, each created as soon as the previous free-trial expired. This set off some of our basic heuristics and then we took manual action.

We definitely won't let our guard down but it is good to know that we are a much harder and less valuable target for abuse than other services on the internet.

Stability

Over the past year FeedMail has been quite stable. We had two major outages, neither of which caused notifications to be lost. There were also a handful of smaller problems such as issues with particular feeds or email addresses but these have become less frequent as the service matured. FeedMail now mostly runs itself as we continue to move slowly and steadily.

Looking Forward

The future is bright and boring, just the way I like it. FeedMail will continue to operate much like it does now. We will slowly add new features and refine our UX but we don't have any big changes planned.

If you have any ideas, suggestions or just want to say hi we are always happy to hear from our customers. Just reach out to our support address.

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.