spamassassin Problems

[A Ve]

Hi !

System: Fedora2, Following Apps installed: spamassassin-2.63-8,
postfix-2.1.4-4.fc2.

Postfix 2.1.4 is finally working - after some help from postfix
mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.

But ... spamassassin still not running. I configured it - as suggested in
the spamassassin doc:

master.cf before:
  smtp      inet  n       -       n       -       -       smtpd

mater.cf after:
smtp      inet  n       -       n       -       -       smtpd -o
content_filter=spamassassin

  spamassassin  unix  -       n       n       -       -       pipe 
user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
${recipient}

(taking care of linebreaks)

I restarted spamassassin + postfix and sent some spam-style mail. The
output from /var/log/maillog:

Aug 30 16:19:22 mail spamd[31884]: clean message (0.0/5.0) for user:200 in
0.1 seconds, 976 bytes.
Aug 30 16:19:22 mail spamc[31883]: exec failed: No such file or directory
Aug 30 16:19:22 mail postfix/pipe[31882]: EB152368423:
to=<user(a)example.com>, relay=spamassassin, delay=1, status=deferred
(system resource problem)

And the mail is not delivered / "vanished away" ... ;-) Any ideas ?

Regards, ave.

[Scot L. Harris]

Let me say up front that I have not used postfix before.

On Mon, 2004-08-30 at 11:02, A Ve wrote:
>  Hi !
>  
>  System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  postfix-2.1.4-4.fc2.
>  
>  Postfix 2.1.4 is finally working - after some help from postfix
>  mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.
>  
>  But ... spamassassin still not running. I configured it - as suggested in
>  the spamassassin doc:
>  
>  master.cf before:
>    smtp      inet  n       -       n       -       -       smtpd
>  
>  mater.cf after:
>  smtp      inet  n       -       n       -       -       smtpd -o
>  content_filter=spamassassin
>  
>    spamassassin  unix  -       n       n       -       -       pipe 
>  user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
>  ${recipient}
>   
Do you really want to use sendmail here?  Do you even have sendmail
installed if you are using postfix?

>  (taking care of linebreaks)
>  
>  I restarted spamassassin + postfix and sent some spam-style mail. The
>  output from /var/log/maillog:
>  
>  Aug 30 16:19:22 mail spamd[31884]: clean message (0.0/5.0) for user:200 in
>  0.1 seconds, 976 bytes. 
Looks like spamassassin ran as expected.

>  Aug 30 16:19:22 mail spamc[31883]: exec failed: No such file or
> directory 
This makes me think that spamassassin tried to exec /usr/sbin/sendmail
and could not find it.  I really suspect that you want to use postfix
here instead of sendmail which is probably not loaded on your system.

>  Aug 30 16:19:22 mail postfix/pipe[31882]: EB152368423:
>  to=<user(a)example.com>, relay=spamassassin, delay=1, status=deferred
>  (system resource problem)
>   
Now postfix does not know what to do since spamassassin threw an error.

>  And the mail is not delivered / "vanished away" ... ;-) Any
> ideas ?
>   
Not sure where postfix keeps it files.  Sendmail normally keeps queued
messages under /var/spool/mqueue if they were in transit or deferred. 

>  Regards, ave. 
-- 
Scot L. Harris
webid(a)cfl.rr.com

I'm so miserable without you, it's almost like you're here.

[HaJo Schatz]

On Mon, 2004-08-30 at 23:16, Scot L. Harris wrote:
>  Let me say up front that I have not used postfix before.
>  
>  On Mon, 2004-08-30 at 11:02, A Ve wrote:
>  > Hi !
>  > 
>  > System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  > postfix-2.1.4-4.fc2.
>  > 
>  > Postfix 2.1.4 is finally working - after some help from postfix
>  > mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.
>  > 
>  > But ... spamassassin still not running. I configured it - as suggested in
>  > the spamassassin doc:
>  > 
>  > master.cf before:
>  >   smtp      inet  n       -       n       -       -       smtpd
>  > 
>  > mater.cf after:
>  > smtp      inet  n       -       n       -       -       smtpd -o
>  > content_filter=spamassassin
>  > 
>  >   spamassassin  unix  -       n       n       -       -       pipe 
>  > user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
>  > ${recipient}
>  > 
>  
>  Do you really want to use sendmail here?  Do you even have sendmail
>  installed if you are using postfix? 
postfix substitutes sendmail with it's own version, that should be OK
(if the system was switched to postfix properly, that is
/usr/sbin/sendmail will be a symlink to /etc/alternatives/mta which will
link to /usr/sbin/sendmail.postfix)

