Subject: Block sender

From: Wendy Cincotta <[email-masked]>
Date: Thu, 1 Apr 1999 13:58:31 -0500 (EST)

Is there a feature on Pine to block unwanted mail from a sender?

On Wed, 31 Mar 1999, Jessica Rasku wrote:

> On Wed, 31 Mar 1999, Scott Leibrand wrote:
> 
> > Sounds like a feature.  :)  Does disable-keymenu disable the bottom two
> > lines that tell you what to press?  I would think you wouldn't want
> > ignorant users (like most the 40,000+ Pine users here at the UW are)
> > disabling that and not knowing what to do...
> 
> 	If you really think that it is something that you don't want
> changed, you can put it in the pine.conf.fixed file, and make it not
> configurable.  I would say that it's not something worth making not
> configurable.  People who want to do it, can get quite irate when certian
> features are no longer avalable...
> 
> 							Jessica
> 
> -- 
> Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, 
> LinuxBox: (250) 362-9668.
> 
> List manager: [email-masked] 
>      send command help ---- To get help with majordomo
>                or lists ---- To get a list of all lists on server.
> 
> WWW: <http://www.geocities.com/RainForest/Andes/8749>
> 
> 
> 
>

---

From: Ken Woods <[email-masked]>
Date: Thu, 1 Apr 1999 14:11:02 -0500 (EST)

> Is there a feature on Pine to block unwanted mail from a sender?

man procmail

Date: Wed, 2 Dec 1998 11:51:26 -0500
From: Ken Woods <[email-masked]>
Newsgroups: comp.mail.pine
Subject: Re: email blocking

On Tue, 29 Dec 1998, naftali wrote:
> I am using pine regularly, and so I want a script for filtering out users
> incorporated with pine and not external.
> Basically it should work like that :
> I compile a list of domains and users I want not to be able to send email
> to me, and it either deletes them as soon as it gets the mail from them or
> doesn't let the message get through the mail port at all.
> Is there such  pine option or script?
> if so tell me how to make it or give me a copy of one.
> thanks in advance 

OK folks, here it is.

o  This is a procmail file, or recipe.
o  This is how to filter mail.
o  You put this file in your home directory.
o  This is used to filter email.
o  This file is called ".procmailrc"
o  One could use this to filter email.
o  Do not use the "'s
o  Filtering email is the art of putting things in different places for
   the ease of reading them.
o  This is from one of my machines. You cannot simply cut and past
   everything from my machine to yours and expect it to work.
o  People use things JUST LIKE THIS ONE to filter email.
o  You have to do some research on YOUR system to make this work
   correctly on YOUR system.

		The dotted line is not included in the file.
			Remove the dotted line.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PATH=$HOME/bin:/usr/bin:/usr/ucb:/bin:/opt/local/bin:.
MAILDIR=/where/you/want/your/mail/stored 
DEFAULT=/where/incoming/mail/is/stored

LOGFILE=/home/username/logfile

:0:
* ^From:[email-masked]
/home/kwoods/mail/nameoffolderwhereyouwanttheirmailtogo

:0:
* ^From:[email-masked]
/dev/null

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  Press the delete key until there are no more "-" in the line above.
		Again, remove the dotted line.

Set MAILDIR to wherever your want your mail stored.
You CAN _NOT_ use the ~username/mail syntax.  The full path MUST be
spelled out, ie, /home/kwoods/mail

Set DEFAULT to wherever the incoming mail is stored. 
most likely, /var/mail/username, or /var/spool/mail/username

The LOGFILE is a log, or record, of what procmail is doing with the mail. 
Useful for troubleshooting.  Again, spell out the full path. This file
will get VERY BIG, VERY quickly.  Remember to delete is every once in a
while. 

Now, if you've gotten this far, and you still need help, go to
http:///www.r-t-f-m.com and go fuck yourself.  
I've helped you as much as I can.

-- 
Ken Woods
[email-masked]

---

From: Chris MacLeod <[email-masked]>
Date: Thu, 1 Apr 1999 14:07:13 -0600 (CST)

Check out procmail it rocks the house for doing any sort of preprocessing
of mail if you don't have access to your mail server.

Stick

On Thu, 1 Apr 1999, Wendy Cincotta wrote:

> Date: Thu, 1 Apr 1999 13:58:31 -0500 (EST)
> From: Wendy Cincotta <[email-masked]>
> To: Pine Discussion Forum <[email-masked]>
> Subject: Block sender
> 
> 

-- 
------------------------------------------------------------------------------
[email-masked]                                     Chris MacLeod
Web Systems Administrator                                www.miscellaneous.net

                  With blue, uncertain, stumbling buzz,
                  Between the light and me,
                  And then the windows failed, and then
                  I could not see to see.

	-Emily Dickenson	"I Heard A Fly Buzz When I Died"
------------------------------------------------------------------------------
 "Beware the penguins..."  -Morphy

 GNUpgp Public key Available - finger [email-masked]

---

From: Jessica Rasku <[email-masked]>
Date: Thu, 1 Apr 1999 15:02:37 -0800 (PST)

> of mail if you don't have access to your mail server.

	And if you have access to the mail server?  Is there a reason not
to use procmail?

							Jessica

---

From: Ian Hall-Beyer <[email-masked]>
Date: Thu, 1 Apr 1999 19:38:37 -0700 (MST)

> 	And if you have access to the mail server?  Is there a reason not

Well, you can always block it at the MTA if you have access to it. :) But
you can still use procmail if you wish, we're certainly not going to stop
you. I've found that my spam went way down once I implemented RBL and some
other spam measures, added some additional anti-spam stuff in procmail,
and lastly, unsubscribed from linux-kernel :) My spam levels are now near
zero.

-Ian

---

From: Chris MacLeod <[email-masked]>
Date: Mon, 5 Apr 1999 07:58:22 -0500 (CDT)

Depends, procmail will let you do things at the user level so you or your
users can customize.  But also the best you can do is preprocess spam and
throw it away (a recipe moving it to /dev/null).  On the mailserver
(sendmail at least) you can have it send a response back to the user
saying 550 error and some message or some things like that.  There is just
a little more control at the mailserver level as far as spam goes.  Plus
if you filter it out at the MTA it never hits your machine wheras procmail
has to receive it first then do something with it.

STick

On Thu, 1 Apr 1999, Jessica Rasku wrote:

> Date: Thu, 1 Apr 1999 15:02:37 -0800 (PST)
> From: Jessica Rasku <[email-masked]>
> To: Chris MacLeod <[email-masked]>
> Cc: Pine Discussion Forum <[email-masked]>
> Subject: Re: Block sender
>

---

From: Jessica Rasku <[email-masked]>
Date: Tue, 6 Apr 1999 13:29:27 -0700 (PDT)

> has to receive it first then do something with it.

	Ah, I can see what you are saying (specifically in respect to the
bouncing an error back).  You can do that through procmail also, it's just
a little more difficult.  I just haven't seen how to setup sendmail to
block senders.  As for ``never hitting my machine'' sendmail, and procmail
are sitting on the same machine, but that's not always the case, probably
won't be the case when I expand services, whenever that is...

							Jessica

---

From: Chris MacLeod <[email-masked]>
Date: Tue, 6 Apr 1999 16:36:49 -0500 (CDT)

Well using sendmail 8.9.2+ you have an access database.

Any address or partial address listed their can be relayed, denyed or
denied with a message.  Whereas with procmail you accept the message then
funnel it to /dev/null with almost the same effect just slightly
different.

On Tue, 6 Apr 1999, Jessica Rasku wrote:

> Date: Tue, 6 Apr 1999 13:29:27 -0700 (PDT)