procmail
[Top] [All Lists]

Re: Re. folder problem

2004-01-19 20:41:32
At 13:57 2004-01-20 +1300, Adam Bogacki wrote:
I rewrote my /home/adam/.procmailrc from scratch and created a .forward file based on your notes and man pages. See below.

If procmail is in fact being invoked as the LDA by your non-sendmail MTA config, a .forward is redundant, and therefore undesired. You should confirm what the LDA is set as in your exim setup.

#RECIPES

Unfortunately, none of the recipes seem to work ...

But at this point, do you know that procmail is actually being invoked?

I'm a bit worried by the last few lines of your procdiag script.

Last few lines of OUTPUT from the script.

USER: adam (adam)
GROUPS: adam audio

Note that you belong to a group which is the same name as your username. Of couse, just looking at this, there's no way to guarantee that you have a group that contains nobody other than yourself, but this is very likely.

FQDN: Tux

THAT still bothers me. An FQDN should incorporate a domain and a TLD. "tux.paradise.net.nz" perhaps.

6755 1 root mail 67496 Tue Nov 4 08:04:47 2003 /usr/bin/procmail
procmail v3.22 2001/09/10
Default rcfile: $HOME/.procmailrc
It may be writable by your primary group

THIS (from procmail) is the confirmation that the primary group should be okay to be writeable.

NOTE: There is no /home/adam/.procmail file.

This means you don't happen to have a directory which many people happen to use, and which the script would have displayed perms for if it had.

0660 1 adam mail 0 Fri Jul 11 21:23:00 2003 /var/mail/adam
CAUTION: /var/mail/adam perms exceed 7755: curb back to 0640

Generic warning. Since procmail is compiled on your system to allow for files which are writeable by your primary group (adam, in your case), this isn't a concern. Generally speaking, GROUP WRITE on your homedir isn't a good thing, but on your system, your primary group is supposed to be uniquely you.

2775 2 root mail 4096 Tue Jan 20 09:29:17 2004 /var/mail/

/var/mail/ is owned by root and all that fun stuff. What specifically alarms you about this?


I'd suggest checking your syslog and seeing what is in there.

---
 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(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

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