On 08/20/05 04:17 PM, Glyn Tebbutt sat at the `puter and typed: > Louis LeBlanc wrote: > > On 08/20/05 08:00 AM, David Kelly sat at the `puter and typed: > > > >>On Aug 20, 2005, at 6:15 AM, Pat Maddox wrote: > >> > >> > >>>I run courier-imap, works really well for me. > >> > >>I'm reading this thread because courier-imap works but I'm less than > >>happy with maillog being flooded with: > >> > >>Aug 20 07:41:12 Grumpy imapd: Failed to create cache file: > >>maildirwatch (dkelly) > >>Aug 20 07:41:12 Grumpy imapd: Error: Input/output error > >>Aug 20 07:41:12 Grumpy imapd: Check for proper operation and > >>configuration > >>Aug 20 07:41:12 Grumpy imapd: of the File Access Monitor daemon (famd). > >> > >>Also MacOS X Mail.app often has connection problems. Suspect that > >>problem has something to do with mutt modifying my Maildir between > >>Mail.app connections as once Mail.app has a good connection it stays > >>good. OTOH procmail delivers to my Maildir INBOX which isn't much > >>different than what I do with mutt. > > > > > > > > Never seen these problems. IIRC, there was a thread about error > > messages coming from famd several months ago. As I understand the > > message, it's just a famd config issue, but I don't know for sure. > > > > I use procmail to pipe through SpamAssassin (spamd) and do some other > > sorting before delivering to maildirs, but I never have connection > > problems (unless I forget to recheck configs after upgrading the > > courier auth package). Of course, I haven't talked my wife into > > letting me buy that PowerBook yet . . . > > > > Courier-imap has been running flawlessly for me for around 3 years. I > > understand it can handle several hundreds (or thousands) of times more > > load than I can give it. It's not idiot proof, but running a mail > > server really shouldn't be, don't you think? > > > > Lou > I also use courier-imap which just sit's back and does it's job nicely. > Can I ask to take a look at your .procmailrc as I've had some issue's > with procmail not filtering my mail into the inbox's properly (all over > folder's were find thou) > Cheers
No problem. You'll find it attached. Hopefully the commentary is clear enough what my intention is. Lou -- Louis LeBlanc FreeBSD-at-keyslapper-DOT-net Fully Funded Hobbyist, KeySlapper Extrordinaire :) Please send off-list email to: leblanc at keyslapper d.t net Key fingerprint = C5E7 4762 F071 CE3B ED51 4FB8 AF85 A2FE 80C8 D9A2 QOTD: "Don't let your mind wander -- it's too little to be let out alone."
FOLDER = $1
PATH="$HOME/bin:/usr/local/cyrus/bin:/usr/bin:/bin:/usr/local/bin:/usr/include:/usr/local/sbin:/bin:/sbin:/usr/sbin:."
SHELL=/bin/sh
MAILDIR=$HOME/.Maildir
LOGFILE=$HOME/.procmail_log
DEFAULT=$HOME/.Maildir
# VERBOSE=on
VERBOSE=off
LOGABSTRACT=all
NL="
"
TIMEOUT=1200
VIRDIR=$MAILDIR/.virus
NIGDIR=$MAILDIR/.spam
PORNDIR=$MAILDIR/.spam
# Need to remove the bogus 'From ' header if it's there.
:0hfw
| formail -I "From "
#############################################################
## NEVER CHANGE ANYTHING ABOVE THIS LINE ON YOUR OWN ##
#############################################################
# Place any antispam or other filtering recipes here.
# Don't write to files or pipe to programs unless you
# are ABSOLUTELY SURE you know what you are doing!
:0
* $ ^To:.*add2list
{
# whitelist - subject with add2white <[EMAIL PROTECTED]> will add the email
# address to my SA whiltelist. Make sure the whitelistpasswd is in the body.
:0
* ^Subject:.*add2white[ ]*\/[^ ].+
{
ADDR=$MATCH
:0Bi:whitelist.lck
* ^whitelistpasswd
|nice -n 20 spamassassin --add-addr-to-whitelist=$ADDR
:0
/dev/null
}
# blacklist - subject with add2black <[EMAIL PROTECTED]> will add the email
# address to my SA blacklist. Make sure the whitelistpasswd is in the body.
:0
* ^Subject:.*add2black[ ]*\/[^ ].+
{
ADDR=$MATCH
:0Bi:blacklist.lck
* ^whitelistpasswd
|nice -n 20 spamassassin --add-addr-to-blacklist=$ADDR
:0
/dev/null
}
}
# I have many "honeypot" addresses which I seeed into newsgroups when I'm
# bored. They are all aliased to [EMAIL PROTECTED] This catches
# them and automagically teaches them to the bayes db. Make sure any posting
# is presented with a very clear warning that the address is a honeypot and
# what is done with messages recieved.
:0
* FOLDER ?? ^^trap^^
{
# VERBOSE=off
# ls -l ~/.honeypot_hits tells you how many you've caught
LOGFILE=$HOME/.honeypot_hits
LOG="."
LOGFILE=$HOME/.procmail_log
# VERBOSE=on
# Report spam
:0c:honeypot.lock
| nice -n 20 /usr/local/bin/spamassassin -r
:0:salearn.lock
| nice -n 20 /usr/local/bin/sa-learn --spam --no-rebuild
:0
/dev/null
}
# VERBOSE=on
# Check for some obvious virii - YAVR adaptations
# this never gets anything since I installed clamav and f-prot
INCLUDERC=/usr/local/etc/mail/procmail/nkvir-rc
# VERBOSE=off
# If the message isn't too big, hasn't already been scanned, and isn't a direct
# dump, scan it. Also, don't scan anything from the SpamAssassin list, since
# it often includes tags that might skew my bayes DB.
:0
* B ?? < 256000
* FOLDER ?? !spam
* FOLDER ?? !assassin
{
# Always try spamc first, if spamd is running and not overloaded, this is
# more efficient.
:0fw
| spamc -x
# If that doesn't work, use spamassassin directly, but count it.
# ls -l ~/.backup_sacheck will tell us how much overflow is occurring.
:0e
{
# VERBOSE=off
LOGFILE=$HOME/.backup_sacheck
LOG="."
LOGFILE=$HOME/.procmail_log
# VERBOSE=on
:0fw
| spamassassin
}
# I segregate autolearned spam (definitely spam) from regular (probably)
# spam.
:0
* autolearn=spam
{
:0
{ FOLDER=spam_autolearn }
}
# My spamlearn.pl will take "confirmed" spam (that marked as "read" which is
# moved to the .../cur/ directory in the spam folder) and pipe it through the
# bayes learner every night.
:0E
* ^X-Spam-Status: YES
{
:0
{ FOLDER=spam }
}
# VERBOSE=off
}
#############################################################
## NEVER CHANGE ANYTHING BELOW THIS LINE ON YOUR OWN ##
#############################################################
# By this time, $FOLDER must be the name of the folder you want this
# message delivered to, or blank if it is to go into the INBOX.
:0
* FOLDER ?? !spam
{
##
## PGP
##
:0
* FOLDER ?? !spam
* FOLDER ?? !trash
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
{
:0 fBhw
* ^-----BEGIN PGP MESSAGE-----
* ^-----END PGP MESSAGE-----
| formail -Y -f -i "Content-Type: application/pgp; format=text;
x-action=encrypt"
:0 fBhw
* ^-----BEGIN PGP SIGNED MESSAGE-----
* ^-----BEGIN PGP SIGNATURE-----
* ^-----END PGP SIGNATURE-----
| formail -Y -f -i "Content-Type: application/pgp; format=text;
x-action=sign"
}
}
:0 fhw
* FOLDER ?? !trash
* FOLDER ?? !spam
* 1^0
* B ?? 1^1 ^.*$
* B ?? -1^0 ($)($)^^
| formail -f -I "Lines: $="
VERBOSE=on
:0 w
* FOLDER ?? .
$MAILDIR/.$FOLDER/
# Only if there was no extension do we try this
:0 wE
$MAILDIR/
# Whichever one we tried, failed
EXITCODE=$?
LOG="$NL"
$DEFAULT
pgpELaRdyV0T2.pgp
Description: PGP signature
