I have a situation that I don't think is easily solvable. I manage an Exchange server environment on domain A. I had a need to create a separate POP3/SMTP server for sending out mail campaigns as domain B. The idea here being that users in domain A could request a POP3 mailbox on this standalone IIS box, send mail through it's SMTP server and out to their recipients as user@domainB.com and retrieve the mail sent back to the POP3 mailbox. Well I figured out how to add the POP3 and SMTP information to an existing MAPI Profile so that I could manage to the messages in Outlook 2003, and I can connect to the POP server all day long and retrieve mail sent to user@domainB.com, but I hit a snag when I went to try and send a message AS user@domainB.com from Outlook. You see, this IIS server hosting these POP3 mailboxes is not a member server in any domain, least of all the same domain that hosts the Exchange environment. In fact, Active Directory isn't even installed on this IIS server. It's completely stand-alone. To make matters a little worse, the IIS server is in our corporate DMZ so there are firewalls between it and the Exchange servers/Domain Controllers in domainA. So the question is, how do I allow user@domainA to send email AS user@domainB in Outlook under these circumstances, and not create a separate MAPI profile? That's the kicker - it must be able to work within user@domainA's existing MAPI profile. $1 trillion to the person who can make this happen (yeah right!)
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!