Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OUTLOOK Delivery Options

Status
Not open for further replies.

psolis

MIS
Feb 28, 2002
47
US
I didn't see any option in exchange admin to create a reply address for a user that is different than the actual address. I could only figure out a workaround by using the outlook client with the pop3 setup.

I set up outlook 2000 on a server with one domain name (domain1.com) and added all the users - then forwarded the emails on domain2.com to go to domain1.com - all users were on a virtual server in Utah and now I changed the MX records to point to the IP address of the exchange server I set up internaly. So in the outlook client I add an exchange server setup and a POP3 setup. The exchange server gets all the mail and is checked at the user user@domain1.com and the POP3 is set up to send the mail out as user@domain2.com so when someone replys to the email it replys to user@domain2.com - when this happens, the mail hits the mailserver that domain2.com is sitting on and the alias files forward it off to the same user @ domain1.com. The problem is that when sending out mail - it uses the smtp server of domain2.com and it lags to be sent out - if I set up in the delivery options to use the exchange server to send out the mail, it goes instantainiously but it shows the user coming from domain1.com insted of domain2.com. I know this seems to be a dumb setup but it works great - its just slow to send out mail - is there a way to make the exchange server send out the mail and say that it is coming from user@domain2.com so people will reply back to that user and of course the forwarding pushes from the virtual server to the exchange server.
 
Outlook has never had this support with a MAPI profile.

Exchange has never done this. The solution is to use SMTP to send the message and fake addresses. Which you see works. Dan
Microsoft Exchange Support @ Microsoft
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top