Home |
Search |
Today's Posts |
![]() |
|
Winemaking (rec.crafts.winemaking) Discussion of the process, recipes, tips, techniques and general exchange of lore on the process, methods and history of wine making. Includes traditional grape wines, sparkling wines & champagnes. |
Reply |
|
LinkBack | Thread Tools | Display Modes |
|
|
|||
|
|||
![]()
Just wondering whether google has any brilliant thoughts about
skipping these emails automatically? Must say, fascinating readings though, but am getting bored quickly. :! |
|
|||
|
|||
![]()
"Rene" > wrote:
> Just wondering whether google has any brilliant thoughts about > skipping these emails automatically? > > Must say, fascinating readings though, but am getting bored quickly. > :! You can file a complaint with the poster's ISP (you will need to send them a copy of the entire message including headers, so they can trace the message to its point of origin). If enough people complain, the offender's account will be terminated --- and then he/she will open another free account under another name, but eventually the child will get tired of the game. You can also file a complaint with google and usenet. Again, if enough people complain, google can block their posts from the archives and/or file a persuasive complaint with the offender's ISP. Meanwhile, you can block the sender with most newsgroup access programs. If you are using Outlook Express, click "Message/Block Sender" when viewing the message. Then you won't see anything more from the child until he/she changes his fake email address again. And, if they cross the line and make certain types of threats, the authorities will be able to trace the post to the originator. Even though this person has forged the headers in an attempt to foil such a trace, he has left a distinct trail. |
|
|||
|
|||
![]()
In message > , Rene
> writes >Just wondering whether google has any brilliant thoughts about >skipping these emails automatically? > >Must say, fascinating readings though, but am getting bored quickly. >:! ![]() Heading a bit off topic here, but here goes... Don't know about Google or other web-based news services, but for off-line newsreaders it should be possible. The 3 prime culprits (although it may all be the work of one troll), regularly change the spoofed addresses they post from, so it's tiresome to kill-file each new address. However, the 3 each have distinguishing lines in the header information of their posts: Torllski: There's only one. NNTP-Posting-Host: 67.74.166.63 NNTP-Posting-Host: 213.48.232.22 3 custom kill rules in my newsreader software (Turnpike) thus: /^Torllski: There's only one./h /^NNTP-Posting-Host: 67.74.166.63/h /^NNTP-Posting-Host: 213.48.232.22/h therefore should reject all posts from the 3 individuals. I don't know about setting up kill rules in Outlook / Outlook Express / Agent / Netscape / whatever, but I imagine it's a reasonably straightforward process using similar expressions. An experienced OE user will shortly be along to tell me it's not... ![]() cheers, robin -- www.newforestartgallery.co.uk www.badminston.demon.co.uk www.robinsomes.co.uk www.amazonian-fish.co.uk www.pisces-conservation.com www.irchouse.demon.co.uk www.blackwell-science.com/southwood Trust me, I'm a webmaster... |
|
|||
|
|||
![]()
"Robin Somes" > wrote:
> Don't know about Google or other web-based news services, but for > off-line newsreaders it should be possible. > > The 3 prime culprits (although it may all be the work of one troll), > regularly change the spoofed addresses they post from, so it's tiresome > to kill-file each new address. However, the 3 each have distinguishing > lines in the header information of their posts: > > Torllski: There's only one. > NNTP-Posting-Host: 67.74.166.63 > NNTP-Posting-Host: 213.48.232.22 > > 3 custom kill rules in my newsreader software (Turnpike) thus: > > /^Torllski: There's only one./h > /^NNTP-Posting-Host: 67.74.166.63/h > /^NNTP-Posting-Host: 213.48.232.22/h > > therefore should reject all posts from the 3 individuals. > > I don't know about setting up kill rules in Outlook / Outlook Express / > Agent / Netscape / whatever, but I imagine it's a reasonably > straightforward process using similar expressions. > > An experienced OE user will shortly be along to tell me it's not... Robin, It's not so easy with Outlook Express, since the "blocked sender" function appears to only allow an email or domain address. But there is 3rd party software which will block this garbage without requiring it to be downloaded. Various methods for various newsreaders are discussed in the following article: http://www.hyphenologist.co.uk/killfile/killfilefaq.htm. However, it makes more sense to me to try to eliminate these children, rather than to simply ignored them and hope they go play in someone else's yard. The ISP for the first IP address (67.74.166.63) is Level 3 Communications, Inc., 1025 Eldorado Blvd., Broomfield, CO 80021. USA. Complaints may also be filed by telephone (1-877-453-8353), or by email ). The ISP for the second IP address (213.48.232.22) is Telewest Broadband IP Network Services, Genesis Business Park, Albert Drive, Woking, Surrey UK GU21 5RW. Complaint may be filed by email: (the ISP states that complaints addressed elsewhere will be ignored, although I suspect they might pay attention to a angry mob armed with pitchforks and tar). I'm considering posting Mr. 'Torllski's true name, address, and telephone numbers in the near future, for the benefit of those of us who believe in DIY remedies. |
|
|||
|
|||
![]()
In message >, Negodki
> writes >> An experienced OE user will shortly be along to tell me it's not... > >Robin, > >It's not so easy with Outlook Express, Doh! Curses, foiled again! ![]() >since the "blocked sender" function appears to only allow an email or >domain address. Aha. Thanks for clarifying that. > > >However, it makes more sense to me to try to eliminate these children, >rather than to simply ignored them and hope they go play in someone >else's yard. >Complaint may be filed by email: (the ISP states >that complaints addressed elsewhere will be ignored, although I suspect >they might pay attention to a angry mob armed with pitchforks and tar). ![]() have changed since) is that they wouldn't even consider a complaint, let alone act on it, unless it conformed *exactly* to the format they specified - which one couldn't discern until one had submitted a complaint. Loop; see Recursive. But there's a chance it might do some good. > >I'm considering posting Mr. 'Torllski's true name, address, and >telephone numbers in the near future, for the benefit of those of us >who believe in DIY remedies. Tsk tsk tsk ![]() cheers, robin -- www.newforestartgallery.co.uk www.badminston.demon.co.uk www.robinsomes.co.uk www.amazonian-fish.co.uk www.pisces-conservation.com www.irchouse.demon.co.uk www.blackwell-science.com/southwood Trust me, I'm a webmaster... |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Rupert kicks the Goos' collective asses. | Vegan | |||
Idiots blowing out their asses | General Cooking |