But, A Ve, fyi, there's an easier way if you use procmail for local
delivery than to patch main.cf. Add the following to /etc/procmailrc:

:0fw
| /usr/bin/spamc

Then, start spamd. Finally, run spamc manually to test the setup:

$ cat mail.txt | spamc > checkedmail.txt

and check the headers of checkedmail.txt


-- 
HaJo Schatz <hajo(a)hajo.net&gt;
http://www.HaJo.Net

PGP-Key:  http://www.hajo.net/hajonet/keys/pgpkey_hajo.txt

[Scot L. Harris]

On Mon, 2004-08-30 at 11:30, HaJo Schatz wrote:

>  
>  postfix substitutes sendmail with it's own version, that should be OK
>  (if the system was switched to postfix properly, that is
>  /usr/sbin/sendmail will be a symlink to /etc/alternatives/mta which will
>  link to /usr/sbin/sendmail.postfix)
>  
>  But, A Ve, fyi, there's an easier way if you use procmail for local
>  delivery than to patch main.cf. Add the following to /etc/procmailrc:
>  
>  :0fw
>  | /usr/bin/spamc
>  
>  Then, start spamd. Finally, run spamc manually to test the setup:
>  
>  $ cat mail.txt | spamc > checkedmail.txt
>  
>  and check the headers of checkedmail.txt
>   
I use procmail in combination with the real sendmail package.  Has
worked very well here.

Also, if you are trying to block spam another tool I have found that is
even more effective is greylisting.  I implemented milter-greylist and
went from 3000-6000 spam a day to 5-10 spam a day.  And those are caught
by spamassassin.

Spamassassin is great.  But on a site that gets significant email you
can end up loading down the server.  I saw some spam spikes that
generated a 20+ load average on the server.  In addition it still took
time every day to review the spam bucket for any false positives and to
feed the spam to the bayes database.  

Greylisting deflects 98 to 99% of spam before you even read the data
portion of the message.  There are several versions of greylisting
available including packages that work with postfix I believe.  

Has got to be one of the most effective spam fighting tools out there. 
I just wish ISPs would implement it on all their servers.

-- 
Scot L. Harris
webid(a)cfl.rr.com

Veni, vidi, vici.
	[I came, I saw, I conquered].
		-- Gaius Julius Caesar

[Mike Burger]

On Mon, 30 Aug 2004, Scot L. Harris wrote:

>  Let me say up front that I have not used postfix before.
>  
>  On Mon, 2004-08-30 at 11:02, A Ve wrote:
>  > Hi !
>  > 
>  > System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  > postfix-2.1.4-4.fc2.
>  > 
>  > Postfix 2.1.4 is finally working - after some help from postfix
>  > mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.
>  > 
>  > But ... spamassassin still not running. I configured it - as suggested in
>  > the spamassassin doc:
>  > 
>  > master.cf before:
>  >   smtp      inet  n       -       n       -       -       smtpd
>  > 
>  > mater.cf after:
>  > smtp      inet  n       -       n       -       -       smtpd -o
>  > content_filter=spamassassin
>  > 
>  >   spamassassin  unix  -       n       n       -       -       pipe 
>  > user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
>  > ${recipient}
>  > 
>  
>  Do you really want to use sendmail here?  Do you even have sendmail
>  installed if you are using postfix? 
Yes...there's a postfix executable file called "sendmail" for the sake of 
compatibility with programs that expect a "sendmail" executable to exist.
-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org

To be notified of updates to the web site, visit 
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a 
message to:

site-update-request(a)bubbanfriends.org

with a message of: 

subscribe

[Scot L. Harris]

On Mon, 2004-08-30 at 11:40, Mike Burger wrote:

>  > 
>  > Do you really want to use sendmail here?  Do you even have sendmail
>  > installed if you are using postfix?
>  
>  Yes...there's a postfix executable file called "sendmail" for the sake of 
>  compatibility with programs that expect a "sendmail" executable to exist.
Ah!  Learn something new everyday.  :)  Like I said I have not used
postfix before.

