Mail::SpamAssassin::Conf:
body SYMBOLIC_TEST_NAME /pattern/modifiers ...
The 'body' in this case is the textual parts of the message body;
any non-text MIME parts are stripped, and the message decoded from
Quoted-Printable or Base-64-encoded format if necessary. The
Why is the STOX stuff all repeated twice?
X-Spam-Report:
* 0.2 STOX_REPLY_TYPE STOX_REPLY_TYPE <--- see, twice on the same line!
* 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider
* (m2243.m8715[at]msa.hinet.net)
* -0.0 RP_MATCHES_RCVD
Help. sa-update is jammed.
What should I do?
rules: failed to run __KAM_BODY_LENGTH_LT_256 test, skipping:
(Can't locate object method "check_body_length" via package
"Mail::SpamAssassin::PerMsgStatus" at (eval 1114) line 419.
etc. etc.
Isn't it bad that X-Spam-Checker-Version doesn't report what sa-update
we are up to so far, and that there is no additional other variable that
we can toggle on in reports to do that.
body J_MAILBOX_FULL /^Your? ((web|E-?) ?mail|mailbox) .*(is|has)
.*(exceed|over)/i
Got to update it every day to stop those bast*rds.
Seen upon SVN update:
lint: config: failed to parse line, skipping, in "rules/70_sandbox.cf":
mimeheader __KAM_BLOCK_UTF7_2 Content-Type =~
/charset=(?:unicode-\d+-\d+-)?utf-7/i at build/mkrules line 255.
ERROR: LINT FAILED, suppressing output: rules/70_sandbox.cf
No wonder, the version I had
Jan 15 09:39:29.620 [6248] dbg: dns: 0.4.3.updates.spamassassin.org => 3.4
1230922, parsed as 3
Jan 15 09:39:29.620 [6248] dbg: channel: current version is 1195375, new
version is 3, skipping channel
Now after updating from SVN it gives
Jan 15 09:45:34.588 [15283] dbg
> "MS" == Michael Scheidell writes:
MS> On 1/11/12 9:35 PM, jida...@jidanni.org wrote:
MS> #1 priority: keep your version of sa updated
MS> Hmmm, taking a look at it, I find the last update was about 2011/10/24.
MS> Too bad sa-update -D doesn't spit out the date.
MS> I meant your ve
> "MS" == Michael Scheidell writes:
MS> #1 priority: keep your version of sa updated
Hmmm, taking a look at it, I find the last update was about 2011/10/24.
Too bad sa-update -D doesn't spit out the date.
> From:... <...@1004.con>
".con"? sounds like a con-job.
Ha, I'm not falling for that again!
Sure a lot of "Your mailbox has exceeded" spam these days. I'll use
body J_MAILBOX_FULL /^Your mailbox has exceeded/
score J_MAILBOX_FULL ...
myself for now.
See also https://bugzilla.wikimedia.org/show_bug.cgi?id=29855
And even if you are a card carrying member of LinkedIn,
header J_CANT_STOP Subject =~ /^LinkedIn Network Updates/
score J_CANT_STOP 222
is needed, as even LinkedIn staff are unable to stop sending them.
> "j" == jdow writes:
j> I seldom if ever opt out if existing spam. That's what my spam filter
j> is for. It simply leads to nicely segregated spam I can deal with in a
j> trice. If I opt out my spam filter feels lonely. It LIKES its food. It
j> gets better with feeding.
Me too. I OPT-IN to
Gentlemen, it turns out it is very hard to debug UNWANTED_LANGUAGE_BODY.
They forgot to put debugging features in the code, apparently TextCat.pm.
Lately spamassassin has decided that several of my mails contain
UNWANTED_LANGUAGE_BODY
X-Spam-Languages: ja.shift-jis
despite that being hogwash.
We
All I know is I first run mail through procmail to filter out the big
items before they get to spamassassin.
Never enabled Bayes and don't intend to.
Hmm, I seem to have described it in http://jidanni.org/comp/spam/spamdealer.html
>>>>> "j" == jidanni writes:
j> Well let's see if at least this reply gets through without needing to
j> resort to Nabble.
OK, it got through. ANOTHER_JIDANNI_STUPID_POST did not fire ☺
Well let's see if at least this reply gets through without needing to
resort to Nabble.
My recent messages never got to this list, even though I'm subscribed etc.
Could it be it thinks they are ... spam?
--
View this message in context:
http://old.nabble.com/My-messages-never-got-to-this-list%2C-even-though-I%27m-subscribed-etc.-tp30962942p30962942.html
Sent from the SpamAssassin -
Gentlemen, I wish there was a
whitelist_from *...@facebookmail.com
rule that would use the Return-Path field,
$ egrep '^(From|Return-Path):' a b
a:Return-Path:
a:From: Facebook
b:Return-Path:
b:From: Facebook
as that is much more reliable.
I see there are other whitelist_ rules, but none tha
SUBJ_ALL_CAPS to you, but not to me:
Subject: RE: 柯小柯
Can't you give the RE: etc. a break?
And also why is the Chinese considered CAPS?
$ unicode P p 柯|grep Category
Category: Lu (Letter, Uppercase)
Category: Ll (Letter, Lowercase)
Category: Lo (Letter, Other)
Sure I can customize this rule for jus
https://issues.apache.org/SpamAssassin/ says "As a result of a security
breach on 4th April 2010, the Apache Infrastructure Team recommends that
all SpamAssassin Bugzilla users change their passwords as a
precautionary measure. Please see the Infrastructure Blog for further
information."
All I know is my friend send me a mail from her FROM_END_DIGIT account
there at Gmail, and there was
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;...
DomainKey-Signature: a=rsa-sha1; c=nofws;...
in the headers too even. And still it got slapped with
FREEM
Well Gosh,
* 2.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends
in
* digit (mb2365[at]gmail.com)
I swear when I recently helped a loved one apply for a Gmail account,
Gmail offered names like "vippenheimer321", "snordsberd123",
nipplovitz246", as the non su
Man you guys blew it.
* 2.5 FREEMAIL_REPLY From and body contain different freemails
All he did was quote my CC.
It is not like he forged anything.
P.S., https://issues.apache.org/SpamAssassin/ doesn't mention when it
itself will someday come back online after maintenance.
FreeMail: RULE (FREEMA
http://catless.ncl.ac.uk/Risks/25.94.html#subj11
I suggest someone send RISKS a clarification if indeed the issue is resolved.
Maybe I accidentally did 'make dist'. OK, never mind.
MM> The usual procedure is:
MM> perl Makefile.PL; make; make test; make install
Ah, that now works only once! Now only
set -e; perl Makefile.PL; make clean; perl Makefile.PL; make; make install
will work each time, even if a few months pass between one's upgrades.
Hmmm, they might want to docum
Maybe they changed something. In the past
perl Makefile.PL PREFIX=$HOME/.spamassassin-tree
also took care of where bin/spamassassin went. Now it seems left behind,
due to this suspicious commented out code?
# needs to be added to MY::install if used
#bin__install: $(INST_SCRIPT)/sa-filter
#
Why does svn update pull in Mail-SpamAssassin-3.4.0.tar.gz?
That's not how things work with Mediawiki.
Help, I dared to update from SVN, and now spamassassin refuses to run:
$ svn update
$ make install
$ sa-update --install http://daryl.dostech.ca/sa-update/asf/>
$ spamassassin
spamassassin: spamassassin script is v3.003000, but using modules v3.004000
$ sa-update
http: GET http://daryl.dostech.ca/sa-update/asf/909775.tar.gz request failed:
404 Not Found
Dear sare-users Adam Katz tried to post these to your list. Please read
http://article.gmane.org/gmane.mail.spam.spamassassin.general/126545
http://article.gmane.org/gmane.mail.spam.spamassassin.general/126547
However, as in
http://article.gmane.org/gmane.mail.spam.spamassassin.general/126330
Anyway, what you are doing here is penalizing all users of that
company's copper wires. No amount of monopoly breakup legislation will
do any good if you penalize based on the wrong part of the physical
infrastructure.
http://en.wikipedia.org/wiki/Common_carrier
http://en.wikipedia.org/wiki/Network
Long ago, I tried mailing directly direct-to-mx style, but that of
course didn't work, e.g., http://www.spamhaus.org/pbl/query/PBL109625
So only 5% of my mail got through.
So then I tried mailing through The ISP Here, Hinet.Net's SMTP server,
but of course Hinet.Net has a bad name. So only 50% of
So what should a Taiwan user (Taiwan~=Hinet)
HINET: Control of approx 8,476,149 IP addresses
http://www.fixedorbit.com/AS/3/AS3462.htm
user do. Buy a SMTP account with a US Company?
But that's what I did, as you see from
http://article.gmane.org/gmane.linux.debian.devel.eeepc/2850/raw
headers.
Fellows, I have the highest spam score vs. all my buddies:
http://article.gmane.org/gmane.linux.debian.devel.eeepc/2850/raw
It's all because
http://www.rulesemporium.com/rules/70_sare_header1.cf
headerSARE_RECV_SPAM_DOMN0bReceived =~
/\bdynamic.hinet\.(?:com|net|org|info)/
describe SARE_
> "MG" == Martin Gregorie writes:
MG> I run this script as a weekly cron job:
I just use one line in my crontab:
33 2 * * * sa-update
If something goes wrong I'll get a mail with the errors. Else nothing
will interrupt my leisure yacht cruise.
$ sa-update
config: failed to parse line, skipping, in
"/tmp/.spamassassin5560GP7SGbtmp/10_default_prefs.cf":
clear_originating_ip_headers
config: failed to parse line, skipping, in
"/tmp/.spamassassin5560GP7SGbtmp/10_default_prefs.cf": originating_ip_headers
X-Yahoo-Post-IP X-Originating-IP X-
Regarding sa-update,
EXIT CODES
An exit code of 0 means an update was available, and was
downloaded and installed successfully if --checkonly was
not specified.
An exit code of 1 means no fresh updates were available.
I would make this:
0 means you are all up to date
OK, thanks. I'd put some contact info on top of http://daryl.dostech.ca/,
above "This blog is currently in a static state pending an upgrade
of WordPress", in case something breaks next time.
Sometimes sa-update works, sometimes one gets
http: GET http://daryl.dostech.ca/sa-update/asf/891585.tar.gz request failed:
403 Forbidden:
You don't have permission to access /sa-update/asf/891585.tar.gz on this server.
Apache/2.2.3 (Fedora) Server at daryl.dostech.ca Port 80
I recommend that htt
http://www.streamsend.com/returnpath_safelist.htm :
"SpamAssassin - Safe List rules help give green light to email"
Not my email though.
header J_STREAMSEND X-Mailer=~/StreamSend/i
score J_STREAMSEND 10
So I thought I would follow
http://wiki.apache.org/spamassassin/DownloadFromSvn instead of getting
snapshots.
So I do
$ svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk
spamassassin-trunk
and end up many more megabytes of files than one gets with snapshots,
and no, I'm not talking
> "MM" == Mark Martinec writes:
MM> Did the rule __RCVD_IN_2WEEKS end up in the current sa-update set?
MM> If so, you can either remove the rule, or install the SA from ... SVN.
If I http://wiki.apache.org/spamassassin/DownloadFromSvn often, does that
mean I don't need to use sa-update anymore
Help, sa-update gives:
rules: failed to run __RCVD_IN_2WEEKS test, skipping:
(Can't locate object method "received_within_months" via package
"Mail::SpamAssassin::PerMsgStatus" at (eval 755) line 19.
)
channel: lint check of update failed, channel failed
Actually there should be one or two more whitelists, so one can e.g., score
-100 one's friends
-10 one's schools
-1 one's country
Sometimes first time spammers end up stuffing the entire body of their
message into the Subject: etc. header. I don't see anything on man
Mail::SpamAssassin::Conf to truncate headers after a reasonable length
(but it would also chop multibyte Unicode, or at least RFC 2047
strings, probably). (Howev
I'd establish a
http://people.apache.org/~jm/devel/README.txt
warning people which one of
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.3.0-alpha1.tar.bz2
http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.3.0.tar.bz2
they really want. I guessed the former.
Never mind. I'll just use report_safe 0.
And what does
>normalize_charset ( 0 | 1) (default: 0) Whether to detect
> character sets and normalize message content to Unicode.
Actually do? It sounds like it will convert all your mail to Unicode,
but it seems not to. Or maybe it will just convert the
Content Preview, as I mentioned in my pr
Gentlemen, why oh why can't the Charset of the Content Preview of the
Report be set to the same as where the Report got it from? E.g.,
$ grep ^Content message
Content-Type: multipart/mixed; boundary="--=_4A446828.7FD08E5A"
Content-Type: text/plain; charset=iso-8859-1 <= Why can't this
Ah ha, you can use something like
header FROM_SAME_AS_TO ALL=~/\nFrom: ([^\n]+)\n.*To: \1/sm
> add spf to your domain
But see e.g., http://david.woodhou.se/why-not-spf.html
How unfair: this triggered SUBJ_ALL_CAPS:
Subject: RE: 請教無線電掃瞄
A little capital E and it gets slammed with SUBJ_ALL_CAPS, no matter how
much Chinese follows.
(source: Subject: =?utf-8?B?UkU6IOiri+aVmeeEoee3mumbu+aOg+eehA==?=)
/
rawbody __J_TRAC_MY_COMMENT /\+-+\n(Changes|Comment) \(by jidanni\):\n/m
meta J_TRAC_OTHERS __J_TRAC_COMMENT && ! __J_TRAC_MY_COMMENT
score J_TRAC_OTHERS -7
Missing To: headers at the trac I used upped SpamAssassin's score so I
didn't need up their threshold to filter.
I ho
So to get mail on others' actions on our bugs, but not our own
actions, we must make fancy SpamAssassin rules:
header __J_TRAC_COMMENT X-Trac-Ticket-URL =~/\#comment/
rawbody __J_TRAC_MY_COMMENT /\+-+\nChanges \(by jidanni\):\n/
meta J_TRAC_OTHERS __J_TRAC_COMMENT && !__J_TRA
I don't suppose there is a way to use environment variables,
header NO_ME ToCc !~ /${USER}/i
without perhaps a preprocessor to turn them into
header NO_ME ToCc !~ /jidanni/i
Or use procmail's *$...$LOGNAME instead of SpamAssassin here.
Here's what I use to only know about other's SourceForge changes, not my own:
header J_SOURCEFORGE exists:X-SourceForge-Tracker-itemupdate-username
score J_SOURCEFORGE -5
header J_SOURCEFORGE_ME
X-SourceForge-Tracker-itemupdate-username=~/^(jidanni|Item Submitter)$/
score J_SOURCEFORGE_ME 10
MU> maybe using spamd and spamc is hat you want...
But that would be a http://wiki.dreamhost.com/Persistent_Processes
I took a look at Mail::SpamAssassin::Plugin::Shortcircuit, but what I
really want to do is "if it is ham, run it through the expensive
'sought' extra tests, to see if it really is ham."
I.e., if the end result is below required_score, continue on into the
"sought" tests.
Probably the only way to
OK, I have just finished
$ sa-update -D --no-gpg --channel sought.rules.yerp.org
And would just like to warn other users that 'sought' rules take three
times longer:
$ time spamassassin --local -t < a_typical_spam_message > /dev/null
real0m14.081s
user0m13.489s
sys 0m0.588s
Up from
rea
HK> If SVN does not ring a bell,
Oh, you mean like the example on
http://svn.savannah.gnu.org/viewvc/trunk/grub2/docs/grub.texi?root=grub&view=log
$ svn co svn://svn.sv.gnu.org/grub/trunk/grub2/docs/grub.texi
svn: URL 'svn://svn.sv.gnu.org/grub/trunk/grub2/docs/grub.texi' refers to a
file, not a
So what's the worst thing that could happen to me with sa-update
--nogpg? Just a little more spam getting through? Ha!
> If you would just follow instructions, you wouldn't need --nogpg
Yes, well, let's just say things didn't work out, and we want to use
--nogpg just for that risky feel. Like smo
m> those I looked at triggered JM_SOUGHT_FRAUD_1. so make sure you use the
m> sought channel in your sa-update.
OK, I did all the research to find what it might be that you were
talking about.
I completed the steps (some of them exposing how sa-update fails to
catch a bumbling user):
$ wget http:
m> http://www.netoyen.net/sa/sa-update.sh.txt
m> http://www.netoyen.net/sa/channel.conf
They give 403 Forbidden.
>> DNS seems to have been reporting 709395 as current for about eight weeks
HK> If you want more up-to-date protection, use latest SVN (3.3). That's where
HK> the development happens. It's been working fine here for a long time.
All I know is I have
$ crontab -l
33 3 * * * PATH=$HOME/bin:$PATH sa
Gentlemen, does one just keep on adding more regexps for each new language
edition of this the spammer makes? Any better way for this particular spam?
body J_NEW_ADDRESS
/\xA7\xDA\xA6\xB3\xB7s\xAA\xBA\xB9q\xB6l\xA6a\xA7}\xA1I\xA7A\xB2{\xA5i\xB9q\xB6l\xB5\xB9\xA7\xDA|I
have a new email address!Yo
Sure we can do
meta META0 TEST1 && TEST2
but say TEST2 is expensive, and we only want it to be run if TEST1 is
positive. I suppose SpamAssassin's whole train of thought has no ifs
ands or buts, other than a method of quitting early, but that not what
I want to do. I suppose branching is only poss
Never mind the below, I solved it with
header J_CHSET3
Subject:raw=~/\s=\?(windows-(125[0125]|874)|koi8-r|GB2312|iso-8859-[28])\?/i
The below:
Here we go again.
How can I filter on
X-Spam-Languages: zh.gb2312
run it through spamassassin a second time?
Use _LANGUAGES_ somehow in a regexp?
Of cours
Gentlemen, it seems spamassassin used full military justice here:
0.0 HTML_MESSAGE BODY: HTML included in message
2.5 MPART_ALT_DIFF BODY: HTML and text parts are different
well of course, because
2.3 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
OK, then
Oh no oh no, man Mail::SpamAssassin::Conf says
Whitespace in the files is not significant, but please note that
starting a line with whitespace is deprecated, as we reserve its use
for multi-line rule definitions, at some point in the future.
OK, sorry. I regret my previous message.
Wait. Wouldn
Gentlemen, I save wads of space in my user_prefs with
header J_YAHOO_CAL X-Yahoo-Newman-Property=~/calendar-invite/
score J_YAHOO_CAL 11
header J_MEDIAWIKI_MAILER X-Mailer=~/MediaWiki mailer/
score J_MEDIAWIKI_MAILER -10
instead of the traditional
header J_YAHOO_CAL X-Yahoo-Newman-Property=~/c
Gentlemen, I am frustrated by the duplication of information in:
X-Spam-Checker-Version: SpamAssassin
3.2.5-mon_sep__8_23_53_29_2008.jidanni2.jidanni.org (2008-06-10) on
jidanni2.jidanni.org
X-Spam-Status: No, score=0.0 required=1.9 tests=none autolearn=disabled
version=3.2.
DCWO> Perhaps you would like to share an example of such a spam
OK, https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5970 thanks.
>> Hello, this is the sa-update program talking to you.
>> We've detected a problem.
>> You need to do
>> $ wget http://spamassassin.apache.org/updates/GPG.KEY
>> $ sa-update --import GPG.KEY
>> and then run sa-update again. Thank you.
DCWO> Patches welcome. Please keep in mind, when parsing the
I set score USER_IN_DEF_WHITELIST 0
as I guess I'm not the well rounded person reflected in the
pre-defined whitelists. Indeed not many people are I bet.
You see one day this spam got through riding high on that -15 point
boost, causing me to notice the existence of these lists. I'm not sure
if my
> "K" == Kelson <[EMAIL PROTECTED]> writes:
K> Pardon me for putting words in someone's mouth, but I got the
K> impression that the original poster's point was not to advocate
K> disabling signature checking, but to suggest that the error message
K> should be more useful.
Yes, I'm saying ins
You know, it is a 1000 times easier to just do
$ sa-update --nogpg
than to try to figure our the right way from the messages that
surround "channel: GPG validation failed, channel failed", or the
sa-update man page, or writing this group and asking what to do. So
there, the result is gpg is defeate
> "TVD" == Theo Van Dinter <[EMAIL PROTECTED]> writes:
TVD> http://wiki.apache.org/spamassassin/SaUpdateKeyNotCrossCertified
OK, I wish sa-update would mention that step upon detecting that error.
Just want to mention that
$ sa-update -D
[7581] dbg: gpg: gpg: WARNING: signing subkey 24F434CE is not cross-certified
[7581] dbg: gpg: gpg: please see
http://www.gnupg.org/faq/subkey-cross-certify.html for more information
The update downloaded successfully, but the GPG signature verification fai
Gentlemen, every few months we must upgrade Spamassassin (the software
itself, not just doing sa-update).
So what script do you use to take the bore out of the process?
Need something like:
set -xeu
set /tmp/$USER.SpamassassinUpgrade
mkdir $1
cd $1
latest=`(fancy code to determine latest version
The following are my (happy) Mail-SpamAssassin-3.2.5 installation
observations.
Seen at untarring:
Please make files dates reflect when they were last changed. Not all
just 2008-06-10.
We see
checking module dependencies and their versions...
NOTE: the optional Mail::SPF module is not insta
>> All a spam program would have to do is say "[EMAIL PROTECTED] posts lots
>> to that list. His address must be a trusted subscriber. Well, here's
>> one more post from him, muhahaha."
SB> If "Bob" posts a lot to a list(s) and is respected within said
SB> list(s), then the other subs of that list
Odd how mailing lists that don't obfuscate addresses don't see more
trusted mailing list subscriber spam.
All a spam program would have to do is say "[EMAIL PROTECTED] posts lots
to that list. His address must be a trusted subscriber. Well, here's
one more post from him, muhahaha."
OK, I suppose
I notice that old unused directories accumulate each time one updates
spamassassin:
$ tree -d var
var
`-- spamassassin
|-- 3.002003
| `-- updates_spamassassin_org
`-- 3.002004
`-- updates_spamassassin_org
This will probably accumulate old perl versions one day too:
lib
`-- per
KD> To dig out exactly why, you'll have to dig down through the layers
KD> of meta tests that go into FORGED_MUA_OUTLOOK. :/
20_ratware.cf is apparently not totally aware of the full MicroSoft
scene. Just wanted to let you know. As I am allergic to MicroSoft: OK
thanks, see you later and I hereby
Dear Spamassassin: today enjoying my usual chastising of people who
send me inferior mails by showing them what Spamassassin has to say, a
user remarked that he really does use MS Outlook, therefore I ended up
looking goofy. So the test heeds an update beyond anything sa-update
on 3.24 can do.
JB>
Gentlemen, reviewing one's spam, ordered by score, and threaded, is
definitely the way to go in one's daily check for false positives.
Here's how it looks for me in gnus, using my brilliant
http://jidanni.org/comp/spam/spamdealer.html orderer:
. 8 080229|2.0|Secretsline In:Best VPN service
.
BP> Using (?: avoids creating backreferences. It should be slightly
BP> faster if the backreference is not used.
Wonder just how faster, in an actual spamassassin (not just perl)
context. Anybody got some timing statistics?
Say, if we're all getting the same spam, isn't that what we're paying
sa-update to catch? :-)
How to enjoy the high scores of --local, but still enjoy network tests?
Man Mail::SpamAssassin::Conf says
If four valid scores are listed, then the score that is used
depends on how SpamAssassin is being used. The first score is used
when both Bayes and network tests are disabled
MK> Call me older fashioned.. I consider line-wrapping a bit too "fancy"
MK> for my config editing preferences.
I see, you must have a billion column wide terminal or something.
Oops. You whippersnappers don't call them terminals these days.
Anyway, I swear I am not dreaming:
$ info make
We spli
MK> Why would there ever be a problem fitting on one line? Lines aren't
MK> limited to 80 characters or anything silly like that..
MK> That sounds a bit like complaining that a ship must fit in the water..
MK> There's a whole ocean out there, so who cares if you can't put one
MK> boat in 2 rain pu
RP> Mind the linebreak :-)
That reminds me of this MINOR ITEM,
Currently, each rule or configuration setting must fit on one-line;
multi-line settings are not supported yet.
Hmm, let me see. I use the below in user_prefs. Hope that helps.
header J_CHSET3 Subject:raw =~
/\s=\?(windows-(125[0125]|874)|koi8-r|iso-8859-[28])\?/i
score J_CHSET3 5
ifplugin Mail::SpamAssassin::Plugin::TextCat
#ok_languages en zh.big5
#http://issues.apache.org/SpamAssassin/show_bug.cgi?id=569
I just use in user_prefs
body J_GIRL /\bgirl.*\bpic(ture)?s\b/
score J_GIRL 5
KB> If you want to trigger on Russian only, list all but ru.
What if to catch Ms. Ba'loney Margar'ine, airport security had to keep a
current list of all the other people in the world. So this is the
wrong approach, as we've been thru before. OK, bye.
KB> User? SA is for administrators, not for users. Also, there is *nothing*
KB> special about SA version numbers.
Is too or else there wouldn't be a user_prefs file or instructions for
installing non-root. And SA version numbers & aliases often need explaining,
just like Debian package version numb
KB> No, you are not. Please note that these are version numbers, not floats.
KB> With respect to minor versions, 24 is massively larger than 2...
It's all a usability (http://www.useit.com/alertbox/) problem. You
might say SpamAssassin is usability exempt, as it is only for computer
pros. But I'm
Let's record my 3.23 to 3.24 upgrade attempt.
I untar Mail-SpamAssassin-3.2.4 and of course read the file entitled
UPGRADE.
In it I find "Note for Users Upgrading to SpamAssassin 3.2.0".
But I am upgrading to 3.24.
Go ahead and call me dumb, but if I mess up, I might endanger my
email.
Now I lo
1 - 100 of 132 matches
Mail list logo
