Maybe another, more simple way to ask the question I asked yesterday:
When my MimeDefang/Spamassassin system tags a message as spam, it adds
the Spamassassin report as an attachment to the original message.
Can somebody confirm for me that it would be a BAD idea to feed these MD
modified message
Alex S Moore wrote:
On Sat, 01 Jan 2005 16:17:58 -0600
Keith Whyte <[EMAIL PROTECTED]> wrote:
Maybe another, more simple way to ask the question I asked yesterday:
When my MimeDefang/Spamassassin system tags a message as spam, it adds
the Spamassassin report as an attachment to the or
Loren Wilton wrote:
When my MimeDefang/Spamassassin system tags a message as spam, it adds
the Spamassassin report as an attachment to the original message.
Can somebody confirm for me that it would be a BAD idea to feed these MD
modified messages to sa-learn?
No, it wouldn't be a bad idea. S
Gustafson, Tim wrote:
Hello
I know that it's generally frowned upon to actually "block" SPAMs (as
opposed to marking them as SPAM and letting the user decide) but my
company has some instances where we get things that are blatantly,
absolutely, unequivocally SPAM (think scores in excess of 100 poin
Kelson wrote:
Keith Whyte wrote:
i send viruses to /dev/null but i bounce spam, partly in the vain
hope that some spammers might actually back off after multiple
failures, and mainly in case of false positives, so that the sender
knows the message wasn't delivered.
And just to stave of
I've seen a few requests for help on this, but no answers:
nothing comes up on google.
I'd had perl 5.6.0 on a system and yesterday I upgraded to 5.8.6 in
order to install SA 3.0.2
make test fails horribly
with:
Use of inherited AUTOLOAD for non-method Digest::SHA1::sha1_hex() is
deprecated at .
Louis LeBlanc wrote:
On 01/03/05 08:28 PM, Keith Whyte sat at the `puter and typed:
make test fails horribly
with:
Use of inherited AUTOLOAD for non-method Digest::SHA1::sha1_hex() is
deprecated at ../blib/lib/Mail/SpamAssassin/Bayes.pm line 987.
and
Can't locate auto/Digest/SHA1/sha1_h
Richard Ozer wrote:
I have sa 3.0.2 and perl 5.8.6 running happily on six different
servers right now.
That is good news.
After installing 5.8.6, you need to make sure that your cpan module
installations and Makefile commands are being done under 5.8.6.
Unless you explicitly removed the earlier
Justin Mason wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, I've seen this when one perl version tries to use another
perl's modules. Another possibility is that the version of Digest::SHA1
is too old, and needs to be updated to a newer version.
I have the latest Digest::SHA1 fr
Dallas L. Engelken wrote:
Easy fix.. I didn't have Digest::base so I installed
http://search.cpan.org/CPAN/authors/id/G/GA/GAAS/Digest-1.10.tar.gz
I re-installed Digest::base on my system, still no joy. not the same error
The full error in debug log was..
@400041da1dc32be8af3c razor2: r
Justin Mason wrote:
not off the top of my head, but for this module, this one-liner will
test if it's working or not:
perl -we 'use Digest::SHA1 qw(sha1_hex);print sha1_hex("1"),"\n";'
should output:
356a192b7913b04c54574d18c28d46e6395428ab
that works!
~$ perl -we 'use Digest::SHA1 qw(sha1_hex);
Justin Mason wrote:
same perl binary being used?
yes, but I have fixed the problem
i got super vicious and ran:
$ find -type f -mtime +30 -exec rm {} \;
in /usr/lib/perl5
then i ran make install again in the perl 5.8.6 source tree.
perl went about making a bunch of modules that it must have skip
Keith Whyte wrote:
i got super vicious and ran:
$ find -type f -mtime +30 -exec rm {} \;
in /usr/lib/perl5
Actually I lie here above.
I'm posting again in case anybody else might be a reckless as me and
DESTROY their perl instalation and then blame it on my mail.
I ran
find -type f -mtim
Marco Supino wrote:
Hi,
From time to time , i get empty emails, no body, no headers, no
subject , no to, only a from header,
Now, although this doesnt count as real spam, as it does not advertise
anything, its still bothering, in my SpamAssassin i get about 3-4
points, which is not enoghe to cl
Chris Santerre wrote:
Pardon my amavisd-new ignorance, but I *think* you need to restart
amavisd-new for the rules to take effect.
Also, check permissions. su to the user that amavisd runs as and try
spamassassin -D --lint as that user.
Keith.
2.3 DATE_IN_FUTURE_12_24 Date: is 12 to 24 hours after Received: date
Just got a FP on this, the 2.3 for DATE_IN_FUTURE_12_24 pushing the score over
the limit.
Does anybody know how common future dates are with spam? I don't seem to get that many.
A score of 2.3 seems a bit severe just for havi
bubba wrote:
Hi,
I've made some progress, but it's still not working :(
It would be more helpful in a case like this, if you were to post the
details of what you discovered.
What did you change to make the progress?
what are the permissions on / ?
on /usr ?
on /usr/bin ?
Any other suggestions?
Gary Funck wrote:
Attached, is a Perl script, mdf2sa.pl, which converts spam messages
that have been marked up by MIMEDefang, into a form that is similar
to the message format used by SA. Also attached is a simple
Hi Gary, just tried out that script, and sorry to say it didn't work at all.
a lo
Joe Zitnik wrote:
some of these e-mails are
getting caught by my rule and some aren't. When I run the ones that are
getting past through spamassassin manually, they hit my rule as well and
are above my spam threshold. So why do they make it past?
Joe, how can you possibly ask that question wit
Could somebody clarify:
When Spamassassin is called from mimedefang, is it possible to match the
Envelope Recipient, as in the one presented to THIS MTA, or is it only
possible to match on the Received: headers (which may contain other
recipients)?
Thanks,
I can't find an answer to this in any
Maybe somebody could explain this to me (if i'm not too off-topic k)
Below are headers from spam I received.
Why is the envelope recipient not in the received header???
i changed the To: user's email to xx for privacy, but this mail also
arrived into a mailbox which was not the mailbox in
Joe Zitnik wrote:
Keith,
Why would you need to be psychic?
Sorry, my way of saying that I didn't think you gave us enough
information with your request for help.
Did you post the mail that you passed through spam assassin manually, or
the one that made it through?
Did you try passing the mai
John Beck wrote:
* u: the SMTP envelope recipient(s), but (and this is the key to your
question) if there is more than one recipient, this macro is unset to
protect the privacy of all recipients (e.g., so if the sender blind
copied anyone, that the others would not be able to determine
Hi Giff, I recently had a lot of problems getting SA 3.0.2 to work, and
it was due to upgrading perl from 5.6.0 to 5.8.6
See thread: what the hell is sha1_hex.al ?? about 2 weeks ago on this list.
A lot of people suggested that I upgrade the offending perl module via
CPAN, which i did, including
Hi Matt, maybe you could try running some mail manually through
spamassassin, or spamc - to see what's causing delay.
I've never used spamc/spamd, so I'm not sure what to do there, but
save a message as /tmp/mailmsg and
cat /tmp/mailmsg | spamassassin -t -D should allow you to see the
spamassassi
It seems ok on my system
linux stock 2.2.17
perl 5.8.6
dunno what other libs might make a difference.
i ran it like this:
wget -O - http://mail.units.it/6474 |spamassassin -t -D
it scored thus:
X-Spam-Status: Yes, score=15.1 required=9.5 tests=BAYES_50,J_CHICKENPOX_26,
J_CHICKENPOX_31,J_CHIC
Is there a way, or a work around to disable bayes on the command line,
similar to using
spamassassin -t -L to disable Network tests?
i realise i could copy my config , disable bayes in the copied config
and then use -C, but maybe a command line option that allowed the
specification of a single
Hi I have a setup with MimeDefang and Spamassassin.
I reject mail scoring over 10 at SMTP level, then i tag the rest with
X-Spam-Level Headers and a
Subject header change - via md's action_change_header(), for spam
scoring over 4.
So now I have a huge junk mail box (procmail filtered) full of spam.
28 matches
Mail list logo
