procmail
[Top] [All Lists]

Re: all In one

2005-01-11 16:05:21
HI again before I begin, I fixed a few mistakes I found on the file
and a few mails are being sorted.



Your first problem should be whether you're actually invoking procmail 
properly.

        true but now that a few mails are being sorted it seems likely
        that procmail is being invoked. But whether properly or not is
        another thing.
I write a recipe in procmail an email arrives and goes to where?

That rather depends upon what MTA you have, what it's set up to deliver to 
for the local delivery, and if you're using a .forward file to invoke 
procmail.

        so it seems. exim4- fetchmail- procmail- mutt (I am not sure
        the order is correct is fetch mail (formail) before or after
        exim4?)


think that with procmail the idea is that the mail is taken from the
server and run through procmail/spamassasin

procmail is unaffiliated with spamassassin.  
        I realize just that spamassassin is somehow in the deliver chain, and
        might be a cause for problems

If your host has SA installed, 
it is quite possible that there's a hardcoded delivery following that which 
may bypass your local .procmailrc file.

        I am running this all locally so as I learn more I can get my
        hands dirty to fix it.
maybe the problem is that procmail isn't being accessed? how do I
check this (running debian)

well, a LOGFILE would help.  Hit the link in my .sig and read a few of the 
things there, and retrieve the procdiag script.

Running a procmail rcfile standalone BEFORE making it a live procmailrc is 
a really good idea -- that would allow you to see it working BEFORE 
subjecting all your actual email to it.

        True I just am such a greenhorn. I really want to get this all
        working but the learning curve is standing in front of me
        still...

        
SHELL=/bin/bash

Unnecessary to set unless you don't HAVE a shell (which is unlikely if 
you're able to log in), or if you're working on an /etc/procmailrc file 
which may process mail for other users who do not have shells.
      
        but probably won't hurt anything, right
PATH=/bin:/usr/bin:/usr/local/bin:/usr/sbin:

PATH generally doesn't need to be set, unless you're adding stuff not 
normally available to your default shell.
      
        ditto
VERBOSE=on

        I changed it
        
this is wrong setting if you're trying to figure out what is wrong.

MAILDIR=$HOME/Mail
LOGFILE=$HOME/Mail/procmaillog

Does $HOME/Mail _exist_?  Is it writeable?

        drwx------    2 aamehl   aamehl       4096 Jan 12 00:13 Mail
DEFAULT=$HOME/Mail/Inbox

This is different from "inbox" in the sense of the default system mailbox 
(in the mail spool).  If your mail is in fact arriving in this mailbox 
file, then procmail must surely be receiving it.

        you mean /var/spool/mail/aamehl right?
        it is empty, which means the mail is coming into ~/Mail/Inbox
        
# Nuke duplicate messages
:0 Wh: msgid.lock
| $FORMAIL -D 8192 msgid.cache

does this msgid.cache file exist?  If so, this recipe must be getting 
invoked.

        theone  aamehl $ find ./ -name msgid.cache
        ./Mail/msgid.cache
:0 c
backup

does the backup mailbox exist?  BTW, you should have a lock flag on the 
flags line...

        theone  aamehl $ ls Mail/
        Aaron  Spam                                 aamehl
        backup    ipaq      linux-il     opie         svg-dev
        Inbox  ^TO(_dot_)emacs-nxml-mode(_at_)yahoogroups(_dot_)com  
admin.incoming
        demudi    lad       msgid.cache  procmaillog  trash
        Sent   ^TOemacs-nxml-mode(_at_)yahoogroups(_dot_)com   ardour
        familiar  lilypond  mutt-users   svg
        theone  aamehl $
:0:
*^TO *(_dot_)emacs-nxml-mode(_at_)yahoogroups(_dot_)com
nxml

The condition line here lacks an asterisk, plus a dot all by itself is a 
SINGLE ANY character - you should also escape the dot you want interpreted 
as an actual dot.

        Wow thanks, I will follow the links and see what I see.
        I hope I haven't wasted your time, because I see that your
        link gives much of the information I need and it is most
        imformative.

        Thank you 
        Aaron
---
 Sean B. Straw / Professional Software Engineering

 Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
 Please DO NOT carbon me on list replies.  I'll get my copy from the list.


____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>