scott ehrlich

Well, I mentioned my incoming email was not getting spam-tagged, and still
isn't.

Someone (sorry, lost the email :-( pointed me to:

http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/node11.html

which didn't seem to do much even after I added it.

I have been using SA successfully on a netbsd box run by an ISP, and at
work on a Linux box run by my sysadmin team but not running exim.

My .procmailrc on my home machine (which is not tagging) looks like:

VERBOSE=no
#SHELL=/bin/sh
LOGFILE=/home/scott/proc-debug.log
#DEFAULT=/var/mail/scott
SPAM=/home/scott/Spam

:0bcager1$LOCKEXT
* ^Received:.*wunderground.com
| /home/scott/wx/warndir/storm-date


I've tried adding /usr/bin/spamc and
:0:
....
| /usr/bin/spamc

but, thus far, nothing works for me :-(


My setup was apt-gotten via http for woody. I have no untested packages.

What/where else do/can I look to get proper spam tagging?


I found a site to make a modification to SA which prompted the spamc
daemon to run. Still no luck :-(

What next...???

Thanks.

Scott


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

scruloose

<SNIP>

This may be too elementary, but I just want to check...
Before calling spamc, you _do_ have the spamd daemon running, right?

If you call spamassassin by the name "spamassassin" it's self-contained,
but kinda hard on resources. If you call it by "spamc" you need to have
spamd _already_ running.
Cheers! -- ,-------------------------------------------------------------------------.

`-------------------------------------------------------------------------'

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/ys12GW5/T9+iw4kRAgEUAKC12g7646/WGAQO6CH+uE15Wv5RKwCggYrk
vzWV/PqH9ajHacn26VHSDx4=
=KSxG
-----END PGP SIGNATURE-----

scott ehrlich

Yes:

more /etc/default/spamassassin
# /etc/default/spamd.conf
# Duncan Findlay
# November 2001

# WARNING read README.spamd before using. THERE ARE SECURITY RISKS!

# Change to one to enable spamd
ENABLED=1

# Options
# See man spamd for possible options. The -d option is automatically
added.
OPTIONS="-c"
#OPTIONS="-F 0"


I've reviewed my procmail log file many times and there are _no_ hints as
to what is going on. At one point, verbose=yes had exim returning a
message to the sending host, as a mailer-daemon notification, simply
saying procmail was running, but no error. I turned verbose=off and that
stopped happening.

Scott


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

monique y. herman

On Mon, 01 Dec 2003 at 10:22 GMT, Scott Ehrlich penned:

(Please don't top post.)

Maybe I'm being pedantic, but do you see it in ps? Here's what I see:

# ps -eaf | grep spamd
root 27187 1 0 Oct24 ? 00:00:17 /usr/sbin/spamd -m 10 -d --pidfile=/var/run/spamd.pid

Also, I'm not sure which "verbose" you're referencing, but when I set
VERBOSE=yes in my .procmailrc, I see the following in my procmail log:

procmail: Executing "/usr/bin/spamc"

--
monique


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

monique y. herman

On Mon, 01 Dec 2003 at 10:22 GMT, Scott Ehrlich penned:

(Please don't top post.)

Maybe I'm being pedantic, but do you see it in ps? Here's what I see:

# ps -eaf | grep spamd
root 27187 1 0 Oct24 ? 00:00:17 /usr/sbin/spamd -m 10 -d --pidfile=/var/run/spamd.pid

Also, I'm not sure which "verbose" you're referencing, but when I set
VERBOSE=yes in my .procmailrc, I see the following in my procmail log:

procmail: Executing "/usr/bin/spamc"

--
monique


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

scott ehrlich

I'll try my best ;-)


root 169 0.0 11.1 8056 6980 ? S 22:36 0:00 /usr/bin/perl /usr/sbin/spamd -d -c
scott 941 0.0 0.6 1332 428 pts/1 S 23:45 0:00 grep -i spam

With /usr/bin/spamc towards the top of my .procmailrc:

procmail: Assigning "SPAM=/home/scott/Spam"
procmail: Skipped "/usr/bin/spamc"
procmail: No match on "^Received:.*wunderground.com"
procmail: No match on "^X-Spam-Flag: YES"
procmail: Locking "/var/mail/scott.lock"
procmail: Assigning "LASTFOLDER=/var/mail/scott"
procmail: Opening "/var/mail/scott"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/mail/scott.lock"

then, with a recipe of
:0:
....
| /usr/bin/spamc
....

procmail: Assigning "SPAM=/home/scott/Spam"
procmail: No match on "^Received:.*wunderground.com"
procmail: Couldn't determine implicit lockfile from "/usr/bin/spamc"
procmail: Locking ".lock"
procmail: Executing "/usr/bin/spamc"
procmail: [28834] Mon Dec 1 16:38:15 2003
procmail: Assigning "LASTFOLDER=/usr/bin/spamc"
procmail: Unlocking ".lock"


Further suggestions welcome.

Thanks.

Scott


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

scott ehrlich

I'll try my best ;-)


root 169 0.0 11.1 8056 6980 ? S 22:36 0:00 /usr/bin/perl /usr/sbin/spamd -d -c
scott 941 0.0 0.6 1332 428 pts/1 S 23:45 0:00 grep -i spam

With /usr/bin/spamc towards the top of my .procmailrc:

procmail: Assigning "SPAM=/home/scott/Spam"
procmail: Skipped "/usr/bin/spamc"
procmail: No match on "^Received:.*wunderground.com"
procmail: No match on "^X-Spam-Flag: YES"
procmail: Locking "/var/mail/scott.lock"
procmail: Assigning "LASTFOLDER=/var/mail/scott"
procmail: Opening "/var/mail/scott"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/mail/scott.lock"

then, with a recipe of
:0:
....
| /usr/bin/spamc
....

procmail: Assigning "SPAM=/home/scott/Spam"
procmail: No match on "^Received:.*wunderground.com"
procmail: Couldn't determine implicit lockfile from "/usr/bin/spamc"
procmail: Locking ".lock"
procmail: Executing "/usr/bin/spamc"
procmail: [28834] Mon Dec 1 16:38:15 2003
procmail: Assigning "LASTFOLDER=/usr/bin/spamc"
procmail: Unlocking ".lock"


Further suggestions welcome.

Thanks.

Scott


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

jiele

I would be wrong, but a recipe like

:0:
....
| /usr/bin/spamc

would eat the message, and nothing would be delivered

You may try this instead:

:0fw:
....
| /usr/bin/spamc

This recipe treat spamc as a filter (indicated by flag 'f'), and the
processed message will be passed to the rest recipes. Anyway, it works
for me.


--
Yours sincerely, \|||/
(o o)
+-----------------------------------ooO--(_)--Ooo--------+
| ZHANG Jiele |
| zhangjl@jiele.net .oooO |
| http://www.jiele.net ( ) Oooo. |
+------------------------------------\ (----( )--------+
\_) ) /
-- (_/


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

jiele

I would be wrong, but a recipe like

:0:
....
| /usr/bin/spamc

would eat the message, and nothing would be delivered

You may try this instead:

:0fw:
....
| /usr/bin/spamc

This recipe treat spamc as a filter (indicated by flag 'f'), and the
processed message will be passed to the rest recipes. Anyway, it works
for me.


--
Yours sincerely, \|||/
(o o)
+-----------------------------------ooO--(_)--Ooo--------+
| ZHANG Jiele |
| zhangjl@jiele.net .oooO |
| http://www.jiele.net ( ) Oooo. |
+------------------------------------\ (----( )--------+
\_) ) /
-- (_/


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org