From owner-freebsd-questions@FreeBSD.ORG Mon Jan 26 06:42:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D892016A4CE for ; Mon, 26 Jan 2004 06:42:19 -0800 (PST) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38AD143D31 for ; Mon, 26 Jan 2004 06:42:18 -0800 (PST) (envelope-from freebsd-questions-lists@morbius.sent.com) Received: from server2.messagingengine.com (server2.internal [10.202.2.133]) by mail.messagingengine.com (Postfix) with ESMTP id 1E1894B9BC4 for ; Mon, 26 Jan 2004 09:42:16 -0500 (EST) Received: by server2.messagingengine.com (Postfix, from userid 99) id 529BF7EF4E; Mon, 26 Jan 2004 09:42:15 -0500 (EST) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.2 (F2.71; T1.001; A1.51; B2.12; Q2.03) From: "Robert Woolley" To: freebsd-questions@freebsd.org Date: Mon, 26 Jan 2004 14:42:14 +0000 X-Sasl-Enc: BeKfgdTvv5wG60amkUq/Zw 1075128134 References: <200401242251.14708.ecrist@adtechintegrated.com> <3.0.5.32.20040125170203.01e45de0@10.0.0.15> <401514E7.2060608@onlinehobbyist.com> In-Reply-To: <401514E7.2060608@onlinehobbyist.com> Message-Id: <20040126144215.529BF7EF4E@server2.messagingengine.com> Subject: Re: Spam Assassin? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 14:42:20 -0000 Though I've not actually used it myself, I did once look at the documentation. I don't think you do actually need spamd, the normal way is to have procmail run spamassassin directly as a perl script. Spamc is a lightweight c-coded frontend that connects to spamd over a socket; it eliminates the overhead of restarting perl for every mail, and it also allow SA to run on a dedicated machine. The spamc/spamd combination is really intended for high traffic mail systems. I can't recall how you pass an email to the SA perl script, but google should turn it up. Robert Woolley On Mon, 26 Jan 2004 08:23:51 -0500, "Clint Gilders" said: > Here's how I have spam assassin setup on my mail server. I installed > spam assassin using perl's CPAN module, so I'm not sure how different > it is from the ports install. > > You need to have the spam assassin daemon (spamd) running. I imagine > the port installs a startup script in /usr/local/etc/rc.d . > > Eric F Crist wrote: > > Ok folks, > > > > I'm very, very overwhelmed here. I think it comes from trying to > > setup too many things at once. I have sendmail running (from base > > install). I need to get SpamAssassin and Procmail working, with > > users having the ability to opt-out of the spam filtering. I mainly > > offer POP3 mail access (via qpopper) and I'm thinking of adding in > > Squirrelmail support with IMAP. I have a working mail/pop server and > > everything is fine there. The spam assassin port and procmail ports > > have been through a make install clean and I haven't the foggiest > > idea on how to get the two of them working together with sendmail. > > Please help. > > > > TIA > > > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd- > questions To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org"