Auteur: Tim Pouget Date: À: exim-users Sujet: [exim] Non-standard Setup of Mail Routing
I have a question which I am told might be non-standard method in setting up
the routing of local mail through our cPanel server. As of right now our MX
Records are currently pointing to Google APPs as they are managing our email
accounts. We also have the server setup as a Local Mail Exchanger which
allows Google to route emails back to our server if the account does not
exist on their end. We do this as we have three email accounts that need to
remain our end. One is piped to a PHP Script, another is used when the
server coughs up an error, and the last is used for our online contact form.
As it stands now, everything is working except the server cannot send emails
to accounts that are setup over at Google. I fully understand the difference
between a Local Mail Exchanger and a Remote Mail Exchanger, so I know where
the problem lies. When I play with the options of switching them around here
is what happens between the two; the solution I am looking is for everything
listed below to work with one of those setting turned on.
If I have Local Mail Exchanger setting turned on (number 4 does not work)
1. If someone emails one of our accounts the routing from our servers to
Google works as emails are received.
2. If an account does not exist with Google, the routing of the emails back
to our server works as the piped PHP script receives the request and
executes accordingly.
3. When the server emails an account on the server that is not setup with
Google it works.
4. When the server emails an account that is setup through Google, it does
not work and generates a no such user error.
If I have Remote Mail Exchanger setting turned on (number 2 and 3 do not
work)
1. If someone emails one of our accounts the routing from our servers to
Google works as emails are received.
2. If an account does not exist with Google, the routing of the emails back
to our server does not work as this domain no longer as permission to
receive and process emails.
3. When the server emails an account on the server that is not setup with
Google it does not work as this domain no longer as permission to process
and send emails.
4. When the server emails an account that is setup through Google, it does
work.
I am in a catch 22 here and would like to know what solution can I do to
make this work?