Verify the permissions and paths on spamc and the sendmail executable. 
Probably already done but sometimes it is something simple like that.

The next thing I would look at is the user that you run spamc as.  It
looks like you are specifying test as the user.  You need to check that
the .spamassassin directory has been configured under that user as this
is where your bayes database will most likely be going.  Also make sure
your various config files (local.cf, user_prefs) has the correct path
settings for the bayes database.  Under the /home/test/.spamassassin
directory you may also have a user_prefs file which can be used to
override some of the options in local.cf.  local.cf is normally under
/etc/mail/spamassassin along with additional rule sets that you may want
to include from the SARE web site.

All of that assumes that spamc is running as the user test.  If not you
will need to sort out which user it is run as to locate the correct set
of config files for it.

-- 
Scot L. Harris
webid(a)cfl.rr.com

"How to make a million dollars:  First, get a million dollars."
-- Steve Martin

[John Thompson]

Scot L. Harris wrote:

>  On Mon, 2004-08-30 at 11:02, A Ve wrote:
>  
> >  spamassassin  unix  -       n       n       -       -       pipe 
> >user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
> >${recipient} 
>  Do you really want to use sendmail here?  Do you even have sendmail
>  installed if you are using postfix? 
IIRC, one of the postfix modules is called "sendmail" for compatibility 
reasons.  Thus it is possible that the OP could be calling "sendmail" as 
the Postfix MTA.

-- 

-John (john(a)os2.dhs.org)

[Gary Allen Vollink]

It appears that /usr/bin/spamc doesn't exist (according to your error message.

On my machine...

% locate spamc
/usr/bin/spamc

Is your spamc located there?  Is Spamassassin installed from the default 
packages (or did you load a different SpamAssassin RPM)?  Perhaps your 
spamc is located elsewhere, like /usr/local/spamassassin/bin/spamc or 
/usr/local/bin/spamc?

Good luck,
Gary Allen Vollink


A Ve wrote:

> Hi !
>
> System: Fedora2, Following Apps installed: spamassassin-2.63-8,
> postfix-2.1.4-4.fc2.
>
> Postfix 2.1.4 is finally working - after some help from postfix
> mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.
>
> But ... spamassassin still not running. I configured it - as suggested in
> the spamassassin doc:
>
> master.cf before:
>   smtp      inet  n       -       n       -       -       smtpd
>
> mater.cf after:
> smtp      inet  n       -       n       -       -       smtpd -o
> content_filter=spamassassin
>
>   spamassassin  unix  -       n       n       -       -       pipe 
> user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
> ${recipient}
>
> (taking care of linebreaks)
>
> I restarted spamassassin + postfix and sent some spam-style mail. The
> output from /var/log/maillog:
>
> Aug 30 16:19:22 mail spamd[31884]: clean message (0.0/5.0) for user:200 in
> 0.1 seconds, 976 bytes.
> Aug 30 16:19:22 mail spamc[31883]: exec failed: No such file or directory
> Aug 30 16:19:22 mail postfix/pipe[31882]: EB152368423:
> to=<user(a)example.com>, relay=spamassassin, delay=1, status=deferred
> (system resource problem)
>
> And the mail is not delivered / "vanished away" ... ;-) Any ideas ?
>
> Regards, ave.
>
>
>
>   
>

[Alexander Dalloz]

Am Mo, den 30.08.2004 schrieb A Ve um 17:02:

>  System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  postfix-2.1.4-4.fc2. 
>    spamassassin  unix  -       n       n       -       -       pipe 
>  user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
>  ${recipient} 
The user=test ... line is hopefully indented by a whitespace.

>  (taking care of linebreaks)
>  
>  I restarted spamassassin + postfix and sent some spam-style mail. The
>  output from /var/log/maillog:
>  
>  Aug 30 16:19:22 mail spamd[31884]: clean message (0.0/5.0) for user:200 in
>  0.1 seconds, 976 bytes.
>  Aug 30 16:19:22 mail spamc[31883]: exec failed: No such file or directory
>  Aug 30 16:19:22 mail postfix/pipe[31882]: EB152368423:
>  to=<user(a)example.com>, relay=spamassassin, delay=1, status=deferred
>  (system resource problem)
>  
>  And the mail is not delivered / "vanished away" ... ;-) Any ideas ?
>  
>  Regards, ave. 
You know that page?

