Quote:
Originally posted by MasterC
Welcome to LQ 
Which IMAP server are you using?
Cool
|
Thanks for the hospitality, great site
I'm using UW Imap. After reading through the documentation, it seems that the only way to get this particular IMAP server to change where it looks for stuff is to recompile. AFAICT
The box that I have this running on is a ClarkConnect box, which is based on RH7.2. I understand why they set everything up this way, because it just *works* right out of the box. I just found it annoying that the main mail spool file sits in /var/spool/mail/$USER and the other mailboxes sit in the root of ~/$USER. I thought it would be nice to be able to make everything nice and neat in ~/$USER/mail, but I did get it working properly by doing this to my .procmailrc, it's just not as neat as I would like: (I included the whole thing FYI)
Code:
MAILDIR=$HOME
DEFAULT=/var/spool/mail/jfeige
LOGFILE=$HOME/mail/proc.log
#
#:0fw: spamassassin.lock
#| /usr/bin/spamc -s 256000
:0fw: spamassassin.lock
* < 256000
| /usr/bin/spamassassin -a
:0
* ^X-Spam-Flag: YES
* ^X-Spam-Level: \*\*\*\*\*
Spam
#
:0
* ^X-Mailing-List: <debian-powerpc@lists.debian.org>
debian-ppc
I decided to use the spamassassin script instead of the spamd/spamc combo since it's a slow machine (P120) with only 96MB RAM and having spamd running all the time chews up about 30MB. I realize there is a little start up overhead for each message, but I'm willing to take that hit.
FYI, I also noticed that if I didn't setup spamd with a process limit like: "spamd -m 2" and I had a bunch of mail to retrieve, it would bring my box to a complete standstill. (Same reason I'm using the spamassassin.lock file with the spamassassin script)
Anyhoo, if you have any thoughts about the UW IMAP server, or perhaps a suggestion on a different IMAP server to use, OR any thoughts about email in general...
Thanks again!
-FB