Subject: | |
From: | |
Reply To: | |
Date: | Wed, 10 May 2000 08:31:04 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Attachments make a mess in digest format. I vote for #1. The collective wisdom
of how to turn off attachments in various clients can be collected and sent to
new subscribers or periodically.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-3737
Jeff Kell <[log in to unmask]> on 05/09/2000 07:07:04 PM
Please respond to [log in to unmask]
To: [log in to unmask]
cc: (bcc: Leonard Berkowitz/CORP/HPHC)
Subject: [HP3000-L] Admistrivia: Good news, bad news
Bad news: Raven crashed miserably Saturday, and we had to reload NT,
restore files from backup, etc. Archives of mail received from
4-10am Saturday (hopefully not much) are in the bit bucket. We had
to reload Apache, Listserv, LSMTP, and other things.
Good news: We installed the Listserv 2000a "service pack", so to
speak. This provides an interesting feature where Listserv can take
action on attachments.
Currently the only attachment handling Listserv does is for those
mailers that sent multipart/alternative attachments in text and HTML
format (for example). This behavior will remain unchanged, and the
HTML piece will silently be deleted. In-line HTML only will also be
passed unchanged. But we have the following new options, and I am
soliciting opinions (please reply privately):
*1 No attachments: Any mail containing attachments will be bounced
back to the sender with an error message.
*2 Filter attachments: Any mail containing attachments will have the
attachments silently removed and only the text (or leading HTML)
are passed to the list.
*3 Selective attachments: Certain MIME type attachments can be passed
through while removing others.
My current thoughts are for option 2, possibly making some exceptions
later with option 3. The first is very restrictive, and made more
difficult by some mailers which make turning off attachments tricky.
Jeff Kell <[log in to unmask]>
|
|
|