I have:
VERBOSE=yes
LOGABSTRACT=all
LOGFILE=/var/log/procmail/procmaillog.`date +%m-%d-%y`
:0fw
| spamc -u $LOGNAME
in my /etc/procmailrc file and then this in my main procmail log:
procmail: Executing "spamc,-u,{user_name}"
procmail: [8286] Thu Mar 28 22:58:05 2002
procmail: Assigning
"PATH=/home/{user_name}/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R6/bin"
Subject: *****SPAM***** Snowhite and the Seven Dwarfs - The REAL story!
Folder: /var/spool/mail/{user_name} 28719
however, the mail is not actually delivered to {user_name}.
Olivier Nicole wrote:
> For all debugging purposes, I suggest one runs spamd without the -d,
> and maybe with -D to see debug information onf screen.
>
> The running as root message is just a warning, not an error, and
> should not prevent spamc/d to tag the message (it can prevent it to
> create user preferences, for that purooise I use -u $LOGNAME on the
> spamc line).
>
> Here is my /etc/procmailrc (site wide):
>
> :0fwE
> | /usr/local/bin/spamc -u $LOGNAME
>
> :0e
> {
> EXITCODE=$?
> }
>
> DATE=`date +%Y%m%d%H%M`
> PID=`echo $$`
> SPAMFILE=$DEFAULT-spam.$DATE.$PID
>
> :0:
> * ^X-Spam-Status: Yes
> $SPAMFILE
>
> Only diffreence from the man is that it push the spam into
> /var/mail/<username>-spam.<date><pid>
>
> This is because I quarantine spam and deliver a daily summary to
> users, allowing them to automatically recover false +ve.
>
> And I run spamd as /usr/local/bin/perl /usr/local/bin/spamd -a -c -d
>
> I also remember reading that the upgrade from 2.01 to 2.11 erased some
> SA site config files (or they changed name).
>
> Olivier
>
>
>
>>I'll throw my 2-cents in and let y'all know I have the same problem
>>
>>Gene Ruebsamen wrote:
>>
>>>Quoting Olivier Nicole <[EMAIL PROTECTED]>:
>>>
>>>
>>>
>>>>>when I run spamc < sample-spam.txt > spam.out
>>>>>spamc seems to work; however, when I receive an incoming mail message, I
>>>>
>>>>get
>>>>
>>>>Does it work or not? Do you get a SA header in the output?
>>>
>>>
>>>Running spamc < sample-spam.txt > spam.out
>>>as a non-root user works fine. I see the SA header in the output.
>>>I also see a message in the maillog file indicating the message was spam.
>>>However, when procmail calls spamc, things do not work, and I get the messages
>>>in my maillog file that I posted earlier.
>>>
>>>
>>>
>>>>>the same error in the maillog:
>>>>>
>>>>>Mar 27 16:55:05 mail spamd[2590]: connection from sandman.realtyroad.com
>>>>
>>>>[
>>>>
>>>>
>>>>>127.0.0.1 ] at port 2017
>>>>>Mar 27 16:55:05 mail spamd[6207]: Still running as root: user not
>>>>>specified, not found, or set to root. Fall back to nobody.
>>>>>
>>>>>
>>>>>And no, the mail is not being sent to (or from) the root user. Why would
>>>>>running spamc (as non root) work; yet, when receiving an e-mail not work?
>>>>
>>>>Means that spamc hands the message out to spamd. And that spamd is
>>>>running as root (well you did not change spamd to run as non-root). So
>>>>both messages are not errors.
>>>>
>>>>Now how do you call spamc from procmail?
>>>
>>>
>>>:0fw
>>>| spamc
>>>
>>>as stated in the www.spamassassin.org/sitewide.html file.
>>>
>>>
>>>
>>>>Olivier
>>>>
>>>>_______________________________________________
>>>>Spamassassin-talk mailing list
>>>>[EMAIL PROTECTED]
>>>>https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>>>
>
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
--
================================
Jeffrey Bacon
================================
Administrator, Breakfast.ca
Student, Carleton U.
Java Programmer, Extr-ordinaire!
--------------------------------
[EMAIL PROTECTED]
http://www.breakfast.ca/~jjbacon
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
