Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <4103A54E.20906@sbcglobal.net>
Date: Sun, 25 Jul 2004 05:19:26 -0700
From: George <d1945@sbcglobal.net>
Reply-To: d1945@sbcglobal.net
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: cygwin <cygwin@cygwin.com>
Subject: Fetchmail and Procmail
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

1.  I'm getting an error about a "suspicious ~/.procmailrc" file.  I'm
guessing this is a permissions problem.  If that's the case, could
someone let me know what the correct permissions should be?  For the
moment, using a '/etc/procmailrc' seems to be the only thing that works.

2.  Procmail seems to be rather slow.  I don't know whether this is
normal, but I've timed one mailbox download and it's taking on average
10 minutes to process 317 messages (2MB total).  Also, is procmail
supposed to be called for each individual message?

My rudimentary config files below.

Thanks.

# ============================
# ~/.fetchmailrc
# ============================

set logfile "/var/log/fetchmail.log"
set invisible
set no bouncemail

poll "pop.myisp.net"
protocol POP3
username "myname@myisp.net"
password "*****"
fetchall
keep
mda "/usr/bin/procmail -f %F -d %T"

# =============================
# /etc/procmailrc
# procmail configuration file
# =============================

VERBOSE=off
MAILDIR=$HOME/spool
DEFAULT=$MAILDIR/mbox
PMDIR=$HOME/.procmail
LOGFILE=$PMDIR/log
INCLUDERC=$PMDIR/subscriptionsrc

:0:
IN.spool

# =============================
# ~/.procmail/subscriptionsrc
# procmail configuration file
# =============================

:0:
* ^TO_NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
IN-S-ntbugtraq

:0:
* ^TO_vim@vim.org
IN-S-vim


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/