So, this is kind of a weird one. I've been forwarding all root email to [email protected] for a domain and email hosted on the local server. However, instead of having an email account for [email protected], I've been using a mail forward from [email protected] to [email protected]. This has been working for a very long time, until last week.
Suddenly, I've started getting mail delivery failed emails from the server with "[email protected] user doesn't exist". What's weird about this is that I'm actually still getting the forwards at [email protected]. Somehow, it seems to be trying to both forward the email and send it to a local mailbox that doesn't exist, using the same email address.
I'm not sure how to fix this. Temporarily I've set the root forward directly to [email protected] (I know). I've looked through domain aliases, dns settings/zones (dns is hosted externally), deleted and recreated the forward, etc., but can't find anything specific to why this might be happening. Possible bug when using a root forward to a locally hosted/forwarded email in a recent update?
Suddenly, I've started getting mail delivery failed emails from the server with "[email protected] user doesn't exist". What's weird about this is that I'm actually still getting the forwards at [email protected]. Somehow, it seems to be trying to both forward the email and send it to a local mailbox that doesn't exist, using the same email address.
I'm not sure how to fix this. Temporarily I've set the root forward directly to [email protected] (I know). I've looked through domain aliases, dns settings/zones (dns is hosted externally), deleted and recreated the forward, etc., but can't find anything specific to why this might be happening. Possible bug when using a root forward to a locally hosted/forwarded email in a recent update?