You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Horde_Mail_Rfc822_Address@matchInsensitive().
Although it would require a bit of refactoring to work in this case since the matching emails are being stored as strings in a hashed array - although I will point out that this only works if the email in the key has previously been stored lowercase (which it shouldn't).
The reason will be displayed to describe this comment to others. Learn more.
Quoting Michael M Slusarz notifications@github.com:
***@***.***().
So, this still matches the user part in a case insensitive manner even
though it's technically supposed to be case sensitive?
Although it would require a bit of refactoring to work in this case
since the matching emails are being stored as strings in a hashed
array - although I will point out that this only works if the email
in the key has previously been stored lowercase (which it shouldn't).
They are NOW stored untouched since, I think last November (See Bug:
12505). They are lowered in code when the hash is built - so that's
easily changed. Thanks for the input.
The reason will be displayed to describe this comment to others. Learn more.
> ***@***.***().
So, this still matches the user part in a case insensitive manner even
though it's technically supposed to be case sensitive?
Yes. Whether to check for case insensitivity or not is a policy
decision. It can't be done when actually sending messages but may be
useful when it comes to local display concerns.
Not sure what this code is doing. But if doing something like
creating an event, and you have two e-mail addresses that match case
insensitively but not case sensitively, the safest option is probably
to add both to the invite.
FWIW, this will likely become more (not less) of an issue in the
future due to the rise of EAI addresses.
The reason will be displayed to describe this comment to others. Learn more.
Quoting Michael M Slusarz notifications@github.com:
> > ***@***.***().
>
> So, this still matches the user part in a case insensitive manner even
> though it's technically supposed to be case sensitive?
Yes. Whether to check for case insensitivity or not is a policy
decision. It can't be done when actually sending messages but may be
useful when it comes to local display concerns.
Not sure what this code is doing. But if doing something like
creating an event, and you have two e-mail addresses that match case
insensitively but not case sensitively, the safest option is probably
to add both to the invite.
Agreed.
FWIW, this will likely become more (not less) of an issue in the
future due to the rise of EAI addresses.
---
Reply to this email directly or view it on GitHub:
185ae67#commitcomment-10190902
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably need to make a more elaborated check, because technically the user part is case sensitive. I bet MMS has some library for that ;-)
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Horde_Mail_Rfc822_Address@matchInsensitive().
Although it would require a bit of refactoring to work in this case since the matching emails are being stored as strings in a hashed array - although I will point out that this only works if the email in the key has previously been stored lowercase (which it shouldn't).
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
185ae67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.