Sorry, I'm not quite sure where you're getting your information about what Mail.App does. I'm getting mine from the server telemetry logs where the client first identifies itself as:

"name" "Mac OS X Mail" "version" "7.0 (1816)"

And then proceeds to issue a COPY command:

UID COPY 3360991:3361069 "INBOX.Junk Mail"

See the "COPY" in there. I am the author of the blog post, and I think my credentials in this particular case trump yours, even if you're the author of Mail.App.

It appears to only be that one user so far - I've seen a few isolated "copy into same folder and expunge the old ones" in the logs (now that I log that) but not enough to be a pattern.

Oh, there are plenty of new RFCs coming out all the time. The most interesting bugs in mail clients tend to be trying to support new RFCs and not getting it right.

We de-duplicate on COPY, so there was only one copy of each email on disk. We don't de-dulplicate metadata though, because it's usually so small, and generally in the cache file of a different folder, where de-duplication isn't possible.

Have you tried FastMail? We updated the web UI today to make it work more efficiently on small screens (phones and the like), and it has a fairly complete keyboard shortcut set.

http://blog.fastmail.fm/2013/10/21/faster-than-native-introducing-fastmails-new-mobile-web-interface/

Free trial, but definitely paid. You're the customer with us, not the product.

Java moto: Write once, fuck you.

i was going all http://www.youtube.com/watch?v=bzkRVzciAZg on the post I replied to...

You could also do it in Visual Basic, with the added advantage that you could create a GUI to trace their IP address.

*fewer

(thanks, I'll be here all... nah, screw it - I'll be getting a beer)

try turning off your screen and trying again...

Yeah, fair enough. The failure to package new versions is a real problem. Thanks for the honest feedback!

Honestly, we won't support 2.2 or earlier any more. 2.3 was released in 2005. There comes a point when you have to move on.

2.3 is still supported for security issues, but it's not going to see much more development.

2.4 is supported just fine, and has been out since 2010. I really object to the characterisation of the mailing list and the IRC channel, since I'm on both and I try pretty hard to deal with any problems, though if you're on 2.2 or 2.3 I will often say "that's fixed in 2.4, and is not really fixable in earlier versions due to massive architectural changes which were required to make the behaviour consistent in the first place".

Poor documentation is a problem, and using berkeley DB was a really stupid idea. The upgrading problems are always due to berkeley version incompatibility. It sucks so bad that transitioning everything away from berkeley is an important goal for 2.5.

Plenty of people still use it, though Dovecot is kinda eating our lunch.

I'm interested in your reasons for avoiding Cyrus. Which version are you looking at?

Not saying it's impossible, just that it's bloody hard.

Well, this is going to be an extra-large shit for us, where me spending 2 years in Norway at head office was significantly easier than bringing people over here for 6 months at a time for skills exchange. HR tells me that Australia is the hardest country in the world they've tried to give people "bridge the world" temporary transfers to. Insular much?