🚀 go-pugleaf

In article <SCOTT.92Apr11141729@nic.gac.edu> scott@nic.gac.edu (Scott Hess) writes:
>In article <1992Apr11.033606.20581@usenet.ins.cwru.edu> mcn@cwru.edu (Michael C. Neuman) writes:
>Later:
>>What's wrong, Sef? Don't like having your mail bounced? If you
>>'have the right' to bounce everyone else's mail, I have the right to
>>bounce yours, even if does create an infinite mail loop--the
>>bandwidth used is your own creation, not mine.
>
>I assure you that you aren't going to be "getting to" Sean Fagan.
>Many people have already tried and failed utterly.

  I'm not trying to 'get to' Sean... I told him straight out that I'm bouncing
all of his mail,and  if he insists on sending me a copy of my RTF,he can eat his
message as many times as it takes for him to take me off of his bounce list...
I told him this IN ADVANCE of him bouncing my RTF message to me...

>And the bandwidth used is just as much your creation as it is his.  It
>takes two people to make a flamewar.

  I'm not starting a flamewar... I mearly don't want to get my post back. And
if he's going to bounce my mail back, I'll bounce his back...

>And (last point, I promise) Sean at least has a reason to do the
>bounces, and I can assure you that he can find a number of backup
>arguments.  You state right out that you want to do it just to piss
>Sean off.  Now _there's_ a reason to abuse resources that other people
>are paying for you to use.

  Bull, if he really "had a reason", all he'd do is send the message to
/dev/null, not send it back... I have a reason too. I don't want to get the
message, "Your email has automagically bounced" and I don't want to see a copy
of my post with his holier than thou, "*sigh*" at the end of it. So I'll
bounce it back. If I wanted to be nice, I would have sent it to /dev/null,but 
I'm just doing the same thing he's doing. I also have a T3, what does he have,
a 56Kbps line max? I have much more bandwidth to burn.

  I also have a question here, maybe he could answer... Does he ever expect
to sell any software to the NeXT community? Unless it's the next best thing
to sliced bread, NO ONE is going to buy it, unless you're one of those people
who thinks immaturity is a sign of a reliable company.

  In the last 45 minutes, I've bounced 125 messages from him. The size of the
message that's going back and forth is currently 32k. I'm going to stop
bouncing his stuff right now, because the internet is designed for more
useful things than net.cops sending back peoples' messages.

By the way, if y'all want to bounce sef's mail (or anyone elses for that
matter), use the following script... Call it 'mailfilter'...

-----------Cut here-----------
#!/bin/sh
cat >/tmp/msg.$$
if grep "From: sef@kithrup.com" /tmp/msg.$$ >/dev/null 2>/dev/null
#
then
  mail -s "Your mail has been bounced too" sef@kithrup.com </tmp/msg.$$
else
  cat /tmp/msg.$$ >>/usr/spool/mail/username
#                                   ^^^^ Put your username here.
fi
rm -f /tmp/msg.$$

------------Cut here-----------
 The put into your .forward
"|/path_to_mailfilter_script/mailfilter"

(Include the quote marks and make the script called 'mailfilter' executable)

------

 This should put an end to the RTF bouncings... Just install this
mailfilter, and you'll never have to hear from sef again! If you want to
be kind, just replace the 'mail -s' line with a ':'...

  Flame away if you want, I'm not telling anyone to bounce anything, I'm just
telling everyone how to do the exact same thing Sef is doing.

-Mike Neuman
mcn@b62103.student.cwru.edu

-- 
Mike Neuman                mcn@b62103.student.cwru.edu
			   NeXTmail accepted!!!
"To make a machine that will be proud of us." - Thinking Machine's motto