Commit | Line | Data |
---|---|---|
23f87bed | 1 | \input texinfo |
dd8839b0 | 2 | |
a1720df0 | 3 | @setfilename ../info/emacs-mime |
dd8839b0 DL |
4 | @settitle Emacs MIME Manual |
5 | @synindex fn cp | |
6 | @synindex vr cp | |
7 | @synindex pg cp | |
dd8839b0 | 8 | |
18f952d5 | 9 | @copying |
dd8839b0 DL |
10 | This file documents the Emacs MIME interface functionality. |
11 | ||
b65d8176 TTN |
12 | Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2004, |
13 | 2005 Free Software Foundation, Inc. | |
dd8839b0 | 14 | |
18f952d5 | 15 | @quotation |
dd8839b0 DL |
16 | Permission is granted to copy, distribute and/or modify this document |
17 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
c5c46a26 DL |
18 | any later version published by the Free Software Foundation; with no |
19 | Invariant Sections, with the Front-Cover texts being ``A GNU | |
23f87bed | 20 | Manual'', and with the Back-Cover Texts as in (a) below. A copy of the |
dd8839b0 | 21 | license is included in the section entitled ``GNU Free Documentation |
2482f038 | 22 | License'' in the Emacs manual. |
dd8839b0 DL |
23 | |
24 | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify | |
25 | this GNU Manual, like GNU software. Copies published by the Free | |
26 | Software Foundation raise funds for GNU development.'' | |
2482f038 DL |
27 | |
28 | This document is part of a collection distributed under the GNU Free | |
29 | Documentation License. If you want to distribute this document | |
30 | separately from the collection, you can do so by adding a copy of the | |
31 | license to the document, as described in section 6 of the license. | |
18f952d5 KB |
32 | @end quotation |
33 | @end copying | |
dd8839b0 | 34 | |
18f952d5 KB |
35 | @dircategory Emacs |
36 | @direntry | |
23f87bed | 37 | * Emacs MIME: (emacs-mime). Emacs MIME de/composition library. |
18f952d5 KB |
38 | @end direntry |
39 | @iftex | |
40 | @finalout | |
41 | @end iftex | |
42 | @setchapternewpage odd | |
dd8839b0 DL |
43 | |
44 | @titlepage | |
45 | @title Emacs MIME Manual | |
46 | ||
47 | @author by Lars Magne Ingebrigtsen | |
48 | @page | |
dd8839b0 | 49 | @vskip 0pt plus 1filll |
18f952d5 | 50 | @insertcopying |
dd8839b0 | 51 | @end titlepage |
dd8839b0 | 52 | |
23f87bed MB |
53 | @node Top |
54 | @top Emacs MIME | |
55 | ||
56 | This manual documents the libraries used to compose and display | |
57 | @acronym{MIME} messages. | |
58 | ||
3d80e1a2 | 59 | This manual is directed at users who want to modify the behavior of |
23f87bed MB |
60 | the @acronym{MIME} encoding/decoding process or want a more detailed |
61 | picture of how the Emacs @acronym{MIME} library works, and people who want | |
62 | to write functions and commands that manipulate @acronym{MIME} elements. | |
63 | ||
64 | @acronym{MIME} is short for @dfn{Multipurpose Internet Mail Extensions}. | |
65 | This standard is documented in a number of RFCs; mainly RFC2045 (Format | |
66 | of Internet Message Bodies), RFC2046 (Media Types), RFC2047 (Message | |
67 | Header Extensions for Non-@acronym{ASCII} Text), RFC2048 (Registration | |
68 | Procedures), RFC2049 (Conformance Criteria and Examples). It is highly | |
69 | recommended that anyone who intends writing @acronym{MIME}-compliant software | |
70 | read at least RFC2045 and RFC2047. | |
71 | ||
72 | @menu | |
73 | * Decoding and Viewing:: A framework for decoding and viewing. | |
74 | * Composing:: @acronym{MML}; a language for describing @acronym{MIME} parts. | |
75 | * Interface Functions:: An abstraction over the basic functions. | |
76 | * Basic Functions:: Utility and basic parsing functions. | |
77 | * Standards:: A summary of RFCs and working documents used. | |
78 | * Index:: Function and variable index. | |
79 | @end menu | |
80 | ||
81 | ||
82 | @node Decoding and Viewing | |
83 | @chapter Decoding and Viewing | |
84 | ||
85 | This chapter deals with decoding and viewing @acronym{MIME} messages on a | |
86 | higher level. | |
87 | ||
88 | The main idea is to first analyze a @acronym{MIME} article, and then allow | |
89 | other programs to do things based on the list of @dfn{handles} that are | |
90 | returned as a result of this analysis. | |
91 | ||
92 | @menu | |
93 | * Dissection:: Analyzing a @acronym{MIME} message. | |
94 | * Non-MIME:: Analyzing a non-@acronym{MIME} message. | |
95 | * Handles:: Handle manipulations. | |
96 | * Display:: Displaying handles. | |
97 | * Display Customization:: Variables that affect display. | |
98 | * Files and Directories:: Saving and naming attachments. | |
99 | * New Viewers:: How to write your own viewers. | |
100 | @end menu | |
101 | ||
102 | ||
103 | @node Dissection | |
104 | @section Dissection | |
105 | ||
106 | The @code{mm-dissect-buffer} is the function responsible for dissecting | |
107 | a @acronym{MIME} article. If given a multipart message, it will recursively | |
108 | descend the message, following the structure, and return a tree of | |
109 | @acronym{MIME} handles that describes the structure of the message. | |
110 | ||
111 | @node Non-MIME | |
112 | @section Non-MIME | |
113 | @vindex mm-uu-configure-list | |
114 | ||
115 | Gnus also understands some non-@acronym{MIME} attachments, such as | |
116 | postscript, uuencode, binhex, yenc, shar, forward, gnatsweb, pgp, | |
117 | diff. Each of these features can be disabled by add an item into | |
118 | @code{mm-uu-configure-list}. For example, | |
119 | ||
120 | @lisp | |
121 | (require 'mm-uu) | |
122 | (add-to-list 'mm-uu-configure-list '(pgp-signed . disabled)) | |
123 | @end lisp | |
124 | ||
125 | @table @code | |
126 | @item postscript | |
127 | @findex postscript | |
128 | Postscript file. | |
129 | ||
130 | @item uu | |
131 | @findex uu | |
132 | Uuencoded file. | |
133 | ||
134 | @item binhex | |
135 | @findex binhex | |
136 | Binhex encoded file. | |
137 | ||
138 | @item yenc | |
139 | @findex yenc | |
140 | Yenc encoded file. | |
141 | ||
142 | @item shar | |
143 | @findex shar | |
144 | Shar archive file. | |
145 | ||
146 | @item forward | |
147 | @findex forward | |
148 | Non-@acronym{MIME} forwarded message. | |
149 | ||
150 | @item gnatsweb | |
151 | @findex gnatsweb | |
152 | Gnatsweb attachment. | |
153 | ||
154 | @item pgp-signed | |
155 | @findex pgp-signed | |
156 | @acronym{PGP} signed clear text. | |
157 | ||
158 | @item pgp-encrypted | |
159 | @findex pgp-encrypted | |
160 | @acronym{PGP} encrypted clear text. | |
161 | ||
162 | @item pgp-key | |
163 | @findex pgp-key | |
164 | @acronym{PGP} public keys. | |
165 | ||
166 | @item emacs-sources | |
167 | @findex emacs-sources | |
168 | @vindex mm-uu-emacs-sources-regexp | |
169 | Emacs source code. This item works only in the groups matching | |
170 | @code{mm-uu-emacs-sources-regexp}. | |
171 | ||
172 | @item diff | |
173 | @vindex diff | |
174 | @vindex mm-uu-diff-groups-regexp | |
175 | Patches. This is intended for groups where diffs of committed files | |
176 | are automatically sent to. It only works in groups matching | |
177 | @code{mm-uu-diff-groups-regexp}. | |
178 | ||
179 | @end table | |
180 | ||
181 | @node Handles | |
182 | @section Handles | |
183 | ||
184 | A @acronym{MIME} handle is a list that fully describes a @acronym{MIME} | |
185 | component. | |
186 | ||
187 | The following macros can be used to access elements in a handle: | |
188 | ||
189 | @table @code | |
190 | @item mm-handle-buffer | |
191 | @findex mm-handle-buffer | |
192 | Return the buffer that holds the contents of the undecoded @acronym{MIME} | |
193 | part. | |
194 | ||
195 | @item mm-handle-type | |
196 | @findex mm-handle-type | |
197 | Return the parsed @code{Content-Type} of the part. | |
198 | ||
199 | @item mm-handle-encoding | |
200 | @findex mm-handle-encoding | |
201 | Return the @code{Content-Transfer-Encoding} of the part. | |
202 | ||
203 | @item mm-handle-undisplayer | |
204 | @findex mm-handle-undisplayer | |
205 | Return the object that can be used to remove the displayed part (if it | |
206 | has been displayed). | |
207 | ||
208 | @item mm-handle-set-undisplayer | |
209 | @findex mm-handle-set-undisplayer | |
210 | Set the undisplayer object. | |
211 | ||
212 | @item mm-handle-disposition | |
213 | @findex mm-handle-disposition | |
214 | Return the parsed @code{Content-Disposition} of the part. | |
215 | ||
216 | @item mm-handle-disposition | |
217 | @findex mm-handle-disposition | |
218 | Return the description of the part. | |
219 | ||
220 | @item mm-get-content-id | |
221 | Returns the handle(s) referred to by @code{Content-ID}. | |
222 | ||
223 | @end table | |
224 | ||
225 | ||
226 | @node Display | |
227 | @section Display | |
228 | ||
229 | Functions for displaying, removing and saving. | |
230 | ||
231 | @table @code | |
232 | @item mm-display-part | |
233 | @findex mm-display-part | |
234 | Display the part. | |
235 | ||
236 | @item mm-remove-part | |
237 | @findex mm-remove-part | |
238 | Remove the part (if it has been displayed). | |
239 | ||
240 | @item mm-inlinable-p | |
241 | @findex mm-inlinable-p | |
242 | Say whether a @acronym{MIME} type can be displayed inline. | |
243 | ||
244 | @item mm-automatic-display-p | |
245 | @findex mm-automatic-display-p | |
246 | Say whether a @acronym{MIME} type should be displayed automatically. | |
247 | ||
248 | @item mm-destroy-part | |
249 | @findex mm-destroy-part | |
250 | Free all resources occupied by a part. | |
251 | ||
252 | @item mm-save-part | |
253 | @findex mm-save-part | |
254 | Offer to save the part in a file. | |
255 | ||
256 | @item mm-pipe-part | |
257 | @findex mm-pipe-part | |
258 | Offer to pipe the part to some process. | |
259 | ||
260 | @item mm-interactively-view-part | |
261 | @findex mm-interactively-view-part | |
262 | Prompt for a mailcap method to use to view the part. | |
263 | ||
264 | @end table | |
265 | ||
266 | ||
267 | @node Display Customization | |
268 | @section Display Customization | |
269 | ||
270 | @table @code | |
271 | ||
272 | @item mm-inline-media-tests | |
273 | @vindex mm-inline-media-tests | |
274 | This is an alist where the key is a @acronym{MIME} type, the second element | |
275 | is a function to display the part @dfn{inline} (i.e., inside Emacs), and | |
276 | the third element is a form to be @code{eval}ed to say whether the part | |
277 | can be displayed inline. | |
278 | ||
279 | This variable specifies whether a part @emph{can} be displayed inline, | |
280 | and, if so, how to do it. It does not say whether parts are | |
281 | @emph{actually} displayed inline. | |
282 | ||
283 | @item mm-inlined-types | |
284 | @vindex mm-inlined-types | |
285 | This, on the other hand, says what types are to be displayed inline, if | |
286 | they satisfy the conditions set by the variable above. It's a list of | |
287 | @acronym{MIME} media types. | |
288 | ||
289 | @item mm-automatic-display | |
290 | @vindex mm-automatic-display | |
291 | This is a list of types that are to be displayed ``automatically'', but | |
292 | only if the above variable allows it. That is, only inlinable parts can | |
293 | be displayed automatically. | |
294 | ||
295 | @item mm-automatic-external-display | |
296 | @vindex mm-automatic-external-display | |
297 | This is a list of types that will be displayed automatically in an | |
298 | external viewer. | |
299 | ||
300 | @item mm-keep-viewer-alive-types | |
301 | @vindex mm-keep-viewer-alive-types | |
302 | This is a list of media types for which the external viewer will not | |
303 | be killed when selecting a different article. | |
304 | ||
305 | @item mm-attachment-override-types | |
306 | @vindex mm-attachment-override-types | |
307 | Some @acronym{MIME} agents create parts that have a content-disposition of | |
308 | @samp{attachment}. This variable allows overriding that disposition and | |
309 | displaying the part inline. (Note that the disposition is only | |
310 | overridden if we are able to, and want to, display the part inline.) | |
311 | ||
312 | @item mm-discouraged-alternatives | |
313 | @vindex mm-discouraged-alternatives | |
314 | List of @acronym{MIME} types that are discouraged when viewing | |
315 | @samp{multipart/alternative}. Viewing agents are supposed to view the | |
316 | last possible part of a message, as that is supposed to be the richest. | |
317 | However, users may prefer other types instead, and this list says what | |
318 | types are most unwanted. If, for instance, @samp{text/html} parts are | |
319 | very unwanted, and @samp{text/richtext} parts are somewhat unwanted, | |
320 | you could say something like: | |
321 | ||
322 | @lisp | |
323 | (setq mm-discouraged-alternatives | |
324 | '("text/html" "text/richtext") | |
325 | mm-automatic-display | |
326 | (remove "text/html" mm-automatic-display)) | |
327 | @end lisp | |
328 | ||
329 | @item mm-inline-large-images | |
330 | @vindex mm-inline-large-images | |
f4dd4ae8 | 331 | When displaying inline images that are larger than the window, Emacs |
23f87bed MB |
332 | does not enable scrolling, which means that you cannot see the whole |
333 | image. To prevent this, the library tries to determine the image size | |
334 | before displaying it inline, and if it doesn't fit the window, the | |
335 | library will display it externally (e.g. with @samp{ImageMagick} or | |
336 | @samp{xv}). Setting this variable to @code{t} disables this check and | |
337 | makes the library display all inline images as inline, regardless of | |
338 | their size. | |
339 | ||
340 | @item mm-inline-override-types | |
341 | @vindex mm-inline-override-types | |
342 | @code{mm-inlined-types} may include regular expressions, for example to | |
343 | specify that all @samp{text/.*} parts be displayed inline. If a user | |
344 | prefers to have a type that matches such a regular expression be treated | |
345 | as an attachment, that can be accomplished by setting this variable to a | |
346 | list containing that type. For example assuming @code{mm-inlined-types} | |
347 | includes @samp{text/.*}, then including @samp{text/html} in this | |
348 | variable will cause @samp{text/html} parts to be treated as attachments. | |
349 | ||
350 | @item mm-text-html-renderer | |
351 | @vindex mm-text-html-renderer | |
352 | This selects the function used to render @acronym{HTML}. The predefined | |
353 | renderers are selected by the symbols @code{w3}, | |
354 | @code{w3m}@footnote{See @uref{http://emacs-w3m.namazu.org/} for more | |
355 | information about emacs-w3m}, @code{links}, @code{lynx}, | |
356 | @code{w3m-standalone} or @code{html2text}. If @code{nil} use an | |
357 | external viewer. You can also specify a function, which will be | |
358 | called with a @acronym{MIME} handle as the argument. | |
359 | ||
360 | @item mm-inline-text-html-with-images | |
361 | @vindex mm-inline-text-html-with-images | |
362 | Some @acronym{HTML} mails might have the trick of spammers using | |
363 | @samp{<img>} tags. It is likely to be intended to verify whether you | |
364 | have read the mail. You can prevent your personal informations from | |
365 | leaking by setting this option to @code{nil} (which is the default). | |
366 | It is currently ignored by Emacs/w3. For emacs-w3m, you may use the | |
367 | command @kbd{t} on the image anchor to show an image even if it is | |
368 | @code{nil}.@footnote{The command @kbd{T} will load all images. If you | |
369 | have set the option @code{w3m-key-binding} to @code{info}, use @kbd{i} | |
370 | or @kbd{I} instead.} | |
371 | ||
372 | @item mm-w3m-safe-url-regexp | |
373 | @vindex mm-w3m-safe-url-regexp | |
374 | A regular expression that matches safe URL names, i.e. URLs that are | |
375 | unlikely to leak personal information when rendering @acronym{HTML} | |
376 | email (the default value is @samp{\\`cid:}). If @code{nil} consider | |
377 | all URLs safe. | |
378 | ||
379 | @item mm-inline-text-html-with-w3m-keymap | |
380 | @vindex mm-inline-text-html-with-w3m-keymap | |
381 | You can use emacs-w3m command keys in the inlined text/html part by | |
382 | setting this option to non-@code{nil}. The default value is @code{t}. | |
383 | ||
384 | @item mm-external-terminal-program | |
385 | @vindex mm-external-terminal-program | |
386 | The program used to start an external terminal. | |
387 | ||
388 | @item mm-enable-external | |
389 | @vindex mm-enable-external | |
10ace8ea | 390 | Indicate whether external @acronym{MIME} handlers should be used. |
23f87bed | 391 | |
10ace8ea | 392 | If @code{t}, all defined external @acronym{MIME} handlers are used. If |
23f87bed MB |
393 | @code{nil}, files are saved to disk (@code{mailcap-save-binary-file}). |
394 | If it is the symbol @code{ask}, you are prompted before the external | |
395 | @acronym{MIME} handler is invoked. | |
396 | ||
397 | When you launch an attachment through mailcap (@pxref{mailcap}) an | |
10ace8ea | 398 | attempt is made to use a safe viewer with the safest options---this isn't |
23f87bed MB |
399 | the case if you save it to disk and launch it in a different way |
400 | (command line or double-clicking). Anyhow, if you want to be sure not | |
401 | to launch any external programs, set this variable to @code{nil} or | |
402 | @code{ask}. | |
403 | ||
404 | @end table | |
405 | ||
406 | @node Files and Directories | |
407 | @section Files and Directories | |
408 | ||
409 | @table @code | |
410 | ||
411 | @item mm-default-directory | |
412 | @vindex mm-default-directory | |
413 | The default directory for saving attachments. If @code{nil} use | |
414 | @code{default-directory}. | |
415 | ||
416 | @item mm-tmp-directory | |
417 | @vindex mm-tmp-directory | |
418 | Directory for storing temporary files. | |
419 | ||
420 | @item mm-file-name-rewrite-functions | |
421 | @vindex mm-file-name-rewrite-functions | |
422 | A list of functions used for rewriting file names of @acronym{MIME} | |
423 | parts. Each function is applied successively to the file name. | |
424 | Ready-made functions include | |
425 | ||
426 | @table @code | |
427 | @item mm-file-name-delete-control | |
428 | @findex mm-file-name-delete-control | |
429 | Delete all control characters. | |
430 | ||
431 | @item mm-file-name-delete-gotchas | |
432 | @findex mm-file-name-delete-gotchas | |
433 | Delete characters that could have unintended consequences when used | |
434 | with flawed shell scripts, i.e. @samp{|}, @samp{>} and @samp{<}; and | |
435 | @samp{-}, @samp{.} as the first character. | |
436 | ||
437 | @item mm-file-name-delete-whitespace | |
438 | @findex mm-file-name-delete-whitespace | |
439 | Remove all whitespace. | |
440 | ||
441 | @item mm-file-name-trim-whitespace | |
442 | @findex mm-file-name-trim-whitespace | |
443 | Remove leading and trailing whitespace. | |
444 | ||
445 | @item mm-file-name-collapse-whitespace | |
446 | @findex mm-file-name-collapse-whitespace | |
447 | Collapse multiple whitespace characters. | |
448 | ||
449 | @item mm-file-name-replace-whitespace | |
450 | @findex mm-file-name-replace-whitespace | |
451 | @vindex mm-file-name-replace-whitespace | |
452 | Replace whitespace with underscores. Set the variable | |
453 | @code{mm-file-name-replace-whitespace} to any other string if you do | |
454 | not like underscores. | |
455 | @end table | |
456 | ||
457 | The standard Emacs functions @code{capitalize}, @code{downcase}, | |
458 | @code{upcase} and @code{upcase-initials} might also prove useful. | |
459 | ||
460 | @item mm-path-name-rewrite-functions | |
461 | @vindex mm-path-name-rewrite-functions | |
462 | List of functions used for rewriting the full file names of @acronym{MIME} | |
463 | parts. This is used when viewing parts externally, and is meant for | |
464 | transforming the absolute name so that non-compliant programs can find | |
465 | the file where it's saved. | |
466 | ||
467 | @end table | |
468 | ||
469 | @node New Viewers | |
470 | @section New Viewers | |
471 | ||
472 | Here's an example viewer for displaying @code{text/enriched} inline: | |
473 | ||
474 | @lisp | |
475 | (defun mm-display-enriched-inline (handle) | |
476 | (let (text) | |
477 | (with-temp-buffer | |
478 | (mm-insert-part handle) | |
479 | (save-window-excursion | |
480 | (enriched-decode (point-min) (point-max)) | |
481 | (setq text (buffer-string)))) | |
482 | (mm-insert-inline handle text))) | |
483 | @end lisp | |
484 | ||
485 | We see that the function takes a @acronym{MIME} handle as its parameter. It | |
486 | then goes to a temporary buffer, inserts the text of the part, does some | |
487 | work on the text, stores the result, goes back to the buffer it was | |
488 | called from and inserts the result. | |
489 | ||
490 | The two important helper functions here are @code{mm-insert-part} and | |
491 | @code{mm-insert-inline}. The first function inserts the text of the | |
492 | handle in the current buffer. It handles charset and/or content | |
493 | transfer decoding. The second function just inserts whatever text you | |
494 | tell it to insert, but it also sets things up so that the text can be | |
495 | ``undisplayed'' in a convenient manner. | |
496 | ||
497 | ||
498 | @node Composing | |
499 | @chapter Composing | |
500 | @cindex Composing | |
501 | @cindex MIME Composing | |
502 | @cindex MML | |
503 | @cindex MIME Meta Language | |
504 | ||
505 | Creating a @acronym{MIME} message is boring and non-trivial. Therefore, | |
506 | a library called @code{mml} has been defined that parses a language | |
507 | called @acronym{MML} (@acronym{MIME} Meta Language) and generates | |
508 | @acronym{MIME} messages. | |
509 | ||
510 | @findex mml-generate-mime | |
511 | The main interface function is @code{mml-generate-mime}. It will | |
512 | examine the contents of the current (narrowed-to) buffer and return a | |
513 | string containing the @acronym{MIME} message. | |
514 | ||
515 | @menu | |
516 | * Simple MML Example:: An example @acronym{MML} document. | |
517 | * MML Definition:: All valid @acronym{MML} elements. | |
518 | * Advanced MML Example:: Another example @acronym{MML} document. | |
519 | * Encoding Customization:: Variables that affect encoding. | |
520 | * Charset Translation:: How charsets are mapped from @sc{mule} to @acronym{MIME}. | |
521 | * Conversion:: Going from @acronym{MIME} to @acronym{MML} and vice versa. | |
522 | * Flowed text:: Soft and hard newlines. | |
523 | @end menu | |
524 | ||
525 | ||
526 | @node Simple MML Example | |
527 | @section Simple MML Example | |
528 | ||
529 | Here's a simple @samp{multipart/alternative}: | |
530 | ||
531 | @example | |
532 | <#multipart type=alternative> | |
533 | This is a plain text part. | |
534 | <#part type=text/enriched> | |
535 | <center>This is a centered enriched part</center> | |
536 | <#/multipart> | |
537 | @end example | |
538 | ||
539 | After running this through @code{mml-generate-mime}, we get this: | |
540 | ||
541 | @example | |
542 | Content-Type: multipart/alternative; boundary="=-=-=" | |
543 | ||
544 | ||
545 | --=-=-= | |
546 | ||
547 | ||
548 | This is a plain text part. | |
549 | ||
550 | --=-=-= | |
551 | Content-Type: text/enriched | |
552 | ||
553 | ||
554 | <center>This is a centered enriched part</center> | |
555 | ||
556 | --=-=-=-- | |
557 | @end example | |
558 | ||
559 | ||
560 | @node MML Definition | |
561 | @section MML Definition | |
562 | ||
563 | The @acronym{MML} language is very simple. It looks a bit like an SGML | |
564 | application, but it's not. | |
565 | ||
566 | The main concept of @acronym{MML} is the @dfn{part}. Each part can be of a | |
567 | different type or use a different charset. The way to delineate a part | |
568 | is with a @samp{<#part ...>} tag. Multipart parts can be introduced | |
569 | with the @samp{<#multipart ...>} tag. Parts are ended by the | |
570 | @samp{<#/part>} or @samp{<#/multipart>} tags. Parts started with the | |
571 | @samp{<#part ...>} tags are also closed by the next open tag. | |
572 | ||
573 | There's also the @samp{<#external ...>} tag. These introduce | |
574 | @samp{external/message-body} parts. | |
575 | ||
576 | Each tag can contain zero or more parameters on the form | |
577 | @samp{parameter=value}. The values may be enclosed in quotation marks, | |
578 | but that's not necessary unless the value contains white space. So | |
579 | @samp{filename=/home/user/#hello$^yes} is perfectly valid. | |
580 | ||
581 | The following parameters have meaning in @acronym{MML}; parameters that have no | |
582 | meaning are ignored. The @acronym{MML} parameter names are the same as the | |
583 | @acronym{MIME} parameter names; the things in the parentheses say which | |
584 | header it will be used in. | |
585 | ||
586 | @table @samp | |
587 | @item type | |
588 | The @acronym{MIME} type of the part (@code{Content-Type}). | |
589 | ||
590 | @item filename | |
591 | Use the contents of the file in the body of the part | |
592 | (@code{Content-Disposition}). | |
593 | ||
594 | @item charset | |
595 | The contents of the body of the part are to be encoded in the character | |
596 | set specified (@code{Content-Type}). @xref{Charset Translation}. | |
597 | ||
598 | @item name | |
599 | Might be used to suggest a file name if the part is to be saved | |
600 | to a file (@code{Content-Type}). | |
601 | ||
602 | @item disposition | |
603 | Valid values are @samp{inline} and @samp{attachment} | |
604 | (@code{Content-Disposition}). | |
605 | ||
606 | @item encoding | |
607 | Valid values are @samp{7bit}, @samp{8bit}, @samp{quoted-printable} and | |
608 | @samp{base64} (@code{Content-Transfer-Encoding}). @xref{Charset | |
609 | Translation}. | |
610 | ||
611 | @item description | |
612 | A description of the part (@code{Content-Description}). | |
613 | ||
614 | @item creation-date | |
615 | RFC822 date when the part was created (@code{Content-Disposition}). | |
616 | ||
617 | @item modification-date | |
618 | RFC822 date when the part was modified (@code{Content-Disposition}). | |
619 | ||
620 | @item read-date | |
621 | RFC822 date when the part was read (@code{Content-Disposition}). | |
622 | ||
623 | @item recipients | |
624 | Who to encrypt/sign the part to. This field is used to override any | |
625 | auto-detection based on the To/CC headers. | |
626 | ||
627 | @item sender | |
628 | Identity used to sign the part. This field is used to override the | |
629 | default key used. | |
630 | ||
631 | @item size | |
632 | The size (in octets) of the part (@code{Content-Disposition}). | |
633 | ||
634 | @item sign | |
635 | What technology to sign this @acronym{MML} part with (@code{smime}, @code{pgp} | |
636 | or @code{pgpmime}) | |
637 | ||
638 | @item encrypt | |
639 | What technology to encrypt this @acronym{MML} part with (@code{smime}, | |
640 | @code{pgp} or @code{pgpmime}) | |
641 | ||
642 | @end table | |
643 | ||
644 | Parameters for @samp{text/plain}: | |
645 | ||
646 | @table @samp | |
647 | @item format | |
648 | Formatting parameter for the text, valid values include @samp{fixed} | |
649 | (the default) and @samp{flowed}. Normally you do not specify this | |
650 | manually, since it requires the textual body to be formatted in a | |
651 | special way described in RFC 2646. @xref{Flowed text}. | |
652 | @end table | |
653 | ||
654 | Parameters for @samp{application/octet-stream}: | |
655 | ||
656 | @table @samp | |
657 | @item type | |
658 | Type of the part; informal---meant for human readers | |
659 | (@code{Content-Type}). | |
660 | @end table | |
661 | ||
662 | Parameters for @samp{message/external-body}: | |
663 | ||
664 | @table @samp | |
665 | @item access-type | |
666 | A word indicating the supported access mechanism by which the file may | |
667 | be obtained. Values include @samp{ftp}, @samp{anon-ftp}, @samp{tftp}, | |
668 | @samp{localfile}, and @samp{mailserver}. (@code{Content-Type}.) | |
669 | ||
670 | @item expiration | |
671 | The RFC822 date after which the file may no longer be fetched. | |
672 | (@code{Content-Type}.) | |
673 | ||
674 | @item size | |
675 | The size (in octets) of the file. (@code{Content-Type}.) | |
676 | ||
677 | @item permission | |
678 | Valid values are @samp{read} and @samp{read-write} | |
679 | (@code{Content-Type}). | |
680 | ||
681 | @end table | |
682 | ||
683 | Parameters for @samp{sign=smime}: | |
684 | ||
685 | @table @samp | |
686 | ||
687 | @item keyfile | |
688 | File containing key and certificate for signer. | |
689 | ||
690 | @end table | |
691 | ||
692 | Parameters for @samp{encrypt=smime}: | |
693 | ||
694 | @table @samp | |
695 | ||
696 | @item certfile | |
697 | File containing certificate for recipient. | |
698 | ||
699 | @end table | |
700 | ||
701 | ||
702 | @node Advanced MML Example | |
703 | @section Advanced MML Example | |
704 | ||
705 | Here's a complex multipart message. It's a @samp{multipart/mixed} that | |
706 | contains many parts, one of which is a @samp{multipart/alternative}. | |
707 | ||
708 | @example | |
709 | <#multipart type=mixed> | |
710 | <#part type=image/jpeg filename=~/rms.jpg disposition=inline> | |
711 | <#multipart type=alternative> | |
712 | This is a plain text part. | |
713 | <#part type=text/enriched name=enriched.txt> | |
714 | <center>This is a centered enriched part</center> | |
715 | <#/multipart> | |
716 | This is a new plain text part. | |
717 | <#part disposition=attachment> | |
718 | This plain text part is an attachment. | |
719 | <#/multipart> | |
720 | @end example | |
721 | ||
722 | And this is the resulting @acronym{MIME} message: | |
723 | ||
724 | @example | |
725 | Content-Type: multipart/mixed; boundary="=-=-=" | |
726 | ||
727 | ||
728 | --=-=-= | |
729 | ||
730 | ||
731 | ||
732 | --=-=-= | |
733 | Content-Type: image/jpeg; | |
734 | filename="~/rms.jpg" | |
735 | Content-Disposition: inline; | |
736 | filename="~/rms.jpg" | |
737 | Content-Transfer-Encoding: base64 | |
738 | ||
739 | /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof | |
740 | Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/wAALCAAwADABAREA/8QAHwAA | |
741 | AQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQR | |
742 | BRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RF | |
743 | RkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ip | |
744 | qrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/9oACAEB | |
745 | AAA/AO/rifFHjldNuGsrDa0qcSSHkA+gHrXKw+LtWLrMb+RgTyhbr+HSug07xNqV9fQtZrNI | |
746 | AyiaE/NuBPOOOP0rvRNE880KOC8TbXXGCv1FPqjrF4LDR7u5L7SkTFT/ALWOP1xXgTuXfc7E | |
747 | sx6nua6rwp4IvvEM8chCxWxOdzn7wz6V9AaB4S07w9p5itow0rDLSY5Pt9K43xO66P4xs71m | |
748 | 2QXiGCbA4yOVJ9+1aYORkdK434lyNH4ahCnG66VT9Nj15JFbPdX0MS43M4VQf5/yr2vSpLnw | |
749 | 5ZW8dlCZ8KFXjOPX0/mK6rSPEGt3Angu44fNEReHYNvIH3TzXDeKNO8RX+kSX2ouZkicTIOc | |
750 | L+g7E810ulFjpVtv3bwgB3HJyK5L4quY/C9sVxk3ij/xx6850u7t1mtp/wDlpEw3An3Jr3Dw | |
751 | 34gsbWza4nBlhC5LDsaW6+IFgupQyCF3iHH7gA7c9R9ay7zx6t7aX9jHC4smhfBkGCvHGfrm | |
752 | tLQ7hbnRrV1GPkAP1x1/Hr+Ncr8Vzjwrbf8AX6v/AKA9eQRyYlQk8Yx9K6XTNbkgia2ciSIn | |
753 | 7p5Ga9Atte0LTLKO6it4i7dVRFJDcZ4PvXN+JvEMF9bILVGXJLSZ4zkjivRPDaeX4b08HOTC | |
754 | pOffmua+KkbS+GLVUGT9tT/0B68eeIpIFYjB70+OOVXyoOM9+M1eaWeCLzHPyHGO/NVWvJJm | |
755 | jQ8KGH1NfQWhXSXmh2c8eArRLwO3HSv/2Q== | |
756 | ||
757 | --=-=-= | |
758 | Content-Type: multipart/alternative; boundary="==-=-=" | |
759 | ||
760 | ||
761 | --==-=-= | |
762 | ||
763 | ||
764 | This is a plain text part. | |
765 | ||
766 | --==-=-= | |
767 | Content-Type: text/enriched; | |
768 | name="enriched.txt" | |
769 | ||
770 | ||
771 | <center>This is a centered enriched part</center> | |
772 | ||
773 | --==-=-=-- | |
774 | ||
775 | --=-=-= | |
776 | ||
777 | This is a new plain text part. | |
778 | ||
779 | --=-=-= | |
780 | Content-Disposition: attachment | |
781 | ||
782 | ||
783 | This plain text part is an attachment. | |
784 | ||
785 | --=-=-=-- | |
786 | @end example | |
787 | ||
788 | @node Encoding Customization | |
789 | @section Encoding Customization | |
790 | ||
791 | @table @code | |
792 | ||
793 | @item mm-body-charset-encoding-alist | |
794 | @vindex mm-body-charset-encoding-alist | |
795 | Mapping from @acronym{MIME} charset to encoding to use. This variable is | |
796 | usually used except, e.g., when other requirements force a specific | |
797 | encoding (digitally signed messages require 7bit encodings). The | |
3d80e1a2 | 798 | default is |
23f87bed MB |
799 | |
800 | @lisp | |
801 | ((iso-2022-jp . 7bit) | |
802 | (iso-2022-jp-2 . 7bit) | |
803 | (utf-16 . base64) | |
804 | (utf-16be . base64) | |
805 | (utf-16le . base64)) | |
806 | @end lisp | |
807 | ||
808 | As an example, if you do not want to have ISO-8859-1 characters | |
809 | quoted-printable encoded, you may add @code{(iso-8859-1 . 8bit)} to | |
810 | this variable. You can override this setting on a per-message basis | |
811 | by using the @code{encoding} @acronym{MML} tag (@pxref{MML Definition}). | |
812 | ||
813 | @item mm-coding-system-priorities | |
814 | @vindex mm-coding-system-priorities | |
815 | Prioritize coding systems to use for outgoing messages. The default | |
816 | is @code{nil}, which means to use the defaults in Emacs. It is a list of | |
0683d241 MB |
817 | coding system symbols (aliases of coding systems are also allowed, use |
818 | @kbd{M-x describe-coding-system} to make sure you are specifying correct | |
819 | coding system names). For example, if you have configured Emacs | |
23f87bed MB |
820 | to prefer UTF-8, but wish that outgoing messages should be sent in |
821 | ISO-8859-1 if possible, you can set this variable to | |
0683d241 | 822 | @code{(iso-8859-1)}. You can override this setting on a per-message |
23f87bed MB |
823 | basis by using the @code{charset} @acronym{MML} tag (@pxref{MML Definition}). |
824 | ||
825 | @item mm-content-transfer-encoding-defaults | |
826 | @vindex mm-content-transfer-encoding-defaults | |
827 | Mapping from @acronym{MIME} types to encoding to use. This variable is usually | |
828 | used except, e.g., when other requirements force a safer encoding | |
829 | (digitally signed messages require 7bit encoding). Besides the normal | |
830 | @acronym{MIME} encodings, @code{qp-or-base64} may be used to indicate that for | |
831 | each case the most efficient of quoted-printable and base64 should be | |
832 | used. | |
833 | ||
834 | @code{qp-or-base64} has another effect. It will fold long lines so that | |
835 | MIME parts may not be broken by MTA. So do @code{quoted-printable} and | |
836 | @code{base64}. | |
837 | ||
838 | Note that it affects body encoding only when a part is a raw forwarded | |
839 | message (which will be made by @code{gnus-summary-mail-forward} with the | |
840 | arg 2 for example) or is neither the @samp{text/*} type nor the | |
841 | @samp{message/*} type. Even though in those cases, you can override | |
842 | this setting on a per-message basis by using the @code{encoding} | |
843 | @acronym{MML} tag (@pxref{MML Definition}). | |
844 | ||
845 | @item mm-use-ultra-safe-encoding | |
846 | @vindex mm-use-ultra-safe-encoding | |
847 | When this is non-@code{nil}, it means that textual parts are encoded as | |
848 | quoted-printable if they contain lines longer than 76 characters or | |
849 | starting with "From " in the body. Non-7bit encodings (8bit, binary) | |
850 | are generally disallowed. This reduce the probability that a non-8bit | |
851 | clean MTA or MDA changes the message. This should never be set | |
852 | directly, but bound by other functions when necessary (e.g., when | |
853 | encoding messages that are to be digitally signed). | |
854 | ||
855 | @end table | |
856 | ||
857 | @node Charset Translation | |
858 | @section Charset Translation | |
859 | @cindex charsets | |
860 | ||
861 | During translation from @acronym{MML} to @acronym{MIME}, for each | |
862 | @acronym{MIME} part which has been composed inside Emacs, an appropriate | |
863 | charset has to be chosen. | |
864 | ||
865 | @vindex mail-parse-charset | |
866 | If you are running a non-@sc{mule} Emacs, this process is simple: If the | |
867 | part contains any non-@acronym{ASCII} (8-bit) characters, the @acronym{MIME} charset | |
868 | given by @code{mail-parse-charset} (a symbol) is used. (Never set this | |
869 | variable directly, though. If you want to change the default charset, | |
870 | please consult the documentation of the package which you use to process | |
871 | @acronym{MIME} messages. | |
872 | @xref{Various Message Variables, , Various Message Variables, message, | |
873 | Message Manual}, for example.) | |
874 | If there are only @acronym{ASCII} characters, the @acronym{MIME} charset US-ASCII is | |
875 | used, of course. | |
876 | ||
877 | @cindex MULE | |
878 | @cindex UTF-8 | |
879 | @cindex Unicode | |
880 | @vindex mm-mime-mule-charset-alist | |
881 | Things are slightly more complicated when running Emacs with @sc{mule} | |
882 | support. In this case, a list of the @sc{mule} charsets used in the | |
883 | part is obtained, and the @sc{mule} charsets are translated to @acronym{MIME} | |
884 | charsets by consulting the variable @code{mm-mime-mule-charset-alist}. | |
885 | If this results in a single @acronym{MIME} charset, this is used to encode | |
886 | the part. But if the resulting list of @acronym{MIME} charsets contains more | |
887 | than one element, two things can happen: If it is possible to encode the | |
888 | part via UTF-8, this charset is used. (For this, Emacs must support | |
889 | the @code{utf-8} coding system, and the part must consist entirely of | |
890 | characters which have Unicode counterparts.) If UTF-8 is not available | |
891 | for some reason, the part is split into several ones, so that each one | |
892 | can be encoded with a single @acronym{MIME} charset. The part can only be | |
893 | split at line boundaries, though---if more than one @acronym{MIME} charset is | |
894 | required to encode a single line, it is not possible to encode the part. | |
895 | ||
896 | When running Emacs with @sc{mule} support, the preferences for which | |
897 | coding system to use is inherited from Emacs itself. This means that | |
898 | if Emacs is set up to prefer UTF-8, it will be used when encoding | |
899 | messages. You can modify this by altering the | |
900 | @code{mm-coding-system-priorities} variable though (@pxref{Encoding | |
901 | Customization}). | |
902 | ||
903 | The charset to be used can be overridden by setting the @code{charset} | |
904 | @acronym{MML} tag (@pxref{MML Definition}) when composing the message. | |
905 | ||
906 | The encoding of characters (quoted-printable, 8bit etc) is orthogonal | |
907 | to the discussion here, and is controlled by the variables | |
908 | @code{mm-body-charset-encoding-alist} and | |
909 | @code{mm-content-transfer-encoding-defaults} (@pxref{Encoding | |
910 | Customization}). | |
911 | ||
912 | @node Conversion | |
913 | @section Conversion | |
914 | ||
915 | @findex mime-to-mml | |
916 | A (multipart) @acronym{MIME} message can be converted to @acronym{MML} | |
917 | with the @code{mime-to-mml} function. It works on the message in the | |
918 | current buffer, and substitutes @acronym{MML} markup for @acronym{MIME} | |
919 | boundaries. Non-textual parts do not have their contents in the buffer, | |
920 | but instead have the contents in separate buffers that are referred to | |
921 | from the @acronym{MML} tags. | |
922 | ||
923 | @findex mml-to-mime | |
924 | An @acronym{MML} message can be converted back to @acronym{MIME} by the | |
925 | @code{mml-to-mime} function. | |
926 | ||
927 | These functions are in certain senses ``lossy''---you will not get back | |
928 | an identical message if you run @code{mime-to-mml} and then | |
929 | @code{mml-to-mime}. Not only will trivial things like the order of the | |
930 | headers differ, but the contents of the headers may also be different. | |
931 | For instance, the original message may use base64 encoding on text, | |
932 | while @code{mml-to-mime} may decide to use quoted-printable encoding, and | |
933 | so on. | |
934 | ||
935 | In essence, however, these two functions should be the inverse of each | |
936 | other. The resulting contents of the message should remain equivalent, | |
937 | if not identical. | |
dd8839b0 | 938 | |
dd8839b0 | 939 | |
23f87bed MB |
940 | @node Flowed text |
941 | @section Flowed text | |
942 | @cindex format=flowed | |
dd8839b0 | 943 | |
23f87bed MB |
944 | The Emacs @acronym{MIME} library will respect the @code{use-hard-newlines} |
945 | variable (@pxref{Hard and Soft Newlines, ,Hard and Soft Newlines, | |
946 | emacs, Emacs Manual}) when encoding a message, and the | |
947 | ``format=flowed'' Content-Type parameter when decoding a message. | |
948 | ||
949 | On encoding text, regardless of @code{use-hard-newlines}, lines | |
950 | terminated by soft newline characters are filled together and wrapped | |
951 | after the column decided by @code{fill-flowed-encode-column}. | |
952 | Quotation marks (matching @samp{^>* ?}) are respected. The variable | |
953 | controls how the text will look in a client that does not support | |
954 | flowed text, the default is to wrap after 66 characters. If hard | |
955 | newline characters are not present in the buffer, no flow encoding | |
956 | occurs. | |
957 | ||
958 | On decoding flowed text, lines with soft newline characters are filled | |
959 | together and wrapped after the column decided by | |
960 | @code{fill-flowed-display-column}. The default is to wrap after | |
961 | @code{fill-column}. | |
dd8839b0 | 962 | |
dd8839b0 | 963 | |
dd8839b0 DL |
964 | |
965 | ||
966 | @node Interface Functions | |
967 | @chapter Interface Functions | |
968 | @cindex interface functions | |
969 | @cindex mail-parse | |
970 | ||
971 | The @code{mail-parse} library is an abstraction over the actual | |
972 | low-level libraries that are described in the next chapter. | |
973 | ||
974 | Standards change, and so programs have to change to fit in the new | |
975 | mold. For instance, RFC2045 describes a syntax for the | |
23f87bed | 976 | @code{Content-Type} header that only allows @acronym{ASCII} characters in the |
dd8839b0 | 977 | parameter list. RFC2231 expands on RFC2045 syntax to provide a scheme |
23f87bed | 978 | for continuation headers and non-@acronym{ASCII} characters. |
dd8839b0 DL |
979 | |
980 | The traditional way to deal with this is just to update the library | |
981 | functions to parse the new syntax. However, this is sometimes the wrong | |
982 | thing to do. In some instances it may be vital to be able to understand | |
983 | both the old syntax as well as the new syntax, and if there is only one | |
984 | library, one must choose between the old version of the library and the | |
985 | new version of the library. | |
986 | ||
23f87bed MB |
987 | The Emacs @acronym{MIME} library takes a different tack. It defines a |
988 | series of low-level libraries (@file{rfc2047.el}, @file{rfc2231.el} | |
989 | and so on) that parses strictly according to the corresponding | |
990 | standard. However, normal programs would not use the functions | |
991 | provided by these libraries directly, but instead use the functions | |
992 | provided by the @code{mail-parse} library. The functions in this | |
993 | library are just aliases to the corresponding functions in the latest | |
994 | low-level libraries. Using this scheme, programs get a consistent | |
995 | interface they can use, and library developers are free to create | |
996 | write code that handles new standards. | |
dd8839b0 DL |
997 | |
998 | The following functions are defined by this library: | |
999 | ||
23f87bed MB |
1000 | @table @code |
1001 | @item mail-header-parse-content-type | |
1002 | @findex mail-header-parse-content-type | |
1003 | Parse a @code{Content-Type} header and return a list on the following | |
1004 | format: | |
dd8839b0 DL |
1005 | |
1006 | @lisp | |
1007 | ("type/subtype" | |
1008 | (attribute1 . value1) | |
1009 | (attribute2 . value2) | |
23f87bed | 1010 | ...) |
dd8839b0 DL |
1011 | @end lisp |
1012 | ||
1013 | Here's an example: | |
1014 | ||
1015 | @example | |
1016 | (mail-header-parse-content-type | |
1017 | "image/gif; name=\"b980912.gif\"") | |
1018 | @result{} ("image/gif" (name . "b980912.gif")) | |
1019 | @end example | |
1020 | ||
23f87bed MB |
1021 | @item mail-header-parse-content-disposition |
1022 | @findex mail-header-parse-content-disposition | |
1023 | Parse a @code{Content-Disposition} header and return a list on the same | |
1024 | format as the function above. | |
dd8839b0 | 1025 | |
23f87bed | 1026 | @item mail-content-type-get |
dd8839b0 | 1027 | @findex mail-content-type-get |
23f87bed MB |
1028 | Takes two parameters---a list on the format above, and an attribute. |
1029 | Returns the value of the attribute. | |
dd8839b0 DL |
1030 | |
1031 | @example | |
1032 | (mail-content-type-get | |
1033 | '("image/gif" (name . "b980912.gif")) 'name) | |
1034 | @result{} "b980912.gif" | |
1035 | @end example | |
1036 | ||
23f87bed MB |
1037 | @item mail-header-encode-parameter |
1038 | @findex mail-header-encode-parameter | |
1039 | Takes a parameter string and returns an encoded version of the string. | |
1040 | This is used for parameters in headers like @code{Content-Type} and | |
1041 | @code{Content-Disposition}. | |
dd8839b0 | 1042 | |
23f87bed MB |
1043 | @item mail-header-remove-comments |
1044 | @findex mail-header-remove-comments | |
1045 | Return a comment-free version of a header. | |
dd8839b0 DL |
1046 | |
1047 | @example | |
1048 | (mail-header-remove-comments | |
1049 | "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)") | |
1050 | @result{} "Gnus/5.070027 " | |
1051 | @end example | |
1052 | ||
23f87bed MB |
1053 | @item mail-header-remove-whitespace |
1054 | @findex mail-header-remove-whitespace | |
1055 | Remove linear white space from a header. Space inside quoted strings | |
1056 | and comments is preserved. | |
dd8839b0 DL |
1057 | |
1058 | @example | |
1059 | (mail-header-remove-whitespace | |
1060 | "image/gif; name=\"Name with spaces\"") | |
1061 | @result{} "image/gif;name=\"Name with spaces\"" | |
1062 | @end example | |
1063 | ||
23f87bed MB |
1064 | @item mail-header-get-comment |
1065 | @findex mail-header-get-comment | |
1066 | Return the last comment in a header. | |
dd8839b0 DL |
1067 | |
1068 | @example | |
1069 | (mail-header-get-comment | |
1070 | "Gnus/5.070027 (Pterodactyl Gnus v0.27) (Finnish Landrace)") | |
1071 | @result{} "Finnish Landrace" | |
1072 | @end example | |
1073 | ||
23f87bed MB |
1074 | @item mail-header-parse-address |
1075 | @findex mail-header-parse-address | |
1076 | Parse an address and return a list containing the mailbox and the | |
1077 | plaintext name. | |
dd8839b0 DL |
1078 | |
1079 | @example | |
1080 | (mail-header-parse-address | |
1081 | "Hrvoje Niksic <hniksic@@srce.hr>") | |
1082 | @result{} ("hniksic@@srce.hr" . "Hrvoje Niksic") | |
1083 | @end example | |
1084 | ||
23f87bed MB |
1085 | @item mail-header-parse-addresses |
1086 | @findex mail-header-parse-addresses | |
1087 | Parse a string with list of addresses and return a list of elements like | |
1088 | the one described above. | |
dd8839b0 DL |
1089 | |
1090 | @example | |
1091 | (mail-header-parse-addresses | |
1092 | "Hrvoje Niksic <hniksic@@srce.hr>, Steinar Bang <sb@@metis.no>") | |
1093 | @result{} (("hniksic@@srce.hr" . "Hrvoje Niksic") | |
1094 | ("sb@@metis.no" . "Steinar Bang")) | |
1095 | @end example | |
1096 | ||
23f87bed MB |
1097 | @item mail-header-parse-date |
1098 | @findex mail-header-parse-date | |
1099 | Parse a date string and return an Emacs time structure. | |
dd8839b0 | 1100 | |
23f87bed MB |
1101 | @item mail-narrow-to-head |
1102 | @findex mail-narrow-to-head | |
dd8839b0 DL |
1103 | Narrow the buffer to the header section of the buffer. Point is placed |
1104 | at the beginning of the narrowed buffer. | |
1105 | ||
23f87bed MB |
1106 | @item mail-header-narrow-to-field |
1107 | @findex mail-header-narrow-to-field | |
1108 | Narrow the buffer to the header under point. Understands continuation | |
1109 | headers. | |
1110 | ||
1111 | @item mail-header-fold-field | |
1112 | @findex mail-header-fold-field | |
1113 | Fold the header under point. | |
1114 | ||
1115 | @item mail-header-unfold-field | |
1116 | @findex mail-header-unfold-field | |
1117 | Unfold the header under point. | |
dd8839b0 | 1118 | |
23f87bed MB |
1119 | @item mail-header-field-value |
1120 | @findex mail-header-field-value | |
1121 | Return the value of the field under point. | |
dd8839b0 | 1122 | |
23f87bed MB |
1123 | @item mail-encode-encoded-word-region |
1124 | @findex mail-encode-encoded-word-region | |
1125 | Encode the non-@acronym{ASCII} words in the region. For instance, | |
1126 |