Hi -
Since the rule for FORGED_MUA_OUTLOOK is 3.5 points, and our threshold
is set at 4.0 (we get an ungodly amount of spam) then we're having a lot
of trouble with mail wrongly being marked as spam, when the mail is
coming from Outlook 2003. (We have the 2003 Beta 2 software from M$.)
How do
Theo Van Dinter wrote:
On Tue, May 27, 2003 at 04:17:11PM -0700, Catherine Pinatiello wrote:
I'm trying to install Razor. Razor requires Net::DNS and whenever I try
to install from CPAN I get a rash of errors in the make test, like the
ones below:
Net::DNS probably has other requirements
Hi -
I'm trying to install Razor. Razor requires Net::DNS and whenever I try
to install from CPAN I get a rash of errors in the make test, like the
ones below:
Can't locate Test/More.pm in @INC (@INC contains: blib/arch blib/lib
/usr/lib/pe
rl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0/i386-linux
Catherine Pinatiello wrote:
Theo Van Dinter wrote:
On Tue, May 27, 2003 at 11:36:15AM -0700, Catherine Pinatiello wrote:
I have another server setup to use Spamassassin with the same
/etc/mail/spamassassin/local.cf and it works just fine. What things
should I check besides local.cf in this
Theo Van Dinter wrote:
On Tue, May 27, 2003 at 11:36:15AM -0700, Catherine Pinatiello wrote:
I have another server setup to use Spamassassin with the same
/etc/mail/spamassassin/local.cf and it works just fine. What things
should I check besides local.cf in this instance?
Did you restart
Theo Van Dinter wrote:
>
> There's an issue with one of the rpc progs (not related to NFS as I
> remember) grabbing 783 sometimes, but that's why an 'lsof -i :783'
> will answer what process is using the port.
Ok I found and installed LSOF. I ran it and it says spamd. I think that
perhaps the shut
sh: lsof: command not found
Theo Van Dinter wrote:
On Tue, May 27, 2003 at 10:57:42AM -0700, Catherine Pinatiello wrote:
Ok I started it with -p 784 switch ... so is 784 a good port to use? I
don't know which port to use that would avoid a conflict like this in
the future ... appar
Mike Anderson wrote:
Because of you I am changing ISP's. There is no such thing as a
whitelist that works. Even if I receive valid mail and you have
targeted it as spam I cannot read it because you control freaks have
altered the e-mail. Anyone else having similar problems? Why not let
us have
Ok I modified my local.cf to include:
rewrite_subject 1
subject_tag *SPAM*
So it will change the subject of all incoming spam...
It is not doing so. They are still being encapsulated as attachments to
the report, and everything else seems to be smooth, but the subject
To further complicate things, I restarted it after it had been on port
784, and on restart it gave me the same error message. Is it not
shutting down appropriately do you think...? Could that be the issue?
Catherine Pinatiello wrote:
> Ok I started it with -p 784 switch ... so is 784 a good p
Ok I started it with -p 784 switch ... so is 784 a good port to use? I
don't know which port to use that would avoid a conflict like this in
the future ... apparently something on my system was already using 783!
Catherine Pinatiello wrote:
> I installed spamassassin on a cobalt Raq3. (Ye
I installed spamassassin on a cobalt Raq3. (Yeah I can hear the groans
already.) So on starting spamd using the script in rc.d it gives this
message:
Starting spamd: spamdCould not create INET socket: Address already in
use IO::Socket::INET: Address already in use
does this mean I need to set
12 matches
Mail list logo