Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Aug 2002 18:46:06 +0200
From:      Roman Neuhauser <neuhauser@bellavista.cz>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Script help
Message-ID:  <20020802164606.GJ52563@freepuppy.bellavista.cz>
In-Reply-To: <3.0.5.32.20020802112435.02ba28a8@mail.sage-one.net>
References:  <20020802155258.GG52563@freepuppy.bellavista.cz> <3.0.5.32.20020802094620.02ba28a8@mail.sage-one.net> <20020802155258.GG52563@freepuppy.bellavista.cz> <3.0.5.32.20020802112435.02ba28a8@mail.sage-one.net>

next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Fri, 02 Aug 2002 11:24:35 -0500
> To: Roman Neuhauser <neuhauser@bellavista.cz>,
> 	freebsd-questions@FreeBSD.ORG
> From: "Jack L. Stone" <jackstone@sage-one.net>
> Subject: Re: Script help
> 
> At 05:59 PM 8.2.2002 +0200, Roman Neuhauser wrote:
> >> From: Roman Neuhauser <neuhauser@bellavista.cz>
> >> > From: "Jack L. Stone" <jackstone@sage-one.net>
> >> > 
> >> > When placing blocks on some ISPs as being sources of spam floods,
> >> > one consideration has to be if it affects a number of innocent
> >> > members on various vhost majordomo mail lists so they may have
> >> > passes.
> >> > 
> >> > I know I can find a list of any that would be affected by
> >> > manually doing this: grep spammer1.net /mj/vhost1.com/lists/list1
> >> > grep spammer1.net /mj/vhost2.org/lists/list2
> >> > grep spammer1.net /mj/vhost2.org/lists/list2-digest
> >> > ..etc, etc.
> >> > 
> >> > ..but, doing that for each list takes a lot of time and some type
> >> > of script would sure speed up things, like this command that runs
> >> > a script to check the above 3 mail lists all at once:
> >> > root@myserver>> check_all_lists <spammer1.net>
> >> > output =	goodguy1@spammer1.net
> >> > 		goodguy2@spammer1.net
> >> > 		goodguy3@spammer1.net
> >> 
> >>     grep -Fl spammer1.net /mj/*/lists/*
> >
> >    hm. if you had enough (like 3000) vhosts you could exceed your
> >    shell's (or is it kernel? anyone?) command line argument count
> >    limit. if that's the case, you could (not tested):
> >
> >    #!/bin/sh
> >
> >    for d in /mj/*; do
> >        grep -Flr spammer1.net $d/lists
> >    done
> >
> 
> Thanks for the quick response. Maybe I wasn't clear enough but that
> gives me a list of the "lists" that contans "spammer1.net" but not a
> list of the email address within those lists.
> My example of output needed:
> output =	goodguy1@spammer1.net
> 		goodguy2@spammer1.net
> 		goodguy3@spammer1.net
> 
> I need to know who is affected in each list so I can set them as OK by
> email addresses, but still block the IPS's general address. Not sure
> I'm being clear yet....

    #!/bin/sh

    for d in /mj/*; do
        grep -Flhr spammer1.net $d/lists
    done

    but this is all in the man page. have you seen it at all?

-- 
FreeBSD 4.6-STABLE
6:31PM up 3 days, 2:07, 9 users, load averages: 0.02, 0.03, 0.00

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020802164606.GJ52563>