Send / Receive emails for 2nd domain on Exchange client

[EssoOil]

Hi, thanks for reading this. I run Exchange 2007 under SBS 2008. I don't use SMTP as I prefer the POP3 connector and smarthost feature which works very well for sending and receiving emails both internally and externally on mydomain.com.

Some PC's use Outlook 2002 and communicate direct with the server and some use Outlook 2007 and synchronise with the server - but they all work fine.

I now need to be able to receive and send emails for a second domain (mydomain2.com). I know you can add a second domain to SBS (but dont know how) so first I thought I'd see if there is an easier way.

When I was looking at Outlook 2007 I noticed that on the 'Tools' menu under 'Accounts' it looks like I might be able to still add a standard POP3 email account (like you do when not using Exchange Server). Will this work?

I appreciate the Exchange server wont be downloading the emails but rather the PC will be doing this, just like it used to before we used exchange.

What are the implications when I log off and the emails in my In Box are moved back to the server?

Would I be able to send emails and would they leave via the PC and not the exchange server? (and arrive via the PC and not the Exchange Server).

What would happen if the user logged on using a different PC (would the Outlook settings for the second domain be remembered?).

Any help or advice about how I can send and receive emails from a different domain name on a PC connected to an Exchange Server would be greatly appreciated.

 

[58sniper]

POP3 is '80s technology that should be avoided if possible. It increases bandwidth, and sends credentials in the clear. It's incredibly inefficient as well.

In Exchange, you'd simply add the new domain as an accepted domain, add an address policy (so that users get an address on the new domain), point the MX record at your public IP, and you're done.

Keep in mind that configuring Outlook to retrieve POP3 is also a bad idea (when Exchange is available), and means that email won't be retrieved if that computer isn't on.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[EssoOil]

I only need the second domain to be available on one PC.

The reason I use the POP3 connector on SBS 2008 and not the SMTP / MX record method is...

1) My ISP offers loads of features and configuration options for mailboxes that make it far easier to manage via a simple control panel than Exchange would. I can create mailboxes and forward them to other mailboxes so I only need to deal with one mailbox for each user on Exchange. It really does keep things simple.

2) The main HUGE benefit is that if my SBS or Broadband connection is down incomming emails aren't bounced back - they are all stored on my ISP mailservers until my SBS downloads them (and they have guaranteed 99% uptime)

3) The smarthost feature means far fewer of my emails will be marked as spam compared with the SMTP method.

We only have 12 PC's and the POP3 connector and smarthost feature are working great for us.

Guess I'll just try it and see what happens.

 

[58sniper]

1) My ISP offers loads of features and configuration options for mailboxes that make it far easier to manage via a simple control panel than Exchange would. I can create mailboxes and forward them to other mailboxes so I only need to deal with one mailbox for each user on Exchange. It really does keep things simple.

You can do all of that easily in Exchange. Having POP3 means you have to configure a POP3 mailbox as well as an Exchange mailbox.

3) The smarthost feature means far fewer of my emails will be marked as spam compared with the SMTP method.

If that's the case, you're not setup correctly.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/