You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Vincenzo Gianferrari Pini (JIRA)" <se...@james.apache.org> on 2006/07/09 16:02:29 UTC
[jira] Created: (JAMES-561) User aliasing does not work
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: 3.0, 2.3.0b2
Reporter: Vincenzo Gianferrari Pini
Priority: Blocker
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-561) User aliasing does not work
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Norman Maurer reassigned JAMES-561:
-----------------------------------
Assign To: Norman Maurer
> 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: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Assignee: Norman Maurer
> Priority: Blocker
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
(JAMES-561) User aliasing does not work
Posted by "Noel J. Bergman" <no...@devtech.com>.
I just found and fixed it. Unfortunately, I'm 30,000 feet in the air, but as soon as I land in LA this evening (about 4 hours from now), I'll commit the fix, unless someone has beaten me to it.
> Norman observed on IM that "The problem is that
> ((JamesUser) user).getAliasing() return false."
Actually, no. I tested for that, and it was working just fine. The problem was elsewhere in the UserRepositoryAliasForwarding mailet. One character. Just one missing character in the condition of an if statement.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-561) User aliasing does not work
Posted by "Noel J. Bergman (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=comments#action_12419928 ]
Noel J. Bergman commented on JAMES-561:
---------------------------------------
Just to keep people following this in the loop, Norman observed on IM that "The problem is that ((JamesUser) user).getAliasing() return false."
> 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: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Assignee: Norman Maurer
> Priority: Blocker
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-561) User aliasing does not work
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=comments#action_12419917 ]
Norman Maurer commented on JAMES-561:
-------------------------------------
After some debug it seems that the UsersRepositoryAliasingForwarding Mailet get not called. No time now to investigate time on this now :-(
> 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: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Priority: Blocker
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-561) User aliasing does not work
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Stefano Bagnara updated JAMES-561:
----------------------------------
Fix Version: 2.3.0b3
(was: 2.3.0)
> 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: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Assignee: Norman Maurer
> Priority: Blocker
> Fix For: 3.0, 2.3.0b3
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-561) User aliasing does not work
Posted by "Vincenzo Gianferrari Pini (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=comments#action_12420117 ]
Vincenzo Gianferrari Pini commented on JAMES-561:
-------------------------------------------------
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.
> 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: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Assignee: Norman Maurer
> Priority: Blocker
> Fix For: 3.0, 2.3.0b3
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-561) User aliasing does not work
Posted by "Noel J. Bergman (JIRA)" <se...@james.apache.org>.
[ 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-561) User aliasing does not work
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Stefano Bagnara updated JAMES-561:
----------------------------------
Fix Version/s: (was: 3.0)
> User aliasing does not work
> ---------------------------
>
> Key: JAMES-561
> URL: http://issues.apache.org/jira/browse/JAMES-561
> Project: James
> Issue Type: Bug
> Components: Matchers/Mailets (bundled)
> Affects Versions: 3.0, 2.3.0b2
> Reporter: Vincenzo Gianferrari Pini
> Assigned To: Norman Maurer
> Priority: Blocker
> Fix For: 2.3.0b3
>
>
> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org