I need help in determining if this use case is possible:
-
We have one primary mail server where we want certain email addresses to be stored from domainA.com
-
All of the rest of the email addresses not defined on primary mail server, we want to be forwarded to a secondary server using secondary MX records (for same domainA.com)
Example: we have a domain which has several business email addresses (employees, sales, support, etc.) but on same domain we also have thousands of 'virtual' emails that we parse for our application. (we don't care about POP3 access etc. for the virtual addresses).
There is a service we are trying to use that can do all of the email parsing for us, but requires us to point our MX records to their server.
We want to be able to control our business emails on our own server, and only send the virtual emails to them.
Any suggestions, on how we can achieve this?
Best Answer
Short of using a different domain name you are going to struggle.
Email works something like this (feel free to correct my mistakes):
Consequently you can't use DNS and hence MX records to route email according to the 'name' part of the email address.
To potentially solve your problem - I don't see why your 'service' needs the MX record pointed at it (of course you may want a reverse DNS lookup or PTR record for SPAM purposes). Just set your MX record to point to a mail server you control and get it to forward on all of your 'virtual' email address to your service - it shouldn't care that they come from you and not the original sender.
Or change your staff email address to a different domain or subdoamin perhaps jon@admin.company.com?