I have set up a configuration that uses userdb and all mail userids are virtual, e.g. [EMAIL PROTECTED]

A number of virtual id's are under a single OS account, master.acct. The directories
are set up like this:

/home/master.acct/Maildir/domain1.com/user1
/home/master.acct/Maildir/domain1.com/user2

I wanted to implement spam assassin filtering on a sitewide basis. I developed a filter
that worked in a test account directory, using a .courier file and a .mailfilter file.

.courier:
| maildrop /home/master.acct/Maildir/domain1.com/user1/.mailfilter

This worked just fine. To reduce maintenance, I tried to move the .mailfilter file to
/etc/courier/maildroprc. I removed the .courier file, expecting  maildrop to run the
file as a default. It didn't seem to be executing.

I replaced the .courier file, this time with the command:
| maildrop /etc/courier/maildroprc

I got, maildrop can't open the file. (not the exact log message). Permissions were not
sufficient, because maildrop apparently has su'd to master.acct at this point, and does
not have write access to /etc/courier files. I tried opening up the permissions to the
maildroprc file, and I get a message to the effect that (permissions are too loose, not
executing for your own good).

After spending several days searching the docs and the web, I decided to try creating
just an account level filter. At least that would reduce the maintenance some. I put
the filter in a file /home/master.acct/Maildir/mailfilter, and I put in the file
/home/master.acct/Maildir/domain1.com/user1/.courier:
| maildrop /home/master.acct/Maildir/mailfilter

This returns the log message "unable to create dot-lock". I've seen all the mail 
requests
from people with this error, and the consistent response to "check permissions." I have
not seen a place where these permissions are documented, though. Here is a list of the
permissions of the relevant files:

drwxrwx---   12 mastera mastera     4.0K Sep 20 13:33 /home/master.acct
drwx------    3 mastera mastera     4.0K Sep 29 10:48 /home/master.acct/Maildir
drwx------    5 mastera mastera     4.0K Sep 29 10:53 
/home/master.acct/Maildir/domain1.com
-rw-------    1 mastera mastera     4.1K Sep 29 10:48 
/home/master.acct/Maildir/mailfilter
drwx------    6 mastera mastera     4.0K Sep 29 11:45 
/home/master.acct/Maildir/domain1.com/user1
-rw-------    1 mastera mastera       55 Sep 29 10:50 
/home/master.acct/Maildir/domain1.com/user1/.courier
drwx------    2 mastera mastera     4.0K Aug 23 19:26 
/home/master.acct/Maildir/domain1.com/user1/cur
drwx------    2 mastera mastera     4.0K Sep 29 11:58 
/home/master.acct/Maildir/domain1.com/user1/new
drwx------    5 mastera mastera     4.0K Sep 29 10:54 
/home/master.acct/Maildir/domain1.com/user1/.spam
drwx------    2 mastera mastera     4.0K Sep 29 11:58 
/home/master.acct/Maildir/domain1.com/user1/tmp

My maildrop is running under courier:
# maildrop -v
maildrop 1.5.3 Copyright 1998-2003 Double Precision, Inc.
GDBM extensions enabled.
Maildir quota extension enabled.

Please help. I think it would help greatly to know where the dot-lock files are
being created, and what relevant permissions need to be to make this work.




------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to