OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Nick Simicich (njs+mandrakescifi.squawk.com)
Date: Tue Apr 10 2001 - 10:07:31 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    At 10:10 PM 4/9/2001 -0600, Vincent Danen wrote:
    >
    >So either you find me a nice email client as powerful as mutt that
    >doesn't automatically create multipart/mime messages, find a way to
    >fix it in mutt, or send it through your demime program, (or ignore all
    >my messages I suppose), we're kinda stuck. Writing my messages in a
    >text editor to clearsign manually and then import into mutt is too
    >much of a PITA to be an option.

    I'd never used mutt before, so I read the man page and then cranked it up.
    All I can say is that there are people with all sorts of tastes. It was a
    lot like sticking myself with pins while I read my mail only real fast so
    it hurt more. I suppose I could get used to it in time. I have used pine
    as my Unix e-mail client for many years.

    At first I thought that

    Set pgp_create_traditional=yes

    in your .muttrc would do it. However, mutt is badly broken in that it does
    not do the "traditional" thing of putting the signed secion into a single
    text/plain section. Instead it tags it as follows:

    Mime-Version: 1.0
    Content-Type: application/pgp; x-action=sign; format=text
    Content-Disposition: inline; filename="msg.pgp"
    User-Agent: Mutt/1.2.5i

    Which makes any mailer that does not grok application/pgp assume that the
    whole message is simply an unviewable attachment. Hardly "traditional" PGP
    at all, and just more incompatible mime crap. And it would bounce off of
    demime.

    When pgp first came out, it produced a plain text section that looked
    exactly like the section that mutt now claims is an application/pgp. I say
    that this is broken because the section is designed to be human readable,
    not read by an application, and is to be used for the express purpose of
    communicating with people with old mailers.

    This is my basic objection to mime: I'm sure that if one mutt user mailed
    another mutt user, that mutt user would know exactly what to do with this
    labeling of the main section. But there are simply too many e-mail clients
    all of which are doing their own incompatible things and calling it mime
    (and it is all legal mime, of course, it just does not interoperate) to
    make this sort of thing reasonable.

    Nope, it looks like, unless I want people's pgp signatures littering my
    attachment directory like little turds, I'm going to have to demime them.
    OK, done.

    >However, I have been looking for a nice gui email client that supports
    >gpg... trying to get pronto installed was a nightmare (who the heck
    >writes a mail client in perl?!?), and last I checked balsa didn't
    >support it. And Evolution is too unstable to be used at all.

    It couldn't possibly be worse than mutt. It threw me into vi when I told
    it I wanted to compose my message body and then it required me to take a
    special action to make the disposition of the single text section inline.
    Then again, you probably get so much mail that you really don't want a gui
    mail client.