Thread

hi-
i have seen others struggle with this, but i have 3 domains on EE each of whom has trouble receiving email sent through an EE contact form if the recipient email is *on* the domain. i realize this is NOT a problem specific to EE, but i’d really like some help from folks who have experienced this. the site i’m currently trying to fix this for uses google apps to handle the mail. the host (ewdhosting.com) says that the emails are being sent by the system *fine*. but they are nowhere in google-land; users don’t see them in their inbox or google spambox.

sorry if this is not the right place for this post, but i’m a little lost in the new forums. 😊

e.g. here’s a test form:
http://www.blueseventy.com/about/emailtest

i receive it, but the @domain email does NOT.

What Email Protocol are you using? This sounds like an MX setup issue on the Google Apps side of things more than anything else. Are you using SPF on Google’s end?

I’m having the same problem too with Google Apps. What do I need to modify on the Google Apps side of things to get this working? I know this isn’t an EE-specific issue so I don’t expect you guys to fully support it but if you could just point me in the right direction I’d be very grateful.

can’t quite remember what fixed this in the end - i just checked the host support tix for this - the last 2 things in our dialog that ended with email working were these:

****
If your website is being hosted by others, please contact the concerned web host to change the e-mail routing to “REMOTE MAIL EXCHANGER”, not the “Automatically Detect Configuration: Local (recommended)”.

When you set it to REMOTE MAIL EXCHANGER”, your web server will recognize that all e-mail received in your domain sold be routed to remote mail exchanger to deliver to highest priority MX record.

When you choose the second option (Automatically Detect….), the your webs server takes responsibility to act as a main mail exchanger for all the mail s received in your domain address.
****
and also:
****
To create an SPF record for a domain:

1. Log in to the administrative console for your domain.

2. Locate the page from which you can update the DNS records.
You may need to enable advanced settings.

3. Create a TXT record containing this text: v=spf1 include:_spf.google.com ~all

Publishing an SPF record that uses -all instead of ~all may result in delivery problems. See Google IP address ranges for details about the addresses for the Google Apps mail servers.

4. If you use Google Message Security, you also need to include the Postini servers as authorized mail servers.
For details, see Configuring SPF for outbound services at the Postini Help Center.

5. Save your changes.
Keep in mind that changes to DNS records may take up to 48 hours to propagate throughout the Internet.

If you have difficulty creating an SPF record, contact your domain provider for assistance.

****

Thanks for the suggestions. I’m in the same boat as you where I can’t administrate the server so I guess the support guy is going to have to look at this.

Chris,

hopefully that advice will help out. Please let us know how you get on

In a nutshell what is going on is that your server sees the same domain and tries to send at a local level hence the email never arriving.