Thanks for the clarification Brian.
I'm needing to check so many messages for the same reason as you, checking the Spam account for false positives.
Regards
Richard
Hi All,
I'm trying to use Pegasus to read the mail of a user whose folder in Mercury contains about 35000 files.
After a pause of a minute or two , during which the Pegasus status bar says 'IMAP: Getting status for 'INBOX'' , Pegasus reports an error & says 'The operation cannot be completed'.
I'm guessing there are just too many mails.
I've looked through the Pegasus IMAP settings, but can't see any place to ask it to get mail in say batches of 1000. Is such a thing possible?
The other thing I thought I might try would be to move all but 1000 files out of that directory on the server, then use Pegasus to look at the Subject lines, delete those I don't need, move the ones I need to keep to another folder via IMAP and then, again on the server return the next batch of 1000 files to the users folder & repeat the process. Would doing that confuse Mercury?
Regards
Richard
So far I know of two Pegasus/Mercury user who have experienced this problem, I am one of them. My problem is machine specific. Of the three machines I have at my home, only one has problems similar to what you describe. I never found a resolution. What I figured out is that I could retrieve 200 new messages at a time. I had to remote connect to the Mercury machine at the office, access the mailbox directory using Window Explorer, move all but 200 .cnm files to a temporary location, make the IMAP connection, deal with those 200, move 200 back from the temp location, deal with those 200,... I worked with lots of 200 because that's about how high the message count went before hang occurred. I don't know whether more than 200 would work.
The other fellow who has the hang problem experiences it randomly on multiple machines. His tests indicate an association with the IMAP header cache and whether or not it is empty. I could never duplicate his experience so it's unknown whether we have the same problem causing the hang. I can successfully IMAP connect to the same mailbox with my Win7 machine, my wifes' Vista machine and from an XP machine at the offices but have never been successfull with my home XP machine.
I've found that NTFS sometimes can't handle many files in the same directory very well, so it could be that Windows takes too long to respond. This could differ depending on OS version and hardware, of course, but you could try increasing the TCP/IP timeout in MercuryI a lot and see if that is an improvement.
The alternative would be to store messages in sub-folders rather than keeping them in the inbox.
/Rolf
Thanks for your replies Brian & Rolf.
[quote user="Rolf Lindby"]
The alternative would be to store messages in sub-folders rather than keeping them in the inbox.
[/quote]
You don't mean 'Message Folders' as created via Pegasus? That operation seems not to create a new directory server side. Where are mails moved into Message Folders stored?
[quote user="rhayward"]You don't mean 'Message Folders' as created via Pegasus? That operation seems not to create a new directory server side. Where are mails moved into Message Folders stored?[/quote]
Pegasus Mail folders (except for the New mail folder) are a made up of a pair of files with the extensions .pmm and .pmi (index file). When in Pegasus Mail you can find out which file pair belongs to which folder by right clicking on the folder name then selecting 'Folder information'.
When I mentioned that I processed 200 messages at a time I failed to state that I was accessing my office Spam mailbox. I reviewed each set of 200 for false positives, forwarded any as needed, then deleted the rest before taking on the next set of 200. If this had not been the Spam mailbox I would have had to move the messages out of the Pegasus new mail folder into a different Pegasus folder before taking on the next 200.
