Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Automating Unsubscription (was unsubscribe ding)
Date: 20 Jan 1996 08:57:47 +0100	[thread overview]
Message-ID: <w8s3f9bpabo.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: steve@miranova.com's message of 16 Dec 1995 13:50:00 -0800

steve@miranova.com (Steven L. Baur) writes:

> I almost forgot.  We need to add atoms to the group structure to
> contain information on unsubscription to mailing lists.  If
> unsubscription can be automated, I'm sure we could get cooperation
> from mailing list owners.  :-)
> 
> The mostly manual steps right now are:
> 1.  Initial subscription to list
>     There are already standard formats for this.  Something that
>     nearly always works is to put ``subscribe list-name address'' in
>     both the Subject: and body (suppressing .signature).
> 
>     At this point, a foreign group can be created and the
>     to-address/to-list atom can be filled in.

Yes, this would be easy enough to do...  A command (`G s' or whatever)
that prompts for the list name, the address, and the select method to
use to read the group.

> 2.  Receive confirmation of subscription back
>     These usually (should be always) contain instructions on how to
>     unsubscribe to the list.

But we don't really need that information, do we?  We know the name of
the list and the admin address, and sending "UNSUBSCRIBE list" to the
list address works on most list servers...

> 2b. Receive first message from list
>     (To have a complete set of headers)
> 
> 3.  Define the split method
>     Given a header to split on (either obtained manually from 2b, or
>     automatically in 2), the .procmailrc/nnmail-split-methods/etc. can
>     be updated with the new list.

This is the tricky part.  

Although when I look at the mail I receive, I notice that most of the
mail I get from list servers have a nice "From " envelope header:

    From ding-request  Sat Dec 16 22:49:33 1995

Perhaps we could just stick this into the split methods when we create
the group?  (Although I'm not sure where we'd put this split rule -- I
don't want to touch `nnmail-split-methods'; that variable should be
reserved the user.  Perhaps we could have an additional variable of
this type that's saved in the .newsrc.eld file?  Or we could use group
parameters, but that might be too inefficient...)

> Further Gnus processing can occur when/if a ``You are now
> unsubscribed'' message comes back, and can be triggered by an
> appropriate mail splitting hook.  If no unsubscription messages are
> received within a certain amount of time, the unsubscribe message
> could even be resent.
> 
> Is this worth it?

No.  :-)

-- 
Home is where the cat is.


      reply	other threads:[~1996-01-20  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-16  5:52 unsubscribe ding Stephen Wray
1995-12-16 21:50 ` Automating Unsubscription (was unsubscribe ding) Steven L. Baur
1996-01-20  7:57   ` Lars Magne Ingebrigtsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=w8s3f9bpabo.fsf@surt.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).