Forum

Hi,

I have a domain name with some emails redirections.

For the second time in a short period, I received all my mails with a 4 days delay (I received this morning mails that got a timestamp of four days ago).

This is really unacceptable.

No, we currently do not support the extension.

i have domain: http://www.goldenberg-law.co.il/
do you have this kind of ltd ? what us the price?

Thank you everyone. We are investigating this issue now. If anyone else has headers, please email them to [email protected]. Thank you so much for your help. We hope to have this resolved soon.

Yes I have exactly the same problem. I am using free Gmail and simple email forwarding from my Dynadot domain. I am not using paid-for Google Apps nor MX records. My Gmail address is still of the @googlemail.com form.

Some emails are getting through to me instantly, but others are delayed by up to 4 days. This started happening only last week.

I have used the same domain to Gmail setup for eight years without a problem, but now it's terrible. I'm selling my house and I have missed several vital emails!!

Examining the headers there are always SPF errors. It seems that the Dynadot parkmail server is not recognised by Google as authorised to send.

Here is an email that was delayed:

Delivered-To: [email protected]
Received: by 10.194.219.162 with SMTP id pp2csp372357wjc;
       Tue, 14 Oct 2014 07:13:36 -0700 (PDT)
X-Received: by 10.69.19.225 with SMTP id gx1mr5793784pbd.64.1413296015912;
       Tue, 14 Oct 2014 07:13:35 -0700 (PDT)
Return-Path: <[email protected]>
Received: from parkmail.dynadot.com (parkmail.dynadot.com. [54.69.45.191])
       by mx.google.com with SMTP id oq9si13176482pdb.19.2014.10.14.07.13.35
       for <[email protected]>;
       Tue, 14 Oct 2014 07:13:35 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning [email protected] does not designate 54.69.45.191 as permitted sender) client-ip=54.69.45.191;
Authentication-Results: mx.google.com;
      spf=softfail (google.com: domain of transitioning [email protected] does not designate 54.69.45.191 as permitted sender) [email protected]
X-Forwarded-To: [email protected]
X-Forwarded-For: chris@my_domain.com [email protected]
Received: from 157.55.1.155 by parkmail.dynadot.com with SMTP; 11 Oct 2014 15:20:55 +0000
Received: from DUB405-EAS144 ([157.55.1.138]) by DUB004-OMC2S16.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
        Sat, 11 Oct 2014 08:20:53 -0700
X-TMN: [SHmqZYgaPmaEeeNezPsuDrnlxlqgvImP]
X-Originating-Email: [[email protected]]
Message-ID: <[email protected]>
Return-Path: [email protected]
Content-Type: multipart/alternative;
       boundary="_36c7681e-501a-48a2-abe3-19d042af4bd3_"
MIME-Version: 1.0
To: <chris@my_domain.com>
From: someone <[email protected]>
Subject: RE: Moving post
Date: Sat, 11 Oct 2014 16:20:27 +0100
X-OriginalArrivalTime: 11 Oct 2014 15:20:53.0230 (UTC) FILETIME=[F257D0E0:01CFE566]

--_36c7681e-501a-48a2-abe3-19d042af4bd3_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"


And here is an email that arrived promptly:

Delivered-To: [email protected]
Received: by 10.194.219.162 with SMTP id pp2csp347765wjc;
       Tue, 14 Oct 2014 04:33:11 -0700 (PDT)
X-Received: by 10.66.119.103 with SMTP id kt7mr4124190pab.107.1413286390927;
       Tue, 14 Oct 2014 04:33:10 -0700 (PDT)
Return-Path: <[email protected]>
Received: from parkmail.dynadot.com (parkmail.dynadot.com. [54.68.4.223])
       by mx.google.com with SMTP id hh2si12726184pbb.80.2014.10.14.04.33.10
       for <[email protected]>;
       Tue, 14 Oct 2014 04:33:10 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning [email protected]
does not designate 54.68.4.223 as permitted sender) client-ip=54.68.4.223;
Authentication-Results: mx.google.com;
      spf=softfail (google.com: domain of transitioning [email protected]
does not designate 54.68.4.223 as permitted sender)
[email protected];
      dkim=pass [email protected];
      dmarc=pass (p=REJECT dis=NONE) header.from=paypal.co.uk
X-Forwarded-To: [email protected]
X-Forwarded-For: shopping@my_domain.com [email protected]
Received: from 173.0.84.226 by parkmail.dynadot.com with SMTP; 14 Oct 2014
11:32:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=paypal.co.uk; s=pp-dkim1;
c=relaxed/relaxed;
       q=dns/txt; [email protected]; t=1413286376;
       h=From:From:Subject:Date:To:MIME-Version:Content-Type;
       bh=NuBgbMOn613sidT3XzIKPT1UYkxdsYglXlczeADWnmA=;
       b=yAqSgUoWsuPtYxsTcaTe6XIClkgcJ20mTTy48KlmAU9u6COaBlLv1PMSWF4A9SMu
       qXwTITcK0BNz6dUjbd94b/BrGgC8AkJM1OEGskhZdKmz3HfWbtU6NR/klq7GTz9F
       jp9cynsBD5UiVsAhpbFmBDkSvPVGXUQNkKupaj8M7+NqU6mjD16CxYohcFnDa/9r
       5xNQBvR4EkqmQJALjDuu7c+/PTo4EXiH7Ase1JFBUJYmQRqfGf6IZELNulMQ7sOQ
       0P491Yxs6wXRGzR55ZR+U/W3kh/PzqtRslIxnSpq7HbMt2ct1butQtqCT4mXgMsO
       bg95KPhis9Dkb9l65JiKYA==;
Received: (qmail 25387 invoked by uid 993); 14 Oct 2014 11:32:56 -0000
Date: Tue, 14 Oct 2014 04:32:56 -0700
Message-Id: <[email protected]>
PP-Correlation-Id: 5d1ea77fae812
Subject: Refund from sjd supplies ltd
X-MaxCode-Template: email_buyer_refund
To: Christopher my_surname <shopping@my_domain.com>
From: "[email protected]" <[email protected]>
X-Email-Type-Id: PP1465 - 5d1ea77fae812
X-XPT-XSL-Name: email_pimp/default/en_GB/transaction/buyer/BuyerRefund.xsl
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=windows-1252
MIME-Version: 1.0

Names and addresses disguised for confidentiality.

The prompt email still has SPF fails. Can someone tell me what the vital difference is between these two sets of headers that led to the delay? Why has Dynadot stopped playing nicely with Google?