http://wiki.apache.org/spamassassin/IntegratedSpamdInPostfix

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp 
Serendipity 18:25:01 up 15:41, 12 users, 0.77, 0.55, 0.38

[Cowles, Steve]

On Stardate 6609.08, A Ve said:

>  Hi !
>  
>  System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  postfix-2.1.4-4.fc2.
>  
>  Postfix 2.1.4 is finally working - after some help from postfix
>  mailinglist and postfix-guru Ralf H and some other helpfull postfix-guys.
>  
>  But ... spamassassin still not running. I configured it - as suggested in
>  the spamassassin doc:
>  
>  master.cf before:
>    smtp      inet  n       -       n       -       -       smtpd
>  
>  mater.cf after:
>  smtp      inet  n       -       n       -       -       smtpd -o
>  content_filter=spamassassin
>  
>    spamassassin  unix  -       n       n       -       -       pipe 
>  user=test argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender}
>  ${recipient}
>   
My requirements are a little different than yours, so I call SA a little 
differently than what you have configured above. The main reason is my 
MTA is also a backup MX for another domain, so I needed the flexibility 
to _NOT_ call SA on e-mails received in a backup MX mode. Anyway, maybe 
the following might get you started in the right direction. Then you can 
fine tune your configuration.

With the above in mind...

In /etc/master.cf

smtp    inet    n       -       y       -       -       smtpd

filter  unix    -       n       n       -       10       pipe
   flags=Fq
   user=spamassassin
   argv=/usr/bin/spamc -f -x -e /usr/sbin/sendmail -i -f $sender $recipient

Note: Don't set the chroot field to *y* until you get things working on 
the smtpd instance. Then, if necessary, enable the chroot'd environment.

In main.cf, I added a call to check_sender_access and 
check_recipient_access in smtpd_recipient_restrictions as follows:

smtpd_recipient_restrictions =
   permit_mynetworks
   permit_sasl_authenticated
   reject_unauth_destination
   ... more tests ...
   check_sender_access hash:/etc/postfix/whitelist_sender
   check_recipient_access hash:/etc/postfix/filtered_domains

Note: The order in which the tests are listed is critical. SA is called 
last. In other words, the first matching test wins. So whitelisted 
senders are not run through SA.

In /etc/postfix/whitelist_sender, I add the envelope sender address 
(mail from) of list servers that I subscribe to so that SA is *not* run 
on these e-mails. Virus checking is done on all inbound e-mails on 
another server. i.e.

# List all list server subscription "mail from" addresses here.
fedora-list-bounces(a)redhat.com     OK
etc...

Then in /etc/postfix/filtered_domains, I add the domain names that I 
want to have SA called. These are all my registered domains, not the 
backup MX domains.

# Add only the domain you want to have filtered (run spamassassin)
mydomain1.com  FILTER  filter:spamassassin
mydomain2.com  FILTER  filter:spamassassin

Note: The call to the FILTER action.
See: http://www.postfix.org/access.5.html for info on the FILTER action 
syntax.

If you want to run SA on *all* e-mails, then you don't need to add the 
call to check_sender_access, just add the check_recipient_access at the end.

Thats it! Good luck
Steve Cowles

[Kenneth Porter]

--On Monday, August 30, 2004 5:02 PM +0200 A Ve <av(a)cointronic.com&gt; wrote:

>  System: Fedora2, Following Apps installed: spamassassin-2.63-8,
>  postfix-2.1.4-4.fc2. 
FYI, SA 3.0 rc2 is available. I'm running it on my FC2 systems and it's 
quite stable and much more effective than 2.63. I'd say that while all the 
3.0 pre-releases had minor problems, all were also improvements over 2.63.

If you download the latest bz2, you can rebuild it into an RPM for FC2 with 
this script:

#!/bin/sh
REALNAME=Mail-SpamAssassin-3.0.0.tar.bz2
[ -h ${REALNAME} ] && ln -fs Mail-SpamAssassin-3.0.0-rc2.tar.bz2 ${REALNAME}
rpmbuild -ta --define 'srcext .bz2' --define 'release 0rc2' ${REALNAME}