Well, I have both inode and block quota and even if the user is in the
limits for both of thenm mail is still delivered.
see en example users quota settngs
Disk quotas for user ceylan (uid 1220):
Filesystem usage quota limit grace files quota limit grace
/home 10314* 5000 6000 none 177* 150 300 none
I dont have /etc/procmailrc but I have /usr/local/etc/procmailrc
It is a simple file to filter spam though.
here is the file
:0
* !^Subject:.*SiFRELi UYDU KANALLARI ARTIK BEDAVA
* !^Subject:.*UCRETSiZ EGiTiM VE KARSILIKSIZ BURS iMKANI
* !B ?? 123spam123
$HOME/mail/INBOX
:0
/usr/local/users/staff/ard/mail/spam
I was wondering if there can be a problem about the UID of the procmail
process? But I checked a new user I created and his INBOX file which was
created by procmail had the right owner and group ids set.
Any more suggestions?
Evren
On Thu, 9 Aug 2001, Philip Guenther wrote:
Evren Yurtesen <yurtesen(_at_)ispro(_dot_)net(_dot_)tr> writes:
hey I have a little problem because procmail continues to deliver to my
users even though they are overquota! I have compiled the procmail to
deliver to home directory of the user. I tried the quota system by su
username and tried to create a file but it didnt succeed which ment to me
that quota system is working fine.
File or disk-block quota? If you can't create a zero-length file then
the user has reached his or her file (inode) quota. Procmail will bounce
the message when the write() system call fails, so it's more concerned
with the disk-block quota.
Also, do you have anything in the /etc/procmailrc file that performs
delivery, or are you letting the implicit delivery to $DEFAULT handle
things?
Philip Guenther
Procmail Maintainer
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail