xsprite:
ok, I didn't see uuencoding some content as attaching it
Problem between keyboard and chair?
(attaching usually refers to mime these days..).
Does it? Why did no-one tell me?
Pasting some config files are still attachments by this definition though.
No, it doesn't, although if they are long, it would be best not to post them, IMO.
Something in the faq/mailing list welcome/reminder, like this might help clear things up: "You should avoid attaching files of any kind, this includes MIME/Base64/uuencoded files. It is quite acceptable to post a short extract from any relevant configuration file or command output. For long contents and additional files, place them on an ftp or http site and post the url. Signatures should not exceed 4 lines. Avoid webmail systems that automagically attach advertising signatures."
Do we really need to add that, or are you just not reading what is already there? The bit about no attachments is already all over the place. The bit about sigs should be common sense and is already in the FAQ. The bit about webmail ads is probably worth adding.
How nannyish do we need to be? My only objective in restricting what can be sent to the list is to minimise complaints. HTML email and attachments generate lots of complaints and errors, so they are not allowed. Pasting relevant config file snips haven't caused significant complaints yet.
I've just had another complaint which indicates you may have killed all our OE-using members... OK, we can probably agree on how crap that email client is, but killing them before we convert them isn't helpful at all. :-( (Did any OE users get that message OK... and why are you using OE?!?)
well, the list isn't just accessible by ~150 people. Posts to the list outlast subscriptions, and yes, I've got this "but what if in $timeperiod someone has the same problem, and we already have a good archive of answers" in my head lots. Information (including addition files) need to be easily accessible to them. I have suffered too much from dead links in archives in the past.
If there's a MIME or UUencode splurge in the mail archives, it's not a hell of a lot of help to most people who may want that file, while the increased list traffic is an obstruction to today's users and people who download the mbox archive files.
[figures]
oh well.. guilty as charged. But maybe over time I shall be redeemed since the saving by sending via http can only decrease (or stay still) with time. :)
Only as long as people actually want that file ;-)