Hello!
It seems to me that the logic how rulesets are applyed to folders has somethat changed from 4.63 to 4.7.
In 4.63 the pmail was practically stalled while the ruleset associated with folder has been processed.
In 4.7 this looks much better as one can continue to work with folders and emails while the rulset is processing the folder.
I have a lot of folders that contain data that is needed only temporaly so these folders have a folder close ruleset that deletes the mails older than X.
In past I had to close these folders one-by-one. Now I can do that in sequence and seems that pmail puts these tasks into process queue.
However - there seems to be problem. If one tries to move emails (by an inbox mail filtering ruleset for instance) to a folder that is in beeing processed by another ruleset at the same time then the pmail hangs (non responding to win). Maybe it's sort of a race condition or smth. as at least once such hanging of pmail has resulted in constantly high processor utilization by pmail process.
Just to note that all the mailboxes in question are IMAP and the OS is WinXP.
Have anybody noticed similar and can confirm this?
<p>Hello!</p><p>It seems to me that the logic how rulesets are applyed to folders has somethat changed from 4.63 to 4.7. </p><p>In 4.63 the pmail was practically stalled while the ruleset&nbsp; associated with folder has been processed.</p><p>In 4.7 this looks much better as one can continue to work with folders and emails while the rulset is processing the folder. </p><p>I have a lot of folders that contain data that is needed only temporaly so these folders have a folder close ruleset that deletes the mails older than X.</p><p>In past I had to close these folders one-by-one. Now I can do that in sequence and seems that pmail puts these tasks into process queue. &nbsp;
</p><p>However - there seems to be problem. If one tries to move emails (by an inbox mail filtering ruleset for instance) to a folder that is in beeing processed by another ruleset at the same time then the pmail hangs (non responding to win). Maybe it's sort of a race condition or smth. as at least once such hanging of pmail has resulted in constantly high processor utilization by pmail process.</p><p>Just to note that all the mailboxes in question are IMAP and the OS is WinXP.
</p><p>Have anybody noticed similar and can confirm this? </p><p>&nbsp;</p><p>&nbsp;</p><p>
</p><p>&nbsp;</p>