Philip B. Howells wrote:
I have considered that last option, however, I was sorta hoping to cheat and use all of my domains, having them as seperate entities.
Eventually you'll find that "cheating" will limit your choice of clients, as it ruins interoperability. Don't try to be clever when you don't have to. Good admins are lazy. :)
I have some very non-technical customers that want a domain name, and they want their email to be the same; [EMAIL PROTECTED] However, I may still do that, only having ssl for one domain.
I'm not sure what you mean by the last sentence, but your clients can all have domains. Their email address can use their domain. It's only the settings in their own email client for the send/receive servers that needs to stick to the one domain in order to have proper SSL security. No one that they communicate with will ever see that, so each of your customers gets their vanity domain, along with good security with only that one compromise that they'll forget the next day anyhow.
------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
