[Mailman-Developers] Future of pipermail?

[Nigel Metheringham]

Continuing the thoughts on integration or separation of archiver 
functions... heres a flow of my ideal wrt to archiving and MIME 
processing of list messages:-

  - Message received by mailman

  - Policy decisions applied to message (ie accept, bounce, moderate)
    depending on things such as sender/recipient/list policy/MIME
    etc

  - Message archived.  MIME attachments/portions split into separate
    retrievable sections.  The archived MIME sections become available
    to latter processes as retrieval URLs.  Overall Message ref also
    available to all subsequent processes (ie as additional header
    with this message archive URL)

  - Send out process set.  This would allow, for example:-
      - some recipients to receive original MIME encoded message
      - some recipients to receive simplified message with limited
        MIME (maybe just text/plain) plus URLs
      - some receive text/plain version as a digest

The send out messages would depend on a combination of list and 
personal policy - ie some people could be on a MIME accepting list, but 
prefer simplified mail.  Or the list could mandate no transmitted MIME. 
  The original policy set could also just block MIME or large MIME.

However this is just one way things could work... I just get this 
feeling that archiving and MIME stripping can be closely related...

	Nigel.
-- 
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham                  Nigel.Metheringham@VData.co.uk ]
[ Phone: +44 1423 850000                         Fax +44 1423 858866 ]