> On 04/29/2008 10:18 AM, Twayne wrote: >> OK, I think this page explains it all: >> http://www.openoffice.org/mail_list.html > > Explains what?
Where it might come from, what to do about it, whom to notify, etc.; just read it and use it. > >> >> I've made the notification but so far no response. I respectfully >> submit that others should follow the same instructions on that page >> to report the situation and bring it under control. I also don't >> think it's simple "backscatter" unless you include intentional >> backscatter in your definition. > > This is backscatter: > http://spamlinks.net/prevent-secure-backscatter.htm <groan>, wanna see several more similar links, interpretations and opinions by reputable sources? > > From what I can see, this is one or more persons >> bashing the servers intentionally thinking they might accomplish >> something by being a nuisance and stopping it is a simple matter for >> the PTB. > > It's coming from one server. Block the server's IP range (91.102.65.0 > - > 91.102.65.255) and the problem is solved. No, problem NOT solved; the activity will continue. Burying your head in the sand is no way to treat abuse of any system or network although it is your perogative to do so. > >> However you look at it, the reports should be submitted by as many >> people here as are willing to do so in order to get it stopped. > > If the abuser has been requested to stop and has not, then an abuse > report should go to their ISP. Duhh, you think? > > That said, _this_ list owner ([EMAIL PROTECTED]) should be > notified and asked to block any further messages from the abuser. It > is the responsibilty of the _list owner_ to take preventive action so > that the emails cease making it to the list, and thereby propagating > to gmane, nabble etc. I thought all one had to do was bury their head in the sand and all would be OK? > > >> >> So, guess it's up to the group for the most part. I'm done and have >> done what I can within bounds of the charters/rules etc. If it keeps >> up, I'll have my first valid use for a killfile entry. >> >> Twayne I don't know what's wrong with you but this is the last I'll address anything to you, so flail & wail away all you want. Then once you figure out what you're talking about maybe it'll make sense to someone else and not appear as a simply parroting of other people's words. When you aren't part of the solution, as the saying goes, you're part of the problem. Twayne. >> >>> >>> It's backscatter. But in all fairness, it's probably just a mail >>> server response from a user that has been terminated, and they need >>> to be notified of the problem first. I'd politely notify them - >>> advise them of the problem, and then if they continue to do it, lart >>> their service provider ([EMAIL PROTECTED]). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
