Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Exchange 2003: Branding outgoing e-mails with a different domain?

Posted on 2005-05-04
Medium Priority
Last Modified: 2010-04-18
A client of ours owns two domain names. For future reference - and simplicity - let's call them 'domain1.com' and 'domain2.com'.

The MX record for domain1.com points to a Windows Server 2003 (Small Business Edition) machine running Exchange 2003.

The MX record for domain2.com points to a POP server hosted by a local ISP. We have set up a POP3 connector on their exchange server to grab the e-mail from that account and dump it into their exchange mailbox. So far so good. But, quite naturally, any e-mail they send comes out as 'soandso@domain1.com'. For legal reasons, our clients are insisting that the e-mails need to be sent from 'soandso@domain2.com'.

To make matters more interesting, the user who needs this particular functionality is a mobile user, roaming the country, laptop in hand, err, lap... sort of thing. This means we can't just set their Outlook client up to just send and recieve from the local ISP server.

So, my question is this: Is there a simple way to get Exchange server to brand outgoing e-mails from a single 'domain1.com' user as 'soandso@domain2.com'?  Can this be done securely? I have tried just changing the 'from:' field, but e-mails just get rejected with a permissions error. They (hopefully...) will be accessing the server via VPN. So I could assign them a static IP address if that's necessary.

If Exchange can't do it natively, I'd wouldn't mind the name of any software under A$500 or so that could also help. Over that price and it'd be cheaper to set up an IMAP server on a Linux box.

Any help would be grealy appreciated.
Question by:brogga
  • 2
LVL 10

Accepted Solution

Seelan Naidoo earned 1500 total points
ID: 13926184
Try adding 2nd SMTP address for domain2. Then set it as primary address within AD for all users.

Author Comment

ID: 13932529
I have tried this previously with no success...

But I figured you probably knew what you were talking about, so I upgraded to Exhange SP1, turned on relaying for everyone, turned off anonymous SMTP access, completely deleted the domain1.com e-mail address for the user in question, then made their domain2.com e-mail address primary.

And, it worked! Outgoing e-mail was now correctly identified. ... but the exchange mailbox was now no longer recieving e-mail from the POP3 connector. (Outlook Remote Access stopped working for that user, too...) I would watch it just vanish into thin air with no error messages or anything. Other mailboxes could recieve e-mail from that same connector just fine, though. So I made a new user 'cheaphack', and put a forwarder on their inbox, pointing it to the user with the broken address.

So now everything looks fine. I think it's a little sick behind the scenes, but as far as the user is concerned everything is gold.

I'll leave this question open a little longer, in case anyone wants to add a few words of wisdom for future generations, or try to explain the odd behaviour. But thanks for pointing me back in the right direction.

Author Comment

ID: 13933426
Solution was to create a recipient policy for @domain2.com

Boy do I feel stupid...

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Loops Section Overview
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question