OT: Messages to the list with attachments (was Re: body of emails in an attachment...)

[Fairlight]

With neither thought nor caution, Kenneth Brody blurted:
> When sent directly to me, it comes like this:

Precisely what I see.

> When sent through the list, a different e-mail came through like this.
> (I haven't yet received the e-mail you cc'ed to me through the list.)
> 
> The header now has right after the "List-*" headers:
> 
> > Content-Type: multipart/mixed; boundary="===============1762750408=="

That makes sense with what it's doing.

Basically, I've noticed in the past that it would sometimes attach the
signature directly as text inline, and other times append it to the end as
an attachment.  The deciding criterion appears to be whether or not the
message is MIME encoded with multiple parts. 

> Notice how the e-mail is now "multipart/mixed", and within those
> multiparts, the first is your entire e-mail, attachments and all,
> and the second is the footer added by mailman.

All of which makes sense, and is how I'm seeing it as well.  Well, we know
the cause, at least.  And I've already set it so that I don't sign in this
folder automatically (as well as two other folders for alternate email
addresses, which makes sense).  

I guess the point is that I'd like to be able to sign -all- my email that
comes from me.  However, I doubt Bill will reverse policy based on -one-
person using PGP, so I'll likely just live with the current configuration I
deployed that makes my mail bearable (in the context of not making the body
an attachment...not in the context of nearly everyone liking what I say
*grin*) here, while letting me sign privately elsewhere.  I don't
necessarily like it, as I prefer to have things uniform, but I can live
with it.

About the only reason it happened -now- was that I finally took a break and
read up on and implemented GPG after using PGP 2.6.2 for years--but not
using it much for email because later versions weren't really all that
compatible with 2.6.2, although GPG can be.  If I'd switched, say, six
months or two years ago, we'd have seen this right when the switch to
Mailman occurred.

Well, my apologies to everyone, again.  And thanks to Brian and Ken for
pointing it out to me so I could alleviate the problem.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html