Thank you David for the reply! :)
This is what I got from my server support team.
I understand the situation that your plugin provider described, but that
isn't the case here. Your web server does correctly see that your MX
records point elsewhere:
email@example.com# host -t mx example.com
example.com mail is handled by 25 ALT2.ASPMX.L.GOOGLE.com.
example.com mail is handled by 50 ASPMX2.GOOGLEMAIL.com.
example.com mail is handled by 50 ASPMX3.GOOGLEMAIL.com.
example.com mail is handled by 10 ASPMX.L.GOOGLE.com.
example.com mail is handled by 25 ALT1.ASPMX.L.GOOGLE.com.
Do you have an example of a message that the server should have delivered
externally but didn't? I'll need the email address it was supposed to go
to and the timestamp of the message.
Here is what I sent them
The problem is http://www.example.com notifications work fine, but http://www.example.com/sub and paypal notifications don't work correctly.
I have contacted support team from my premium plugin called "Gravity Forms" and they told me to say this to you.
What is happening is your web server thinks it hosts your email so it's trying to send the email internally, but because your email isn't hosted locally it's not sending the mail out remotely.
Your web server doesn't know it isn't hosting your email so it is trying to route it internally rather than sending it out remotely so it never gets to your Google apps hosted email account.
Here is the official support article from Google on this issue:
Here is a more specific answer to this in the Google Apps help forum:
To sum it up you need to tell your web server that your email is hosted remotely so it will send it remotely. Contact your web host to find out specifics on how to do this. It's typically a control panel settings change.
Explain to them the email for your domain name is hosted with Google Apps and email sent via PHP on your web server is not arriving to those accounts but it is arriving to accounts not associated with your domain name. They should be able to assist you. You can show them the first Google link above which should provide them with enough information to assist you in correcting the issue.
So, I believe what we need to do is to change the e-mail routing to "REMOTE MAIL EXCHANGER", not the "Automatically Detect Configuration: Local (recommended)". I changed the MX record but I am not sure why it is behaving this way..
Can you please take a look at see what's wrong?
I think they are also saying that it's not their issue. Please help us solve this problem :(
Posted 7 years ago on Wednesday June 6, 2012 | Permalink