I sympathize with your pain.   If you do a search for 'Android Mail 12/31/1969' you will find this is a common concern.  I apparently relates to mail header parsing by the default mail client, specifically the inability to read the received timestamp unless it's in a particular format.   Apparently Ebay causes the same date issue.

I'd bet they've fixed the problem in the most recent releases of Android, but that's phone specific.  There are other mail clients which are supposed to work fine.  One user on a list suggested one called 'K-9'. 

So your options are:
    1    Find the datestamp difference in the Surge headers as compared to whatever the phone is looking for and ask NetWin to alter their header
    2    Use a different mail client or change a config option that might alter the behavior.

Good luck
ben



On 06/21/2011 11:04, Glenn Meadows wrote:

Hello "group".

I have a very odd problem.  We've just moved our mail from an outside host to a newly installed Surge server.  I've run Surge at other companies for years, and never run into this problem, and it's REALLY STRANGE.  I would hope that some of you might have seen this, or have some inkling of what/where I should look for some obscure setting that needs to be changed.

The problem occurs ONLY on one persons phone (of course it's the owner).

When mail is sent from ANY account on the main server, either via a connected client (Thunderbird), or other peoples phones, mail ONLY to his phone, shows up with a time stamp of 12/31/1969, and thus ends up at the far end of his mail list.  Mail from OUTSIDE servers conneting to us, and mail to him, shows up properly, time stamped correctly.

The mail from internal generated mail, arrives in ALL other clients (webmail, Thunderbird, etc), with the PROPER time stamp.  ONLY the mail arriving on HIS phone, a Motorola Android based phone, does this problem occur.

ANY pointers/ideas/solutions would be helpful.

As a test, I put a forward on his Surgemail to forward to his Gmail account, and the time stamp IS correct there as well.

Only when POP retrieve from the Surge server is it messed up.

<ARGH!!!!!> <sigh>.

Thoughts?  Anyone?