 
|
| Sender: |
|
| Date: |
Sat, 8 Oct 2005 14:21:46 -0500 |
| Reply-To: |
|
| Content-Transfer-Encoding: |
7bit |
| Subject: |
|
| From: |
|
| Content-Type: |
text/plain; charset=ISO-8859-1; format=flowed |
| In-Reply-To: |
<4347D9BA.11654.1AC7282A@localhost> |
| Organization: |
University of Notre Dame |
| MIME-Version: |
1.0 |
On 10/8/2005 13:37, Paul Karagianis wrote:
>
> So, uh, it looks like a probable bug in a zombie network... they intended
> to hit a bunch of different targets but seem to have gotten themselves
> stuck on you?
>
We had a rash of these within the last two weeks, and they were directed at
several lists. Most had owner-$listname forged as the sender address, but
some had owner-listserv forged as the sender address. I am the LISTSERV
postmaster, so I added [log in to unmask] to the site-wide
filter list in go.user, and added the following statement to each of the
list header templates in the LIST-LIBRARY template.
* Filter= Also,owner-&+LISTNAME;@listserv.nd.edu
--
Paul Russell
Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
|
|
|
