From owner-freebsd-questions Fri Jun 7 8: 0:52 2002 Delivered-To: freebsd-questions@freebsd.org Received: from federation.addy.com (addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id B751037B400 for ; Fri, 7 Jun 2002 08:00:33 -0700 (PDT) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id LAA85286 for ; Fri, 7 Jun 2002 11:00:25 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Fri, 7 Jun 2002 11:00:25 -0400 (EDT) From: Jim Sander Cc: freebsd-questions@FreeBSD.ORG Subject: Re: List email bomb In-Reply-To: <3.0.5.32.20020607092722.00fc2288@mail.sage-one.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > lists were subjected to a sort of a "flood attack" It wasn't necessarily a malicious attack. I've seen this happen a few times, and the perpetrators were usually just clueless and often suffered more inconvenience as they caused me. What you did is as close to "correct" as I think you can get. (if anyone has a better plan, I'd love to hear- now that I think about it, using sendmail's access features might be more appropriate) I usually add a step of emailing the admin of the server in question, just to be safe. What I think you might be seeing is a typical loop scenario, caused by brain-dead autoresponders or mail servers. Someone subs to a list on your server, and when majordomo sends them something it generates a response (either a bounce, or a "we got your mail" message) that is (probably improperly) sent to 'majordomo' - which of course majordomo doesn't understand, so it thoughtfully sends them the 'help' message. The help message then causes the generation of another response. And so on... -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message