On Tue, Jul 22, 2003 at 01:31:03AM -0700, Andi Payn wrote: > On Tuesday 22 July 2003 00:30, Dave Cotton wrote: > > Does this mean MIME-defang works? > > Apparently. > > But is it possible to configure it to move all that text except the first > sentence to the end of the message? It's a bit annoying to have to scroll > through 40-odd lines of wordy warnings to get to the 10-line message. > > Also, what exactly did MIME-defang do in this case? As a guess, it seems to > have converted text/plain attachments with useful names into > application/octet-stream attachments with meaningless names, apparently > without changing the content at all. Which means that you have to skim the > warnings to figure out which file is which--and, at least for kmail users, > that they open in kwrite instead of in your default text editor (or inline, > or in the built-in text viewer). What is this protecting us from? > > Finally, it's a bit strange to say, "... if you were not expecting a file of > this type..." and never mention what type the file originally was. Couldn't > MIME-defang say, "An attachment named 'foo' of type 'mime/type' was > converted..."?
Yup that's what it did. The .init file tripped the match for .ini, I'll lfix that match so it's more specific. As far as the wordy warning, that's my configuration not anyone elses and I think it's desireable to make the message obvious and at the beginning so users will see it... Incidentally, I've been running this for about 2 years and this is the first message that I've ever had that I sent that accidentally tripped it on the outbound. -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org "What upsets me is not that you lied to me, but that from now on I can no longer believe you." -- Nietzsche
