[ https://issues.apache.org/jira/browse/JAMES-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474003#comment-16474003 ]
ASF GitHub Bot commented on JAMES-2389: --------------------------------------- Github user chibenwa commented on the issue: https://github.com/apache/james-project/pull/114 Not necessarily... While being more simple, the restriction (to avoid case variation) still stands without address normalization (to lower case). If I want to use `benoit.tell...@domain.com`, forbidding the use of `benoit.tell...@domain.com` avoids confusions, but I can not see reasons to restrict it to `benoit.tell...@domain.com`. (Though I do agree case normalisation works badly... We would need a mailet allowing to normalize to the right case variation in the example I gave above.) But that is just my opinion here. Maybe more feedback would be constructive... > Inbox User Name is case sensitive so wrong inbox generated > ---------------------------------------------------------- > > Key: JAMES-2389 > URL: https://issues.apache.org/jira/browse/JAMES-2389 > Project: James Server > Issue Type: Bug > Components: data > Affects Versions: 3.0.1 > Reporter: mostafa vtp > Priority: Major > > Hi > When sending an email to a user with no lower case user name, a new Inbox is > created for that user. > For example assume: > I have a user with "test1@t.t1" name for example. When I send mail to > "*Test1*@t.t1", James accepts it but *creates a new mail box* with > "Test1@t.t1" name in database(JAMES_MAILBOX table in USER_NAME field) *and > "test1@t.t1" user can't see the email.* > It seems user existence check is case insensitive but mailbox creation is > case sensitive. > James should not create a new inbox in this situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org