[<--] Indice [-->]

From marc0 <marc0@autistici.org>
Date Thu, 16 Oct 2003 01:26:01 +0200
Subject Re: [hackmeeting] gnupg help....please 

You on Wed, 15 Oct 2003 17:34:29 +0000 (UTC) writes:

> On Wed, 15 Oct 2003 13:12:54 +0200, <alieno74@libero.it> wrote:
>
>> Sto configurando gnupg per l'utilizzo con mutt, ma ho qualche problemino.
>>
>> ###########################################################################=
>> set pgp_encrypt_only_command=3D"gpg --batch --quiet --no-verbose --output -=
>
> non so se quel "3D" e' un problema di copia e incolla ma di sicuro non
> ci deve stare li. 

tempo fa' mi sono scontrato per caso coi "3D":

RFC 1341: MIME

[...]
            5.1  Quoted-Printable Content-Transfer-Encoding

            The Quoted-Printable encoding is intended to represent  data
            that largely consists of octets that correspond to printable
            characters in the ASCII character set.  It encodes the  data
            in  such  a way that the resulting octets are unlikely to be
            modified by mail transport.  If the data being  encoded  are
            mostly  ASCII  text,  the  encoded  form of the data remains
            largely recognizable by humans.  A body  which  is  entirely
            ASCII  may also be encoded in Quoted-Printable to ensure the
            integrity of the data should  the  message  pass  through  a
            character-translating, and/or line-wrapping gateway.

            In this encoding, octets are to be represented as determined
            by the following rules:

                 Rule #1:  (General  8-bit  representation)  Any  octet,
                 except  those  indicating a line break according to the
                 newline convention of the canonical form  of  the  data
                 being encoded, may be represented by an "=" followed by
                 a two digit hexadecimal representation of  the  octet's
                 value. The digits of the hexadecimal alphabet, for this
                 purpose, are "0123456789ABCDEF". Uppercase letters must
                 be
                 used when sending hexadecimal  data,  though  a  robust
                 implementation   may   choose  to  recognize  lowercase
                 letters on receipt. Thus, for  example,  the  value  12
                 (ASCII  form feed) can be represented by "=0C", and the
                 value 61 (ASCII  EQUAL  SIGN)  can  be  represented  by
                 "=3D".   Except  when  the  following  rules  allow  an
                 alternative encoding, this rule is mandatory.
[...]

-- 
marc0@autistici.org - 0x4E8899C2
_______________________________________________
hackmeeting mailing list
hackmeeting@kyuzz.org
http://lists.kyuzz.org/mailman/listinfo/hackmeeting
[<--] Indice [-->]