I’ll do my best to keep this as short and concise as possible. I have two separate, external email servers. One server handles email for example.net and the other is a MIAB instance and it handles email for example.com.
I have a couple of Dell servers that have iDrac 7. In the iDrac settings, I have specified my external MIAB server as the SMTP server for iDrac to use for sending alerts. Unfortunately, iDrac 7 will only use the domain name of the Dell server as the sender (from address). That domain name differs from my MIAB domain so I had to add an alias to MIAB so that the iDrac alert emails are not rejected.
For example, my Dell server’s from email address is: firstname.lastname@example.org Due to iDarc 7 limitations, this from email address cannot be changed to match the domain of my MIAB server which is: example.com. In the iDrac settings, I use my email@example.com user account and it’s password to send the emails.
So in MIAB, I have firstname.lastname@example.org set as an alias for email@example.com which forwards the alerts to firstname.lastname@example.org. I encountered this same type of limitation on some different Linux servers that also use my MIAB server to send email. For those servers, I had to set up an additional alias. So I have the following aliases specified in MIAB:
This all works but doing it this way creates another problem.
Your message did not reach some or all of the intended recipients. Subject: test Sent: 10/13/2023 10:40 PM The following recipient(s) cannot be reached: 'John Doe' on 10/13/2023 10:40 PM Server error: '550 5.1.1 <email@example.com>: Recipient address rejected: User unknown in virtual mailbox table'
So it seems just adding those aliases to MIAB causes MIAB to not consider example.net a remote domain. At least that’s what it looks like to me.
On MIAB, I have tried setting the correct, custom A records and an MX record for example.net but that did not seem to make any difference.
Can someone help me sort this out, please?