Here's something that tripped me up for a few hours: The <servername> element implies an actual machine, while a domain is unlikely to resolve to an IP address. This is confusing because <servername> will not work if you use a host name, but will work if you use a domain name.
To further the confusion, the docs state you can use an IP address, which furthers the case that it really will work with a host name (but it doesn't).
I vote for <servername> to change to <domainname>.
If it needs to work with IP addresses as well, perhaps add an element: <serverIP> (sub-element of servername).
Fair enough. I like domain (over domainname), since what does "name" really give you? It also matches the grammar definition for email addresses (RFC 822 6.1 calls the part after @ a domain).
Speaking of which, maybe we should change org.apache.mailet.MailAddress from getHost() to getDomain(). Then change the matchers checking Host to be named Domain instead.
I'm not sure which is right, but it seems these should be consistent.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
