Article View: alt.os.windows-xp
Article #1692Re: ERROR CODE oXC0150004
From: caenogenesis
Date: Sat, 11 Jan 2003 20:02
Date: Sat, 11 Jan 2003 20:02
38 lines
2655 bytes
2655 bytes
skinny kin <skin@1fresserve.co.uk> asked wistfully... || your help would be much appreciated thank you The first thing you need to do then is get hold of any of these dodgy emails and print off the message source. Then get a genuine email from Lyn and print that off for comparison. Make sure you label them appropriately. You will probably want to get hold of a highlighter pen and simply mark all the details which are different. There should be various places where the originating IP address is listed. Based on the header information, the date and time, and the ip addresses you should have enough info to prove that the email is a fake, hopefully enough info for the originating ISP to pinpoint where it came from and so on and so forth. Perhaps you two should agree to send each other an email with an address as yet undisclosed. Use that to exchange real email addresses and work from there. It is probably better to not publish your real or at least usual email address within a news group. Let me know if you need any help. -- Gazwad Freelance scientist and people tester. Guardian: alt.os.windows-xp Moderator: alt.warez.uk http://angry.at/gazwad http://gazwad.servebeer.com
Technical Details
Message-ID:
<3e207863$1@news2.power.net.uk>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!news.tele.dk!news.tele.dk!small.news.tele.dk!peer1.news.newnet.co.uk!newsfeed.freenet.de!feed.news.nacamar.de!easynet-monga!easynet.net!news-feed.power.net.uk!news.power.net.uk!news2.power.net.ukReferences:
<avki84$q8t$1@newsg3.svr.pol.co.uk> <avkink$cm3$1@news7.svr.pol.co.uk> <avpn5e$jii$1@news6.svr.pol.co.uk> <3e206c9c@news2.power.net.uk> <avpqsd$7fg$1@news7.svr.pol.co.uk> <3e2070cc$1@news2.power.net.uk> <avps84$g20$1@newsg2.svr.pol.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10116a,a4d8e60e6de2a967 X-Google-Attributes: gid10116a,public X-Google-Thread: fd7d7,a4d8e60e6de2a967 X-Google-Attributes: gidfd7d7,public X-Google-Thread: 10a768,a4d8e60e6de2a967 X-Google-Attributes: gid10a768,public X-Google-ArrivalTime: 2003-01-11 12:03:24 PST From: "caenogenesis" <Dont Be So Far King Wee Tar Did> Newsgroups: alt.os.windows-xp,freeserve.help.windows.misc,microsoft.public.windowsxp.basics References: <avki84$q8t$1@newsg3.svr.pol.co.uk> <avkink$cm3$1@news7.svr.pol.co.uk> <avpn5e$jii$1@news6.svr.pol.co.uk> <3e206c9c@news2.power.net.uk> <avpqsd$7fg$1@news7.svr.pol.co.uk> <3e2070cc$1@news2.power.net.uk> <avps84$g20$1@newsg2.svr.pol.co.uk> Subject: Re: ERROR CODE oXC0150004 Date: Sat, 11 Jan 2003 20:02:51 -0000 Lines: 40 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1123 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123 NNTP-Posting-Host: 195.60.9.173 Message-ID: <3e207863$1@news2.power.net.uk> X-Trace: news2.power.net.uk 1042315363 195.60.9.173 (11 Jan 2003 20:02:43 +0100) Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!news.tele.dk!news.tele.dk!small.news.tele.dk!peer1.news.newnet.co.uk!newsfeed.freenet.de!feed.news.nacamar.de!easynet-monga!easynet.net!news-feed.power.net.uk!news.power.net.uk!news2.power.net.uk