Peter,
You probably know all of this, but let me recap for those who haven't read
this part of the code. In the current code, aliasing and forwarding are
very similar. An alias is a local username, whereas a forwarding address is
an SMTP address. If there is an alias, then it replaces the current user
name in James.storeMail. If there is a forwarding address, then
James.storeMail calls sendMail with the forwarding address.
I wouldn't change this right now, other than to clarify the documentation.
The user repository can be (and should be) revisited post-2.1 release.
--- Noel
-----Original Message-----
From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 16:13
To: 'James Developers List'
Subject: Aliasing
All,
The aliasing implementation in James appears to be backwards. An alias
is an "additional name" (see www.m-w.com). So what you'd expect is that
mails sent to an alias would be delivered to the base username. But in
fact, if you set things up following the docs in the
RemoteManagerHandler help, you wind up with the opposite situation.
This is further complicated by the fact that the set/getAlias methods of
the JamesUser class are misnamed - the member being set is in fact a
base username, and the JamesUser is the alias.
I'd like to fix this. Thoughts? Disagreements?
--Peter
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
