[#JAMES-561] User aliasing does not work

JAMES Server

User aliasing does not work

Created: 09/Jul/06 09:01 PM Updated: 21/Nov/07 08:31 AM

Return to search

Component/s:

Matchers/Mailets (bundled)

Affects Version/s:

2.3.0, 3.0

Fix Version/s:

2.3.0

Time Tracking:

Not Specified

Resolution Date:

10/Jul/06 11:24 AM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Norman Maurer added a comment - 09/Jul/06 10:51 PM

After some debug it seems that the UsersRepositoryAliasingForwarding Mailet get not called. No time now to investigate time on this now :-(

[ Permlink | « Hide ]

Noel J. Bergman added a comment - 10/Jul/06 01:37 AM

Just to keep people following this in the loop, Norman observed on IM that "The problem is that ((JamesUser) user).getAliasing() return false."

[ Permlink | « Hide ]

Noel J. Bergman added a comment - 10/Jul/06 11:24 AM

Committed fix to both trunk and v2.3 branch. The check for an aliased name had the wrong polarity.

[ Permlink | « Hide ]

Vincenzo Gianferrari Pini added a comment - 11/Jul/06 12:21 AM

It works now for me. Thanks to all of the team for the work.
I'll test 2.3.0b2 again in production on the weekend of July 22-23.

[ Permlink | « Hide ]

Danny Angus added a comment - 21/Nov/07 08:31 AM

Closing issue fixed in released version.