I am going thru a phase where one of my kmail folders is about to roll over the 65,536 for number of msgs.
Unforch as it approaches this it goes thru a phase where a group of messages is not being marked as they are being read, so everytime I leave that folder after having read the same 28 (this mornings count) messages for about the 10th time, and it does mark them read as I re-read them, but when I come back to that folder, it takes 30 secs or so to scan it for unread, and them marks them as unread again. Doing an ls -l on Mail/emc/cur shows these files without the appendages as follows:
-rw-r--r-- 1 gene gene 9223 Mar 27 08:03 1553688235.6391.LiBdm:2,S -rw-r--r-- 1 gene gene 9246 Mar 27 08:16 1553688964.6391.BJZIy:2,RS -rw-r--r-- 1 gene gene 9322 Mar 27 08:50 1553691034.6391.5xr6g:2,S -rw-r--r-- 1 gene gene 8944 Mar 27 09:16 1553692607.6391.0Q1hQ -rw-r--r-- 1 gene gene 10866 Mar 27 14:06 1553709994.6005.a5pLa -rw-r--r-- 1 gene gene 11497 Mar 27 14:18 1553710720.6005.jKZVa -rw-r--r-- 1 gene gene 10992 Mar 27 14:42 1553712166.6005.RBD79 -rw-r--r-- 1 gene gene 12402 Mar 27 14:55 1553712913.6005.pCJ8s -rw-r--r-- 1 gene gene 10043 Mar 27 15:52 1553716351.6005.9yXfM -rw-r--r-- 1 gene gene 8038 Mar 27 16:40 1553719225.6005.V1wmO -rw-r--r-- 1 gene gene 9095 Mar 27 17:04 1553720673.6005.nsaQf -rw-r--r-- 1 gene gene 9384 Mar 27 17:07 1553720854.6005.zJ0nJ -rw-r--r-- 1 gene gene 11269 Mar 27 19:35 1553729726.6005.SnEOl -rw-r--r-- 1 gene gene 14813 Mar 27 20:11 1553731902.6005.CwKRo -rw-r--r-- 1 gene gene 11731 Mar 27 20:29 1553732987.6005.H6Oq1 -rw-r--r-- 1 gene gene 8933 Mar 27 21:11 1553735515.6005.O3hqS -rw-r--r-- 1 gene gene 8889 Mar 27 21:39 1553737161.6005.vdlh5 -rw-r--r-- 1 gene gene 9105 Mar 27 22:00 1553738447.6005.Jrmmh -rw-r--r-- 1 gene gene 12810 Mar 28 16:16 1553804210.9481.5wDVe -rw-r--r-- 1 gene gene 9690 Mar 28 16:16 1553804211.9481.FXlrf -rw-r--r-- 1 gene gene 8851 Mar 28 16:16 1553804213.9481.RFXOf -rw-r--r-- 1 gene gene 7964 Mar 28 16:16 1553804216.9481.0ysrQ -rw-r--r-- 1 gene gene 9512 Mar 28 16:16 1553804217.9481.1c0Gn -rw-r--r-- 1 gene gene 8792 Mar 28 16:16 1553804217.9481.hBg3G -rw-r--r-- 1 gene gene 9021 Mar 28 16:16 1553804217.9481.ODcCm -rw-r--r-- 1 gene gene 8846 Mar 28 16:16 1553804217.9481.xLM3g -rw-r--r-- 1 gene gene 7845 Mar 28 17:33 1553808826.9481.epVh2 -rw-r--r-- 1 gene gene 8826 Mar 28 17:37 1553809025.9481.Y4qD9 -rw-r--r-- 1 gene gene 7956 Mar 28 22:04 1553825086.9481.alSnz -rw-r--r-- 1 gene gene 8934 Mar 28 22:04 1553825087.9481.aw1c0 -rw-r--r-- 1 gene gene 11298 Mar 29 01:43 1553838220.9481.v5Iqy
Does anyone have a clue how I might fix this. I just did a mark all as read, clears the displayed count, without it showing in the next ls -l.
The current msg count is 60103 with these 27 once again claimed to be unread. And from past experience with another list folder, it will eventually get well, but will be a pita until the message count passes another "magic boundary" which I don't recall the value of.
kmail has also, according to htop, taken to using 100% of a cpu for half an hour at a time as it tries to fix thatever has gotten out of kilter.
Thank you.
Cheers, Gene Heskett
On Friday 29 March 2019 08:16:53 Gene Heskett wrote:
I am going thru a phase where one of my kmail folders is about to roll over the 65,536 for number of msgs.
Unforch as it approaches this it goes thru a phase where a group of messages is not being marked as they are being read, so everytime I leave that folder after having read the same 28 (this mornings count) messages for about the 10th time, and it does mark them read as I re-read them, but when I come back to that folder, it takes 30 secs or so to scan it for unread, and them marks them as unread again. Doing an ls -l on Mail/emc/cur shows these files without the appendages as follows:
-rw-r--r-- 1 gene gene 9223 Mar 27 08:03 1553688235.6391.LiBdm:2,S -rw-r--r-- 1 gene gene 9246 Mar 27 08:16 1553688964.6391.BJZIy:2,RS -rw-r--r-- 1 gene gene 9322 Mar 27 08:50 1553691034.6391.5xr6g:2,S -rw-r--r-- 1 gene gene 8944 Mar 27 09:16 1553692607.6391.0Q1hQ -rw-r--r-- 1 gene gene 10866 Mar 27 14:06 1553709994.6005.a5pLa -rw-r--r-- 1 gene gene 11497 Mar 27 14:18 1553710720.6005.jKZVa -rw-r--r-- 1 gene gene 10992 Mar 27 14:42 1553712166.6005.RBD79 -rw-r--r-- 1 gene gene 12402 Mar 27 14:55 1553712913.6005.pCJ8s -rw-r--r-- 1 gene gene 10043 Mar 27 15:52 1553716351.6005.9yXfM -rw-r--r-- 1 gene gene 8038 Mar 27 16:40 1553719225.6005.V1wmO -rw-r--r-- 1 gene gene 9095 Mar 27 17:04 1553720673.6005.nsaQf -rw-r--r-- 1 gene gene 9384 Mar 27 17:07 1553720854.6005.zJ0nJ -rw-r--r-- 1 gene gene 11269 Mar 27 19:35 1553729726.6005.SnEOl -rw-r--r-- 1 gene gene 14813 Mar 27 20:11 1553731902.6005.CwKRo -rw-r--r-- 1 gene gene 11731 Mar 27 20:29 1553732987.6005.H6Oq1 -rw-r--r-- 1 gene gene 8933 Mar 27 21:11 1553735515.6005.O3hqS -rw-r--r-- 1 gene gene 8889 Mar 27 21:39 1553737161.6005.vdlh5 -rw-r--r-- 1 gene gene 9105 Mar 27 22:00 1553738447.6005.Jrmmh -rw-r--r-- 1 gene gene 12810 Mar 28 16:16 1553804210.9481.5wDVe -rw-r--r-- 1 gene gene 9690 Mar 28 16:16 1553804211.9481.FXlrf -rw-r--r-- 1 gene gene 8851 Mar 28 16:16 1553804213.9481.RFXOf -rw-r--r-- 1 gene gene 7964 Mar 28 16:16 1553804216.9481.0ysrQ -rw-r--r-- 1 gene gene 9512 Mar 28 16:16 1553804217.9481.1c0Gn -rw-r--r-- 1 gene gene 8792 Mar 28 16:16 1553804217.9481.hBg3G -rw-r--r-- 1 gene gene 9021 Mar 28 16:16 1553804217.9481.ODcCm -rw-r--r-- 1 gene gene 8846 Mar 28 16:16 1553804217.9481.xLM3g -rw-r--r-- 1 gene gene 7845 Mar 28 17:33 1553808826.9481.epVh2 -rw-r--r-- 1 gene gene 8826 Mar 28 17:37 1553809025.9481.Y4qD9 -rw-r--r-- 1 gene gene 7956 Mar 28 22:04 1553825086.9481.alSnz -rw-r--r-- 1 gene gene 8934 Mar 28 22:04 1553825087.9481.aw1c0 -rw-r--r-- 1 gene gene 11298 Mar 29 01:43 1553838220.9481.v5Iqy
Does anyone have a clue how I might fix this. I just did a mark all as read, clears the displayed count, without it showing in the next ls -l.
The current msg count is 60103 with these 27 once again claimed to be unread. And from past experience with another list folder, it will eventually get well, but will be a pita until the message count passes another "magic boundary" which I don't recall the value of.
kmail has also, according to htop, taken to using 100% of a cpu for half an hour at a time as it tries to fix thatever has gotten out of kilter.
Thank you.
Cheers, Gene Heskett
Now to add the final insult of this crazy story, I looked at, but changed nothing in the emc folders propertries, but instead of clicking on cancel, I clicked on "OK" which took it about a minute and I think its fixed. Had there been no changes to commit, I would have thought the response would have been instant, to have it lock up kmails gui for a minute or more, tells me something did get re-written, but I've no clue what.
I wonder if excedrin has a number for this headache?
Cheers, Gene Heskett
On Friday 29 March 2019 08:40:37 am Gene Heskett wrote:
Now to add the final insult of this crazy story, I looked at, but changed nothing {snip}
Hi Gene,
Like you I have multiple folders with 50+k messages (a rolling 2 months of a server's 'utterances,' so multiple folders is a not really an option). I've lived with kmail doing the 100% of a cpu for an hour at startup for years and from this list I've gotten the fuzzy notion it's related to some index problem. I’ve done cleanup activities multiple times, but no real luck ‘fixing’ the issue.
I looked at, but changed nothing in the emc folders propertries, but instead of clicking on cancel, I clicked on "OK"
Would you fully explain what you did here? I’d guess ‘emc’ is a folder you have, but I’d rather have what steps you truly preformed so I can try the exact same thing.
Thanks, Michael
On Friday 29 March 2019 10:05:47 Michael wrote:
On Friday 29 March 2019 08:40:37 am Gene Heskett wrote:
Now to add the final insult of this crazy story, I looked at, but changed nothing {snip}
Hi Gene,
Like you I have multiple folders with 50+k messages (a rolling 2 months of a server's 'utterances,' so multiple folders is a not really an option). I've lived with kmail doing the 100% of a cpu for an hour at startup for years and from this list I've gotten the fuzzy notion it's related to some index problem. I’ve done cleanup activities multiple times, but no real luck ‘fixing’ the issue.
Same here. I've alway blamed it on the size of the email corpus here, as some of it goes back to 2001. Several gigabytes.
I looked at, but changed nothing in the emc folders propertries, but instead of clicking on cancel, I clicked on "OK"
Would you fully explain what you did here? I’d guess ‘emc’ is a folder you have, but I’d rather have what steps you truly preformed so I can try the exact same thing.
I left clicked the folder name, chose properties, didn't see anything unusual but clicked ok, not cancel. It took the gui about a minute to come back to life. But it didn't turn out to be fixed, the next time I scanned that folder, it took about a minute to scan, and that same 27 msgs were once again unmarked and showing as unread.
My setup here has offloaded all external mail fetching from kmail, using fetchmail instead which passes off to procmail for the spam and virus checks. The only connection kmail gets from all that is a notification to go get, from /var/mail, the name of the mailfile to read via dbus, so kmails mail retrieval never hits the cable. Thats accomplished by having inotifywait watching that directory. When a new mail has coming and procmail puts it in /var/mail, its only a millisecond or so before that file is zeroed out, but fetchmail takes a 3 minute snooze between fetch runs. So I'm not pounding on my isp's mailserver.
Thats my story. Copy of the mailwatcher bash script on request.
Thanks, Michael
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
Hi Gene,
I am going thru a phase where one of my kmail folders is about to roll over the 65,536 for number of msgs.
Unforch as it approaches this it goes thru a phase where a group of messages is not being marked as they are being read,
Does anyone have a clue how I might fix this.
An old saying is: KISS (keep it simple stupid). Why don't you create a new folder, say foldera, and move the oldest 50k mails from the original folder therein?
Regards Peter.
On Friday 29 March 2019 09:42:08 phiebie@drei.at wrote:
Hi Gene,
I am going thru a phase where one of my kmail folders is about to roll over the 65,536 for number of msgs.
Unforch as it approaches this it goes thru a phase where a group of messages is not being marked as they are being read,
Does anyone have a clue how I might fix this.
An old saying is: KISS (keep it simple stupid). Why don't you create a new folder, say foldera, and move the oldest 50k mails from the original folder therein?
Regards Peter.
If I'm to keep an archive folder, then I need to have a way to disable showing that archive in the gui unless I want to dig into that history. The list is within a line or 2 of screen high now. The coco folder has now 108K msgs in it, and that folder went thru this same phase as it went past a msg count in the 60k's but eventually got well. It hasn't done this in 3 or more years.
Cheers, Gene Heskett
On Friday 29 March 2019 08:16:53 Gene Heskett wrote:
I am going thru a phase where one of my kmail folders is about to roll over the 65,536 for number of msgs.
Unforch as it approaches this it goes thru a phase where a group of messages is not being marked as they are being read, so everytime I leave that folder after having read the same 28 (this mornings count) messages for about the 10th time, and it does mark them read as I re-read them, but when I come back to that folder, it takes 30 secs or so to scan it for unread, and them marks them as unread again. Doing an ls -l on Mail/emc/cur shows these files without the appendages as follows:
-rw-r--r-- 1 gene gene 9223 Mar 27 08:03 1553688235.6391.LiBdm:2,S -rw-r--r-- 1 gene gene 9246 Mar 27 08:16 1553688964.6391.BJZIy:2,RS -rw-r--r-- 1 gene gene 9322 Mar 27 08:50 1553691034.6391.5xr6g:2,S -rw-r--r-- 1 gene gene 8944 Mar 27 09:16 1553692607.6391.0Q1hQ -rw-r--r-- 1 gene gene 10866 Mar 27 14:06 1553709994.6005.a5pLa -rw-r--r-- 1 gene gene 11497 Mar 27 14:18 1553710720.6005.jKZVa -rw-r--r-- 1 gene gene 10992 Mar 27 14:42 1553712166.6005.RBD79 -rw-r--r-- 1 gene gene 12402 Mar 27 14:55 1553712913.6005.pCJ8s -rw-r--r-- 1 gene gene 10043 Mar 27 15:52 1553716351.6005.9yXfM -rw-r--r-- 1 gene gene 8038 Mar 27 16:40 1553719225.6005.V1wmO -rw-r--r-- 1 gene gene 9095 Mar 27 17:04 1553720673.6005.nsaQf -rw-r--r-- 1 gene gene 9384 Mar 27 17:07 1553720854.6005.zJ0nJ -rw-r--r-- 1 gene gene 11269 Mar 27 19:35 1553729726.6005.SnEOl -rw-r--r-- 1 gene gene 14813 Mar 27 20:11 1553731902.6005.CwKRo -rw-r--r-- 1 gene gene 11731 Mar 27 20:29 1553732987.6005.H6Oq1 -rw-r--r-- 1 gene gene 8933 Mar 27 21:11 1553735515.6005.O3hqS -rw-r--r-- 1 gene gene 8889 Mar 27 21:39 1553737161.6005.vdlh5 -rw-r--r-- 1 gene gene 9105 Mar 27 22:00 1553738447.6005.Jrmmh -rw-r--r-- 1 gene gene 12810 Mar 28 16:16 1553804210.9481.5wDVe -rw-r--r-- 1 gene gene 9690 Mar 28 16:16 1553804211.9481.FXlrf -rw-r--r-- 1 gene gene 8851 Mar 28 16:16 1553804213.9481.RFXOf -rw-r--r-- 1 gene gene 7964 Mar 28 16:16 1553804216.9481.0ysrQ -rw-r--r-- 1 gene gene 9512 Mar 28 16:16 1553804217.9481.1c0Gn -rw-r--r-- 1 gene gene 8792 Mar 28 16:16 1553804217.9481.hBg3G -rw-r--r-- 1 gene gene 9021 Mar 28 16:16 1553804217.9481.ODcCm -rw-r--r-- 1 gene gene 8846 Mar 28 16:16 1553804217.9481.xLM3g -rw-r--r-- 1 gene gene 7845 Mar 28 17:33 1553808826.9481.epVh2 -rw-r--r-- 1 gene gene 8826 Mar 28 17:37 1553809025.9481.Y4qD9 -rw-r--r-- 1 gene gene 7956 Mar 28 22:04 1553825086.9481.alSnz -rw-r--r-- 1 gene gene 8934 Mar 28 22:04 1553825087.9481.aw1c0 -rw-r--r-- 1 gene gene 11298 Mar 29 01:43 1553838220.9481.v5Iqy
Does anyone have a clue how I might fix this. I just did a mark all as read, clears the displayed count, without it showing in the next ls -l.
The current msg count is 60103 with these 27 once again claimed to be unread. And from past experience with another list folder, it will eventually get well, but will be a pita until the message count passes another "magic boundary" which I don't recall the value of.
kmail has also, according to htop, taken to using 100% of a cpu for half an hour at a time as it tries to fix thatever has gotten out of kilter.
Thank you.
Cheers, Gene Heskett
i take it back, clicking on the folder causes a rescan, and those 27 unread msg's are back again. Help!
Cheers, Gene Heskett
-
Gene Heskett -
Michael -
phiebie＠drei.at