Link to home
Start Free TrialLog in
Avatar of Steven
StevenFlag for United States of America

asked on

configuring mx record for alternate delivery location

my company used microsoft hosted exchange services (bpos for short)

my mx record is pointing to microsoft

i have an internal server setup to receive mail @companyname.com
the same domain that my microsoft hosted exchange services uses

can i setup a second mx record SO if the user is not found on my hosted exchanged environment, it will try to deliver to the alternate location?

im using an app internally which generates email accounts for receiving messages.  these accounts are never setup in microsoft hosted exhange, so when i email these accounts microsoft sends a NDR that the recipients email address does not exist.

is it possible to correct this with additional mx records?
Avatar of Neil Russell
Neil Russell
Flag of United Kingdom of Great Britain and Northern Ireland image

No.
The MX points to any valid Mail server for your domain. If the server on the end of it is valid for your domain and returns a USER NOT KNOWN error to a sending smtp server than that server assumes that it is an authorative answer.
WHat server do you have setup internally? You could set your MX to to your server and then configure it to forward on all unknown mail directly to the server pointed to by your current MX record.
Avatar of Steven

ASKER

its a third party product, ecm solution which runs its own mail server
this server is externally accessible

are you saying i may possibly be able to have my hosted exchange forward unknown mail to the second mx record?  or does it involve a different process?  i can call microsoft to check, i just want to be clear first

thanks for your help
Avatar of Member_2_4694817
Member_2_4694817

If you have one mx pointing to microsoft and one mx pointing to your server, then all mail will typically be tried to deliver to the "better" one (lower priority value). In case of e.g. connection failure the mx with worse priority should be tried next, but not in case of a permanent error (such as USER NOT KNOWN).
In theory, if you could coerce your server to respond with a different (non-permanent) error message instead, things *might* work out, i.e. senders might try the microsoft server instead. (Note that this woul d not be RFC compliant, so don't do it anyway).
However, in case of congestion etc. that server might be tried anyway even for existing users.
Avatar of Steven

ASKER

very good explanation hagman

so it sounds like this simply isnt going to work
Its exactly the same explination as I gave you in the first post with a few extra words thrown in :D
ASKER CERTIFIED SOLUTION
Avatar of Neil Russell
Neil Russell
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial