[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spamassassin-users
Subject:    Re: The rewrite_header Subject [SPAM] directive has stopped working?!
From:       Richard Troy <rtroy () ScienceTools ! com>
Date:       2023-03-03 17:58:13
Message-ID: 7e030a75-2096-24a6-645f-54c23d97a96b () ScienceTools ! com
[Download RAW message or body]


Hmmm... I think I'm close here!

Thanks for the tip about procmail, and I was delighted to find that my 
system not only has procmail already installed but there was even an 
active  - APPARENTLY active! - ~/.procmailrc  ... that even already had 
Spam Assassin setup in it?! Nice!

Here's what ha(d/s):

##############################

#:0fw
#| /usr/bin/spamassassin
:0
* ^X-Spam-Status: *Yes
* ^X-DSPAM-Result: *!Innocent
$HOME/mail/spam/

##############################

Well... The only thing I want a tiny bit different there is to send it to 
Spam instead of spam, because I want to use one of them for confirmed 
spam, for possible future training, and the other for suspected spam.

However, it's not actually doing anything at present...

Can someone save me from reading a heck of a lot of the docs to find out 
how to configure this in WITHOUT creating a problem for using Dovecot, 
too? ...We DO need Dovecot, it's just not authenticating the imap 
connections properly and I just don't have time right now to focus on it.

Parking the damned spam somehow is a great help. And, this is perhaps 
BETTER than gettting the subject line rewrite working again because it'll 
be automagically moved for folks! Win!

Thanks much,
Richard
[prev in list] [next in list] [prev in thread] [next in thread]