Esempi messaggi Usenet

Esempio di messaggio in cui compaiono i boundary (MIME multipart):

From: Nathaniel Borenstein
To: Ned Freed
Subject: Sample message
MIME-Version: 1.0
Content-type: multipart/mixed; boundary=”simple
boundary”
This is the preamble. It is to be ignored, though it
is a handy place for mail composers to include an
explanatory note to non-MIME conformant readers.
–simple boundary
This is implicitly typed plain ASCII text.
It does NOT end with a linebreak.
–simple boundary
Content-type: text/plain; charset=us-ascii
This is explicitly typed plain ASCII text.
It DOES end with a linebreak.
–simple boundary–
This is the epilogue. It is also to be ignored.

Esempio di messaggio MIME multipart/alternative:

From: Nathaniel Borenstein
To: Ned Freed
Subject: Formatted text mail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=boundary42
–boundary42
Content-Type: text/plain; charset=us-ascii
…plain text version of message goes here….
–boundary42
Content-Type: text/richtext
…. RFC 1341 richtext version of same message goes here …
–boundary42
Content-Type: text/x-whatever
…. fanciest formatted version of same message goes here

–boundary42–

Esempio di messaggio MIME multipart/digest:

From: Moderator-Address
To: Recipient-List
MIME-Version: 1.0
Subject: Internet Digest, volume 42
Content-Type: multipart/digest;
boundary=”—- next message —-”
—— next message —-
From: someone-else
Subject: my opinion
…body goes here …
—— next message —-
From: someone-else-again
Subject: my different opinion
… another body goes here…
—— next message ——

Esempio di messaggio MIME message/partial:

For example, if an audio message is broken into two parts, the first part might look something like this:
X-Weird-Header-1: Foo
From: Bill@host.com
To: joe@otherhost.com
Subject: Audio mail
Message-ID:
MIME-Version: 1.0
Content-type: message/partial;
id=”ABC@host.com”;
number=1; total=2
X-Weird-Header-1: Bar
X-Weird-Header-2: Hello
Message-ID:
MIME-Version: 1.0
Content-type: audio/basic
Content-transfer-encoding: base64
… first half of encoded audio data goes here…
and the second half might look something like this:
From: Bill@host.com
To: joe@otherhost.com
Subject: Audio mail
MIME-Version: 1.0
Message-ID:
Content-type: message/partial;
id=”ABC@host.com”; number=2; total=2
… second half of encoded audio data goes here…
Then, when the fragmented message is reassembled, the resulting
message to be displayed to the user should look something like this:
X-Weird-Header-1: Foo
From: Bill@host.com
To: joe@otherhost.com
Subject: Audio mail
Message-ID:
MIME-Version: 1.0
Content-type: audio/basic
Content-transfer-encoding: base64
… first half of encoded audio data goes here…
… second half of encoded audio data goes here…

Esempio di messaggio MIME message/external-body:

From: Whomever
To: Someone
Subject: whatever
MIME-Version: 1.0
Message-ID:
Content-Type: multipart/alternative; boundary=42
Content-ID:
–42
Content-Type: message/external-body;
name=”BodyFormats.ps”;
site=”thumper.bellcore.com”;
access-type=ANON-FTP;
directory=”pub”;
mode=”image”;
expiration=”Fri, 14 Jun 1991 19:13:14 -0400 (EDT)”
Content-type: application/postscript
Content-ID:
–42
Content-Type: message/external-body;
name=”/u/nsb/writing/rfcs/RFC-MIME.ps”;
site=”thumper.bellcore.com”;
access-type=AFS
expiration=”Fri, 14 Jun 1991 19:13:14 -0400 (EDT)”
Content-type: application/postscript
Content-ID:
–42
Content-Type: message/external-body;
access-type=mail-server
server=”listserv@bogus.bitnet”;
expiration=”Fri, 14 Jun 1991 19:13:14 -0400 (EDT)”
Content-type: application/postscript
Content-ID:
get RFC-MIME.DOC
–42–

Esempio di messaggio MIME-PEM:

