Weird situation.
A customer has an email account that is - for reasons unknown and beyond our control - sending out munged reply addresses for his emails occasionally.
Instead of [email protected] it's sending out [email protected].
The webserver is set up as secondary MX for the domain already and therefore has a default account set up for domain.com - the mailserver (separate box) collects mail from this periodically using POP3.
I know that this isn't the sane solution (i.e. fix the issue causing the error in the reply address) but is there any possible way I can get EXIM to accept mail for the www "subdomain" and deliver it to the default address for the account? It wont let me set up a forwarder for a subdomain that doesn't exist. I can't set up a www subdomain because it already exists as a special subdomain for the web traffic.
Hope someone can help!
A customer has an email account that is - for reasons unknown and beyond our control - sending out munged reply addresses for his emails occasionally.
Instead of [email protected] it's sending out [email protected].
The webserver is set up as secondary MX for the domain already and therefore has a default account set up for domain.com - the mailserver (separate box) collects mail from this periodically using POP3.
I know that this isn't the sane solution (i.e. fix the issue causing the error in the reply address) but is there any possible way I can get EXIM to accept mail for the www "subdomain" and deliver it to the default address for the account? It wont let me set up a forwarder for a subdomain that doesn't exist. I can't set up a www subdomain because it already exists as a special subdomain for the web traffic.
Hope someone can help!