Roberto C. Sanchez wrote:
Quoting Dave Hornford <Dave.Hornford@HornfordAssociates.com>:Are you also running an older version of Thunderbird? If so, you should upgrade to the 1.0 release. Thunderbird v.old & Cyrus v.very_old has a good chance of very weird anomalies.I am running 1.0 from here: http://www.jwsdot.com/debian/
Fact so often kill great troubleshooting theories.
Backporting isn't hard, but it is another treadmill of unknowns - with products for MTA, MDA, junk, virus, route mgmt, local sort, authentication, encryption & IDS all calling a plethora of libraries it is not a good use of time. We'd do it for early moving products or to capture an important point update, not for full version upgrades of the entire suite. We have 9 product edges to move email from the outside world to where a client can access it. We'd have to be in love with an OS to think about backporting the entire suite.I understand your pain on the aging infrastructure of Woody. We moved our email infrastructure off Debian - made the decision our servers we were going to stay on a 'supported/stable' platform and with the increased risks from viruses & spam couldn't keep email that far in the past. (Yes we know that Debian 'testing' is 'more stable' than many other distros, but it is 'testing' & I'm not signing up for an unknown update treadmill in production)Thankfully, in my case it is a personal server and I am really the only user. I can "bear the pain" until Sarge goes stable. Though I understand what you mean about not wanting to get on an unknown update treadmill with Sarge, backporting individual packages as necessary is always an option. I use sbuild and maintain a couple of packages backported from experimental to Sarge and some from Sarge to Woody. As long as you are not trying to backport libc (what would be the point, right?), it is not very difficult. -Roberto
Your error sounds like you are chasing a ghost. The problem is in a mainstream part of Thunderbird and is not replicable on other IMAP clients. The inability to replicate points to Thunderbird, that the error is in mainstream functionality points to your old server/anomaly in your config. Thunderbird has other areas where it doesn't handle errors well. I'd try creating a new account and using your existing Thunderbird install. This will confirm you don't have a ghost lurking in your account. Then I'd try a new Thunderbird install in a different client account against both (i.e. create mailtest on your server & desktop then mix & match) If all combinations have the error you have a bad ghost. If one or more don't have the error you know where to look.
Dave