165126 - Mixed letter cases in e-mail causes duplicate notification e-mails to the same person

Status: RESOLVED DUPLICATE of bug 117297

(Bugzilla :: Email Notifications, defect)

Description

[Jan Vlcinsky]

Steps to reproduce
==================
Supposing there exists an account [e-mail] and I am user with 
another account. [e-mail] hes set his e-mail notification as 
usually (do not send changes I made and notify me about every other change)
Edit or create a bug.
Fill into cc an e-mail "[e-mail]" (note the uppercase J)
Submit the change

Expected
========
[e-mail] will recieve just one notification e-mail about this 
bug/change.

Observed
=========
After bug was submited, program confirms adding comment/bug into database and 
reports sending e-mails
"Email sent to: [e-mail], [e-mail]"

This is true also for other fields
==================================
The same problem exists for other fields, where e-mail can be entered.

Comment 1

[J. Paul Reed [:preed]]

This isn't really a bug.

While most MTAs these days consider [e-mail] and
[e-mail] to be the same person, that's not guaranteed by the SMTP
RFC (2821, if you wanna look it up).

In fact, it specifically says that the mailbox local part of the address *must*
be treated with case sensitivity:

(from section 2.4):

   Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command
   and extension name keywords) are not case sensitive, with the sole
   exception in this specification of a mailbox local-part (SMTP
   Extensions may explicitly specify case-sensitive elements).  That is,
   a command verb, an argument value other than a mailbox local-part,
   and free form text MAY be encoded in upper case, lower case, or any
   mixture of upper and lower case with no impact on its meaning.  This
   is NOT true of a mailbox local-part.  The local-part of a mailbox
   MUST BE treated as case sensitive.  Therefore, SMTP implementations
   MUST take care to preserve the case of mailbox local-parts.  Mailbox
   domains are not case sensitive.  In particular, for some hosts the
   user "smith" is different from the user "Smith".  However, exploiting
   the case sensitivity of mailbox local-parts impedes interoperability
   and is discouraged.

Marking WONTFIX (although, this is really INVALID, but I do see your point,
which is why I'm marking it WONTFIX).

You can try to convince otherwise if you like...

Comment 2

[Bradley Baetz (:bbaetz)]

actually, um, this was fixed; see bug 117297.

The grounds for doing that was that accounts are currently case insensiteve,
mostly because mysql string comparisons are case insensitive.....

If they weren't, then sending twice would still be wrong, because we should have
aborted when the address wasn't a valid login_name.

reopening to mark as a dupe

Comment 3

[Bradley Baetz (:bbaetz)]

*** This bug has been marked as a duplicate of 117297 ***

Comment 4

[J. Paul Reed [:preed]]

I stand corrected. :-)

Thanks bbaetz!