On 11 July 2002, Ryan Cleary said:
> I'm using it with perl 5.005:
>
> [tryanc@steward tryanc]$ perl --version
>
> This is perl, version 5.005_03 built for i386-linux
>
> There were a number of prerequisites that needed to be installed, but it
> does work just fine.
Yeah, I did get it working
Does SpamAssassin 2.31 now require Perl 5.6? I'm trying to build it on
a Red Hat 6.2 box that only has Perl 5.005 installed and running into
all sorts of problems: the spamassassin script now requires Pod::Usage,
which requires File::Spec 0.8 or later, etc.
Thanks --
Greg
On 21 March 2002, Theo Van Dinter said:
> What I'm arguing is: don't replace the regexp of INVALID_MSGID with one
> that isn't actually checking for invalid message-ids.
Right, understood. Makes sense to me.
> Adding a new test that looks for ".+@.+\..+" would be fine by me, since it's
> a new
On 20 March 2002, Theo Van Dinter said:
> But that is a valid Message-Id according to RFC 2822. Unless you really
> want to get into the RFC and do a regex check by the strict standards, all
> you can really check is that the Message-Id is of the form /^<.+@.+>$/.
> That can probably be made a li
ccept it anyways, then use
your regular SMTP daemon, pipe messages through SA at delivery time, and
save a copy. I'm sure this is easy to do with procmail or maildrop.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
On 19 March 2002, Craig Hughes said:
> I think this is a more substantial problem than that which requires a
> bit more work. Thanks for the patch though. I've made a note in
> bugzilla #115 about my intention to incorporate MIME::Tools for doing a
> lot of the hard work for us. We should be ab
but not all sites can. And of
course, not everyone uses Exim.
Furthermore, I recently got a spam with a syntactically correct
"undisclosed-recipients"-style "To" header. I never get that kind of
mail legitimately, and even if I did, so what if it scores 0.5 o
On 18 March 2002, Nick Fisher said:
> 1) SA Doesn't work Win32
> Line 649 of SpamAssassin.pm (2.11) has getpwuid on it. This appears to be
> getting the user's home directory but I don't know why. I've hacked it to
> return something but I'd love to know why it's doing this so I can write a
> prop
d and probably the Right Thing to
do, so if a rule like this gets added to SA by default, it should
probably score < 1.0.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
server, would you expect all email to be
filtered through it? You'll have to read the docs for your MTA to find
out how it works.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
On 15 March 2002, CertaintyTech - Ed Henderson said:
> In my case I use maildrop and deliver to Maildirs. I assume that maildrop
> handles the file locking properly. But on occasion I do see the messed up
> messages like I posted yesterday. I am using maildrop v1.3.6.
If you're using Maildir, y
be built with "-lgdbm", and 2)
SpamAssassin uses Perl's idea of how to build Perl extensions to build
spamc, which is a standalone C program that has nothing to do with Perl.
That does it -- I'm filing a bug report on this one. Sick of typing the
same thing again and again and
rint socket.gethostname()"
or this (requires a relatively recent Python -- 2.0 or later, maybe?):
python -c "import socket; print socket.getfqdn()"
?
Also, you haven't said which version of which OS you're using.
Greg
--
Greg Ward - software devel
On 15 March 2002, Olivier Nicole said:
> I am writting a small script that will send email to my users.
>
> I want the email message not to be checked by SA.
>
> I am wondering if there is any way to do so. I am using
> procmail/spamc/spamd.
You could tweak your procmail instructions so that me
ject "libgdbm.so.2" not found
Rebuild spamc without linking in that library. It probably came from
Perl's standard-set-of-libraries-for-building-Perl-extensions, which
isn't relevant for spamc.
(You can either edit the Makefile, or run some variation on
cc -o spamc spamc.c
man
;s locking syntax. Like everything
procmail, it's cryptic and non-obvious.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-t
t; is seeing this on occasion? Or is this a known problem with 2.11? It seems
> to be a random event and not neccessarily from the same sender.
Might conceivably be a locking problem. How are you delivering
messages, and to what sort of message store (mbox, maildir, etc.)?
Gre
On 13 March 2002, Kerry Nice said:
> Very cool. But it only worked when I changed it from body to rawbody.
> I assume that is because it is at the very end of the message.
>
> rawbody UNIQUE_BODY_ID/^(?:(?:[\w\d]{7,}-)+)[\w\d]{7,}$/
^^
uoted too
much spammy material.
*None* of my false positives have been mail that would be worth
responding to so that some stranger who happens to be on the same
mailing list as me can send me mail. But that's just my experience.
Greg
--
Greg Ward - software developer
On 13 March 2002, Rob McMillin said:
> -p only reads user scores. Did you try
>
> :0fw:
> | spamassassin -P -c https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
u do with that stdout is up to you and
your MTA configuration to decide.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk ma
ome control.
Pipe your message through "spamassassin -t" to see a full report
regardless of how spammy it is.
If you're using spamc/spamd (and you should be, for efficiency
reasons!), note that spamd doesn't always see your user_prefs file. It
usually boils down to a permissi
lize this, but that's not (yet) a priority for me.
I'll probably put these scripts on my web page at some point.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
_
On 13 March 2002, Olivier Nicole said:
> To test the validity of an email address, one does not need to send an
> empty message. As long as no DATA is sent, the SMTP transaction is
> aborted. And you have already checked that the RCPT was ok.
>
> I implemented something like that long time ago to
extensions, even though spamc is a standalone C program and not a
Perl extension.
It should be safe to edit your Makefile and remove the "-ldb" reference,
although this is a kludge. There's something wrong either with your
Perl build or with SA's Makefile.PL.
Greg
-
sed to
go through spamc, and again watch spamd's output.
Any help?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassas
ot find -liconv
> *** Error code 1
Did you build your own Perl, or did it come with the OS?
If you built it, did you build it on this version of the OS, or an older
version?
Have you ever successfully built any Perl extensions on this machine,
with the current Perl build and OS installation?
Wha
On 12 March 2002, Charlie Watts said:
> In my spam collection, they're all already caught by the DNS blacklists -
> but some of y'all aren't using the blacklists.
>
> I'm seeing more and more of a strange phenomenon - spam with no body.
What? You mean after the last header, there's a blank line
izing the scores, under SA 2.0 and later
you need to edit ~/.spamassassin/user_prefs.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassass
ced by setting
the group score for the anti-false-positive rule group to -1.
Hmmm: putting a rule into two groups, one with a group score < 0 and
another with a group score > 0, could be confusing. Should probably
warn about that case.
Greg
--
Greg Ward - software developer
st of email
addresses there as "your addresses", and use them to look for things
like
Subject: kerry_nice
or, my pet peeve:
To: gward <[EMAIL PROTECTED]>
which is also a pretty sure spam marker for me.
Greg
--
Greg Ward - software developer[EMAIL PROTE
).
Was that gem manually crafted, or has someone fed a zillion spams into
Dissociated Press (or something similar)?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.m
e the same as user
> nobody or something, and then just use the standard user_prefs location.
That sounds like almost as much fun as selecting, installing,
maintaining, and updating a relational database. No thanks.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEM
clobbered my user_prefs?
confused-and-slightly-embarassed,
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL
; just submit a message (spam, please!) using
spamassassin -Dr. Wait a minute or so, then run the message through
spamassassin -P, and the Razor test should score.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
yesterday, the exact same thing happened to five messages in
succession. As soon as I fixed local.cf, my mail was fine again. So
it's not some random, timing-sensitive lock-related race condition.
Greg
--
Greg Ward - software developer
On 07 March 2002, Bart Schaefer said:
> What version of procmail?
The procmail-3.21-0.62 RPM from Red Hat 6.2.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.
Just got this in a spam:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
The FROM_AND_TO_SAME rule didn't match because it doesn't normalize
case. Perhaps the last line of the function should be changed to
(lc($from) eq lc($to));
?
Greg
--
Greg Ward - software
ust crashed and
that's that [1]. I don't see why it would have consumed one character of my
message and not the rest.
Greg
[1] although it would be nice if it didn't crash on a syntax error
in local.cf ... ;-)
--
G
I just got a spam with this "To" header:
To:
...is that malformed? (No, I still haven't memorized RFC 2822, sorry.)
The TO_MALFORMED test does *not* catch it.
(In fact, *no* tests caught this spam -- not a single one! But that's
another issue...)
Greg
--
Ooh, this is bad: it looks like "make install" in SA 2.11 clobbers your
~/.spamassassin/user_prefs file. *Very* annoying -- I had a lot of
stuff in mine! Waahhh!!
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourcef
hon script that launches spamc) will figure out which config
file to use, and tell spamc. Presumably, spamc will then tell spamc to
use that config file instead of ~user/.spamassassin/user_prefs, which
will be irrelevant most of the time.
Greg
--
Greg Ward - software developer
n't see an easy way to do this.
If I could specify the exact config file to use for checking any
particular piece of email, then SA doesn't need to get much more complex
-- I can put my config files wherever I please, and update them however
I like.
Greg
--
Greg Ward - s
ct mail based on bogus "From:" headers.
Apparently, the preferred way to use spamassassin-sightings now is to
submit the spam as an attachment.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
obably these are the ones spamming thousands-to-tens-of-
thousands of people, not millions-to-hundreds-of-millions.
Anyways, if you're going to go to the trouble to put
"To: [EMAIL PROTECTED]" in spam for me, you might as well
add "Dear: gward". It just seems like som
yone
> else has seen this.
All the time. 3 years ago, 99+% of spam had a completely bogus "To"
header. Nowadays it's maybe 50%.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchan
org
(or whatever) through some other protocol. Hell, make the database
of received email addresses accessible through a CGI script and make
it HTTP. The database then says what the address of the current
user is.
While writing this completely crazy idea up, I've already tho
ought to be worth a point or so. But I don't see a good way to do
*that* with a regex. That sort of thing really should be done by fully
parsing the message header, pulling out the local-part of the "To"
address, and then looking in the body for that.
Greg
--
Greg
On 01 March 2002, Craig R Hughes said:
> Just changed it in CVS to:
>
> header SUBJ_ALL_CAPS Subject =~ /^[^a-z]*$/
But that'll match an empty subject. (No comments on whether that's a
spam discriminator, but it probably happens more often in non-spam than
an "ALL CAPS" subject does
g to be?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
t;non-spam" MUAs, because
as soon as the smart spammers notice that rule, guess what they'll add
to their headers...
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangeht
: I have seen several "Nigerian" scams that
are actually about Zimbabwe or Sierra Leone or some other African
country. (They sound like the same scam, though.) Does this collection
include any of those?
Greg
--
Greg Ward - software developer
es SA
strip whitespace after the colon before feeding headers to rules?
And do I need to modify any other file to make the GA pay attention to
this rule and evolve its score?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehtt
On 28 February 2002, Mike Loiterman said:
> But now I have another question. How can those of us with private
> domains prevent spammers from using our domains as the reply to
> address or bouncing their crap off our servers?
You can't. The Internet just doesn't work that way. Be thankful your
[I suggest a new rule]
> Here's a quick and dirty attempt:
>
> header TO_REALNAME_EQ_LOCALPARTTo =~ /\"?(\w+)\"?\s+<\1\@[^<>]+>/i
> describe TO_REALNAME_EQ_LOCALPART Real name in "To:" equals local part
> score TO_REALNAME_EQ_LOCALPART 2.5
[Craig responds]
> Sounds like a good rule -- e
it figures out what the list reply address (this is how mutt works,
AFAICT).
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spama
to
think that you're the unusual case here. Most people's names are
different from their email addresses.
> BTW, You would also have to handle headers formatted as
> To: [EMAIL PROTECTED] (gward)
S'pose so, but I don't recall seeing much spam that looks l
s to which
scores are spam markers and which are not, so it can keep spam markers
out of negative territory. Maybe it should warn about spam-marker tests
that want to be negative: that indicates that there's something wrong
either with the test or with the corpus.
Greg
--
Greg
nsitive and handle RFC 822
address quoting, of course.
Here's a quick and dirty attempt:
header TO_REALNAME_EQ_LOCALPARTTo =~ /\"?(\w+)\"?\s+<\1\@[^<>]+>/i
describe TO_REALNAME_EQ_LOCALPART Real name in "To:" equals local part
score TO_REALNAME_
On 27 February 2002, Craig R Hughes said:
>181 98 83 RATWARE
That's interesting. I wonder if the RATWARE regex is too broad --
perhaps if it were toned down a bit, it would be better focussed on
spam. This ought to be a well-focused rule; how many people use
spamware
On 27 February 2002, Nick Fisher said:
> Hi folks,
> I'm rusty on Perl and I'm working on Win32... Is there is a Win32 FAQ
> somewhere I'd love a link!
> The main problem I'm tackling now is that I get the following error when
> running spamassassin:
>
> "The getpwuid function is unimplemen
On 27 February 2002, Woodworth, Eric said:
> On 2 of my boxes, when I edit local.cf and change required_hits to 7, it
> doesn't take. When I check my spam reports it still tells me that the
> required hits is only 5.
Is this running as spamassassin or spamc/spamd? If the latter, what
user does
rkstations. I'm currently maintaining SA on two
Linux machines, soon to be three; two are running Red Hat 6.x and one is
Debian 2.2 -- all of which have Perl 5.005 installed. I know Perl 5.6
has been out for quite a while now, but I would like to see SA maintain
compatibility with 5.005.
On 27 February 2002, Mike Loiterman said:
> Just discovered that my aliases as defined in /etc/mail/aliases don't
> work anymore. Is this because I swithed my MDA from /usr/bin/mail to
> /usr/local/sbin/procmail or does this have something to do with
> SpamAssassin?
Depends on your MTA. I know
if
Razor is there when you build/install SA. You might try rebuilding/
reinstalling SA.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassass
efeeds vs carriage
> returns, and is there anyway to fix it?
Unlikely, since mutt is -- for the first time ever -- in the same camp
as Outhouse Express, and displays the terse header report just fine.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS E
rely on the MTA supplying. Some MTAs put the
envelope sender in an environment variable, sometimes "Return-path" has
it, but there's nothing standard. So I think you'll probably have to
write your own test that looks at "Return-path" for this one (assuming
you can
On 22 February 2002, Michael Moncur said:
> I think virtually any message sent as one big graphic would be spam,
> but I can't think of a good way to detect it using a regular
> expression. Perhaps you could look for number greater than x (300?).
I don't think a regex is the right tool to use he
On 22 February 2002, Craig R Hughes said:
> Were you using spamassassin or spamc/spamd greg? I believe
> spamassassin allows you to have user rules, spamd does not.
I was using spamassassin; you are correct, user-defined rules are obeyed
by spamassassin but not spamc/spamd. I just filed bug #49
might be doable, even easy, but it's scope
creep.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL P
easant surprise, it worked!
IMHO this ought to be a configuable option for
/etc/spamassassin/local_prefs -- on some systems, it's perfectly
reasonable to let users write their own rules.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
when
it's not needed.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourc
"&&" should
be recognized by the rule parser instead.)
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAI
OS it happens to be running
* plunk down the money for Philip Hazel's Exim book -- I have to
admit I have't actually looked at it myself, but I bet it's
a good way to learn how to run a Unix mail server
Greg
--
Greg Ward - software developer[EMAI
I assume that second snippet is from your
/etc/services.
Filesystem corruption, perhaps?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
ing procmail, it will look *something* like this:
# send spam to [EMAIL PROTECTED]
:0
* ^X-Spam-Flag: YES
! [EMAIL PROTECTED]
# save everything else to ~/Maildir
:0
Maildir/
(I might be missing some vital piece of punctuation here; I am not a
procmail expert and do not ever want to be on
gards.
Barrister Anthony Dozie
PRINCIPAL CONSULTANT
__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
- End forwarded message -
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
On 14 February 2002, CertaintyTech - Ed Henderson said:
> I have been seeing alot more Spam get thru (false negatives) in v2.01 than
> with v1.5. I have been comparing the scores of 1.5 with 2.01 to see why.
> Here is an interesting discovery: there are several scores in the
> 50_scores.cf file
:26:31 2002
@@ -110,4 +110,3 @@
spamd/spamc: spamd/spamc.c
- $(CFCC) $(CFCCFLAGS) $(CFOPTIMIZE) spamd/spamc.c \
- -o $@ $(CFLDFLAGS) $(CFLIBS)
+ $(CFCC) $(CFCCFLAGS) $(CFOPTIMIZE) spamd/spamc.c -o $@
Craig, if you haven't already changed Makefile.PL like this, you mig
ne in my life...
Hmmm, everyone's going on about libndbm, but nobody's asking about Perl.
It might be Perl's fault that -lndbm is included in the link command for
spamc. Which Perl version are you using? Is it the Debian package, or
did you build it yourself? What does "pe
hat
1) there's no real name in "From", but SA doesn't catch this
because of the quoting
2) the real name in "To" is the same as the address, but SA doesn't
catch this because of the quoting
Anyone notice a consistent theme here? ;-)
I'll post
ted in /etc/exim/spamcheck_users). And it relies on Exim's
highly configurable and flexible nature. Dunno if postfix is quite as
configurable.
Hope this helps --
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://
On 31 January 2002, CertaintyTech - Ed Henderson said:
> Thanks for the reply. I am not so good interpreting the tests. Does anyone
> know of a good reference that would help me to interpret what the test is
> doing?
Randall Schwartz, *Learning Perl*
Larry Wall et. al., *Programming Perl*
Jef
On 31 January 2002, CertaintyTech - Ed Henderson said:
> What puzzles me is that this one should have gotten a LINE OF YELLING and
> UNSUBSCRIBE. Something appears broken.
The LINE_OF_YELLING test is (IMHO) too picky in SA 2.0 (and, I presume,
2.01). See the archive for details. Bottom line, t
recipient
headers. Seems like a good spam flag to me, but I don't recall seeing a
rule like this when browsing SA's current ruleset. Is it there?
If not, should it be added?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchange
s and come up with our
own score sets. But why bother?
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL P
nor implementation oversight.
I think his suggestion was right on: don't update the auto-whitelist in
testing mode.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
__
ut should be automatic.
If you want multiple reports, you'd probably have to write a custom
script. Something like:
if SA's RAZOR_CHECK didn't match:
pipe through spamassassin -r
if SA didn't flag it as spam:
send to spamassassing-sightings
... etc ...
Doesn&#x
{40,} -- or whatever
minimum length works.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
have to
be coded as an "eval"?
Here's a slightly subtler variation:
/^[A-Z0-9\$\.,\'\!\?\s]+$/ && /\b[A-Z]+\b/
Same as above except the line must contain a complete uppercase word.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exc
On 24 January 2002, Matt Sergeant said:
> No, this is Perl. Version numbers are floating point numbers. (yes I know
> it's a crap situation, but that's just how it works).
I think that rule was broken when the next version after Perl 5.005
became Perl 5.6. Didn't they even introduce a new type e
at any such header)
For the record, that's exactly what I did -- check my shell code again.
Greg
--
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org
___
t; * mail to any /(hotmail|msn|yahoo|...).com/ address should earn a
> point or so
I think the above idea were properly fleshed out, this one would be
unnecessary.
Greg
--
Greg Ward - Python bigot[EMAIL PROTECTED]
http://starship.python.net/~gward/
K
for Content-length and Lines and munge them too. (IMHO.)
Greg
--
Greg Ward - Linux geek [EMAIL PROTECTED]
http://starship.python.net/~gward/
"He's dead, Jim. You get his tricorder and I'll grab his wallet."
___
e positives, eg. you'd have to
populate your recipient whitelist before using SA, and if you are
a hotmail/msn/yahoo user you might not want to add a point to every
message addressed to you.
Greg
--
Greg Ward - just another Python hacker [EMAIL PROTECTED]
http://
t place; this maildir started life as
an mbox, and I just converted it so I could access one message at a time
more easily.)
Perhaps SpamAssassin should munge the Content-Length and/or Lines
headers when it adds a header or footer?
Greg
--
Greg Ward - Unix nerd
ts -
Anyone else seen anything like this?
Note again that SA 2.0 seems to handle sample-spam.txt just fine, even
with my unusual installation and explicit "-c ~/share/spamassassin"
stuff.
Greg
--
Greg Ward - Linux geek [EMAIL
97 matches
Mail list logo
