Spamassassin the "SuSE" way?
I've been using a self-compiled version of spamassassin on Other Distro for a long time now. Having just upgraded to SuSE 8.2, I'm wondering: What's the proper "SuSE" way of using spamassassin with postfix? I'm used to using a system-wide /etc/procmailrc that feeds all mail through spamassassin, but I wonder if the SuSE folks have set it up to uncomment a line somewhere that will automatically send all mail though `spamd'. I just don't even know where to start looking. Can anyone help me out? TIA, dk
On 05/02/2003 07:40 PM, David Krider wrote:
I'm used to using a system-wide /etc/procmailrc that feeds all mail through spamassassin, but I wonder if the SuSE folks have set it up to uncomment a line somewhere that will automatically send all mail though `spamd'. I just don't even know where to start looking. Can anyone help me out?
AFAIK, that is the SuSE way as well, at least that is the way I am doing it on 8.0. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
* Joe Morris (NTM);
On 05/02/2003 07:40 PM, David Krider wrote:
I'm used to using a system-wide /etc/procmailrc that feeds all mail through spamassassin, but I wonder if the SuSE folks have set it up to uncomment a line somewhere that will automatically send all mail though `spamd'. I just don't even know where to start looking. Can anyone help me out?
AFAIK, that is the SuSE way as well, at least that is the way I am doing it on 8.0.
IIRC the SuSE way is setting up the /etc/sysconfig/spamd and letting the users adjust their own procmairc or KMAIL whatever # The arguments passed to spamd. # See spamd(1) man page and README.spamd # Please take care of security considerations! # Default is "-d -c -a" SPAMD_ARGS="-d -c -a" -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
On Fri, 2003-05-02 at 10:12, Togan Muftuoglu wrote:
IIRC the SuSE way is setting up the /etc/sysconfig/spamd and letting the users adjust their own procmairc or KMAIL whatever
# The arguments passed to spamd. # See spamd(1) man page and README.spamd # Please take care of security considerations! # Default is "-d -c -a" SPAMD_ARGS="-d -c -a"
I don't know if I understand what this is used for. Following /usr/share/doc/packages/spamassassin/README.SuSE, I setup a change in postfix's master.cf file that invokes procmail to munge the mail. Then I created the /etc/procmail file by example, which invokes spamassassin directly. Reading the README.spamd file, it says to simply use `spamc' in place of `spamassassin'. To start using the daemon (the one started with /etc/init.d/spamd), is this all I do, i.e. change the command? And if I do so, this would give me the dual benefits of 1) being "faster" and 2) reading ~/.spamassassin per-user rules. Have I got it? Thanks, dk -- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
On Fri, 2003-05-02 at 10:30, David Krider wrote:
On Fri, 2003-05-02 at 10:12, Togan Muftuoglu wrote:
IIRC the SuSE way is setting up the /etc/sysconfig/spamd and letting the users adjust their own procmairc or KMAIL whatever
# The arguments passed to spamd. # See spamd(1) man page and README.spamd # Please take care of security considerations! # Default is "-d -c -a" SPAMD_ARGS="-d -c -a"
I don't know if I understand what this is used for. Following /usr/share/doc/packages/spamassassin/README.SuSE, I setup a change in postfix's master.cf file that invokes procmail to munge the mail. Then I created the /etc/procmail file by example, which invokes spamassassin directly. Reading the README.spamd file, it says to simply use `spamc' in place of `spamassassin'. To start using the daemon (the one started with /etc/init.d/spamd), is this all I do, i.e. change the command? And if I do so, this would give me the dual benefits of 1) being "faster" and 2) reading ~/.spamassassin per-user rules. Have I got it?
I still think this is true, but my problem now is that after /etc/procmail gets done with it, it's delivered to the user's mailbox, and it's done. The mail delivery process isn't paying attention to the user's .procmailrc file (where mail should be getting sorted). Anyone know why this might be? Thanks, dk
On Friday 02 May 2003 15:18 pm, David Krider wrote:
On Fri, 2003-05-02 at 10:30, David Krider wrote:
On Fri, 2003-05-02 at 10:12, Togan Muftuoglu wrote:
IIRC the SuSE way is setting up the /etc/sysconfig/spamd and letting the users adjust their own procmairc or KMAIL whatever
# The arguments passed to spamd. # See spamd(1) man page and README.spamd # Please take care of security considerations! # Default is "-d -c -a" SPAMD_ARGS="-d -c -a"
I don't know if I understand what this is used for. Following /usr/share/doc/packages/spamassassin/README.SuSE, I setup a change in postfix's master.cf file that invokes procmail to munge the mail. Then I created the /etc/procmail file by example, which invokes spamassassin directly. Reading the README.spamd file, it says to simply use `spamc' in place of `spamassassin'. To start using the daemon (the one started with /etc/init.d/spamd), is this all I do, i.e. change the command? And if I do so, this would give me the dual benefits of 1) being "faster" and 2) reading ~/.spamassassin per-user rules. Have I got it?
I still think this is true, but my problem now is that after /etc/procmail gets done with it, it's delivered to the user's mailbox, and it's done. The mail delivery process isn't paying attention to the user's .procmailrc file (where mail should be getting sorted). Anyone know why this might be?
I've always assumed you could either have a global /etc/procmailrc or use local ~/.procmailrc's but you couldn't really use both. But then, it's been a long time since I first set up procmail and the details get fuzzy.
Thanks, dk
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/02/03 15:56 + +----------------------------------------------------------------------------+ "Auntie Em. Hate you, hate Kansas, taking the dog." Dorothy
The 03.05.02 at 14:18, David Krider wrote:
I still think this is true, but my problem now is that after /etc/procmail gets done with it, it's delivered to the user's mailbox, and it's done. The mail delivery process isn't paying attention to the user's .procmailrc file (where mail should be getting sorted). Anyone know why this might be?
First, you have got to tell postfix to use procmail for local delivery, either with Yast, or manually. You must also define a user to get root's mail, it's explained on the postfix faq: Root's mail is delivered to nobody If you use procmail (or some other command) for local mail delivery, Postfix will not deliver mail as root. Instead, Postfix runs procmail (or whatever) as nobody. Perhaps some day Wietse will trust Postfix enough to run external commands as root. As a side effect, /etc/procmailrc is not even read - at least, mine wasn't: it is owned by root, so procmail can not even read it, being run as "nobody". -- Cheers, Carlos Robinson
On Sat, 2003-05-03 at 13:35, Carlos E. R. wrote:
First, you have got to tell postfix to use procmail for local delivery, either with Yast, or manually.
Ah... Yast. What a time I've had with Yast. At least I understand what it's doing to me... I mean, what it's doing. The problem is that I couldn't find any documentation that told me that setting up postfix the way the README.SuSE file said I should (to work with Spamassassin) would prevent me from using user-defined .procmailrc files.
You must also define a user to get root's mail, it's explained on the postfix faq:
I'm clear there. I just create an alias for root, like I've done for years on EVERY open system I've admin'ed. I finally got postfix, spamassassin, procmail, and even apache and squirrelmail (with stunnel, since uw-imap doesn't do plaintext auth and squirrelmail doesn't do SSL) all working like I like... AND how SuSE expects me to configure it. I guess I've been initiated... Thanks, dk
The 03.05.03 at 18:37, David Krider wrote:
First, you have got to tell postfix to use procmail for local delivery, either with Yast, or manually.
Ah... Yast. What a time I've had with Yast. At least I understand what it's doing to me... I mean, what it's doing. The problem is that I couldn't find any documentation that told me that setting up postfix the way the README.SuSE file said I should (to work with Spamassassin) would prevent me from using user-defined .procmailrc files.
The postfix/README.SuSE doesn't mention SpamAssassin. :-? Ah, You must be refering to postfix/SPAMASSASSIN+POSTFIX.SuSE. Let me see... [...] Ugh. I don't like it at all... It doesn't surprise me you had problems - I'm assuming 8.2 has the same docs as my 8.1 Read instead spamassassin/README.spamd - although it requires action by all users, on their .procmailrc files. The problem I had with postfix in 8.1 was that I was used to sendmail, and didn't know that root had to be aliased, so that my procmailrc files did not work as expected. Then virus checking broke somehow. But SpamAssassin worked first time - but I guess I'm used to SuSE ways ;-)
I finally got postfix, spamassassin, procmail, and even apache and squirrelmail (with stunnel, since uw-imap doesn't do plaintext auth and squirrelmail doesn't do SSL) all working like I like... AND how SuSE expects me to configure it. I guess I've been initiated...
X-) The trick, normally, is to let Yast configure it, at least once. When it works, then you go in manually. -- Cheers, Carlos Robinson
participants (5)
-
Bruce Marshall -
Carlos E. R. -
David Krider -
Joe Morris (NTM) -
Togan Muftuoglu