Sorry, I know absolutely nothing about cyrus.
Greg
> could you describe an alternative scenario using cyrus
>
> On Fri, 30 May 2003, Greg Webster wrote:
>
>> Hello, SpamAssassin mailing list :)
>>
>> Some new documentation I've created. I'll be placing
(s) examined).
Why would it show that it 'Learned from 0 message(s)'? I told it that
these were verified as spam and ham, shouldn't it try to learn them?
Greg
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an
They've noted that we give HABEAS_SWE a score of -4.6 I think. I'm
adjusted it for my machines to zero. Here's the headers:
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: from beefcake.intouch.ca (beefcake.intouch.ca [64.69.91.201])
by intouch.ca (Postfix) with ESMT
; repository but I have no clue where that is, how to browse it, etc. :/
So what is the current "official" site for this?
---
I would be interested in the official site (download site) as well.
I have been using spamstats.pl written by Vincent Deffont
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
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
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://
ouched.
No -- I ran a loop like this:
for msg in greg-spam.mdir/cur/* ; do
echo $msg
out=greg-spam-out.mdir/cur/`basename $msg`
spamassassin -c ~/share/spamassassin -t < $msg> $out
done
The only console output from this was the 68 filenames in
greg-spam.mdir/cur. When I l
gt; where you put known recipients, including mailing lists you're o
[Charlie Watts reacts]
> How does spamassassin know your address? This is a nice test, but how do
> you get your addresses into spamassassin?
Well, I've whipped up a very ad-hoc version already:
header TO_UNKNO
[me, explaining my test run of SA]
> No -- I ran a loop like this:
>
> for msg in greg-spam.mdir/cur/* ; do
> echo $msg
> out=greg-spam-out.mdir/cur/`basename $msg`
> spamassassin -c ~/share/spamassassin -t < $msg> $out
> done
[dman responded]
> Ho
introduce a new type especially for
version numbers?
Greg
___
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
east two adjacent
words of four letters each.
Anyways, I'm just pottering around. Hopefully someone who can do
something has noticed that LINE_OF_YELLING is too picky in 2.0...
> Or keep the previous rule's minimum length of 40 characters?
Easy enough, just change the + in my first regex to
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
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
__
t can be found in the SpamAssassin source directory. I can't find
it, though. So, I'm at a loss. With no patch in the source directory, has
the Mail::Audit module been fixed? If so, why am I getting this error?
Sorry if this is a
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
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
m line, the line has to be >=
45 characters long, and there has to be a YELLING word >= 5 chars long
>= 20 chars from either end. I proposed a couple of lame replacements,
most of which were promptly (and rightly) shot down.
Greg
___
Sp
ontract bars me from recommending that. But Perl's not so bad,
really... ;-)
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
Hi folks.
I'm the one who wrote the other day to ask if anyone had heard of the
error I mentioned regarding SpamProxy, and the silence was deafening.
So, I wrote to the author, and he'd not heard of anything like it. So,
I'm left to ask a very BASIC question:
I actually DO have spamassassin wo
On 31 January 2002, Greg Blakely said:
> I actually DO have spamassassin working with procmail, quite nicely,
> thank you.
>
> But I have a situation where not all my received mail is for users homed
> on that machine. Nor, for that matter, are they able to reach it via
> NFS.
ponse on SpamProxy Question Now
another
> On 31 Jan 2002 at 23:04, Greg Blakely wrote:
>
> > I actually DO have spamassassin working with procmail, quite nicely,
> > thank you.
> >
> > But I have a situation where not all my received mail is for users homed
>
Hi, folks. I've made a lot of noise here, and received a lot of useful
information from many of you. So, I thought that it would be a good
time to give a little bit back.
I finally got the "spamproxyd" smtp filter going with Postfix, and it
was all just one little thing that was missing.
In /
866 is. 855 and 844 are planned to be.
I work for a long distance company, and have had to hold the hands of
many of our customers as they reprogrammed their PBXes to realize that
866 shouldn't be restricted as if it actually cost them something...
-Original Message-
From: Craig Hughes
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
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
: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
It probably doesn't apply, but then again... anything to help narrow it
down, right?
I successfully have the proxyfilter working on a FreeBSD box, using
Postfix.
So, it'd probably point towards milter rather than FreeBSD.
( Just in case someone was thinking that FreeBSD was what one should
avo
higher most of my false negatives would have been caught.
I second that suggestion. I have bumped up several of the 0.01 scores
in my ~/.spamassassin/user_prefs file after some fairly obvious spam
leaked through. Would have been nice not to have to do th
When I find something that SpamAssassin can't filter, I'll just add it
to the filter tables of my MTA (Postfix). It can filter based on IP
address, "HELO" host, words in the subject line, etc.
Spam Assassin does a better job than doing it yourself, but, in my case,
since I know nobody in mainlan
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
me, I have a copy of Ian's newest script here. Unless he objects,
I can provide a copy of it for you.
-Original Message-
From: Stewart, John [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:32 PM
To: '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Cc: Greg Bla
/SpamAssassin/SMTP/SmartHost.pm
Coulda been hazardous mixing my apples with my oranges, but, in this
case, it worked.
-Original Message-
From: Stewart, John [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 5:33 PM
To: 'Craig Hughes'; '[EMAIL PROTECTED]';
'[E
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
}
> }
[...]
> And this was also in the auto-whitelist.db file:
>
> l2tp115 L2TP# Layer Two Tunneling Protocol
> ddx 116 DDX # D-II Data Exchange
[...]
That Perl code looks like the output of sys2ph, ie. a C header file
translated to Perl. And
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
"&&" 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
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
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
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
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 fil
e right tool to use here. SA has stretched
regex usage to impressive extremes, but it's *not* a Turing-complete
language! This should be implemented as an eval test.
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lis
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
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
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
your MTA. I know Exim (in its conventional configuration)
and qmail both do alias processing long before local delivery, so
switching MDAs shouldn't be an issue.
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists
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.
what
user does spamd run as? Perhaps it's a permissions problem.
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
IOW, it sounds as if SA is Unix-specific, until proven otherwise. Why
on earth would you trust Windows to process your email, anyways? >duck<
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
spamware to send out regular email?
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
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_
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
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
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
e appropriate
than \w+ is used, or so it doesn't match when there are mismatched
quotes? Or do you want to take over from here?
I'm not really clear on how strict SA's regexes should be -- ie. is the
goal to follow the grammar in the RFC, or to just do a good enough job
that most
t way. Be thankful your
domain name is not as popular as, say, hotmail.com for spammers.
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
On 28 February 2002, Craig Hughes said:
> Greg, I think I'm going to be busy for a few days just with scoring
> refinements. If you could solidify the regex I'd appreciate it.
OK, here's a patch relative to CVS:
--- rules/20_head_tests.cf 26 Feb 2002 12:04:21 -000
: 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
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
Perl 5.005, this rule is broken. It uses
regex features added in Perl 5.6. I changed it to
header SUBJ_ALL_CAPSSubject =~ /^[^a-z]{6,}$/
which is clearly biased against non-English languages, but at least it
works with Perl 5.005.
Craig, this hasn't been fixed in CVS. Is it goin
"ALL CAPS" subject does.)
How 'bout this:
header SUBJ_ALL_CAPS Subject =~ /^[^a-z]{3,}$/
(for some value of 3)?
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
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
r specifies his address; if you don't have it, you can't use your
special code.
Greg
[1] OK, OK, I thought of an idea: send a message to a special cooked
address that you (the programmer) control; for SA, it might be
"[EMAIL PROTECTED]". A script behind this a
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's a signed message for your tests.
- --
Greg Leffler| GPG Key Fingerprint (ID 0x5C49D3CA)
http://greg.louisville.ky.us| 2845 598C 879C 8B73 0EAB
[EMAIL PROTECTED] | 8DA1 7579 C1B6 5C49 D3CA
GPG Key available a
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
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
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 PROTEC
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
--
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
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
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.
On 07 March 2002, Bart Schaefer said:
> Got this reply from the procmail list. Are you (Greg and/or Daniel) sure
> that you're using the proper procmailrc lockfile syntax on recipes that
> deliver to mailboxes?
I don't think locks are relevant in my case, since the bogus me
; 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
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
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
).
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
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
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
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
the last header, there's a blank line and then
nothing? No MIME cruft? Ummm, where's the spam then? Do they just put
their 800 number or URL in the subject?
Greg
PS. wow, a message where every sentence is a question -- new record!
___
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
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
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
-
t long time ago to check that users
> entered a valid email address in a Web from.
Not true. Testing as far as RCPT TO can determine if an email address
is sure to fail, but it cannot determine that it's sure to succeed.
Greg
___
Spamass
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
_
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
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
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
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
-)+)[\w\d]{7,}$/
^^^^
The \d's there are unnecessary, as \w includes digits. That means a
character class is not needed, so the regex simplifies to
rawbody UNIQUE_BODY_ID/^(?:(?:\w{7,}-)+)\w{7,}$/
Greg
___
Spamassassin-talk ma
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
;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
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
structions so that messages that match
some signature -- eg. subject line, maybe last Received header -- are
delivered directly, not piped through SA.
Greg
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/lis
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
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
1 - 100 of 212 matches
Mail list logo
