In comp.os.linux.advocacy, Meat Plow
<meat@xxxxxxxxxxxxxx>
wrote
on Mon, 02 Oct 2006 19:20:47 -0400
<pan.2006.10.02.23.20.46.728000@xxxxxxxxxxxxxxxxxxxxxxx>:
> On Mon, 02 Oct 2006 23:08:19 +0000, The Ghost In The Machine Has Frothed:
>
>> In comp.os.linux.advocacy, Meat Plow
>> <meat@xxxxxxxxxxxxxx>
>> wrote
>> on Mon, 02 Oct 2006 18:02:01 -0400
>> <pan.2006.10.02.22.02.00.617000@xxxxxxxxxxxxxxxxxxxxxxx>:
>>> On Mon, 02 Oct 2006 23:50:57 +0200, Peter Köhlmann Has Frothed:
>>>
>>>> Meat Plow wrote:
>>>>
>>>>> On Mon, 02 Oct 2006 22:29:59 +0100, Roy Schestowitz Has Frothed:
>>>>>
>>>>>> Subject: [News] 64.4% of E-mail is SPAM (Thanks, Microsoft!)
>>>>>> From:
>>>>>> Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx> Reply-To:
>>>>>> newsgroups@xxxxxxxxxxxxxxx Newsgroups: comp.os.linux.advocacy Date:
>>>>>> Mon, 02 Oct 2006 22:29:59 +0100
>>>>>>
>>>>>> Old spammers learn new tricks
>>>>>>
>>>>>> ,----[ Quote ]
>>>>>> | Spam Bot operations are increasing in particularly in South
>>>>>> | American countries where it is the favoured method of distributing
>>>>>> | bank trojans and phishing scams.
>>>>>> `----
>>>>>>
>>>>>>
>>>>>> Zombie PCs spew out 80% of spam
>>>>>
>>>>> That's retransmitted by 'nix mx servers.
>>>>>
>>>>>
>>>> Which is exactly their purpose.
>>>
>>> mx server's purpose is to retransmit spam. LOL
>>>
>>>
>> OK, dumb question. How does one distinguish spam from legit emails?
>
> Configure your server to check any one or all of over 300 spam databases
> available. So it slows shit down but not as much as a hijack or zombie.
> Live the fuck with it.
I shall research that. Of course all this is is a standard
blacklist method, AFAICT. Given DHCP issues, I'll admit
to wondering.
>
> I guess some of these fucks think you just put a fucking
> sendmail and popper box on the internet and WHAM you gotts
> yerself an mx box.
That's about all that's needed, unless the system uses
a *whitelist* (which AFAIK it doesn't, at the moment).
Spam needs little more than a Perl script to send out,
and the protocols are readily available. RFC822 for the
formatting, RFC821 for the actual communication.
(If one doesn't like Perl, substitute VB, Tcl, Bash,
Python, or a fair number of other things as required.
Form letter mailers have been known since I don't know
when.)
>
> As you can tell I'm fed up with these pious fucks here in COLA. That
> bullshit article about the St. Louis PD computer crash being Windows or
> anything x86 architecture for all that matters was the straw. And if that
> wasn't enough, the OP had to backpedal to 2003 to save face. What a bunch
> of fuckin bullshit.
>
The St. Louis computer was probably a sloppily-maintained
Linux or Unix box. No way for me to know, really, without
a lot more research; the news system says absolutely
nothing about it at all, beyond that it "crashed" and that
it had some data they wanted to recover...and you and I
both know that there are many types of crash, from the
anomalous return of a process daemon stating "something
went wrong" to kernel freezups.
So call it sloppy reporting as well. We can conclude *nothing*.
We can suspect, guess, headscratch. That's about it.
--
#191, ewill3@xxxxxxxxxxxxx
Linux. The choice of a GNU generation.
Windows. The choice of a bunch of people who like very weird behavior on
a regular basis, random crashes, and "extend, embrace, and extinguish".
|
|
