On Fri, 6 Jan 2012, Mark Crispin wrote:
> The only fix for this problem is to fix GMail. GMail violates the IMAP
> protocol. Google has known about the problem for years, and does not care.
--LOL! Great answer, thanks! ;)
Had a feeling GMail was the cause, but wasn't sure if there was a
workaround or not......??
> Perhaps you should ask yourself why you use a provider that uses products
> that violate the specifications.
--My ISP _at one time_ (this is key) was the geekiest one in my state
(Hawai'i). Sadly, due to market pressures and loss of staff, etc.,
they've had to cave into the "pop culch" and go to the "Cloud" (bleh). ;=(
However, they've made a concerted effort to maintain a virtual server for
those of us poor geeks still surviving......So, it's not as bad as it
could be, but worse than when I started with them. ;/
The only other local ISP I could go with would be my workplace
(university), but they, also, due to financial concerns, server space,
etc., are also caving in and strongly encouraging faculty/staff to go to
the "Cloud" (double-bleh). :=(
I'd rather not mix business and pleasure, so am staying with the only
local ISP that supports shell access.
> Once upon a time, people demanded that the underlying cause of a
> diagnostic message be fixed, rather than cover up the diagnostic. But that
> isn't popular any more. Everybody is too busy worshipping Google or Apple
> or Microsoft, regardless of the fact that these companies are dumping
> total crap on the marketplace.
--Totally agreed. Except I'm also a long-time Mac user as well, so maybe
excepting Apple. ;) LOL
> If you are one of the exceptional few that actually wants problems fixed,
> instead of covered up, you will complain to Google that their server
> violates IMAP protocol. They will then pat you on the head and say "don't
> worry little one, we are the googley experts and we never screw up."
--Do you know whom I should complain to at Google??
Though agreed, they probably won't care, since it's not part of their protocol.....;/