What did you expect? Generally the date shown is the date received on the mail server. The date received is whenever you added the mail to the account. IMAP is NOT a filling system. Despite many folk thinking it is at least something like that.

Matt, my process using TB sync to gmail has maintained the original email date for years. Only recently this problem started where most (not all) emails synchronized pick up the current date. Any suggestions would be greatly appreciated.

I would start by checking the date information in the email header (ctrl+U) pre and post upload. If the header information has changed, your issue is one you need to discuss with Google. Regardless of what it did in the past.

Header date looks good when exported. In fact, it shows correctly when imported into TB. The problem only exists when TB syncs up with my (auxiliary) google account.

I want you to check the header "AFTER" the sync to the google account. It is only by doing so that what is happening can be determined.

Hi Matt, Interesting, the email header indicates the email date of 01/31/17, but the date shown on my Gmail inbox indicates 01/22/24. I just can't figure this out. I appreciate your help in troubleshooting this issue!

X-Mozilla-Keys: X-GM-THRID: 1558083729388816771 X-Gmail-Labels: Category Purchases,Forward to bblxxxx@optonline.net,Inbox,Important,Category Updates,Unread,2017 Gmail,BBLxxxx email Delivered-To: bblxxxxxx.com Received: by 10.103.117.150 with SMTP id q144csp2182253vsc;

       Tue, 31 Jan 2017 15:13:55 -0800 (PST)

X-Received: by 10.129.88.133 with SMTP id m127mr19530553ywb.51.1485904435266;

       Tue, 31 Jan 2017 15:13:55 -0800 (PST)

Return-Path: <prvs=02013d50ae=pkginfo@ups.com> Received: from tessa5.ups.com (tessa5.ups.com. [153.2.234.138])

       by mx.google.com with ESMTPS id r7si923500ybd.266.2017.01.31.15.13.54
       for <bblxxxx@gmail.com>
       (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
       Tue, 31 Jan 2017 15:13:55 -0800 (PST)

Received-SPF: pass (google.com: domain of prvs=02013d50ae=pkginfo@ups.com designates 153.2.234.138 as permitted sender) client-ip=153.2.234.138; Authentication-Results: mx.google.com;

      dkim=pass header.i=@ups.com;
      spf=pass (google.com: domain of prvs=02013d50ae=pkginfo@ups.com designates 153.2.234.138 as permitted sender) smtp.mailfrom=prvs=02013d50ae=pkginfo@ups.com;
      dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=ups.com

X-NAI-Header: Modified by McAfee Email Gateway (5500) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ups.com; s=selector_ups; t=1485904432; h=From: To:Subject:MIME-Version:Content-Type:Date: Message-ID; bh=HnG97uVip9rkqeTPbwh9buiDdj gdtOYGx4Ja+CG5WbA=; b=AekmessDuCGGnz+Ygixn6Iist0/G wPQrjecWN/iaWMmuYG1SDsIhz9eVkMmOZXSZpQOi6kBw2BpX/Y G8DttqA6LWx7GUra+wQ49E1zOxmsIGgN6dhvCeL5bR8azF+/K3 vDNsg3gSBPGEhfAltJ8QG59/pja+g5pWa6Ftqv+ZepQ= Received: from gaalplpapp0154 (unknown [153.2.244.85]) by tessa5.ups.com with smtp id 2760_26d9_dc7922ec_964d_4817_8603_54fd69ca6d88; Tue, 31 Jan 2017 18:13:51 -0500 From: UPS My Choice <mcinfo@ups.com> To: bbxxxx@gmail.com Subject: Your UPS Package was delivered MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----NextPart_1485904432409.0010238494 Date: Tue, 31 Jan 2017 18:13:52 -0500 (EST) Message-ID: <323341713.20446087.1485904432417.JavaMail.beawl@drevil-vip.ups.com>

Hi Matt, Here's the header AFTER the sync to Gmail. The date in the Gmail UI is 1/26/24. The message header shows 1/9/17, but "Delivered after 222327696 seconds, which I believe this resetting the gmail UI date to 1/26/24. Is there any way to prevent this "delivery delay" from adding to the UI message date? I appreciate your help and thoughts.

Original Message Message ID <CAAn--_q6Sg7udhwTE+sU69eax0Kchzi-an3LzgdcPT0Cs41Dtw@mail.gmail.com> Created at: Mon, Jan 9, 2017 at 8:16 AM (Delivered after 222327696 seconds)