[plug] unsubscibe ATTN: LIST OWNER

bp plug at broometime.com
Mon Mar 26 09:54:59 WST 2001


woops I meant 75 characters

-----Original Message-----
From: bp [mailto:plug at broometime.com]
Sent: Monday, 26 March 2001 9:53 AM
To: plug at plug.linux.org.au
Subject: RE: [plug] unsubscibe ATTN: LIST OWNER


simon

All your emails come through with the line wrapping all messed up - does
anybody else notice this.  I set my outgoing email line wrapping to 75
lines I think.

Is this just my problem or what ?

bp

-----Original Message-----
From: Simon Scott [mailto:simon.scott at flexiplan.com]
Sent: Monday, 26 March 2001 9:53 AM
To: plug at plug.linux.org.au
Subject: Re: [plug] unsubscibe ATTN: LIST OWNER


	How about subscribing them instantly? Stay with me, that way you
could send the old test

		1. Read all points below before doing anything.
		2. Send an email to plug-request with the subject
'subscribe'. Any decent email client blah blah
		......
		10. Do none of the points above. You are already subscribed
and any action on your behalf will result in a permanent ban.....

	If anyone responds to the email, add unsubscribe them and add them
to the 'stupid' list :)




	From:	Christian <christian at amnet.net.au> on 26-03-2001 09:49 AM
	Please respond to plug at plug.linux.org.au@SMTP at Exchange
	To:	plug at plug.linux.org.au@SMTP at Exchange
	cc:

	Subject:	Re: [plug] unsubscibe ATTN: LIST OWNER

	On Sun, Mar 25, 2001 at 03:49:22PM +0800, The Thought Assassin
wrote:

	> How were you planning on filtering people who can't even spell
	> "unsubscribe", Bernard? :)
	>
	> > or simply attach the line: "To unsubscribe <do this>"
	> > as a footer to every message? 100 bytes x what 300 users?... 30
kb.
	> > Think of the bandwidth it'd save in the bitching going on.
	>
	> It's not per user, it's per post. Even if it prevented the
problem, it
	> would waste more bandwidth than it saves. In reality, it doesn't
even
	> solve the problem. I speak from experience of other lists that do
this,
	> and I'm sure others here will be nodding their heads. If people
aren't
	> going to read what you send them, it doesn't matter how or how
often you
	> send it. *sigh*. I don't think this problem has an easy solution,
short of
	> not letting people who won't read doco onto the list in the first
place,
	> and that kind of defeats one of the major purposes of the list.
(teaching
	> people how and where to look for appropriate doco, and how to use
it)

	Spot on.  My proposal is that, in order to join the list, the person
has
	to:
	  1. Send an email to a certain address with the "subscribe"
request.
	     The email will be rejected with an appropriate (rude?) message
if they
	     send HTML.
	  2. Read the instructions in the response they get to learn how to
	     complete the subscription process.  In particular it tells them
how to
	     unsubscribe and makes it really clear that if they stuff it up
then they
	     won't be all that popular.  The instructions to complete
subscription
	     must require that the person read all of the email (an exercise
left to
	     the readership) and not be too hard while still requiring
actual
	     *thought*.
	  3. The subscription completion process also represents an
agreement to
	     endeavour to abide by some informal code of conduct for the
list which I
	     think is already established.

	It won't necessarily solve the problem but it will hopefully help.

	All emails accusing me of attempting to create a police state to
	/dev/null please.

	--
	DSA 0x0EC1D28C: BBCB 0D79 4EBB 078A A066  7267 8BED E9D6 0EC1 D28C



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************





More information about the plug mailing list