Opened 13 years ago
Last modified 11 years ago
#188 reopened defect
Matching of identities appears to be case-sensitive
Reported by: | Owned by: | ||
---|---|---|---|
Version: | 0.6.8 | Keywords: | |
Cc: | michael.roland@…, Mozilla@… |
Description
Since version 0.6.0rc1 (I previously used 0.5.12) it seems as if recipient addresses are now matched against existing identities in a case-sensitive manner (i.e. Michael.Roland@... is no longer the same as michael.roland@...). The version 0.5.12 seemed to match case-insensitively.
Although, I have to admit that the new behavior complies to the RFC in that the user part of mail addresses is (or may be) case-sensitive, I would at least like to see an option to enable case-insensitive matching. (I the same way as there is an option to "ignore full name while comparing email addresses with exisiting identities".)
As I'm not sure if this is an intended change or a bug in rc1, I will leave this ticket a defect report rather than an enhancement request for the moment.
Kind regards, Michael
Change History (6)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Hi Michael,
rc1 was completely broken, matching should still be case-insensitive (related to #181) Please check if this issue reoccurs with rc2, closing the ticket for now.
Nice regards and thanks for the report, Rene
comment:3 Changed 13 years ago by
Cc: | michael.roland@… added |
---|---|
Resolution: | duplicate |
Status: | closed → reopened |
Summary: | Allow case-insensitive matching of identities → Matching of identities appears to be case-sensitive |
Version: | → 0.6.0rc2 |
Hallo Rene,
the problem still exists with rc2. When I reply to an email with the header field
From: Roland Michael <Michael.Roland@PROVIDER5>
it will not trigger the identity "Michael Roland <michael.roland@PROVIDER5>". But when I change the identity's settings to "Michael Roland <Michael.Roland@PROVIDER5>" (i.e. change case of email address to match the from field), the identity is found.
I will try to record some log files during the next week.
Kind regards, Michael
comment:4 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Hi Michael,
right, catched the problem. It is fixed in [218b2bba4f6b2c] and part of rc3.
The problem was, that in your case the first time the FullName was ignored while comparing with the existing identities. Which is right, the probably adapted FullName should have been used later - therefore the later checks for existing identities failing in your case. Which is all like it should, but the already found existing identity was not remembered, which is done now.
Happy new year, Rene
comment:5 Changed 12 years ago by
Cc: | Mozilla@… added |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Version: | 0.6.0rc2 → 0.6.8 |
It seems this bug has crept back in sometime before/as of version 0.6.8. Virtual Identity does not match existing stored entries with different case. Let me know if you need me to provide more details....
comment:6 Changed 11 years ago by
I experience the very same issue in 0.8.7. Any chance it gets fixed (again)? Thanks a lot.
Update:
I just went though the log file and it seems as if the proper identitity is found at first but dropped in a second cycle.
Line
suggests that the proper identity is found at first (id24 is the identity that I expected it to use), but then in
the identity is no longer found and the default identity (id1) is used as a base for the new virtual identity "Michael Roland <Michael.Roland@PROVIDER5>".
Kind regards, Michael