Google Apps don't receive mail.

naneur

New member
Joined
Feb 15, 2012
Messages
4
Hi,

I need help here. I use Google Apps for my email account, let say [email protected]. I've used it for a while until I realized that I haven't received some emails (sending part is fine). I mean I got some of them but some just can't be delivered.

Then I tried to send from my gmail.com account and it bounced back with below message;

Delivery to the following recipient failed permanently:

[email protected]

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 authentication required (state 14).

----- Original message -----

MIME-Version: 1.0
Received: by 10.52.173.79 with SMTP id bi15mr484289vdc.31.1329372829745; Wed,
15 Feb 2012 22:13:49 -0800 (PST)
Received: by 10.220.5.71 with HTTP; Wed, 15 Feb 2012 22:13:49 -0800 (PST)
In-Reply-To: <CAHkjivRPntNkCbgwAXxeccakWye5NgbYse6LL7i0RC3FUC+THA@mail.gmail.com>
References: <CAHkjivRPntNkCbgwAXxeccakWye5NgbYse6LL7i0RC3FUC+THA@mail.gmail.com>
Date: Thu, 16 Feb 2012 13:13:49 +0700
Message-ID: <CABaAh0XduV-+CXbqZPvtcaviSB=n4a2w_+iM_7pR9DVZN6c=ig@mail.gmail.com>
Subject: Re: test send
From: "My Gmail" <[email protected]>
To: "Sales" <[email protected]>
Content-Type: multipart/alternative; boundary=bcaec51b9ce34a835904b90ebbf7


This is what I set MX record on my Direct Admin;

domain.com. A 203.170.192.115
ftp A 203.170.192.115
localhost A 127.0.0.1
mail A 203.170.192.115
pop A 203.170.192.115
smtp A 203.170.192.115
www A 203.170.192.115
domain.com. NS ns1.name.com.
domain.com. NS ns2.name.com.
ALT1.ASPMX.L.GOOGLE.COM. MX 20
ALT2.ASPMX.L.GOOGLE.COM. MX 30
ASPMX.L.GOOGLE.COM. MX 10
ASPMX2.GOOGLEMAIL.COM. MX 40
ASPMX3.GOOGLEMAIL.COM. MX 50
domain.com. TXT "v=spf1 a mx ip4:203.170.192.115 include:_spf.google.com ~all"


Anything wrong with my setting?
 
You've got your domain miss-configured at either hosting provider (DNS section in Directadmin), or at your domain registrar (or even at both of them):

http://intodns.com/crthailand.com

NS records got from your nameservers listed at the parent NS are:

ns1.webmasterbangkok.com ['203.170.192.115'] [TTL=14400]
ns2.webmasterbangkok.com [] (NO GLUE) [TTL=14400]
ns4.afraid.org ['174.128.246.102'] [TTL=86400]
ns2.afraid.org ['174.37.196.55'] [TTL=86400]
ns3.afraid.org ['72.20.15.62'] [TTL=86400]
ns1.afraid.org ['50.23.197.95'] [TTL=86400]

FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns1.afraid.org
ns2.webmasterbangkok.com

You should fix it.
 
Another issue I saw (I get to look at the deleted posts as well) is that in the links user naneur posted in the the thread-starters which got moderated he has the ns recores with no trainling dot character (.) after them. That could have been a typo, since he edited the domain name, but if not, it could have caused the problem.

Also, naneur, be certain that you've got the box unchecked on your MX Records screen (link from the main user-level login) for the domain.

Jeff
 
Hi,

Ok. I just did registrar transfer from 1and1 to Webnic. NS seems find now but still can't receive some emails. I don't know what else is wrong. Please help.

crthailand.com. A 203.170.192.115
ftp A 203.170.192.115
localhost A 127.0.0.1
mail A 203.170.192.115
pop A 203.170.192.115
smtp A 203.170.192.115
www A 203.170.192.115
crthailand.com. NS ns1.webmasterbangkok.com.
crthailand.com. NS ns2.webmasterbangkok.com.
ALT1.ASPMX.L.GOOGLE.COM. MX 20
ALT2.ASPMX.L.GOOGLE.COM. MX 30
ASPMX.L.GOOGLE.COM. MX 10
ASPMX2.GOOGLEMAIL.COM. MX 40
ASPMX3.GOOGLEMAIL.COM. MX 50
crthailand.com. TXT "v=spf1 a mx ip4:203.170.192.115 include:_spf.google.com ~all"
TTL 14400
 
This is message of what I receive after sending test mail. Just wondering it's been transferred from 1and1 for few days but MX still shown 1and1.

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

[email protected]
SMTP error from remote mail server after RCPT TO:<[email protected]>:
host mx00.1and1.com [74.208.5.3]: 550 <[email protected]>:
invalid address

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
Received: from ppp-58-9-119-209.revip2.asianet.co.th ([58.9.119.209] helo=nanPC)
by ns1.webmasterbangkok.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <[email protected]>)
id 1S3IKj-0008CP-8l
for [email protected]; Fri, 02 Mar 2012 09:35:01 +0700
From: "Pixel Interactive" <[email protected]>
To: "'Sales - C.R. Group'" <[email protected]>
Subject: test info
Date: Fri, 2 Mar 2012 09:34:53 +0700
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0033_01CCF857.B8DF8000"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acz4HQw2xwSHsK3DQe2dr9IhvK85Mw==
Content-Language: en-us
X-Antivirus: avast! (VPS 120301-0, 03/01/2012), Outbound message
X-Antivirus-Status: Clean

This is a multi-part message in MIME format.

------=_NextPart_000_0033_01CCF857.B8DF8000
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
 
The error message:
Code:
SMTP error from remote mail server after RCPT TO:<[email protected]>:
host mx00.1and1.com [74.208.5.3]: 550 <[email protected]>:
invalid address
is telling you that a server at 74.208.5.3 is getting the email but has no address for [email protected]. Your job is to find out why. Does that IP# belong to your server? If so, then possibly you haven't unchecked the checkmark in MX Records on your DirectAdmin login, and the address isn't set up on your server.

If the checkmark has been removed, and this is your IP#, then possibly wherever you're sending from (if not your server) is still caching stale DNS.

If neither, then find out why a 1and1 IP# is being given out for that domain. (It could be stale cached DNS.)

Jeff
 
Back
Top