[ http://issues.apache.org/jira/browse/JAMES-508?page=comments#action_12413193 ]
Noel J. Bergman commented on JAMES-508: --------------------------------------- I don't have a problem with adding isLocalEmail to eventually replace isLocalUser, but we should keep isLocalServer, since there are some checks to just see if that domain is locally hosted. > Make MailetContext.isLocalUser domain aware > ------------------------------------------- > > Key: JAMES-508 > URL: http://issues.apache.org/jira/browse/JAMES-508 > Project: James > Type: Improvement > Components: James Core > Reporter: Stefano Bagnara > Assignee: Stefano Bagnara > Fix For: 2.4.0 > > Trying to resume an old task: > Currently we run MailetContext.isLocalServer(domain) and in the following > call MailetContext.isLocalUser(local-part). > Having 2 different calls does not allow us to check users associated to a > specific domain. > The proposed solution is: > 1) change the isLocalUser documentation saying that you MUST provide the > full email address > 2) eventually allowing to use names without @ (the system will consider > automatically @localhost) > This would replace the current client code: > mailetContext.isLocalServer(recipient.getHost()) && > mailetContext.isLocalUser(recipient.getUser()) > With > mailetContext.isLocalEmail(recipient) > IMHO this is a good improvement over the current API way to resolve local > users (double call) and this would allow us to implement automatic > virtualhosting support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
