[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gnus issues
From: |
Dave Love |
Subject: |
Re: Gnus issues |
Date: |
Wed, 29 Sep 2004 18:08:43 +0100 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux) |
Reiner Steib <address@hidden> writes:
> Sorry, I didn't read carefully enough.
I sympathize :-/.
> When I added `mml-minibuffer-read-disposition', I wasn't sure if there
> are other valid values. I don't know if the `extension-token'
> mentioned in rfc2183.txt might be relevant for Gnus.
Ah, good point. I didn't realize there were other possible values.
IANA has:
Mail Content Disposition Values
Name Description Reference
----- ------------ ---------
inline displayed automatically [RFC2183]
attachment user controlled display [RFC2183]
form-data process as form response [RFC2388]
signal tunneled content to be processed silently [RFC3204]
alert the body is a custom ring tone to alert the [RFC3261]
user
icon the body is displayed as an icon to the user [RFC3261]
render the body should be displayed to the user [RFC3261]
session the body describes a communications session, [RFC3261]
for example, an RFC2327 SDP body
signed-receipt-protocol requested signature format for signed [RFC3335]
receipt
signed-receipt-micalg requested signature algorithm for signed [RFC3335]
receipt
aib Authenticated Identity Body
[RFC-draft-ietf-sip-authid-body-03.txt]
I haven't checked what they all are. Perhaps it's best just to allow
inline and attachment; people can edit the inserted tag if they know
what they're doing.
Re: Gnus issues, Reiner Steib, 2004/09/29