ISPConfig 126.96.36.199 - Mail() does not route to remote MX when to domain on local server
I hate to ask a question for my first post, but I have a route added to transport to google's IP. This is added under Advanced Email Routing. The domain uses google apps.
When I try to send an email using PHP's mail() function to any other email address, it works fine. When sending to an email address of a site on the local server, it tries to route it to localhost:
Mar 28 15:01:31 vds1 postfix/smtpd: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 <email@example.com>: Recipient address rejected: User unknown in relay recipient table; from=<firstname.lastname@example.org> to=<email@example.com> proto=ESMTP helo=<xxxxxxxxxxx.com>
Mar 28 15:01:31 vds1 sendmail: r2SC1UVX000652: firstname.lastname@example.org, email@example.com (48/48), delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=30079, relay=[127.0.0.1] [127.0.0.1], dsn=5.1.1, stat=User unknown
The domain xxxxxxxxxxx.com is added as a site, but not a mail domain. Do I have this configured wrong, or is something else wrong? This is causing a form to not properly deliver emails.
I don't have much experience with using Google to send and receive email with apps, but you might have to include Google's special SPF record inside your mailing domain's TXT record to send mail properly.
Google's SPF record for Apps is here.
From that page...
To create an SPF record for a domain:
Log in to the administrative console for your domain.
Locate the page from which you can update the DNS records. You may need to enable advanced settings.
Create a TXT record containing this text: v=spf1 include:_spf.google.com ~all
*(My note: this is NOT a separate TXT record if you already have one, just add the include:_spf.google.com part to your existing domain an ~all if necessary)
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.
If your registrar also requires a host setting (such as @), see the TXT records for specific domain providers list for precise instructions.
Save your changes.
Keep in mind that changes to DNS records may take up to 48 hours to propagate throughout the Internet.
|All times are GMT +2. The time now is 00:30.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.