> > The POP3 protocol does not have a domain name; there is nothing
> >to "detect" unless you impose a convention for the login name.
> yes thats exactly what the problem is.
No, I maintain that these are separate and orthogonal issues. SMTP knows
about users and domains, POP knows about mailboxes. There is no agreed upon
solution for adding "domains" to POP3, other than conventions; the current
system supports the conventions. What we need to address is the SMTP
delivery issue.
Consider the aforementioned example, which used the config.xml file. A
separate mailet is installed for each address. Those addresses are
forwarded to other addresses for processing. My solution moves that map
into a standard James structure (a table for JDBC use, serialized map for
file system), supported by a mapping mailet and a change in the user
management tools, rather than an ad hoc solution that requires updating
config.xml for each new address.
Look at JDBCAlias, for example.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
