cmellon
asked on
Exchange 2003: Recipient Email Addresses
Hi All,
Not sure how to word this problem but here goes.
In exchnage we have our default email address set, i.e. everyone's default mail address is username@mydomain.com
I now have another email account, lets say NewDomain.com. I have set up a pop3 connector to download the mail, and i have added the email address to the users list of email addresses.
so in user properties the users exchange email address page has the two entries:
username@mydomain.com
user@newdomain.com
The new email account has been setup slightly differently, i.e. internal mail the users email address is username@mydomain.com, but the new email address is user@newdomain.com.
All works fine with downloading the email, but then when exchange goes to deliver the email, the event log reports :
The message <id: {D9D58D9C-ADE0-422A-BD80-1
Original Recipient: <user@newdomain.com>.
- routed via domain substitution to <user@mydomain.com>.
Is there anyway to stop this, i.e. the mail should be delivered to username@mydomain.com, not user@mydomain.com (user@mydomain.com does not exist, and the mail is intended for username@mydomain.com)
I have searched the net and cannot seem to find a solution.
I assume that if i change the email address to username@newdomain.com it would route correctly, but i cannot do this as the user is using the email address user@newdomain.com.
Any help would be greaty appreciated.
Thanks
Craig
Not sure how to word this problem but here goes.
In exchnage we have our default email address set, i.e. everyone's default mail address is username@mydomain.com
I now have another email account, lets say NewDomain.com. I have set up a pop3 connector to download the mail, and i have added the email address to the users list of email addresses.
so in user properties the users exchange email address page has the two entries:
username@mydomain.com
user@newdomain.com
The new email account has been setup slightly differently, i.e. internal mail the users email address is username@mydomain.com, but the new email address is user@newdomain.com.
All works fine with downloading the email, but then when exchange goes to deliver the email, the event log reports :
The message <id: {D9D58D9C-ADE0-422A-BD80-1
Original Recipient: <user@newdomain.com>.
- routed via domain substitution to <user@mydomain.com>.
Is there anyway to stop this, i.e. the mail should be delivered to username@mydomain.com, not user@mydomain.com (user@mydomain.com does not exist, and the mail is intended for username@mydomain.com)
I have searched the net and cannot seem to find a solution.
I assume that if i change the email address to username@newdomain.com it would route correctly, but i cannot do this as the user is using the email address user@newdomain.com.
Any help would be greaty appreciated.
Thanks
Craig
ASKER
Can you not have multiple aliases to one user?
The problem is that the email addresses already exist and its not possible to change (i.e. business cards have been printed)
so the alias is different, internally the mail is username@mydomain.com but the new external address is user@newdomain.com, but i need one account to get both email addresses, i.e. username@mydomain.com and also user@newdomain.com.
Is this not possible in exchange? does the alias have to be the same for every email address?
Regards
Craig
The problem is that the email addresses already exist and its not possible to change (i.e. business cards have been printed)
so the alias is different, internally the mail is username@mydomain.com but the new external address is user@newdomain.com, but i need one account to get both email addresses, i.e. username@mydomain.com and also user@newdomain.com.
Is this not possible in exchange? does the alias have to be the same for every email address?
Regards
Craig
cmellon,
you should have a default recipient or some other recipient policy which tells exchange which domains it's responsible for. Check under Recipients, Recipient Policies in the ESM and see if you have a policy that specifies both @mydomain.com and @newdomain.com.
here's a tutorial on how to add it:
http://www.msexchange.org/tutorials/MF010.html
next you can add a second policy that will automatically assign the new address in the proper format, but we can worry about that later.
the only downside to this is that the reply mail will always have the sent smtp of the primary email address.
hth,
kris.
you should have a default recipient or some other recipient policy which tells exchange which domains it's responsible for. Check under Recipients, Recipient Policies in the ESM and see if you have a policy that specifies both @mydomain.com and @newdomain.com.
here's a tutorial on how to add it:
http://www.msexchange.org/tutorials/MF010.html
next you can add a second policy that will automatically assign the new address in the proper format, but we can worry about that later.
the only downside to this is that the reply mail will always have the sent smtp of the primary email address.
hth,
kris.
ASKER
Hi Kris,
I have this setup correclty (Only difference is that i cannot specify exhcnage as been responsible for this domain, the reason being that there are a lot of external users with mailboxes from the newdomain.com, and because of bandwidth etc its better for them to collect mail straight from isp)
So basically i have the newdomain.com setup, my primary email account is mydomain.com, so in my user propertiers I have two email addresses, one for the primary which works fine, craigmellon@mydomain.com and then another one for craig@newdomain.com. The mail comes into exchange, and looking at the event logs it receives the email correctly, but then when it tries to deliver into my mailbox it tries to substitute craig@newdomain.com with craig@mydomain.com but there isn;t a user specified with the email address craig@mydomain.com.
I think from your email above, that the second policy is the thing i need to do, to automatically assign the new address, not sure how to do this though.
The downside you mentioned about when sending emails out, is there anything that can be done about this, or will exchange always put the senders address as the primary email domain.
Thanks
Craig
I have this setup correclty (Only difference is that i cannot specify exhcnage as been responsible for this domain, the reason being that there are a lot of external users with mailboxes from the newdomain.com, and because of bandwidth etc its better for them to collect mail straight from isp)
So basically i have the newdomain.com setup, my primary email account is mydomain.com, so in my user propertiers I have two email addresses, one for the primary which works fine, craigmellon@mydomain.com and then another one for craig@newdomain.com. The mail comes into exchange, and looking at the event logs it receives the email correctly, but then when it tries to deliver into my mailbox it tries to substitute craig@newdomain.com with craig@mydomain.com but there isn;t a user specified with the email address craig@mydomain.com.
I think from your email above, that the second policy is the thing i need to do, to automatically assign the new address, not sure how to do this though.
The downside you mentioned about when sending emails out, is there anything that can be done about this, or will exchange always put the senders address as the primary email domain.
Thanks
Craig
so it sounds like if you assign all your users with an address of firstname@mydomain.com it might work. is this what you're thinking as well?
as for the smtp sender, the only way to get around this is to use a 3rd party product or write your own event sink. i think ivasoft makes something to handle this.
kris.
as for the smtp sender, the only way to get around this is to use a 3rd party product or write your own event sink. i think ivasoft makes something to handle this.
kris.
ASKER
Is there anyway i can put something in Exchange to route emails received for craig@newdomain to craigmellon@mydomain.com?
Hi,
Yes there is, you can use either Wizard Rules or just make sure to change the user settings (in AD Users & Computers)that makes sure mail is being send through...
Yes there is, you can use either Wizard Rules or just make sure to change the user settings (in AD Users & Computers)that makes sure mail is being send through...
ASKER
Hi rhandels,
In Active Directory on user properties i have the address in there, i have craigmellon@mydomain.com and craig@newdomain.com.
The problem i have is that when i receive email, the event log records that the email has been received for craig@newdomain.com and that it is routing it via domain substitution, and then changes the address to craig@mydomain.com. And i never receive the email.
Is there any way to stop it doing the domain substitution?
If my newdomain email address was craigmellon@newdomain.com it would work find, but unfortunately i cannot change this, and we have about 50+ accounts which different aliases for different domains.
Any ideas?
Below is a copy of the event log message:
The message <id: {D9D58D9C-ADE0-422A-BD80-1
Original Recipient: <craig@newdomain.com>.
- routed via domain substitution to <craig@mydomain.com>.
In Active Directory on user properties i have the address in there, i have craigmellon@mydomain.com and craig@newdomain.com.
The problem i have is that when i receive email, the event log records that the email has been received for craig@newdomain.com and that it is routing it via domain substitution, and then changes the address to craig@mydomain.com. And i never receive the email.
Is there any way to stop it doing the domain substitution?
If my newdomain email address was craigmellon@newdomain.com it would work find, but unfortunately i cannot change this, and we have about 50+ accounts which different aliases for different domains.
Any ideas?
Below is a copy of the event log message:
The message <id: {D9D58D9C-ADE0-422A-BD80-1
Original Recipient: <craig@newdomain.com>.
- routed via domain substitution to <craig@mydomain.com>.
Hi,
Just a small note, do you have multiple MX records for those domains??? So the mydomain and newdomain, do they point to your mailserver?? Else you cannot recieve multiple domains, maybe this is the problem..
Just a small note, do you have multiple MX records for those domains??? So the mydomain and newdomain, do they point to your mailserver?? Else you cannot recieve multiple domains, maybe this is the problem..
ASKER
Hi Rhandels,
The email is collected using POP3 connectors. I am aware of the way to do this by pointing the MX records to our server, but we cannot do that, as we have hundreds of external agents that have email accounts. So from our point of view its much easier to let the agents use the ISPS webmail functions than for us to provide email from our servers to them.
Also we only have an ISDN line for the whole office (Although broadband will be fitted in february) so we just wouldn;t be able to handle the amount of traffic for all external agents as well as internal employees (They send large emails throughout the day, such as brochures etc)
Our email provider (oneandone) allows me to create mailboxes for each user, which i have done, and i can get exchange to collect the mail and put it in the right mailbox, but that will involve me creating 40+ pop connectors in exchnage, so i was hopeing to use the master mail account which collects all emails to unknown users on the domain and then get exchange to route them to the relevant people.
Craig
The email is collected using POP3 connectors. I am aware of the way to do this by pointing the MX records to our server, but we cannot do that, as we have hundreds of external agents that have email accounts. So from our point of view its much easier to let the agents use the ISPS webmail functions than for us to provide email from our servers to them.
Also we only have an ISDN line for the whole office (Although broadband will be fitted in february) so we just wouldn;t be able to handle the amount of traffic for all external agents as well as internal employees (They send large emails throughout the day, such as brochures etc)
Our email provider (oneandone) allows me to create mailboxes for each user, which i have done, and i can get exchange to collect the mail and put it in the right mailbox, but that will involve me creating 40+ pop connectors in exchnage, so i was hopeing to use the master mail account which collects all emails to unknown users on the domain and then get exchange to route them to the relevant people.
Craig
ASKER
Hi All,
This is just incase anyone else finds this and is having the same problem.
I knew this would be something simple, so heres how i did it.
In the pop3 connector settings in Exchange, select edit on the mailbox (Which is newdomain in my case) and then click routing rules. I then just added a line to route emails to craig@newdomain.com to my mailbox, and hey presto it works.
if the first part of my email address at the new domain matches the existing domain then everything is ok, i.e. if i had craigmellon@newdomain.com then i would assume everything would route through as expected using domain substitution, but because the first part was different domain substitution was trying to direct email to craig@newdomain to craig@mydomain.com which didn;t exist. Putting the routing rule on the pop3 connector solved this problem by routing mail received for craig@newdomain straigh to my mailbox.
Thanks for everyones responses,
Regards
Craig
This is just incase anyone else finds this and is having the same problem.
I knew this would be something simple, so heres how i did it.
In the pop3 connector settings in Exchange, select edit on the mailbox (Which is newdomain in my case) and then click routing rules. I then just added a line to route emails to craig@newdomain.com to my mailbox, and hey presto it works.
if the first part of my email address at the new domain matches the existing domain then everything is ok, i.e. if i had craigmellon@newdomain.com then i would assume everything would route through as expected using domain substitution, but because the first part was different domain substitution was trying to direct email to craig@newdomain to craig@mydomain.com which didn;t exist. Putting the routing rule on the pop3 connector solved this problem by routing mail received for craig@newdomain straigh to my mailbox.
Thanks for everyones responses,
Regards
Craig
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When adding a new e-mail address, did you make sure to only add a new mail address?? Looks like the alias (the part that comes before the @domain.com) has been changed. You can have multiple e-mail address connected to one single user, but it looks like the alias changed in some way..