—–BEGIN PRIVACY-ENHANCED MESSAGE—–
Proc-Type: 4,ENCRYPTED
Content-Domain: RFC822
DEK-Info: DES-CBC,F8143EDE5960C597
Originator-ID-Symmetric: linn@zendia.enet.dec.com,,
Recipient-ID-Symmetric: linn@zendia.enet.dec.com,ptf-kmc,3
Key-Info: DES-ECB,RSA-MD2,9FD3AAD2F2691B9A,
B70665BB9BF7CBCDA60195DB94F727D3
Recipient-ID-Symmetric: pem-dev@tis.com,ptf-kmc,4
Key-Info: DES-ECB,RSA-MD2,161A3F75DC82EF26,
E2EF532C65CBCFF79F83A2658132DB47
cMlK1Z6720dcBWGGsDLpTpSCnpotdXd/H5LMDWnonNvPCwQUHt==
—–END PRIVACY-ENHANCED MESSAGE—–

Esempio di messaggio criptato PGP:

From: Michael Elkins
To: Michael Elkins
Mime-Version: 1.0
Content-Type: multipart/encrypted; boundary=foo;
protocol=”application/pgp-encrypted”
–foo
Content-Type: application/pgp-encrypted
Version: 1
–foo
Content-Type: application/octet-stream
—–BEGIN PGP MESSAGE—–
Version: 2.6.2
X4uT1tNCWEIIBoqqvCeIMpp7UQ2IzBrXg6GtukS8NxbukLeamqVW31yt21DYOjuLzcMNe/JNsD9vDVCvOOG3OCi8=
=zzaA
—–END PGP MESSAGE—–
–foo–

Esempio di messaggio firmato PGP

From: Michael Elkins
To: Michael Elkins
Mime-Version: 1.0
Content-Type: multipart/signed; boundary=bar; micalg=pgp-md5;
protocol=”application/pgp-signature”
–bar
& Content-Type: text/plain; charset=iso-8859-1
& Content-Transfer-Encoding: quoted-printable
&
& =A1Hola!
&
& Did you know that talking to yourself is a sign of senility?
&
& It’s generally a good idea to encode lines that begin with
& From=20because some mail transport agents will insert a greater-
& than (>) sign, thus invalidating the signature.
&
& Also, in some cases it might be desirable to encode any =20
&railing whitespace that occurs on lines in order to ensure =20
& that the message signature is not invalidated when passing =20
& a gateway that modifies such whitespace (like BITNET). =20
&
& me
–bar
Content-Type: application/pgp-signature
—–BEGIN PGP MESSAGE—–
Version: 2.6.2
08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9BrnHOxEa44b+EI=
=ndaj
—–END PGP MESSAGE—–
–bar—

Esempio di messaggio firmato e poi criptato PGP

Content-Type: multipart/encrypted;
protocol=”application/pgp-encrypted”; boundary=foo
–foo
Content-Type: application/pgp-encrypted
Version: 1
–foo
Content-Type: application/octet-stream
—–BEGIN PGP MESSAGE—–
& Content-Type: multipart/signed; micalg=pgp-md5
& protocol=”application/pgp-signature”; boundary=bar
&
& –bar
& Content-Type: text/plain; charset=us-ascii
&
& This message was first signed, and then encrypted.
&
& –bar
& Content-Type: application/pgp-signature
&
& —–BEGIN PGP MESSAGE—–
& Version: 2.6.2
&
& iQCVAwUBMJrRF2N9oWBghPDJAQE9UQQAtl7LuRVndBjrk4EqYBIb3h5QXIX/LC//
& jJV5bNvkZIGPIcEmI5iFd9boEgvpirHtIREEqLQRkYNoBActFBZmh9GC3C041WGq
& uMbrbxc+nIs1TIKlA08rVi9ig/2Yh7LFrK5Ein57U/W72vgSxLhe/zhdfolT9Brn
& HOxEa44b+EI=
& =ndaj
& —–END PGP MESSAGE—–
&
& –bar–
—–END PGP MESSAGE—–

Annunci

Rispondi

Inserisci i tuoi dati qui sotto o clicca su un'icona per effettuare l'accesso:

Logo WordPress.com

Stai commentando usando il tuo account WordPress.com. Chiudi sessione / Modifica )

Foto Twitter

Stai commentando usando il tuo account Twitter. Chiudi sessione / Modifica )

Foto di Facebook

Stai commentando usando il tuo account Facebook. Chiudi sessione / Modifica )

Google+ photo

Stai commentando usando il tuo account Google+. Chiudi sessione / Modifica )

Connessione a %s...