You wouldn't need to add additional primary to the account. If the domain is added as an alias in the system, you can redirect your MX Records to McAfee and allow those messages to be filtered. If the domain alias addresses have a different format than the primary addresses, you can add username aliases to each user account as well, e.g. of email@example.com is the primary, and firstname.lastname@example.org is the format for the alias, you would ad bsmith as a username alias which will create the association to email@example.com.
Let me know if you have any questions
Bradly McGarr, Security+, MCP, MTA-Windows OS, CIW-WFA, A+
McAfee SaaS Email & Web Security Technical Support Technician
I tried that. Maybe this is some sort of configuration issue on our exchange server. We have changed our mx records in exchange to the mcafee records and when I test primary smtp accounts I can see the messages being routed through mcafee servers along with aliases that end in the same domain. However when I test an email alias that end in a different domain than the primary account the traffic goes directly to our exchange server and not through mcafee servers.
Hi there here2help!
I would recommend contacting your McAfee support team for additional assistance on this issue. They will be able to look at your account and do additional testing as needed to help determine where this issue is occurring and help you find the correct solution!
System Support Specialist
SaaS Email and Web Security
McAfee. Part of Intel Security.
I'll assume the obvious, that the @otherdomain.com is using the McAfee MX records?