Loading Profile...
Recent activity
Subscribe to this feed
A comment on the problem "Storage in mail files make back-up difficult" in Postbox, Inc.:
Why don't you just symlink your Postbox folder to your second partition/drive? – besson3c, on October 08, 2009 08:17-
besson3c replied on September 27, 2009 02:53 to the question "Moving large amounts of mail w. Postbox/Courier IMAP over IMAP causes infinite loop" in Postbox, Inc.:
I forgot to add, I also ran a ktrace of my imapd process while this was going on, and it appeared to go through my messages in sequential order, and then run through them again once it was done. There were several imapd processes open (at one time probably around 6-10), so I'm assuming they were all doing the same thing in parallel which was what was making the messages in tmp accumulate in such quantity.
There is something fishy about the way Postbox/Thunderbird sends these IMAP move commands to Courier IMAP, although it's hard to put my finger on what is going on exactly. -
besson3c replied on September 27, 2009 02:40 to the question "Moving large amounts of mail w. Postbox/Courier IMAP over IMAP causes infinite loop" in Postbox, Inc.:
Around 7000 messages or so. The infinite loop goes on on the server side in continuing to write message to the tmp folder in the maildir. Like I said, over 300,000 messages accumulated there for me before I intervened. Did you read the thread I posted above? It sounds like exactly the problem I'm experiencing, only I'm not using NFS and I have played around with increasing the Postbox timeout value from 60 seconds to 120 to no avail.
Thanks for your time and effort here, I appreciate it! -
besson3c replied on September 27, 2009 02:17 to the question "Moving large amounts of mail w. Postbox/Courier IMAP over IMAP causes infinite loop" in Postbox, Inc.:
Okay, I did discover the error console, although I didn't find much there of use.
It appears that Postbox marks items for deletion when large numbers of messages are moved, but it doesn't actually delete them until the move has been confirmed (which is good). While struggling with this problem I restarted Postbox several times and manually deleted the tmp folder from the server. This is no doubt what has caused Postbox to be confused as far as it showing the spinning wrist watch now.
However, the number of messages in my Inbox does not match the actual number. What is confusing is that rebuilding the Index via folder properties -> Rebuild Index button yields different results than Tools -> Index -> Index this Folder. I suppose the latter rebuilds Postbox's internal index, but does not actually rebuild the local IMAP cache by downloading headers again?
This part was merely confusing, but again, the real problem here is the infinite loop I'm able to consistently invoke. Developers, please let me know if I can help you with reproducing this! -
besson3c asked a question in Postbox, Inc. on September 27, 2009 01:50:
Moving large amounts of mail w. Postbox/Courier IMAP over IMAP causes infinite loopMoving large amounts of mail into folders using Postbox and Courier-IMAP IMAP (such as archiving messages) causes an infinite loop of creating new messages in .Archive/tmp on the server and gobbling up disk space (mine had grown to over 300,000 messages). Moreover, there is no real progress bar or any sort of indication as to what Postbox is actually doing, which is particularly problematic for a problem such as this.
What sort of information do you need from me to help solve this problem? This problem sounds similar to the one reported here: http://www.nabble.com/nfs-mounted-mai... except I'm not using NFS. I'm still getting the spinning wristwatch after deleting this folder (I will recover my lost email via backup), and I have no idea what Postbox thinks it is doing.
Being able to bring an entire server to its knees this way with a badly behaving client is quite troublesome. What can be done? -
besson3c replied on April 27, 2009 15:44 to the problem "Not receiving growl notifications" in Postbox, Inc.:
I was having this problem, but uninstalling and reinstalling Growl seemed to fix this. For some reason Postbox wasn't registered in my Growl applications listing at Postbox launch, but it was added once I received my first email message.
Then again, Growl has always been rather temperamental for me, so this may not be a Postbox specific problem.
