Solved Forwarder for [email protected] is failing but works for any other alias

[simplificare]

I have a weird issue happening on one account:

Client wanted [email protected] to forward to a Google Workspace account [email protected]. They already had [email protected] forwarding to [email protected] and it was working fine.

I setup the forwarder in DA forwarder menu told them it was all set but received a support ticket a few minutes later that [email protected] wasn't forwarding but instead users were getting bounce backs with "Undeliverable recipient".

My first thought was maybe [email protected] doesn't exist. But it does, I've since confirmed that with emailing directly with the client at [email protected].

If I create a forwarder like [email protected] to forward to [email protected], it works.

What could the message be failing on when it is set to [email protected]?

Any thoughts/help would be greatly appreciated!

Thanks,
Michael

 

[Richard G]

My first thought was maybe [email protected] doesn't exist.

Just FYI. Forwarders don't require to have an existing same e-mail account to be able to work.

What could the message be failing on when it is set to [email protected]?

Might be some SPF or DKIM or other issue on the Google check. We can't check this without knowing the real domain name.

Set the forwarder back to GMail (or what you used before), then send a mail from some private mail address to that [email protected] (so to the forwarder) and in the mean time, have an SSH window open and monitor your Exim's main and error log and see what happens and what errors are shown.

Still.... it's odd that a name with a dot will work the same way.

 

[simplificare]

Turns out it was my outbound provider that had marked the address as suspicious, because it had tried to forward mail but received hard bounce prior to us having set up the forwarder.

All is good now!