Fred Lindberg writes:
> On 19 Jan 1999 20:11:56 -0000, Russell Nelson wrote:
>
> >Okay, VERP has solved the bounce problem. Now we need VERB (Variable
> >Envelope Recipient in Body) to solve the unsubscribe problem.
> >Basically, we need qmail-remote to merge the envelope recipient into
> >the message somewhere. The problem, of course, is *where* to insert
>
> I think the substitution idea is good, but putting it into the message
> is Not Good (TM). qmail should not under any circumstances corrupt the
> message, which might contain any character sequence.
Right, that's the conundrum. It has to be in the body to be useful,
yet it cannot be in the body. Maybe a magical header which means
"When you see X, substitute the envelope recipient"? Like this:
VERB-Substitute: 4jiu%8@#l
No header, no body munging.
> Putting it into the header circumvents that problem. Also, the amount
> of text that has to be parsed is limited this way. Yes, there are
> disadvantages (stupid subscribers), but that's less important than
> message integrity.
It's more a matter of ignorant than stupid (ignorant returns a 4XX
error; stupid is a 5XX error :). No matter; the cost of correcting
the ignorance means that the list gets extraneous messages. It is
this problem I expect VERB to fix.
> For subscribers, you could to a message trailer add "see
> List-Unsubscribe: header for info on how to unsubscribe". As Sen Nagata
> pointed out on the ezmlm list, rfc2069 may not be such a bad idea, and
> good MUAs will rapidly support it once it's used more. ezmlm would
> support this "out of the box".
Is rfc2069 in effect now? Is it an Internet Standards track RFC? Or
just an Informational RFC like my RFCs?
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
