| truemagic |
8 Apr 2026 10:38 AM |
Quote:
Originally Posted by jarland
(Post 647071)
It looks like stripped down sieve filtering. Honestly I get it. Even the more knowledgeable people screw themselves with sieve filters and then blame their mail host. When you're trying to make something for people of all different levels of competence, simple has value.
|
I've experienced sieve scripts as well, and they can easily go wrong, so I prefer a UI that helps shape the sieve script behind the scenes, just like RoundCube and Horde do, where they allow you to export the sieve script from whatever you configured in the UI. That's really cool.
I understand not everyone uses filtering. In my early years of using email, everything just went into the main inbox, but as I got older, I started to appreciate having everything organized into folders, which saves me time and reduces the mess.
Quote:
Originally Posted by hadaso
(Post 647225)
Most users have only one email address and don't understand the concept of "envelope". They would filter on "To" or "Cc" to separate mail that only have them on "Cc" (or "Bcc") from mail where they are the main recipient.
|
Quote:
Originally Posted by JeremyNicoll
(Post 647231)
But if a user only receives a mail because they were BCCed, nothing in "To:" or "CC:" is reliably always relevant. Of course on non-spam email "To:" &/ "CC:" will sometimes be relevant.
|
Yes, that's where I appreciate filtering by header. Even Netflix sends marketing emails with a generic @netflix.com, but you can filter them by header, for example, if it does not contain "List-Unsubscribe: netflix.com" ? straight to Trash :D
Quote:
Originally Posted by dojyx
(Post 647234)
Additionally, the FROM filter allows only one email address.
|
Exactly, that's what makes it very hard to use for "advanced" users like me lol, because my needs are more complex than having just one condition. A workaround is to do it on a client, for example FairEmail, but that's a pain.
|