On 5 Jun 2020, at 15:02, Pete Resnick wrote:
On 5 Jun 2020, at 12:50, Fabian Blechschmidt wrote:
On 5 Jun 2020, at 19:45, Eric Sharakan wrote:
Hi, I have several smart mailboxes with a condition of "To Contains
sharakan". Someone just sent me an email with my last name
capitalized, and the condition wasn't satisfied.
Since email addresses are case-insensitive, shouldn't the filters
also be?
Perhaps it's because I'm using a more recent version (1.13.1), but at
the bottom of the "contains" drop down, you will see "Options", one of
which is "Case Sensitive". Is it checked or unchecked?
Wow, I had not noticed that before! And I certainly don't remember
setting the case sensitive flag on any of my conditions, but one was in
fact set. Once I cleared it, thing are working as expected.
Thanks for the tip!
-Eric
unfortunately is the local-part (before the @) technically case
sensitive.
https://stackoverflow.com/a/9808332/1480397
Not only is the local-part case insensitive, you would not believe the
awful things you can put in there (all sorts of symbols, and spaces,
and other obnoxiousness, if you enclose it in double-quotes). A lot of
that was to allow for routing through weird legacy systems. But that's
why it's set up that way.
The sentence I like the best is:
In short, you are safe to treat email addresses as case-insensitive.
Mostly, but no guarantees.
It is up to Benny, but at least I agree and think this is a bug which
should be fixed 😅
If you don't have "Case sensitive" turned on and it's not matching,
then yes, probably a bug.
pr
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
_______________________________________________
mailmate mailing list
[email protected]
https://lists.freron.com/listinfo/mailmate
_______________________________________________
mailmate mailing list
[email protected]
https://lists.freron.com/listinfo/mailmate
