Yes, actually, I do. The problem, I think, is that you're trying to have each user's account write the spam to /var/spool/mail/caughtspam.
Only one user can own that file, and if it's not been set with permissions to allow world to write to it, they won't be able to. Hence the reason I filter it to "$HOME/mail/caughtspam"...it's going to the user's own subdirectory, off of their own home directory, where they'll have permission to write. On Wed, 26 Jun 2002, K.Deepak wrote: > Dear Mike, > > I even tried this. I tried filtering the ^Subject. but it > didn'work. even the ~caughtspam folder doesn't have the mail. but, i have noticed a >strange > thing during the entire period. i.e, even if i have ^X-Spam-Flag or ^Subject, the >file > /var/spool/mail/caughtspam file is being touched , but nothing is being written into >the > folder. rather it writes the mail to the recipient folder only > > Any clues > > Thanks > K.Deepak > > > Mike Burger wrote: > > > Look in ~/caughtspam > > > > Personally, I use the example put forth in the SpamAssassin docs: > > > > :0: > > * ^Subject:.*\*\*\*\*SPAM\*\*\*\* > > $HOME/mail/caughtspam > > > > Since SA usually puts *****SPAM***** into the subject line, as well as the > > X-Spam-Flag, this usually catches it with no problem. > > > > On Tue, 25 Jun 2002, K.Deepak wrote: > > > > > Dear Harry, > > > > > > I tried for the past two days , but all in vain. i am >not able > > > to deliver the spammed messages into the folder caughtspam. I gave in the >addtional > > > entries given by you . the procmail log says "No match found for ^X-Spam-Flag: >Yes " . > > > I even tried replacing this statement in procmail with the egrep command > > > | /bin/egrep\ -e\ "^X-Spam-Flag: YES" > > > > > > I am attaching both my procmailrc file and the procmail log file . please help >me out. > > > it would be good if you can be give a detailed step by step procedure > > > > > > > > > Thanks > > > K.Deepak > > > > > > > > > > > > Harry Putnam wrote: > > > > > > > "K.Deepak" <[EMAIL PROTECTED]> writes: > > > > > > > > > Please help me out by telling the exact rules which will make the >spamassassing to > > > > > deliver the spammed messsages to the folder > > > > > /var/spool/mail/caughtspam > > > > > > > > Sounds like something else is wrong here. > > > > > > > > If you have the rule you posted: > > > > :0fw > > > > | spamassassin > > > > * ^X-Spam-Flag: Yes > > > > caughtspam > > > > It must mean that no `X-Spam-Flag: Yes' header is being inserted into > > > > the message. check for that headers presence in some of the mail you > > > > think should have gone to `caughtspam'. > > > > > > > > Or the procmail setup itself may not be configured correctly. > > > > > > > > I'd have to know more about your actual rule and the rest of your > > > > setup. But you might be able to help yourself by setting these > > > > variables in /etc/procmailrc .. first to make sure /etc/procmailrc is > > > > even being read. > > > > > > > > LOGABSTRACT=ALL > > > > LOGFILE=/some/log.file > > > > VERBOSE=YES > > > > > > > > Hopefully the log output in `log.file' will give some clues. > > > > > > > > Post any interesting log messages, or if you get none, we should look > > > > at how procmail is being invoked. > > > > > > > > _______________________________________________ > > > > Redhat-list mailing list > > > > [EMAIL PROTECTED] > > > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > > _______________________________________________ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
