> I reckon that if we could detect the hostname that users [thought they] were > connecting to for POP3 then the problem would start to evaporate.
The POP3 protocol does not have a domain name; there is nothing to "detect" unless you impose a convention for the login name. > one of the issues is that we'd like people's login username > to [equal] their mailaddress username for each domain. Mail addresses don't map 1:1 with POP3 identities. I may have, and in fact often have, multiple e-mail addresses funnel into a single POP3 mailbox. Other addresses may exist for the sole purpose of contacting some bit of mailet programming, e.g., a list address or monitor. Actually, it looks as if a good chunk of this is already done. :-) The [user, domain] -> address mapping looks like what Serge Knystautas had in mind with the JDBCAlias mailet (http://jakarta.apache.org/james/javadocs/org/apache/james/transport/mailets /JDBCAlias.html), but it doesn't appear supported by the user management tools. I am guessing that his source address column is assumed to have the domain embedded within it. --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
