Re: OT- How do the phishers clean their trail???



"Bill" <kinzie@xxxxxxxx> wrote in news:1137819896.702378.124250
@g14g2000cwa.googlegroups.com:


>
> My point is there are no other "recieved from" ip addresses in the
> trail. It's squeeky clean. No one could trace that header. Compare that
> header to any mail you have.
>
> Btw, I see that UXN Spamcombat is no longer around.
>

It was sent by a zombie on some poor uninformed persons computer, most
likely with a dynamic IP. Most spammers use drones now so they can't be
traced.


--
Anthony

You can't 'idiot proof' anything....every time you try, they just make
better idiots.

Remove sp to reply via email
.



Relevant Pages

  • [RFC] Common Trace Format Proposal for Linux (v1)
    ... The goal of the present document is to propose a trace format that suits the ... Packet: A sequence of physically contiguous events within a section. ... A metadata section contains information on trace event types. ... Per-section event header description. ...
    (Linux-Kernel)
  • [RFC tracing] Common Trace Format for Linux (v1.1)
    ... In order to get things rolling, I hereby append my trace format proposal as RFC. ... Packet: A sequence of physically contiguous events within a section. ... A metadata section contains information on trace event types. ... Per-section event header description. ...
    (Linux-Kernel)
  • Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108
    ... If we remove ASCII> event tracing from LKET, we could remove CPU id from the event header as> well. ... The original idea for keeping ASCII trace was that a user may have wanted to look at trace output information in real-time as it was being printed onto the screen. ... Since the user is> free to chose which tracepoints he wants to use for his workload, we can> not guarantee that scheduler tracepoints are going to be available. ...
    (Linux-Kernel)
  • [PATCH 2/11] LTTng-core 0.5.108 : core-header
    ... +struct ltt_channel_struct { ... a dynamic per trace alignment value must be set. ... so the buffer header and trace header are aligned. ... * The event header must be a size multiple of the void* size. ...
    (Linux-Kernel)
  • [PATCH 2/11] LTTng-core 0.5.111 : Relay+DebugFS
    ... +struct ltt_channel_struct { ... a dynamic per trace alignment value must be set. ... so the buffer header and trace header are aligned. ... * The event header must be a size multiple of the void* size. ...
    (Linux-Kernel)