OK, we got a work-a-round that the owner likes, and will use.
We went to the K-9 free mail client. That one reads the mail just fine.
The phone in question is a Droid2 from Verizon. The mail client program
is a 1.0 program that's bundled with the phone, and supplied by Verizon,
I doubt it's as good as the default Android mail program though, but
with Verizon, you don't get the chance to even see if that's the
problem. It's also a shame that there is no way to view the headers in
the mail either <sigh>.
Anyway, we've installed that on his phone, and setup the 2 accounts he
gets from the office.
IMAP wouldn't work that well for him because of the size of his
mailstore on his main email computer, as well as he's probably got 50+
folders he moves mail around into. All of the other locations are just
"check the email" without having to go back to his main office
computer. The office computer is the one that controls how long mail is
kept on the servier, set for 14 days.
Thanks all, I suspect that there's an RFC for the formatting of the time
stamp, I wonder if it's a rigid spec, or if we're dealing with the
flexible portion of the RFC? No need to check though, the solution
2825 Erica Place
Nashville, TN 37204
On 6/21/2011 10:22 AM, Ben Hanson wrote:
> 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
> 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?
> *Ben Hanson*
> 540 433 9101 *office*
> 646 342 0396*mobile*
> www.transprintusa.com <http://www.transprintusa.com/>
> www.colorep.com <http://www.colorep.com/>
> Learn more about our
> newest waterless
> sustainable technology at
> www.airdye.com <http://www.airdye.com/>