Hmm. I am using 3.14, but I am not using maildir. I am using imap.
Either way, like I said, procmail works fine if the 'Lines' header
recipe is commented out. Here is what I find in the ~/.procmail.log:
procmail: [3167] Fri Jun 15 02:58:30 2001
procmail: Match on ! ^Lines:
procmail: Score:
BTW, this is my /etc/procmailrc, in case it is helpful:
SHELL=/bin/sh
MAILDIR=/usr/cyrus
LOGFILE=$HOME/.procmail.log
VERBOSE=yes
# Place any antispam or other universal filters here. Don't
# write to files or pipe to programs unless you are ABSOLUTELY
# SURE you know what you are doing!
# :0
Good news. I left sendmail up using the procmail config, and all mail
that came to me between roughly 3:30 and 9:00 this morning went to
/dev/null for some reason. I think it is the user+detail@server
format I use for mail sorting. Usually deliver handles that.
I also noticed something odd in
I was just going to forward your message to procmail list and saw that you
did that yourself :)
On Fri 15 Jun 2001, Louis LeBlanc wrote:
Good news. I left sendmail up using the procmail config, and all mail
that came to me between roughly 3:30 and 9:00 this morning went to
/dev/null for some
On Fri 15 Jun 2001, Louis LeBlanc wrote:
Hmm. I am using 3.14, but I am not using maildir. I am using imap.
Either way, like I said, procmail works fine if the 'Lines' header
recipe is commented out. Here is what I find in the ~/.procmail.log:
This is really odd. It works fine for me on 3
On 06/15/01 09:44 AM, Igor Pruchanskiy sat at the `puter and typed:
On Fri 15 Jun 2001, Louis LeBlanc wrote:
Hmm. I am using 3.14, but I am not using maildir. I am using imap.
Either way, like I said, procmail works fine if the 'Lines' header
recipe is commented out. Here is what I find
On Fri, Jun 15, 2001 at 12:48:24PM -0400, Louis LeBlanc wrote:
I don't know what the deal is. Like I said in the procmail message, I
suspect that part of the problem is in the lock attempt at
/var/spool/mail/leblanc.lock
What do you do there? do you have permissions to write to that dir?
On 06/15/01 01:04 PM, Dan Boger sat at the `puter and typed:
On Fri, Jun 15, 2001 at 12:48:24PM -0400, Louis LeBlanc wrote:
can't you just set $LOCKFILE to someplace else where you do have write
permissions?
Apparently not. I entered the following line at the top of the
/etc/procmailrc
On Fri, Jun 15, 2001 at 02:14:54PM -0400, Louis LeBlanc wrote:
On 06/15/01 01:04 PM, Dan Boger sat at the `puter and typed:
On Fri, Jun 15, 2001 at 12:48:24PM -0400, Louis LeBlanc wrote:
can't you just set $LOCKFILE to someplace else where you do have write
permissions?
Apparently
Hmm. I made a couple changes:
in /etc/procmailrc:
DEFAULT=$HOME/
unset LOCKFILE
This is what I got for headers:
Return-Path: leblanc
Received: (from leblanc@localhost)
by acadia.ne.mediaone.net (8.9.3/8.9.3) id OAA18915
for [EMAIL PROTECTED]; Fri, 15 Jun 2001
14:15:43 -0400
What version of procmail are you using ?
I am using procmail-3.15, which is the only version that does not need to
be patched to use Maildir. Also make sure that it finds formail. Try
giving in the full path and see what procmail log file has to say about
this.
amorphis:~$ grep LOG .procmailrc
add to your .procmailrc
:0 Bfh
* H ?? !^Lines:
* -1^0
* 1^1 ^.*$
| formail -A Lines: $=
On Wed 30 May 2001, Louis LeBlanc wrote:
I noticed that mutt does not look at how many lines a message has
until you explicitly read it. Once you do, mutt only remembers the
number until you quit. Some
12 matches
Mail list logo
