against the same libs perl was linked
> against. It's overkill, but it's an easier way of making sure that we
> get the right libs for the particular platform you're on.
>
> C
>
> On Mon, 2002-02-18 at 23:05, Uwe Willenbacher wrote:
>> On Mon, 18 Feb 2002 23:25:
On Mon, 18 Feb 2002 23:25:11 -0700 (Mountain Standard Time)
Charlie Watts <[EMAIL PROTECTED]> wrote:
>On Mon, 18 Feb 2002, Uwe Willenbacher wrote:
>
>> Sorry to bug you, but I decided today to install the latest greatest
>>dev
>> version of SpamAssassin 2.1, ho
Hi all,
Sorry to bug you, but I decided today to install the latest greatest dev
version of SpamAssassin 2.1, however, I got following compile error:
gcc -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O Hi all,
spamd/spamc.c \
-o spamd/sp
--On Wednesday, February 06, 2002 4:22 PM -0600 Dallas Engelken
<[EMAIL PROTECTED]> wrote:
> First of all, I run SA2.1.. here is my log output.
Is 2.1 ready for production environments?
>
> Feb 3 04:51:38 whitehat spamd[28483]: connection from
> localhost.localdomain [ 127.0.0.1 ] at p
Hi all,
I am using spamd and spamc in my set up and I find following somewhat
strange: I get lots of syslog messages with following content:
Feb 6 13:53:58 server spamd[16597]: connection from localhost [ 127.0.0.1
] at port 20506
Feb 6 13:54:00 server spamd[17335]: clean message for (unknow
Sorry for this long post, but I am in need for some advice/help (pretty
please:)
I just updated to SpamAssassin 2.0 (the release version) after doing a full
deinstall. However, SA still seems to have a problem with CommuniGate Pro:
I defind every command option to launch spamd (see below) and
