Leandro Facchinetti

@marcandreuf & @rhythms06 Can y’all work together to modify the pull request and introduce the changes we discussed? First, introduce the “delete inbox” link at the bottom of each Atom...

I implemented this idea and it’ll be out on the next release of Kill the Newsletter! Thanks for the conversation.

Hmmm 🤔 It sounds like a good idea in principle. Of course, as you mentioned, there are costs associated with this, both in terms of storage but mainly in terms...

Hi y’all, I added support for attachments in version 2.0.5. They are included in the feed entries as a ``. Enjoy.

Hi y’all 👋 As you pointed out, unfortunately Kill the Newsletter! doesn’t support this scenario because we don’t want to get in the business of **sending** emails and having to...

Hi @joyoner, I hope at this point you’ve figured things out. Just in case, here’s the latest example configuration: https://github.com/leafac/kill-the-newsletter/blob/37caf3a24bcff9d620698dafbd115feff1f0f377/configuration/example.mjs The code and documentation for Kill the Newsletter! have been...

Hi @retiolus, Thanks for reaching out. The feed you mentioned doesn’t seem to exist anymore. I don’t know what could have happened. Can you please start over by creating a...

Hi everyone 👋 As some of you have determined, emails coming from other sources are processed by Kill the Newsletter! just fine, so the issue seems to be on Substack’s...

Hi y’all, Yes, unfortunately some newsletter publishers blocklist Kill the Newsletter! I wrote a paragraph about this in the [new version](https://kill-the-newsletter.com/) under the “Why can’t I subscribe to a newsletter...

Hi @Mynacol, Yes, the solution really ended up being monitoring the filesystem for updates on the certificate and restarting the email server. I’ll look into the other suggestions in the...