Hi Jeff & all,

I'm one of the unlucky people affected by an ongoing duplicate e-mail issue since 10.6 . See this forum thread. Briefly - some incoming e-mails seem not to get deleted from the server, regardless of the account setting for removing from server. Only guaranteed way to prevent duplication is to check the server (Mail.app > account inbox > right-click > Get account info) for undeleted old messages and manually delete them from there. (Select relevant messages > press "Remove from server" button.)

It appears that Apple are not in any great hurry to fix it. We all anticipated a fix in the 10.6.2 update, but it didn't happen as far as one can tell.

Anyway, I'm just wondering whether Purify might offer any clues - at least in my case. (Recognising that most posters on the above thread won't be using Purify.) Thing is nearly all the messages I get duplicated are spam - and rated as such by Purify (using the new post-download rating method) ... and it also happens with Purify's (rare) false positives. But never (or at least very nearly never) happens with legitimate messages or false negatives.

So my question ... Could it be that SL's Mail.app reacts to some code that Purify adds to those messages it rates as spam, to cause the known non-deletion from server issue??

Any ideas ... ?

I don't think so. The message will be deleted using the message number returned by your server, or using the UUID of the message, and Purify's rating doesn't have any impact on this.

OK, fair enough. Just grasping at every straw really ....

Hi Lance,
Another possibility is to change mail clients - I use Thunderbird and it works fine. I've never had the problems you mention. Don't know if it's Applescriptable, though.
Cheers, Mike.

Hi Mike,

Thanks for the suggestion. I guess I could do that .. just not sure whether I want to go through the bother. Having made the switch from Eudora to Mail several years ago, I'm really liking the benefits of Mail's integration with the other iApps and the OS. I'm just hoping at his stage that Apple will actually do something to fix an issue that's clearly widespread - and virtually unique to Snow Leopard. If 10.6.3 comes out and it's still not fixed, well then I might reconsider ....