On 13 May 1999 06:11:52 -0000, D. J. Bernstein wrote:
>If the information changes, there should be a new confirmation message.
It may have been read with a different MUA/computer.
>list. Trying to cram the same information into the header of every
>mesasge is counterproductive.
Your solution has the advantage of making it easy to include the
subscription address. A simple patch to qmail makes it possible to do
that within rfc2369. QMTP/QMQP are no problem since it will be done by
the final "exploder".
Your solution has the disadvantage of requiring considerable
intelligence at the MUA level, a standardized format for confirmation
messages, list-id, and new routines at the MLM level; i.e., the
likelihood of general support at either end is low.
rfc2369 doesn't fix all problems, but all problems can be solved within
rfc2369 using qmail [much harder with other MTA]. It's easy to support
at both ends and it is an RFC.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
