[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] Unhappy procmail



>> > procmail: Suspicious rcfile
>"/home/sites/site1/users/username/.procmailrc"
>> > procmail: Couldn't read "/home/sites/site1/users/username/.procmailrc"
>> >
>> > Here is what my user .procmailrc file contains
>> >
>> > #filter all messages from cerain user
>> > :0:user.lock
>> > * ^From: .*\<user@domain\.com\>
>> > /dev/null
>> >
>> > Permissions are set to 644 (-rw-r--r-- )
>> >
>> > What's wrong with this??
>> >
>> Who is the owner? IIRC, it must be owned by the username.
>
>I chowned it to the username after I created it. No good.
>
>Kevin

From:  man procmail


       Suspicious rcfile "x"  The  owner  of the rcfile was not the recipient or root, the file was world writable, or
                              the directory that contained it was world writable,  or  this  was  the  default  rcfile
                              ($HOME/.procmailrc)  and either it was group writable or the directory that contained it
                              was group writable (the rcfile was not used).


This error popped up with the change from Raq2 to Raq3. Cobalt compiled procmail differently on the Raq3 perhaps leaving out the
GROUP_PER_USER option. If procmail is compiled with the GROUP_PER_USER option then procmail will trust the .procmailrc file if the
group involved is the user's primary group.

So chmod the .procmailrc file to 644 and chmod the username's directory to 744

We use the this setup to do autoresponders: the above permissions on a new user just for autoresponders. Set an alias on that user
name for each autoresponder matching the text files you want returned. If anyone needs the procmail recipe for this let me know.

Tony