Weekly Fitbit reports not coming through email

edited June 2019 in Email

I used to get a weekly email from fitbit but now they are not coming through for some reason. I have tried contacting fitbit and they advised on some troubleshooting steps:

If the Fitbit is syncing and working correctly, then I'd like to recommend that we try turning the report off and then on. Please follow these steps:

Go into the Notification settings on your web Dashboard.
There, scroll down to the Weekly Summary option and verify if it is checked.
If it is, uncheck it and then save the settings.
Then check it once again and save the settings.

After that we'd need to wait for the new report to be sent. They are sent between Monday and Tuesday so please keep an eye on that.

I am still not getting them. Any issues as to why they would not come through? I wonder if you can check to see if there is an issue?


  • Do you know the address that they come from?

    Can you also PM me your address?

  • Sure.


  • edited June 2019

    So over the last 14 days nothing has hit our servers from that address to yours. It's likely that from address is just a cover for Fitbits automated system though.

    Do you have a header from a fitbit email in the past?

  • Sure here is a header from the last email I received from them:

    Delivered-To: 32@the$53.com Return-Path: <bounces+30983-f43a-@email.fitbit.com> Delivered-To: $5344the$53.com Received: from director9.mail.iad3b.thexyz.net ([]) by backend26.mail.iad3b.thexyz.net with LMTP id SOlcF8Q4kFyPYQAAEzVAuw for <$5344the$53.com>; Mon, 18 Mar 2019 20:33:08 -0400 Received: from proxy14.mail.iad3a.thexyz.net ([]) by director9.mail.iad3b.thexyz.net with LMTP id IOYtF8Q4kFwIIQAAbC0CoQ ; Mon, 18 Mar 2019 20:33:08 -0400 Received: from smtp20.gate.iad3a ([]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by proxy14.mail.iad3a.thexyz.net with LMTP id GACfFsQ4kFxXEgAA1+b4IQ ; Mon, 18 Mar 2019 20:33:08 -0400 Return-Path: <bounces+30983-f43a-@email.fitbit.com> X-Spam-Threshold: 95 X-Spam-Score: 0 X-Spam-Flag: NO X-Virus-Scanned: OK X-Orig-To: p@$53.am X-Originating-Ip: [] Authentication-Results: smtp20.gate.iad3a.thexyz.net; iprev=pass policy.iprev=""; spf=pass smtp.mailfrom="bounces+30983-f43a-p=$53.am@email.fitbit.com" smtp.helo="o3.email.fitbit.com"; dkim=pass header.d=email.fitbit.com; dmarc=pass (p=reject; dis=none) header.from=fitbit.com X-Suspicious-Flag: NO X-Classification-ID: 90e38408-49de-11e9-821e-525400aab2f3-1-1 Received: from [] ([] helo=o3.email.fitbit.com) by smtp20.gate.iad3a.thexyz.net (envelope-from <bounces+30983-f43a-p=$53.am@email.fitbit.com>) (ecelerity r(😃) with ESMTPS (cipher=DHE-RSA-AES128-GCM-SHA256) id B8/E0-07665-3C8309C5; Mon, 18 Mar 2019 20:33:08 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=email.fitbit.com; h=content-type:from:mime-version:subject:to; s=smtpapi; bh=iWoKbyOSY83YLxb/v5mBHetohpI=; b=kSBy/4pDfrh4gFfmUy WnCPtd53SsBG0y9l7VT79Iaw9JvkwDUNQPA+XhroUNAx/x3NGfhj56H2fOINCPMq myAJFUFSSD7IWY5gS+20FPS1OZ3b1Pyrq0gUUoljlvSFq7jN7eu8cLuiYJPfl+bA kjJ/nCPxHISy4CWDtu1//IAA0= Received: by filter1763p1mdw1.sendgrid.net with SMTP id filter1763p1mdw1-27989-5C9038C3-9 2019-03-19 00:33:07.264986188 +0000 UTC m=+3544.220074712 Received: from MzA5ODM (proxy-169-45-144-134.fitbit.com []) by ismtpd0005p1las1.sendgrid.net (SG) with HTTP id hb-oApgqQC-IWQFtrGSIgQ for <p@$53.am>; Tue, 19 Mar 2019 00:33:07.120 +0000 (UTC) Content-Type: multipart/alternative; boundary=cb687595918f1240e339a6205e29010440a4daa148be015d3b8767911746 Date: Tue, 19 Mar 2019 00:33:07 +0000 From: "Fitbit" <noreply@fitbit.com> Mime-Version: 1.0 Subject: Your weekly progress report from Fitbit! Message-ID: <hb-oApgqQC-IWQFtrGSIgQ@ismtpd0005p1las1.sendgrid.net> X-SG-EID: OLYgpfZ8EFS36QhnpXQfb3IjKjaNwpcSdKfx5emU/x1QuDQnE7i3K+D9F+JM9LHFo3Cy/u7g+bGEM8 c7wA4ihE5Kbjq2yA+8P6ry+08Iua5708UebAgX510HvF7GMuH9SJzsG6tP+CF8Sjqj1jirs/QbO3Ke rejIFikCldkjxS8+rmZ1Sj3/yaNl/kmiinc8JGkDwYvdnsyWqByjyaTTrA== X-SG-ID: dzI3NVsxklWVChkgslvFIVeKBQwQU+Cvmlg52CKMHuY=

  • Well I can for sure tell you that nothing has hit our servers to your mailbox from Fitbit. From fitbit in this case. It has to be an issue with the sender.

Sign In or Register to comment.