Charles Marcus wrote, at 10/06/2008 04:27 PM: > I'm going to be writing up instructions for users who will be using > these new domains how to set up their mail clients (Thunderbird mainly, > but I also include instructions for the Microsoft clients)... so I > wanted to confirm that I can use the hosts 'smtp.example1.com' and > 'smtp.example2.com' for their SMTP (outbound) server setting in their > clients. [snip] > Well... it does, if I want users getting mail at example1.com to be able > to reference smtp.example1.com in their client settings. > > It will be awkward to tell a user to put smtp.fred.com for their > outbound server setting, if their email address is [EMAIL PROTECTED], don't > you think?
If the name resolves, they'll connect to your server. However, if you're going to offer STARTTLS, you have a problem. How are you going to support all of these different domains in a single certificate? Currently, you can't, so you'll need to pick a name (mail.example.com) for your SMTP/IMAP/POP3 server and stick with it. Otherwise, you'll need to use a more complicated approach, such as multiple instances each with their own certificate. Users can't infer the server settings from an email address, so you'll have to explicitly provide it, anyway. The problems caused by the wrong certificate are likely to create more support calls.
