Someone recently advised against sending MIME to the news.answers addresses.
Let me add an exclamation point to that -- after many frustrating experiences
of shipping files around to various places where I could read the MIME stuff
easily, and finding it was mostly ms-tnef attachments with no serious content,
I now habitually junkmail all incoming MIME. Previous more kindly moderators
would leave it around hoping to find time to decode it, but I decided it was
too much work for too little value.
------------------------------------------------------------------------
On the *.answers queue, I've caught up with faq-maintainers-announce mailing
list subscribes and unsubscribes (those identifiable by their subject lines)
up to last Friday, and faq checker submissions, with a couple of small
exceptions, to the same date. I'll start handling the non-faq-checker inputs
(sadly, the bulk of the queue) next session.
The auto-responder appears still to be shut off; later today or tomorrow I'll
ask the MIT staff (again) to turn it on, and will submit new-account requests
for the 3-4 people who volunteered to start learning how to help out. Because
of last month's HipCrime attack, we no longer autorespond to cancel messages,
and in fact junkmail them - it's nearly useless to cancel a FAQ posting,
since by the time we see your note, the message has probably propagated widely
and also expired (at sites with expire after 3 days, a common limit).
Creating a secure rapid-response cancel mechanism is very, very, low on the
priority list.
- David Alex Lamb, one of the *.answers moderators
news-answers-request@mit.edu
This archive was generated by hypermail 2b29 : Sat Aug 05 2000 - 12:25:31 CDT