Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the ''Subscribe' to IMAP folders in Mail.app with a proxy' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
'Subscribe' to IMAP folders in Mail.app with a proxy
Authored by: moritzh on Nov 08, '05 04:52:48PM

I'm using the newest version of the script (about a month old or so), but I have the following problem: After having Mail.app running for a while (maybe 10 minutes) without any problems at all, the script suddenly goes crazy and consumes all the CPU power of the computer. I've doublechecked that it is indeed the script by looking at the Activity Monitor (it shows up as a process named "perl" in the list as it is a Perl script) and stopping/starting the script manually in the Terminal via "sudo imapfilter.pl". Strange enough, Mail.app basically still functions, it (and everything else) is just very slow as the CPU is so busy. As soon as I quit Mail.app, the CPU usage goes down to normal again. When I restart Mail.app, same game: At first it's OK, but somewhen it goes crazy again.

Anybody any ideas? I have configured the script as a Startup Item, I connect via port 443 to localhost from which a SSL connection on port 993 goes to my actual mail server. I've set up Mail.app to check for new mail every 5 minutes. To be sure, I have even told my keychain to lock itself only after a much longer time than 5 minutes (20 minutes) to make sure it has nothing to do with Mail.app/the script lacking the required access to the password - but to no avail. At first I had the feeling that the problem went away when I selected some mailboxes on the IMAP server to cause a refresh or after manually entering the password, but this turned out to be an illusion.

I have contacted the author and asked about it, but he does not reply.

Ah yes, one more thing I guess I should mention: I have a firewall set up in stealth mode (the Mac OS X built-in firewall, that is). I can't remember for sure, but even though I have not opened port 443/993 on the firewall, I am quite positive that I did try opening these ports for testing but without success. I'm using Mac OS X 10.4.3 (but the problem has always been there, from 10.4.0 and some minor versions of imapfilter.pl before the current one - it's been there for as long as I've been using the script).

I'd very much appreciate some help as I really need the feature to `unsubscribe' from the houndreds of public folders with millions of messages on my university IMAP server. Thanks!



[ Reply to This | # ]
Correction: I use port 1143 instead of 443
Authored by: moritzh on Nov 08, '05 04:57:15PM

Small correction: I do use another port (1143) instead of 443 for the local connection to avoid coflicts with the standard port 443, I wrote 443 by mistake.



[ Reply to This | # ]