On Mon, 6 Jan 2003, Tobias von Koch wrote:
> Hi,
>
> just found this on REUTERS:
>
> http://www.reuters.com/newsArticle.jhtml?type=technologyNews&storyID=1997874
>
> and in German
>
> http://www.heise.de/newsticker/data/anw-06.01.03-003/
>
> Wow, this one killed me.
I don't know about you guys,
On Fri, 27 Sep 2002, Max Clark wrote:
> Has anyone ever used smtpprox? To integrate with Spamassassin and
> Postfix?
>
> http://bent.latency.net/smtpprox/
I looked at that code. In fact, that was one of the original code bases I
was using when I was originally designing the SMTP "guts" for wh
Hi, all.
Just thought I would interject something about my work as published as
part of the SA sources, being a fellow Postfix user (or should that be
"junkie"? *pats a vein in his forearm* :) ).
I would imagine that a lot of the "pipe" methods that are used with
various other MTAs, such as Exi
On Tue, 26 Mar 2002, Morrison, Trevor (Trevor) wrote:
> HI,
>
> I have successfully setup spamassassin to work on my PC running RH 7.1
> with a 2.4.17 modular kernel running Sendmail-8.11. The program is run
> out of my home directory where I installed it. My question is I have a
> .forward f
Hi, all.
I was going over in my mind how best I could improve the proxy. Then it
hit me: Why not do things the same way that spamc/spamd do? That way,
only one process really chews up memory, and all the proxy does is field
the message, then send it through spamd rather than doing all the che
On Sat, 2002-03-09 at 10:38, Donald Greer wrote:
>Keith,
>Look through the archives. Somebody posted an answer to this before.
> Basically, what they did, was follow the "simple" configuration
> described in the README.filter and in the shell script they used
> "spamc". I don't know
On Wed, 27 Feb 2002, Marc G. Fournier wrote:
>
> earth# /usr/bin/spamproxyd localhost:10025 localhost:10026
> Failed to run A_FROM_IN_AUTO_WLIST SpamAssassin test, skipping:
> (Can't locate object method "check_for_auto_whitelist" via package
>"Mail::SpamAssassin::PerMsgStatus" at
>/u
On Tue, 2002-02-26 at 20:51, Mike Loiterman wrote:
> But the problem I'm encountering is that the process is called
> /usr/bin/perl /usr/local/sbin/spamd. The killall command is not
> accepting any of the derivatives of that line I give it. For example,
> killall spamd, killall /usr/local/sbin/
Hi, all.
I have upgraded spamproxyd for use with newer versions of the
SpamAssassin modules and its accompanying modules which will be released
with SpamAssassin 2.1.
However, if you don't want to wait until 2.1 and/or would like to
preview it, I have released it as a stand-alone package. It st
