Re: Yet another 'duplicate' thread

2013-11-15 Thread Jonas Petong
On 15.Nov 2013, 01:18, Gregor Zattler wrote: > Hi Jonas, > * Jonas Petong [13. Nov. 2013]: > > On 13.Nov 2013, 13:01, Nathan Stratton Treadway wrote: > >> On Wed, Nov 13, 2013 at 18:50:44 +0100, Jonas Petong wrote: > >>> Cameron, you were right, the message id's are the same. From the matter > >>

Re: Yet another 'duplicate' thread

2013-11-14 Thread Gregor Zattler
Hi Jonas, * Jonas Petong [13. Nov. 2013]: > On 13.Nov 2013, 13:01, Nathan Stratton Treadway wrote: >> On Wed, Nov 13, 2013 at 18:50:44 +0100, Jonas Petong wrote: >>> Cameron, you were right, the message id's are the same. From the matter of >>> fact >>> that limiting my Inbox by ~= did not work l

Re: Yet another 'duplicate' thread

2013-11-14 Thread Jonas Petong
On 14.Nov 2013, 10:24, Cameron Simpson wrote: > On 13.Nov 2013, 13:01, Nathan Stratton Treadway wrote: > > (Note that as I understand this limit only works when the sort order is > > > "thread". That is, with no limit applied you should be seeing the > > > duplicate messages marked with an "=" char

Re: Yet another 'duplicate' thread

2013-11-13 Thread Maurice McCarthy
Cameron Many thanks indeed for taking the time to write out a detailed explanation! Best Regards Maurice On 13/11/2013, Cameron Simpson wrote: > On 13Nov2013 20:20, Maurice McCarthy wrote: >> Please excuse a numpty interrupting, but could an old procmail recipe >> be adapted for use here. What

Re: Yet another 'duplicate' thread

2013-11-13 Thread Cameron Simpson
On 13.Nov 2013, 13:01, Nathan Stratton Treadway wrote: > (Note that as I understand this limit only works when the sort order is > > "thread". That is, with no limit applied you should be seeing the > > duplicate messages marked with an "=" character your mailbox index > >

Re: Yet another 'duplicate' thread

2013-11-13 Thread Cameron Simpson
On 13Nov2013 20:20, Maurice McCarthy wrote: > Please excuse a numpty interrupting, but could an old procmail recipe > be adapted for use here. What I've got I don't understand and it was > poached from somewhere or other > > # Get rid of duplicates > :0 Whc: .msgid.lock > | formail -D 16384 .msgi

Re: Yet another 'duplicate' thread

2013-11-13 Thread Maurice McCarthy
Please excuse a numpty interrupting, but could an old procmail recipe be adapted for use here. What I've got I don't understand and it was poached from somewhere or other # Get rid of duplicates :0 Whc: .msgid.lock | formail -D 16384 .msgid.cache :0 a /dev/null Regards Maurice

Re: Yet another 'duplicate' thread

2013-11-13 Thread Jonas Petong
On 13.Nov 2013, 13:01, Nathan Stratton Treadway wrote: > On Wed, Nov 13, 2013 at 18:50:44 +0100, Jonas Petong wrote: > > Cameron, you were right, the message id's are the same. From the matter of > > fact > > that limiting my Inbox by ~= did not work led me to the conclusion that > > their > > ID

Re: Yet another 'duplicate' thread

2013-11-13 Thread Nathan Stratton Treadway
On Wed, Nov 13, 2013 at 18:50:44 +0100, Jonas Petong wrote: > Cameron, you were right, the message id's are the same. From the matter of > fact > that limiting my Inbox by ~= did not work led me to the conclusion that their > IDs have been different. Seems like you've teached me wrong so. What ha

Re: Yet another 'duplicate' thread

2013-11-13 Thread Jonas Petong
On 13.Nov 2013, 14:11, Cameron Simpson wrote: > On 13Nov2013 09:06, Chris Down wrote: > > On 2013-11-12 19:22:24 +0100, Jonas Petong wrote: > > > Today I accidentally copied my mails into the same folder where they had > > > been > > > stored before (evil keybinding!!!) and now I'm faced with abo

Re: Yet another 'duplicate' thread

2013-11-13 Thread Jonas Petong
On 13.Nov 2013, 00:48, Ken Moffat wrote: > On Tue, Nov 12, 2013 at 07:22:24PM +0100, Jonas Petong wrote: > > Today I accidentally copied my mails into the same folder where they had > > been > > stored before (evil keybinding!!!) and now I'm faced with about a 1000 > > copies > > within my inbox.

Re: Yet another 'duplicate' thread

2013-11-12 Thread Cameron Simpson
On 13Nov2013 09:06, Chris Down wrote: > On 2013-11-12 19:22:24 +0100, Jonas Petong wrote: > > Today I accidentally copied my mails into the same folder where they had > > been > > stored before (evil keybinding!!!) and now I'm faced with about a 1000 > > copies > > within my inbox. Since those d

Re: Yet another 'duplicate' thread

2013-11-12 Thread Chris Down
On 2013-11-12 19:22:24 +0100, Jonas Petong wrote: > Today I accidentally copied my mails into the same folder where they had been > stored before (evil keybinding!!!) and now I'm faced with about a 1000 copies > within my inbox. Since those duplicates do not have a unique mail-id, it's > hopeless t

Re: Yet another 'duplicate' thread

2013-11-12 Thread Ken Moffat
On Tue, Nov 12, 2013 at 07:22:24PM +0100, Jonas Petong wrote: > Today I accidentally copied my mails into the same folder where they had been > stored before (evil keybinding!!!) and now I'm faced with about a 1000 copies > within my inbox. Since those duplicates do not have a unique mail-id, it's

Yet another 'duplicate' thread

2013-11-12 Thread Jonas Petong
Today I accidentally copied my mails into the same folder where they had been stored before (evil keybinding!!!) and now I'm faced with about a 1000 copies within my inbox. Since those duplicates do not have a unique mail-id, it's hopeless to filter them with mutts integrated duplicate limiting pat