[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Noel J. Bergman resolved JAMES-561:
-----------------------------------
Fix Version: 2.3.0
3.0
Resolution: Fixed
Committed fix to both trunk and v2.3 branch. The check for an aliased name had
the wrong polarity.
> User aliasing does not work
> ---------------------------
>
> Key: JAMES-561
> URL: http://issues.apache.org/jira/browse/JAMES-561
> Project: James
> Type: Bug
> Components: Matchers/Mailets (bundled)
> Versions: 2.3.0b2, 3.0
> Reporter: Vincenzo Gianferrari Pini
> Assignee: Norman Maurer
> Priority: Blocker
> Fix For: 3.0, 2.3.0
>
> If user A is an alias of user B ( or viceversa - remote manager help is
> misleading) messages sent to A have to go (and were going) to B's inbox. Now
> it ends in A's inbox, that should not even exist.
> The problem has been found by me using both "file" and "db" repositories
> under 2.3.0b2, but I expect it to occur also under 3.0.
--
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]
