# Evolution Mail Users Easily Trackable Part 3, One Year On

One year ago this week, [I wrote](/Evolution_Mail_Users_Easily_Trackable)
([twice](/Evolution_Mail_Users_Easily_Trackable_Part_2)) about some privacy
problems that were being experienced by users of the [Evolution
Mail](https://help.gnome.org/evolution/) email client from [the Gnome
project](https://www.gnome.org). Problems that they turned out to have known
about for years, and [weren't
happy](https://gitlab.gnome.org/GNOME/evolution/-/work_items/3095#note_2499294)
about me publicising.

A few days later, [I wrote](/Fun_with_Gzip_Bombs_and_Email_Clients) about a bug
that allows an email sender to easily consume all of an Evolution Mail users
free disk space, within seconds of the recipient simply opening an email. Also,
a bug with how they handle caching of attachments.

One year on, none of these problems have been dealt with:

- [https://gitlab.gnome.org/GNOME/evolution/-/work_items/3101](https://gitlab.gnome.org/GNOME/evolution/-/work_items/3101)
- [https://gitlab.gnome.org/GNOME/evolution/-/work_items/3095](https://gitlab.gnome.org/GNOME/evolution/-/work_items/3095)
- [https://gitlab.gnome.org/GNOME/evolution/-/work_items/2727](https://gitlab.gnome.org/GNOME/evolution/-/work_items/2727)
- [https://bugs.webkit.org/show_bug.cgi?id=259787](https://bugs.webkit.org/show_bug.cgi?id=259787)

If you're an Evolution Mail user, you should know that you're using software
that is managed by people who don't care about these issues. They are happy to
create an issue upstream for a dependency and then wash their hands of it,
letting it rot for years.

I switched to using [Claws Mail](https://www.claws-mail.org/) with the light
HTML extension because of this, and I have been using it for most of the last
year. But to be honest, I prefer Evolution Mail's UI, and I missed it. It is an
otherwise good piece of software, and it pains me to see it's development
managed so poorly.

I recently switched back to using Evolution Mail, but only after I made it
safe(r) to use by [sanitising my incoming email](/Sanitising_Email) at delivery
time. I filter my incoming email through
[Sanimail](https://gitlab.com/grepular/sanimail) so that the HTML parts that
cause network traffic without clicking "Load Remote Content" are removed, thanks
to `--policy standard`. The gzip bomb and cache problems are addressed by a
combination of Sanimail's `--remote-inline` option and `--remote-max-bytes` and
`--remote-item-max-bytes` defaults.

There are many benefits to using Sanimail; making Evolution Mail safer to use is
only one of them. Check out [the
documentation](https://gitlab.com/grepular/sanimail/-/blob/main/README.md?ref_type=heads)
for the rest.

See you in a year (probably) for the next enthralling chapter of, "yeah, this
shit is still broken 🤦‍♂️"