1 This is ../../msmtp/doc/msmtp.info, produced by makeinfo version 4.11
2 from ../../msmtp/doc/msmtp.texi.
4 This manual was last updated December 24, 2008 for version 1.4.17 of
7 Copyright (C) 2005, 2006, 2007, 2008 Martin Lambers
9 Permission is granted to copy, distribute and/or modify this
10 document under the terms of the GNU Free Documentation License,
11 Version 1.2 or any later version published by the Free Software
12 Foundation; with no Invariant Sections, no Front-Cover Texts, and
13 no Back-Cover Texts. A copy of the license is included in the
14 section entitled "GNU Free Documentation License".
16 INFO-DIR-SECTION Individual utilities
18 * msmtp: (msmtp). An SMTP client.
22 File: msmtp.info, Node: Top, Next: Introduction, Up: (dir)
27 This manual was last updated December 24, 2008 for version 1.4.17 of
30 Copyright (C) 2005, 2006, 2007, 2008 Martin Lambers
32 Permission is granted to copy, distribute and/or modify this
33 document under the terms of the GNU Free Documentation License,
34 Version 1.2 or any later version published by the Free Software
35 Foundation; with no Invariant Sections, no Front-Cover Texts, and
36 no Back-Cover Texts. A copy of the license is included in the
37 section entitled "GNU Free Documentation License".
41 * Introduction:: Basic concepts.
42 * Configuration files:: Configuration file commands.
43 * Invocation:: Command line options.
44 * Transport Layer Security:: How to use TLS/SSL.
45 * Authentication:: How to use authentication.
46 * Delivery Status Notifications:: How to use DSN.
47 * Sendmail mode:: How to send mail.
48 * Server information mode:: How to obtain information about
50 * Remote Message Queue Starting mode:: How to send RMQS requests.
51 * Examples:: Usage examples.
52 * Development:: About the development process.
53 * Copying Information:: How you can copy and share mpop.
56 File: msmtp.info, Node: Introduction, Next: Configuration files, Prev: Top, Up: Top
61 msmtp is an SMTP client.
63 In its default mode of operation, it reads a mail from standard
64 input and sends it to a predefined SMTP server that takes care of
65 proper delivery. Command line options and exit codes are compatible to
68 Supported SMTP features include:
69 * Authentication methods PLAIN, LOGIN, CRAM-MD5 and EXTERNAL (and
70 GSSAPI, DIGEST-MD5 and NTLM when compiled with GNU SASL support)
72 * TLS encrypted connections with the OpenSSL or GnuTLS libraries
73 (including server certificate verification and the possibility to
74 send a client certificate)
76 * Support for Internationalized Domain Names (IDN)
78 * DSN (Delivery Status Notification) support
80 * PIPELINING support for increased transmission speed
82 * RMQS (Remote Message Queue Starting) support (ETRN keyword)
84 The best way to start is probably to have a look at the Examples
85 section. *Note Examples::.
87 In addition to sendmail mode, there are two other modes of operation:
88 * Server information mode. In this mode, msmtp prints as much
89 information as it can get about a given SMTP server (supported
90 features, maximum mail size, ...).
92 * Remote Message Queue Starting mode. In this mode, msmtp sends a
93 Remote Message Queue Starting request for a host, domain, or queue
94 to a given SMTP server.
96 Normally, a system wide configuration file and/or a user
97 configuration file contain information about which SMTP server to use
98 and how to use it, but almost all settings can also be configured on
101 The information about SMTP servers is organized in accounts. Each
102 account describes one SMTP server: host name, authentication settings,
103 TLS settings, and so on. Each configuration file can define multiple
107 File: msmtp.info, Node: Configuration files, Next: Invocation, Prev: Introduction, Up: Top
109 2 Configuration files
110 *********************
112 msmtp supports a system wide configuration file and a user
113 configuration file. Both are optional and need not exist.
115 If it exists and is readable, a system wide configuration file
116 `SYSCONFDIR/msmtprc' will be loaded, where `SYSCONFDIR' depends on your
117 platform. The default is `/usr/local/etc'. Use `--version' to find out
118 which directory your version uses.
120 If it exists and is readable, a user configuration file will be
121 loaded (`~/.msmtprc' by default). Accounts defined in the user
122 configuration file override accounts from the system configuration
123 file. The user configuration file must have no more permissions than
124 user read/write. Configuration data from either file can be changed by
125 command line options.
127 A configuration file is a simple text file. Empty lines and comment
128 lines (whose first non-blank character is '#') are ignored. Every other
129 line must contain a command and may contain an argument to that command.
130 The argument may be enclosed in double quotes (").
132 If the first character of a filename is the tilde (~), this tilde
133 will be replaced by `HOME'. If a command accepts the argument `on', it
134 also accepts an empty argument and treats that as if it was `on'.
136 Commands form groups. Each group starts with the `account' command
137 and defines the settings for one SMTP server.
145 Set defaults. The following configuration commands will set
146 default values for all following account definitions in the
147 current configuration file.
149 `account NAME [: ACCOUNT[,...]]'
150 Start a new account definition with the given name. The current
151 default values are filled in (see *note defaults::).
152 If a colon and a list of previously defined accounts is given
153 after the account name, the new account, with the filled in
154 default values, will inherit all settings from the accounts in the
158 The SMTP server to send the mail to. The argument may be a host
159 name or a network address. Every account definition must contain
163 The port that the SMTP server listens on. The default port will
164 be acquired from your operating system's service database: for
165 SMTP, the service is "smtp" (default port 25), unless TLS without
166 STARTTLS is used, in which case it is "ssmtp" (465). For LMTP, it
169 `timeout (off|SECONDS)'
170 Set or unset a network timeout, in seconds. The argument `off'
171 means that no timeout will be set, which means that the operating
172 system default will be used. For compatibility with older
173 versions, `connect_timeout' is accepted as an alias for this
176 `protocol (smtp|lmtp)'
177 Set the protocol to use. Currently only SMTP and LMTP are
178 supported. SMTP is the default. See *note port:: for default ports.
181 This command sets the argument of the SMTP EHLO (or LMTP LHLO)
182 command. The default is `localhost', which is stupid but should
183 always work. Possible choices are the domain part of your mail
184 address (`provider.example' for `joe@provider.example') or the
185 fully qualified domain name of your host (if available).
187 2.2 Authentication commands
188 ===========================
190 *Note Authentication::.
192 `auth [(on|off|METHOD)]'
193 This command enables or disables SMTP authentication and
194 optionally chooses an authentication method to use. It should not
195 be necessary to choose a method; with the argument `on', msmtp
196 will choose the best one available. Accepted methods are `plain',
197 `cram-md5', `digest-md5', `gssapi', `external', `login', and
198 `ntlm'. *Note Authentication::.
200 Set your user name for SMTP authentication. An empty argument
201 unsets the user name. Authentication must be activated with the
205 Set your password for SMTP authentication. An empty argument
206 unsets the password. Authentication must be activated with the
207 `auth' command. If no password is set but one is needed during
208 authentication, msmtp will try to find it in `~/.netrc'. If that
209 fails, it will try to find it in `SYSCONFDIR/netrc' (use
210 `--version' to find out what `SYSCONFDIR' is on your platform). If
211 that fails, it will try to get it from a system specific keychain
212 (if available). If that fails but a controlling terminal is
213 available, msmtp will prompt you for it. *Note Authentication::.
215 `ntlmdomain [NTLMDOMAIN]'
216 Set a domain for the `ntlm' authentication method. The default is
217 to use no domain (equivalent to an empty argument), but some
218 servers seem to require one, even if it is an arbitrary string.
223 *Note Transport Layer Security::.
226 This command enables or disables TLS/SSL encrypted connections to
227 the SMTP server. Not every server supports TLS, and a few that
228 support it require the `tls_starttls off' command.
229 To use TLS/SSL, it is required to either use the `tls_trust_file'
230 command (highly recommended) or to disable `tls_certcheck'. *Note
231 Transport Layer Security::.
233 `tls_trust_file [FILE]'
234 This command activates strict server certificate verification.
235 The given file must contain one or more certificates of trusted
236 Certification Authorities (CAs) in PEM format.
237 On Debian based systems, you can install the `ca-certificates'
238 package and use the file `/etc/ssl/certs/ca-certificates.crt'.
239 An empty argument disables this feature.
241 `tls_crl_file [FILE]'
242 This command sets or unsets a certificate revocation list (CRL)
243 file for TLS, to be used during strict server certificate
244 verification as enabled by the *note tls_trust_file:: command.
245 This allows the verification procedure to detect revoked
246 certificates. *Note Transport Layer Security::.
248 `tls_key_file [FILE]'
249 This command (together with the `tls_cert_file') command enables
250 msmtp to send a client certificate to the SMTP server if requested.
251 The file must contain the private key of a certificate in PEM
252 format. An empty argument disables this feature. *Note Transport
255 `tls_cert_file [FILE]'
256 This command (together with the `tls_key_file' command) enables
257 msmtp to send a client certificate to the SMTP server if requested.
258 The file must contain a certificate in PEM format. An empty
259 argument disables this feature. *Note Transport Layer Security::.
261 `tls_certcheck [(on|off)]'
262 This command enables or disables checks for the server certificate.
263 WARNING: When the checks are disabled, TLS/SSL sessions will be
264 vulnerable to man-in-the-middle attacks! *Note Transport Layer
266 For compatibility with older versions, `tls_nocertcheck' is
267 accepted as an alias for `tls_certcheck off'.
269 `tls_starttls [(on|off)]'
270 This command enables or disables the use of the STARTTLS SMTP
271 command to start TLS encryption. It is enabled by default. *Note
272 Transport Layer Security::. For compatibility with older
273 versions, `tls_nostarttls' is accepted as an alias for
276 `tls_force_sslv3 [(on|off)]'
277 Force TLS/SSL version SSLv3. This might be needed to use SSL with
278 some old and broken servers. Do not use this unless you have to.
279 *Note Transport Layer Security::.
281 `tls_min_dh_prime_bits [BITS]'
282 Set or unset the minimum number of Diffie-Hellman (DH) prime bits
283 that msmtp will accept for TLS sessions. The default is set by the
284 TLS library and can be selected by using an empty argument to this
285 command. Only lower the default (for example to 512 bits) if there
286 is no other way to make TLS work with the remote server. *Note
287 Transport Layer Security::.
289 `tls_priorities [PRIORITIES]'
290 Set the priorities for TLS sessions. The default is set by the TLS
291 library and can be selected by using an empty argument to this
292 command. Currently this command only works with sufficiently
293 recent GnuTLS releases. See the GnuTLS documentation of the
294 `gnutls_priority_init' function for a description of the
295 PRIORITIES string. *Note Transport Layer Security::.
297 2.4 Commands specific to sendmail mode
298 ======================================
300 *Note Sendmail mode::.
302 `auto_from [(on|off)]'
303 Enable or disable automatic envelope-from addresses. The default is
305 When enabled, an envelope-from address of the form user@domain
306 will be generated. The local part will be set to `USER' or, if
307 that fails, to `LOGNAME' or, if that fails, to the login name of
308 the current user. The domain part can be set with the
309 `maildomain' command (see *note maildomain::). If the maildomain
310 is empty, the envelope-from address will only consist of the user
311 name and not have a domain part.
312 When disabled, the envelope-from address must be set explicitly
313 with the `from' command (see *note from::).
314 *Note Envelope-from address::.
317 Set the envelope-from address. This address will only be used when
318 `auto_from' is disabled. *Note Envelope-from address::.
320 `maildomain [DOMAIN]'
321 Set a domain part for the generation of an envelope-from address.
322 This is only used when `auto_from' is enabled. The domain may be
323 empty. *Note Envelope-from address::.
325 `dsn_notify (off|CONDITION)'
326 This command sets the condition(s) under which the mail system
327 should send DSN (Delivery Status Notification) messages. The
328 argument off disables explicit DSN requests, which means the mail
329 system decides when to send DSN messages. This is the default.
330 The CONDITION must be `never', to never request notification, or a
331 comma separated list (no spaces!) of one or more of the following:
332 `failure', to request notification on transmission failure,
333 `delay', to be notified of message delays, `success', to be
334 notified of successful transmission. The SMTP server must support
335 the DSN extension. *Note Delivery Status Notifications::.
337 `dsn_return (off|AMOUNT)'
338 This command controls how much of a mail should be returned in DSN
339 (Delivery Status Notification) messages. The argument off disables
340 explicit DSN requests, which means the mail system decides how
341 much of a mail it returns in DSN messages. This is the default.
342 The AMOUNT must be `headers', to just return the message headers,
343 or `full', to return the full mail. The SMTP server must support
344 the DSN extension. *Note Delivery Status Notifications::.
347 This command controls whether to remove or keep the Bcc header
348 when sending a mail. The default is to remove it. *Note Bcc
352 This command enables or disables logging to the specified file. An
353 empty argument disables this feature. The file name `-' directs
354 the log information to standard output. *Note Logging::.
356 `syslog [(on|off|FACILITY)]'
357 This command enables or disables syslog logging. The facility can
358 be one of `LOG_USER', `LOG_MAIL', `LOG_LOCAL0', ..., `LOG_LOCAL7'.
359 The default facility is `LOG_USER'. Syslog logging is disabled by
360 default. *Note Logging::.
363 File: msmtp.info, Node: Invocation, Next: Transport Layer Security, Prev: Configuration files, Up: Top
371 * Sendmail mode (default):
372 `msmtp [OPTION...] [--] RECIPIENT...'
373 `msmtp [OPTION...] -t [--] [RECIPIENT...]'
375 * Server information mode:
376 `msmtp [OPTION...] --serverinfo'
378 * Remote Message Queue Starting mode:
379 `msmtp [OPTION...] --rmqs=(HOST|@DOMAIN|#QUEUE)'
384 Options override configuration file settings. They are compatible with
385 sendmail where appropriate.
387 3.2.1 General options
388 ---------------------
391 Print version information. This includes information about the
392 library used for TLS/SSL support (if any), the library used for
393 authentication, the authentication mechanisms supported by this
394 library, and the default locations of the system and user
402 Print the configuration settings that would be used, but do not
403 take further action. An asterisk ('*') will be printed instead of
408 Print lots of debugging information, including the whole
409 conversation with the SMTP server. Be careful with this option:
410 the (potentially dangerous) output will not be sanitized, and your
411 password may get printed in an easily decodable format!
413 3.2.2 Changing the mode of operation
414 ------------------------------------
418 Print information about the SMTP server and exit. This includes
419 information about supported features (mail size limit,
420 authentication, TLS, DSN, ...) and about the TLS certificate (if
421 TLS is active). *Note Server information mode::.
423 `--rmqs=(HOST|@DOMAIN|#QUEUE)'
424 Send a Remote Message Queue Starting request for the given host,
425 domain, or queue to the SMTP server and exit. *Note Remote
426 Message Queue Starting mode::.
428 3.2.3 Configuration options
429 ---------------------------
431 Most options in this category correspond to a configuration file
432 command. Please refer to *note Configuration files:: for detailed
436 Use the given file instead of `~/.msmtprc' as the user
441 Use the given account instead of the account named `default'. This
442 option cannot be used together with the `--host' option. *Note
443 Choosing an account::.
446 Use this SMTP server with settings from the command line; do not
447 use any configuration file data. This option cannot be used
448 together with the `--account' option. It disables loading of
449 configuration files. *Note Choosing an account::.
452 Set the port number to connect to. *Note port::.
454 `--timeout=(off|SECONDS)'
455 Set a network timeout. *Note timeout::. For compatibility with
456 older versions, `--connect-timeout' is accepted as an alias for
459 `--protocol=(smtp|lmtp)'
460 Set the protocol. *Note protocol::.
462 `--domain=[ARGUMENT]'
463 Set the argument of the SMTP EHLO (or LMTP LHLO) command. *Note
466 `--auth[=(on|off|METHOD)]'
467 Enable or disable authentication and optionally choose the method.
471 Set or unset the user name for authentication. *Note user::.
474 Enable or disable TLS/SSL. *Note tls::.
476 `--tls-starttls[=(on|off)]'
477 Enable or disable STARTTLS for TLS encryption. *Note
480 `--tls-trust-file=[FILE]'
481 Set or unset a trust file for TLS encryption. *Note
484 `--tls-crl-file=[FILE]'
485 Set or unset a certificate revocation list (CRL) file for TLS.
486 *Note tls_crl_file::.
488 `--tls-key-file=[FILE]'
489 Set or unset a key file for TLS encryption. *Note tls_key_file::.
491 `--tls-cert-file=[FILE]'
492 Set or unset a cert file for TLS encryption. *Note tls_cert_file::.
494 `--tls-certcheck[=(on|off)]'
495 Enable or disable server certificate checks for TLS encryption.
496 *Note tls_certcheck::.
498 `--tls-force-sslv3[=(on|off)]'
499 Force TLS/SSL version SSLv3. *Note tls_force_sslv3::.
501 `--tls-min-dh-prime-bits=[BITS]'
502 Set or unset minimum bit size of the Diffie-Hellman (DH) prime.
503 *Note tls_min_dh_prime_bits::.
505 `--tls-priorities=[PRIORITIES]'
506 Set or unset TLS priorities. *Note tls_priorities::.
508 3.2.4 Options specific to sendmail mode
509 ---------------------------------------
511 `--auto-from[=(on|off)]'
512 Enable or disable automatic envelope-from addresses. The default
513 is off. *Note auto_from::.
517 Set the envelope-from address. It is only used when `auto_from' is
519 If no account was chosen yet (with `--account' or `--host'), this
520 option will choose the first account that has the given
521 envelope-from address (set with the `from' command). If no such
522 account is found, "default" is used. *Note Choosing an account::.
524 `--maildomain=[DOMAIN]'
525 Set the domain part for generated envelope-from addresses. It is
526 only used when `auto_from' is on. *Note maildomain::.
529 `--dsn-notify=(off|CONDITION)'
530 Set or unset DSN notification conditions. *Note dsn_notify::.
533 `--dsn-return=(off|AMOUNT)'
534 Set or unset the DSN notification amount. *Note dsn_return::.
535 Note that `hdrs' is accepted as an alias for `headers' to be
536 compatible with sendmail.
538 `--keepbcc[=(on|off)]'
539 Enable or disable the preservation of the Bcc header. *Note
544 Set or unset the log file. *Note logfile::.
546 `--syslog[=(on|off|FACILITY)]'
547 Enable or disable syslog logging. *Note syslog::.
551 Send the mail to the recipients given in the To, Cc, and Bcc
552 headers of the mail in addition to the recipients given on the
554 If any Resent- headers are present, then the addresses from any
555 Resent-To, Resent-Cc, and Resent-Bcc headers in the first block of
556 Resent- headers are used instead.
559 Read the envelope from address from the From header of the mail.
562 This marks the end of options. All following arguments will be
563 treated as recipient addresses, even if they start with a '-'.
565 The following options are accepted but ignored for sendmail
566 compatibility: `-BTYPE', `-bm', `-FNAME', `-G', `-hN', `-i', `-L TAG',
567 `-m', `-n', `-O option=VALUE', `-ox VALUE', `-v'
569 3.3 Choosing an account
570 =======================
572 There are three ways to choose the account to use. It depends on the
573 circumstances which method is the best.
575 1. `--account=ACCOUNT'
576 Use the given account. Command line settings override
577 configuration file settings.
580 Use only the settings from the command line; do not use any
581 configuration file data.
583 3. `--from=ADDRESS' or `--read-envelope-from'
584 Choose the first account from the system or user configuration
585 file that has a matching envelope-from address as specified by a
586 `from' command. This works only when neither `--account' nor
588 If none of the above options is used (or if no account has a
589 matching `from' command), then the account "default" is used.
594 The standard exit codes from `sysexits.h' are used.
599 ``SYSCONFDIR/msmtprc''
600 The system configuration file. Use the `--version' option to find
601 out what `SYSCONFDIR' is on your platform.
604 The default user configuration file.
606 ``~/.netrc' and `SYSCONFDIR/netrc''
607 The `netrc' file contains login information. If a password is not
608 found in the configuration file, msmtp will search it in
609 `~/.netrc' and `SYSCONFDIR' before prompting the user for it. The
610 syntax of `netrc' files is described in the `netrc(5)' or `ftp(1)'
617 These variables override the user's login name when constructing an
618 envelope-from address. `LOGNAME' is only used if `USER' is unset.
621 Directory to create temporary files in. If this is unset, a system
622 specific default directory is used.
623 A temporary file is only created when the `-t'/`--read-recipients'
624 or `--read-envelope-from' option is used. The file is then used to
625 buffer the headers of the mail (but not the body, so the file
626 won't get very large).
628 ``EMAIL', `SMTPSERVER''
629 These environment variables are used only if neither `--host' nor
630 `--account' is used and there is no default account defined in the
631 configuration files. In this case, the host name is taken from
632 `SMTPSERVER', and the envelope from address is taken from `EMAIL',
633 unless overridden by `--from' or `--read-envelope-from'. Currently
634 `SMTPSERVER' must contain a plain host name (no URL), and `EMAIL'
635 must contain a plain address (no names or additional information).
638 File: msmtp.info, Node: Transport Layer Security, Next: Authentication, Prev: Invocation, Up: Top
640 4 Transport Layer Security
641 **************************
643 Transport Layer Security (TLS) is a new name for Secure Socket Layer
644 (SSL). The TLS 1.0 protocol is an updated version of the SSL 3.0
645 protocol. TLS and SSL mean the same thing.
647 Quoting from RFC2246, the TLS 1.0 protocol specification:
648 "The TLS protocol provides communications privacy over the Internet.
649 The protocol allows client/server applications to communicate in a way
650 that is designed to prevent eavesdropping, tampering, or message
653 SMTP servers can use TLS in one of two modes:
654 * Immediately. This is SMTP tunneled through TLS, aka SSMTP. The
655 default port for this mode is 465 (ssmtp).
657 * Via the STARTTLS SMTP command. The SMTP session begins normally.
658 The client sends the STARTTLS command when it wishes to begin TLS
659 encryption. The default port for this mode is the default SMTP
661 msmtp can switch between these modes with the `tls_starttls' command
662 (see *note tls_starttls::) command or the `--tls-starttls' option (see
663 *note --tls-starttls::).
665 When TLS is started, the server sends a certificate to identify
666 itself. This certificate contains information about the certificate
667 owner, the certificate issuer, and the activation and expiration times
668 of the certificate. This information can be displayed in server
669 information mode. *Note Server information mode::.
671 To use TLS, it is required to either enable full server certificate
672 verification using the `tls_trust_file' command or `--tls-trust-file'
673 option, or to disable all certificate checks using `tls_certcheck off'
674 or `--tls-certcheck=off'. WARNING: When certificate checks are disabled,
675 TLS/SSL sessions are vulnerable to man-in-the-middle attacks! See
676 *note tls_trust_file::, *note --tls-trust-file::, *note tls_certcheck::,
677 *note --tls-certcheck::.
679 If your system has a file that collects all system-wide trusted CA
680 certificates, it is easiest to just use this in the `defaults' section
681 of your configuration file. On Debian-based systems, for example, the
682 adequate command would be `tls_trust_file
683 /etc/ssl/certs/ca-certificates.crt'.
685 But you can also find out manually which CA certificate you need to
686 trust. The following example works as of 2007-04-18.
688 For the Gmail SMTP server, you first issue the following command:
689 $ msmtp --serverinfo --host=smtp.gmail.com --tls=on --port=587 \
691 The option `--port=587' is specific to Gmail and should not be used
692 with other servers. The option `--tls-certcheck=off' allows msmtp to
693 accept any certificate, so that it can print some information about it.
695 According to the output of this command, the common name of the
696 server certificate issuer is "Thawte Premium Server CA". This means
697 that you have to trust the Thawte CA to use full TLS security. You can
698 download the Thawte CA certificate bundle from
699 `http://thawte.com/roots'. You get a ZIP file with different
700 certificates. The one you need for the `tls_trust_file' command is
701 `Thawte Server Roots/ThawtePremiumServerCA_b64.txt'.
703 The following command should now succeed:
704 $ msmtp --serverinfo --host=smtp.gmail.com --tls=on --port=587 \
705 --tls-trust-file="Thawte Server Roots/ThawtePremiumServerCA_b64.txt"
707 If the server requests it, the client can send a certificate, too.
708 This allows the server to verify the identity of the client. See the
709 EXTERNAL mechanism in *note Authentication::. The
710 `tls_key_file'/`tls_cert_file' commands or the
711 `--tls-key-file'/`--tls-cert-file' options can be used to set a client
712 certificate. See *note tls_key_file::/*note --tls-key-file::, *note
713 tls_cert_file::/*note --tls-cert-file::. Note that GnuTLS will only
714 send a client certificate if it matches one of the CAs advertised by
715 the server. If you set a client certificate but it is not send to the
716 server, it probably was not issued by any CA that the server trusts.
718 If you need to fine tune TLS parameters or have problems connecting
719 to your server, have a look at the *note tls_force_sslv3::, *note
720 tls_min_dh_prime_bits::, and *note tls_priorities:: commands.
723 File: msmtp.info, Node: Authentication, Next: Delivery Status Notifications, Prev: Transport Layer Security, Up: Top
728 Many SMTP servers require a client to authenticate itself before it is
729 allowed to send mail.
731 Multiple authentication methods exist. Most SMTP servers support
732 only some of them. Some methods send authentication data in plain text
733 (or nearly plain text) to the server. These methods should only be used
734 when TLS is active to prevent others from stealing the password. *Note
735 Transport Layer Security::.
737 By default, msmtp chooses a method automatically, and it will never
738 choose one that puts the authentication data at risk. See below for
741 msmtp supports the following authentication methods:
743 This authentication method needs a user name and a password. Both
744 are send in BASE64 encoding, which can be easily decoded to plain
748 This authentication method needs a user name and a password. The
749 authentication data is not sent in plain text, which means this
750 method can safely be used without TLS.
753 This authentication method needs a user name and a password. The
754 authentication data is not sent in plain text, which means this
755 method can safely be used without TLS.
758 This authentication method needs a user name. The Kerberos
759 framework takes care of secure authentication, therefore this
760 method can safely be used without TLS.
763 This is a special authentication method: The actual authentication
764 happens outside of the SMTP protocol, typically by sending a TLS
765 client certificate (see *note Transport Layer Security::).
766 The EXTERNAL method merely confirms that this authentication
767 succeeded for the given user (or, if no user name is given,
768 confirms that authentication succeeded). Thus it may not be
769 necessary for authentication to use this method, and if the server
770 does not support the EXTERNAL method, this does not mean that it
771 does not support authentication with TLS client certificates.
772 This authentication method is not chosen automatically; you have
773 to request it manually.
774 Note: Sendmail 8.12.11 advertises the EXTERNAL mechanism only
775 after a TLS client certificate has been send. It seems to ignore
776 the optional user name. Does anyone know more about this?
779 This is a non-standard authentication method similar to (but worse
780 than) PLAIN. It needs a user name and a password, both of which
781 are send in BASE64 encoding, which can be easily decoded to plain
785 This is an obscure non-standard authentication method. It needs a
786 user name and a password and in some cases a special domain
787 parameter (see *note ntlmdomain::). The authentication data is
788 not send in plain text, but since NTLM is not an open standard, it
789 should be considered broken and insecure.
791 It depends on the underlying authentication library and its version
792 whether a particular method is supported or not. Use the `--version' to
793 find out which methods are supported by your version of msmtp.
795 Authentication data can be set with the `user' and `password'
796 commands or with the `--user' option. See *note user::, *note
797 password::, *note --user::. If no password is set but one is needed
798 during authentication, msmtp will try to find it in `~/.netrc'. If that
799 fails, it will try to find it in `SYSCONFDIR/netrc' (use `--version' to
800 find out what `SYSCONFDIR' is on your platform). If that fails, it will
801 try to get it from a system specific keychain (if available). If that
802 fails but a controlling terminal is available, msmtp will prompt you
805 Currently supported keychains are the GNOME keychain and the Mac OS
806 X keychain. *Note Using the Mac OS X Keychain::.
808 The authentication method can be chosen with the `auth' command or
809 `--auth' option, but it is usually sufficient to just use the `on'
810 argument to let msmtp choose the method itself. See *note auth::, *note
813 If msmtp chooses the method itself, it will never choose an insecure
814 method. If TLS is active, all methods are considered secure in this
815 context, because the connection to the server is protected by TLS. If
816 TLS is not active, only the CRAM-MD5, DIGEST-MD5, and GSSAPI methods
817 are considered secure in this context, because all the others methods
818 put the authentication data at risk.
820 If you really want to risk your authentication data, you have to
821 force msmtp to do that by manually setting the authentication method
824 5.1 Using the Mac OS X Keychain
825 ===============================
827 A Mac OS X user can store a password in a keychain item using the
828 Keychain Access GUI application. The `account name' is simply the value
829 of the msmtp `user' argument. However, the `keychain item name' is
830 `smtp://<hostname>' where `<hostname>' matches the msmtp `host'
831 argument. Using `smtp://' is needed so that the item is created of kind
832 `internet password'. For example, selecting `File->Get Info' on a
833 keychain item that corresponds to `host smtp.freemail.example' and
834 `user joe.smith' will show:
836 Name: smtp.freemail.example
837 Kind: Internet password
839 Where: smtp://smtp.freemail.example
842 File: msmtp.info, Node: Delivery Status Notifications, Next: Sendmail mode, Prev: Authentication, Up: Top
844 6 Delivery Status Notifications
845 *******************************
847 In situations such as delivery failure or very long delivery delay, the
848 mail system often generates a message for the sender of the mail in
849 question, informing him about the difficulties.
851 Delivery Status Notification (DSN) requests, defined in RFC 3461,
852 try to give the sender of the mail control about how and when these DSN
853 messages are sent. The SMTP server must support the DSN extension.
854 *Note Server information mode::.
856 A first parameter controls when such messages should be generated:
857 never, on delivery failure, on delivery delay, and/or on success. This
858 can be set with `dsn_notify'/`--dsn-notify', see *note
859 dsn_notify::/*note --dsn-notify::.
861 A second parameter controls how much of the original mail should be
862 contained in a DSN message: only the headers, or the full mail. This
863 can be set with `dsn_return'/`--dsn-return', see *note
864 dsn_return::/*note --dsn-return::. Note that this parameter only
865 applies to DSNs that indicate delivery failure for at least one
866 recipient. If a DSN contains no indications of delivery failure, only
867 the headers of the message are returned.
870 File: msmtp.info, Node: Sendmail mode, Next: Server information mode, Prev: Delivery Status Notifications, Up: Top
877 * Envelope-from address:: Information about envelope-from addresses
878 * Logging:: Different logging methods
879 * Bcc header:: Bcc header handling
882 File: msmtp.info, Node: Envelope-from address, Next: Logging, Up: Sendmail mode
884 7.1 Envelope-from address
885 =========================
887 The SMTP server expects a sender mail address for each mail. This is the
888 envelope-from address. It is independent of the From header (because it
889 is part of the mail _envelope_, not of the mail itself), but in most
890 cases both addresses are the same.
892 Envelope-from addresses can be generated automatically (when
893 `auto_from' is enabled with the `auto_from' command or `--auto-from'
894 option) or set explicitly with the `from' command and `--from' option.
895 See *note auto_from::, *note from::.
897 When `auto_from' is enabled, an envelope-from address of the form
898 user@domain will be generated. The local part will be set to `USER' or,
899 if that fails, to `LOGNAME' or, if that fails, to the login name of the
900 current user. The domain part can be set with the `maildomain' command
901 and `--maildomain' option (see *note maildomain::). If the maildomain
902 is empty, the envelope-from address will only consist of the user name
903 and not have a domain part.
906 File: msmtp.info, Node: Logging, Next: Bcc header, Prev: Envelope-from address, Up: Sendmail mode
911 Logging is enabled on a per account basis. If it is enabled, msmtp will
912 generate one log line for each mail it tries to send via the account in
915 The line will include the following information:
916 * Host name of the SMTP server: `host=hostname'
918 * Whether TLS was used: `tls=(on|off)'
920 * Whether authentication was used: `auth=(on|off)'
922 * The user name used for authentication (only if authentication is
925 * The envelope-from address: `from=address'
927 * The recipient addresses: `recipients=addr1,addr2,...'
929 * The size of the mail as transferred to the server, in bytes (only
930 if the delivery succeeded): `mailsize=number'
932 * The SMTP status code and SMTP error message (only in case of
933 failure and only if available): `smtpstatus=number',
934 `smtpmsg='message''. Multiline SMTP messages will be concatenated
937 * The msmtp error message (only in case of failure and only if
938 available): `errormsg='message''
940 * The msmtp exit code (from `sysexits.h'; `EX_OK' indicates
941 success): `exitcode=EX_...'
943 If a logfile is given with the `logfile' command or `--logfile'
944 option, this log line will be prepended with the current date and time
945 and appended to the specified file. See *note logfile::, *note
948 If syslog logging is enabled with the `syslog' command or `--syslog'
949 option, the log line is passed to the syslog service with the specified
950 facility. See *note syslog::, *note --syslog::.
953 File: msmtp.info, Node: Bcc header, Prev: Logging, Up: Sendmail mode
958 msmtp transmits mails unaltered to the SMTP server, with one exception:
959 the Bcc header(s) will be removed before the transmission. This
960 behavior can be changed with the `keepbcc' command and `--keepbcc'
961 option, see *note keepbcc::/*note --keepbcc::.
964 File: msmtp.info, Node: Server information mode, Next: Remote Message Queue Starting mode, Prev: Sendmail mode, Up: Top
966 8 Server information mode
967 *************************
969 In server information mode, msmtp prints as much information about the
970 SMTP server as it can get and then exits.
972 The SMTP features that can be detected are:
974 The maximum message size that the SMTP server accepts.
977 Whether certain SMTP commands may be send in groups rather than
978 one by one. This can speed up mail transmission if the recipient
979 list is long. This feature is used automatically.
982 *Note Transport Layer Security::.
985 *Note Authentication::.
988 *Note Delivery Status Notifications::.
991 *Note Remote Message Queue Starting mode::.
993 If TLS is activated for server information mode, the following
994 information will be printed about the SMTP server's TLS certificate (if
1001 * Organizational unit
1009 * Issuer information
1014 * Organizational unit
1032 File: msmtp.info, Node: Remote Message Queue Starting mode, Next: Examples, Prev: Server information mode, Up: Top
1034 9 Remote Message Queue Starting mode
1035 ************************************
1037 Remote Message Queue Starting (RMQS) is defined in RFC 1985. It is a
1038 way for a client to request that a server start the processing of its
1039 mail queues for messages that are waiting at the server for the client
1040 machine. If any messages are at the server for the client, then the
1041 server creates a new SMTP session and sends the messages at that time.
1043 msmtp can only send the request (using the ETRN SMTP command); a
1044 mail server on the client side should then accept the connection of the
1045 remote SMTP server to receive the mail.
1047 RMQS requests can be sent with the `--rmqs' option (see *note
1048 --rmqs::). Destinations defined in RFC 1985 are:
1050 Request the messages for the given host.
1053 Request the messages for the given domain.
1056 Request the delivery of the messages in the given queue.
1059 File: msmtp.info, Node: Examples, Next: Development, Prev: Remote Message Queue Starting mode, Up: Top
1066 * A system wide configuration file::
1067 * A user configuration file::
1068 * Using msmtp with Mutt::
1069 * Using msmtp with mail::
1072 File: msmtp.info, Node: A system wide configuration file, Next: A user configuration file, Up: Examples
1074 10.1 A system wide configuration file
1075 =====================================
1077 # A system wide configuration is optional.
1078 # If it exists, it usually defines a default account.
1079 # This allows msmtp to be used like /usr/sbin/sendmail.
1082 # The SMTP smarthost.
1083 host mailhub.oursite.example
1085 # Construct envelope-from addresses of the form "user@oursite.example".
1087 #maildomain oursite.example
1091 #tls_trust_file /etc/ssl/certs/ca-certificates.crt
1093 # Syslog logging with facility LOG_MAIL instead of the default LOG_USER.
1097 File: msmtp.info, Node: A user configuration file, Next: Using msmtp with Mutt, Prev: A system wide configuration file, Up: Examples
1099 10.2 A user configuration file
1100 ==============================
1102 # Set default values for all following accounts.
1105 tls_trust_file /etc/ssl/certs/ca-certificates.crt
1106 logfile ~/.msmtp.log
1108 # A freemail service
1110 host smtp.freemail.example
1111 from joe_smith@freemail.example
1116 # A second mail address at the same freemail service
1117 account freemail2 : freemail
1118 from joey@freemail.example
1120 # The SMTP server of the provider.
1122 host mail.provider.example
1123 from smithjoe@provider.example
1128 # Set a default account
1129 account default : provider
1132 File: msmtp.info, Node: Using msmtp with Mutt, Next: Using msmtp with mail, Prev: A user configuration file, Up: Examples
1134 10.3 Using msmtp with Mutt
1135 ==========================
1137 Create a configuration file for msmtp and add the following lines to
1138 your Mutt configuration file:
1139 set sendmail="/path/to/msmtp"
1141 set realname="Your Name"
1142 set from=you@example.com
1143 set envelope_from=yes
1145 The `envelope_from=yes' option lets Mutt use the `-f' option of
1146 msmtp. Therefore msmtp chooses the first account that matches the from
1147 address you@example.com. Alternatively, you can use the `-a' option:
1148 set sendmail="/path/to/msmtp -a my_account"
1150 Or set everything from the command line:
1151 set sendmail="/path/to/msmtp --host=mailhub -f me@example.com --tls"
1152 *Note Choosing an account::.
1154 If you have multiple mail accounts in your msmtp configuration file
1155 and let Mutt use the `-f' option to choose one, you can easily switch
1156 accounts in Mutt with the following Mutt configuration lines:
1157 macro generic "<esc>1" ":set from=you@example.com"
1158 macro generic "<esc>2" ":set from=you@your-employer.example"
1159 macro generic "<esc>3" ":set from=you@some-other-provider.example"
1160 Now you can use <esc>1, <esc>2, and <esc>3 to switch accounts.
1162 The following example uses a different approach: it maps the single
1163 key `<tab>' in Compose context for switching between the various
1164 account in a handy visual way. In the same Compose context, `=' is
1165 mapped in order to show the current msmtp account. This example was
1166 contributed by Thomas Baruchel.
1167 # Define <tab> and = in order to switch or see the current msmtp account
1168 # Don't forget to put the right path for msmtp binary
1169 macro compose \Cx_ ":set sendmail"
1170 macro compose \Cx| "\Cx_ = \"/usr/local/bin/msmtp"
1171 macro compose \Cx& ":macro compose \\t \\Cx"
1172 macro compose <tab> "\Cx0"
1173 macro compose = "\Cx_\n"
1174 # Put the account in the following lines (here three accounts)
1175 # Don't forget to put the number of the account at the beginning
1176 # of the line, and the number of the next account after the '&'
1177 macro compose \Cx0 "\Cx|\"\n\Cx&1\n\Cx_\n" # default and switch to 1
1178 macro compose \Cx1 "\Cx| -a example_account\"\n\Cx&2\n\Cx_\n" # switch to 2
1179 macro compose \Cx2 "\Cx| -a gmail\"\n\Cx&0\n\Cx_\n" # switch to 0
1180 # End of the accounts
1183 File: msmtp.info, Node: Using msmtp with mail, Prev: Using msmtp with Mutt, Up: Examples
1185 10.4 Using msmtp with mail
1186 ==========================
1188 Define a default account, and put the following into `~/.mailrc':
1189 set sendmail="/path/to/msmtp"
1191 You need to define a default account, because mail does not allow
1192 extra options to the msmtp command line.
1195 File: msmtp.info, Node: Development, Next: Copying Information, Prev: Examples, Up: Top
1200 The homepage of msmtp is `http://msmtp.sourceforge.net/'; the
1201 SourceForge project page is `http://sourceforge.net/projects/msmtp/'.
1203 The mailing list `msmtp-users' can be accessed from the project page.
1205 Please send any questions, suggestions, and bug reports either to
1206 the mailing list or to Martin Lambers (<marlam@marlam.de>, OpenPGP key:
1207 `http://www.marlam.de/key.txt'). If you send a bug report, please
1208 include the output of `msmtp --version'.
1211 File: msmtp.info, Node: Copying Information, Prev: Development, Up: Top
1213 Appendix A Copying Information
1214 ******************************
1218 * GNU Free Documentation License:: License for copying this manual.
1219 * GNU GPL:: License for copying the program.
1222 File: msmtp.info, Node: GNU Free Documentation License, Next: GNU GPL, Up: Copying Information
1224 GNU Free Documentation License
1225 ==============================
1227 Version 1.2, November 2002
1229 Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
1230 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
1232 Everyone is permitted to copy and distribute verbatim copies
1233 of this license document, but changing it is not allowed.
1237 The purpose of this License is to make a manual, textbook, or other
1238 functional and useful document "free" in the sense of freedom: to
1239 assure everyone the effective freedom to copy and redistribute it,
1240 with or without modifying it, either commercially or
1241 noncommercially. Secondarily, this License preserves for the
1242 author and publisher a way to get credit for their work, while not
1243 being considered responsible for modifications made by others.
1245 This License is a kind of "copyleft", which means that derivative
1246 works of the document must themselves be free in the same sense.
1247 It complements the GNU General Public License, which is a copyleft
1248 license designed for free software.
1250 We have designed this License in order to use it for manuals for
1251 free software, because free software needs free documentation: a
1252 free program should come with manuals providing the same freedoms
1253 that the software does. But this License is not limited to
1254 software manuals; it can be used for any textual work, regardless
1255 of subject matter or whether it is published as a printed book.
1256 We recommend this License principally for works whose purpose is
1257 instruction or reference.
1259 1. APPLICABILITY AND DEFINITIONS
1261 This License applies to any manual or other work, in any medium,
1262 that contains a notice placed by the copyright holder saying it
1263 can be distributed under the terms of this License. Such a notice
1264 grants a world-wide, royalty-free license, unlimited in duration,
1265 to use that work under the conditions stated herein. The
1266 "Document", below, refers to any such manual or work. Any member
1267 of the public is a licensee, and is addressed as "you". You
1268 accept the license if you copy, modify or distribute the work in a
1269 way requiring permission under copyright law.
1271 A "Modified Version" of the Document means any work containing the
1272 Document or a portion of it, either copied verbatim, or with
1273 modifications and/or translated into another language.
1275 A "Secondary Section" is a named appendix or a front-matter section
1276 of the Document that deals exclusively with the relationship of the
1277 publishers or authors of the Document to the Document's overall
1278 subject (or to related matters) and contains nothing that could
1279 fall directly within that overall subject. (Thus, if the Document
1280 is in part a textbook of mathematics, a Secondary Section may not
1281 explain any mathematics.) The relationship could be a matter of
1282 historical connection with the subject or with related matters, or
1283 of legal, commercial, philosophical, ethical or political position
1286 The "Invariant Sections" are certain Secondary Sections whose
1287 titles are designated, as being those of Invariant Sections, in
1288 the notice that says that the Document is released under this
1289 License. If a section does not fit the above definition of
1290 Secondary then it is not allowed to be designated as Invariant.
1291 The Document may contain zero Invariant Sections. If the Document
1292 does not identify any Invariant Sections then there are none.
1294 The "Cover Texts" are certain short passages of text that are
1295 listed, as Front-Cover Texts or Back-Cover Texts, in the notice
1296 that says that the Document is released under this License. A
1297 Front-Cover Text may be at most 5 words, and a Back-Cover Text may
1298 be at most 25 words.
1300 A "Transparent" copy of the Document means a machine-readable copy,
1301 represented in a format whose specification is available to the
1302 general public, that is suitable for revising the document
1303 straightforwardly with generic text editors or (for images
1304 composed of pixels) generic paint programs or (for drawings) some
1305 widely available drawing editor, and that is suitable for input to
1306 text formatters or for automatic translation to a variety of
1307 formats suitable for input to text formatters. A copy made in an
1308 otherwise Transparent file format whose markup, or absence of
1309 markup, has been arranged to thwart or discourage subsequent
1310 modification by readers is not Transparent. An image format is
1311 not Transparent if used for any substantial amount of text. A
1312 copy that is not "Transparent" is called "Opaque".
1314 Examples of suitable formats for Transparent copies include plain
1315 ASCII without markup, Texinfo input format, LaTeX input format,
1316 SGML or XML using a publicly available DTD, and
1317 standard-conforming simple HTML, PostScript or PDF designed for
1318 human modification. Examples of transparent image formats include
1319 PNG, XCF and JPG. Opaque formats include proprietary formats that
1320 can be read and edited only by proprietary word processors, SGML or
1321 XML for which the DTD and/or processing tools are not generally
1322 available, and the machine-generated HTML, PostScript or PDF
1323 produced by some word processors for output purposes only.
1325 The "Title Page" means, for a printed book, the title page itself,
1326 plus such following pages as are needed to hold, legibly, the
1327 material this License requires to appear in the title page. For
1328 works in formats which do not have any title page as such, "Title
1329 Page" means the text near the most prominent appearance of the
1330 work's title, preceding the beginning of the body of the text.
1332 A section "Entitled XYZ" means a named subunit of the Document
1333 whose title either is precisely XYZ or contains XYZ in parentheses
1334 following text that translates XYZ in another language. (Here XYZ
1335 stands for a specific section name mentioned below, such as
1336 "Acknowledgements", "Dedications", "Endorsements", or "History".)
1337 To "Preserve the Title" of such a section when you modify the
1338 Document means that it remains a section "Entitled XYZ" according
1341 The Document may include Warranty Disclaimers next to the notice
1342 which states that this License applies to the Document. These
1343 Warranty Disclaimers are considered to be included by reference in
1344 this License, but only as regards disclaiming warranties: any other
1345 implication that these Warranty Disclaimers may have is void and
1346 has no effect on the meaning of this License.
1350 You may copy and distribute the Document in any medium, either
1351 commercially or noncommercially, provided that this License, the
1352 copyright notices, and the license notice saying this License
1353 applies to the Document are reproduced in all copies, and that you
1354 add no other conditions whatsoever to those of this License. You
1355 may not use technical measures to obstruct or control the reading
1356 or further copying of the copies you make or distribute. However,
1357 you may accept compensation in exchange for copies. If you
1358 distribute a large enough number of copies you must also follow
1359 the conditions in section 3.
1361 You may also lend copies, under the same conditions stated above,
1362 and you may publicly display copies.
1364 3. COPYING IN QUANTITY
1366 If you publish printed copies (or copies in media that commonly
1367 have printed covers) of the Document, numbering more than 100, and
1368 the Document's license notice requires Cover Texts, you must
1369 enclose the copies in covers that carry, clearly and legibly, all
1370 these Cover Texts: Front-Cover Texts on the front cover, and
1371 Back-Cover Texts on the back cover. Both covers must also clearly
1372 and legibly identify you as the publisher of these copies. The
1373 front cover must present the full title with all words of the
1374 title equally prominent and visible. You may add other material
1375 on the covers in addition. Copying with changes limited to the
1376 covers, as long as they preserve the title of the Document and
1377 satisfy these conditions, can be treated as verbatim copying in
1380 If the required texts for either cover are too voluminous to fit
1381 legibly, you should put the first ones listed (as many as fit
1382 reasonably) on the actual cover, and continue the rest onto
1385 If you publish or distribute Opaque copies of the Document
1386 numbering more than 100, you must either include a
1387 machine-readable Transparent copy along with each Opaque copy, or
1388 state in or with each Opaque copy a computer-network location from
1389 which the general network-using public has access to download
1390 using public-standard network protocols a complete Transparent
1391 copy of the Document, free of added material. If you use the
1392 latter option, you must take reasonably prudent steps, when you
1393 begin distribution of Opaque copies in quantity, to ensure that
1394 this Transparent copy will remain thus accessible at the stated
1395 location until at least one year after the last time you
1396 distribute an Opaque copy (directly or through your agents or
1397 retailers) of that edition to the public.
1399 It is requested, but not required, that you contact the authors of
1400 the Document well before redistributing any large number of
1401 copies, to give them a chance to provide you with an updated
1402 version of the Document.
1406 You may copy and distribute a Modified Version of the Document
1407 under the conditions of sections 2 and 3 above, provided that you
1408 release the Modified Version under precisely this License, with
1409 the Modified Version filling the role of the Document, thus
1410 licensing distribution and modification of the Modified Version to
1411 whoever possesses a copy of it. In addition, you must do these
1412 things in the Modified Version:
1414 A. Use in the Title Page (and on the covers, if any) a title
1415 distinct from that of the Document, and from those of
1416 previous versions (which should, if there were any, be listed
1417 in the History section of the Document). You may use the
1418 same title as a previous version if the original publisher of
1419 that version gives permission.
1421 B. List on the Title Page, as authors, one or more persons or
1422 entities responsible for authorship of the modifications in
1423 the Modified Version, together with at least five of the
1424 principal authors of the Document (all of its principal
1425 authors, if it has fewer than five), unless they release you
1426 from this requirement.
1428 C. State on the Title page the name of the publisher of the
1429 Modified Version, as the publisher.
1431 D. Preserve all the copyright notices of the Document.
1433 E. Add an appropriate copyright notice for your modifications
1434 adjacent to the other copyright notices.
1436 F. Include, immediately after the copyright notices, a license
1437 notice giving the public permission to use the Modified
1438 Version under the terms of this License, in the form shown in
1441 G. Preserve in that license notice the full lists of Invariant
1442 Sections and required Cover Texts given in the Document's
1445 H. Include an unaltered copy of this License.
1447 I. Preserve the section Entitled "History", Preserve its Title,
1448 and add to it an item stating at least the title, year, new
1449 authors, and publisher of the Modified Version as given on
1450 the Title Page. If there is no section Entitled "History" in
1451 the Document, create one stating the title, year, authors,
1452 and publisher of the Document as given on its Title Page,
1453 then add an item describing the Modified Version as stated in
1454 the previous sentence.
1456 J. Preserve the network location, if any, given in the Document
1457 for public access to a Transparent copy of the Document, and
1458 likewise the network locations given in the Document for
1459 previous versions it was based on. These may be placed in
1460 the "History" section. You may omit a network location for a
1461 work that was published at least four years before the
1462 Document itself, or if the original publisher of the version
1463 it refers to gives permission.
1465 K. For any section Entitled "Acknowledgements" or "Dedications",
1466 Preserve the Title of the section, and preserve in the
1467 section all the substance and tone of each of the contributor
1468 acknowledgements and/or dedications given therein.
1470 L. Preserve all the Invariant Sections of the Document,
1471 unaltered in their text and in their titles. Section numbers
1472 or the equivalent are not considered part of the section
1475 M. Delete any section Entitled "Endorsements". Such a section
1476 may not be included in the Modified Version.
1478 N. Do not retitle any existing section to be Entitled
1479 "Endorsements" or to conflict in title with any Invariant
1482 O. Preserve any Warranty Disclaimers.
1484 If the Modified Version includes new front-matter sections or
1485 appendices that qualify as Secondary Sections and contain no
1486 material copied from the Document, you may at your option
1487 designate some or all of these sections as invariant. To do this,
1488 add their titles to the list of Invariant Sections in the Modified
1489 Version's license notice. These titles must be distinct from any
1490 other section titles.
1492 You may add a section Entitled "Endorsements", provided it contains
1493 nothing but endorsements of your Modified Version by various
1494 parties--for example, statements of peer review or that the text
1495 has been approved by an organization as the authoritative
1496 definition of a standard.
1498 You may add a passage of up to five words as a Front-Cover Text,
1499 and a passage of up to 25 words as a Back-Cover Text, to the end
1500 of the list of Cover Texts in the Modified Version. Only one
1501 passage of Front-Cover Text and one of Back-Cover Text may be
1502 added by (or through arrangements made by) any one entity. If the
1503 Document already includes a cover text for the same cover,
1504 previously added by you or by arrangement made by the same entity
1505 you are acting on behalf of, you may not add another; but you may
1506 replace the old one, on explicit permission from the previous
1507 publisher that added the old one.
1509 The author(s) and publisher(s) of the Document do not by this
1510 License give permission to use their names for publicity for or to
1511 assert or imply endorsement of any Modified Version.
1513 5. COMBINING DOCUMENTS
1515 You may combine the Document with other documents released under
1516 this License, under the terms defined in section 4 above for
1517 modified versions, provided that you include in the combination
1518 all of the Invariant Sections of all of the original documents,
1519 unmodified, and list them all as Invariant Sections of your
1520 combined work in its license notice, and that you preserve all
1521 their Warranty Disclaimers.
1523 The combined work need only contain one copy of this License, and
1524 multiple identical Invariant Sections may be replaced with a single
1525 copy. If there are multiple Invariant Sections with the same name
1526 but different contents, make the title of each such section unique
1527 by adding at the end of it, in parentheses, the name of the
1528 original author or publisher of that section if known, or else a
1529 unique number. Make the same adjustment to the section titles in
1530 the list of Invariant Sections in the license notice of the
1533 In the combination, you must combine any sections Entitled
1534 "History" in the various original documents, forming one section
1535 Entitled "History"; likewise combine any sections Entitled
1536 "Acknowledgements", and any sections Entitled "Dedications". You
1537 must delete all sections Entitled "Endorsements."
1539 6. COLLECTIONS OF DOCUMENTS
1541 You may make a collection consisting of the Document and other
1542 documents released under this License, and replace the individual
1543 copies of this License in the various documents with a single copy
1544 that is included in the collection, provided that you follow the
1545 rules of this License for verbatim copying of each of the
1546 documents in all other respects.
1548 You may extract a single document from such a collection, and
1549 distribute it individually under this License, provided you insert
1550 a copy of this License into the extracted document, and follow
1551 this License in all other respects regarding verbatim copying of
1554 7. AGGREGATION WITH INDEPENDENT WORKS
1556 A compilation of the Document or its derivatives with other
1557 separate and independent documents or works, in or on a volume of
1558 a storage or distribution medium, is called an "aggregate" if the
1559 copyright resulting from the compilation is not used to limit the
1560 legal rights of the compilation's users beyond what the individual
1561 works permit. When the Document is included in an aggregate, this
1562 License does not apply to the other works in the aggregate which
1563 are not themselves derivative works of the Document.
1565 If the Cover Text requirement of section 3 is applicable to these
1566 copies of the Document, then if the Document is less than one half
1567 of the entire aggregate, the Document's Cover Texts may be placed
1568 on covers that bracket the Document within the aggregate, or the
1569 electronic equivalent of covers if the Document is in electronic
1570 form. Otherwise they must appear on printed covers that bracket
1571 the whole aggregate.
1575 Translation is considered a kind of modification, so you may
1576 distribute translations of the Document under the terms of section
1577 4. Replacing Invariant Sections with translations requires special
1578 permission from their copyright holders, but you may include
1579 translations of some or all Invariant Sections in addition to the
1580 original versions of these Invariant Sections. You may include a
1581 translation of this License, and all the license notices in the
1582 Document, and any Warranty Disclaimers, provided that you also
1583 include the original English version of this License and the
1584 original versions of those notices and disclaimers. In case of a
1585 disagreement between the translation and the original version of
1586 this License or a notice or disclaimer, the original version will
1589 If a section in the Document is Entitled "Acknowledgements",
1590 "Dedications", or "History", the requirement (section 4) to
1591 Preserve its Title (section 1) will typically require changing the
1596 You may not copy, modify, sublicense, or distribute the Document
1597 except as expressly provided for under this License. Any other
1598 attempt to copy, modify, sublicense or distribute the Document is
1599 void, and will automatically terminate your rights under this
1600 License. However, parties who have received copies, or rights,
1601 from you under this License will not have their licenses
1602 terminated so long as such parties remain in full compliance.
1604 10. FUTURE REVISIONS OF THIS LICENSE
1606 The Free Software Foundation may publish new, revised versions of
1607 the GNU Free Documentation License from time to time. Such new
1608 versions will be similar in spirit to the present version, but may
1609 differ in detail to address new problems or concerns. See
1610 `http://www.gnu.org/copyleft/'.
1612 Each version of the License is given a distinguishing version
1613 number. If the Document specifies that a particular numbered
1614 version of this License "or any later version" applies to it, you
1615 have the option of following the terms and conditions either of
1616 that specified version or of any later version that has been
1617 published (not as a draft) by the Free Software Foundation. If
1618 the Document does not specify a version number of this License,
1619 you may choose any version ever published (not as a draft) by the
1620 Free Software Foundation.
1622 ADDENDUM: How to use this License for your documents
1623 ====================================================
1625 To use this License in a document you have written, include a copy of
1626 the License in the document and put the following copyright and license
1627 notices just after the title page:
1629 Copyright (C) YEAR YOUR NAME.
1630 Permission is granted to copy, distribute and/or modify this document
1631 under the terms of the GNU Free Documentation License, Version 1.2
1632 or any later version published by the Free Software Foundation;
1633 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
1634 Texts. A copy of the license is included in the section entitled ``GNU
1635 Free Documentation License''.
1637 If you have Invariant Sections, Front-Cover Texts and Back-Cover
1638 Texts, replace the "with...Texts." line with this:
1640 with the Invariant Sections being LIST THEIR TITLES, with
1641 the Front-Cover Texts being LIST, and with the Back-Cover Texts
1644 If you have Invariant Sections without Cover Texts, or some other
1645 combination of the three, merge those two alternatives to suit the
1648 If your document contains nontrivial examples of program code, we
1649 recommend releasing these examples in parallel under your choice of
1650 free software license, such as the GNU General Public License, to
1651 permit their use in free software.
1654 File: msmtp.info, Node: GNU GPL, Prev: GNU Free Documentation License, Up: Copying Information
1659 Version 3, 29 June 2007
1661 Copyright (C) 2007 Free Software Foundation, Inc. `http://fsf.org/'
1663 Everyone is permitted to copy and distribute verbatim copies of this
1664 license document, but changing it is not allowed.
1669 The GNU General Public License is a free, copyleft license for software
1670 and other kinds of works.
1672 The licenses for most software and other practical works are designed
1673 to take away your freedom to share and change the works. By contrast,
1674 the GNU General Public License is intended to guarantee your freedom to
1675 share and change all versions of a program--to make sure it remains
1676 free software for all its users. We, the Free Software Foundation, use
1677 the GNU General Public License for most of our software; it applies
1678 also to any other work released this way by its authors. You can apply
1679 it to your programs, too.
1681 When we speak of free software, we are referring to freedom, not
1682 price. Our General Public Licenses are designed to make sure that you
1683 have the freedom to distribute copies of free software (and charge for
1684 them if you wish), that you receive source code or can get it if you
1685 want it, that you can change the software or use pieces of it in new
1686 free programs, and that you know you can do these things.
1688 To protect your rights, we need to prevent others from denying you
1689 these rights or asking you to surrender the rights. Therefore, you
1690 have certain responsibilities if you distribute copies of the software,
1691 or if you modify it: responsibilities to respect the freedom of others.
1693 For example, if you distribute copies of such a program, whether
1694 gratis or for a fee, you must pass on to the recipients the same
1695 freedoms that you received. You must make sure that they, too, receive
1696 or can get the source code. And you must show them these terms so they
1699 Developers that use the GNU GPL protect your rights with two steps:
1700 (1) assert copyright on the software, and (2) offer you this License
1701 giving you legal permission to copy, distribute and/or modify it.
1703 For the developers' and authors' protection, the GPL clearly explains
1704 that there is no warranty for this free software. For both users' and
1705 authors' sake, the GPL requires that modified versions be marked as
1706 changed, so that their problems will not be attributed erroneously to
1707 authors of previous versions.
1709 Some devices are designed to deny users access to install or run
1710 modified versions of the software inside them, although the
1711 manufacturer can do so. This is fundamentally incompatible with the
1712 aim of protecting users' freedom to change the software. The
1713 systematic pattern of such abuse occurs in the area of products for
1714 individuals to use, which is precisely where it is most unacceptable.
1715 Therefore, we have designed this version of the GPL to prohibit the
1716 practice for those products. If such problems arise substantially in
1717 other domains, we stand ready to extend this provision to those domains
1718 in future versions of the GPL, as needed to protect the freedom of
1721 Finally, every program is threatened constantly by software patents.
1722 States should not allow patents to restrict development and use of
1723 software on general-purpose computers, but in those that do, we wish to
1724 avoid the special danger that patents applied to a free program could
1725 make it effectively proprietary. To prevent this, the GPL assures that
1726 patents cannot be used to render the program non-free.
1728 The precise terms and conditions for copying, distribution and
1729 modification follow.
1731 TERMS AND CONDITIONS
1732 ====================
1736 "This License" refers to version 3 of the GNU General Public
1739 "Copyright" also means copyright-like laws that apply to other
1740 kinds of works, such as semiconductor masks.
1742 "The Program" refers to any copyrightable work licensed under this
1743 License. Each licensee is addressed as "you". "Licensees" and
1744 "recipients" may be individuals or organizations.
1746 To "modify" a work means to copy from or adapt all or part of the
1747 work in a fashion requiring copyright permission, other than the
1748 making of an exact copy. The resulting work is called a "modified
1749 version" of the earlier work or a work "based on" the earlier work.
1751 A "covered work" means either the unmodified Program or a work
1752 based on the Program.
1754 To "propagate" a work means to do anything with it that, without
1755 permission, would make you directly or secondarily liable for
1756 infringement under applicable copyright law, except executing it
1757 on a computer or modifying a private copy. Propagation includes
1758 copying, distribution (with or without modification), making
1759 available to the public, and in some countries other activities as
1762 To "convey" a work means any kind of propagation that enables other
1763 parties to make or receive copies. Mere interaction with a user
1764 through a computer network, with no transfer of a copy, is not
1767 An interactive user interface displays "Appropriate Legal Notices"
1768 to the extent that it includes a convenient and prominently visible
1769 feature that (1) displays an appropriate copyright notice, and (2)
1770 tells the user that there is no warranty for the work (except to
1771 the extent that warranties are provided), that licensees may
1772 convey the work under this License, and how to view a copy of this
1773 License. If the interface presents a list of user commands or
1774 options, such as a menu, a prominent item in the list meets this
1779 The "source code" for a work means the preferred form of the work
1780 for making modifications to it. "Object code" means any
1781 non-source form of a work.
1783 A "Standard Interface" means an interface that either is an
1784 official standard defined by a recognized standards body, or, in
1785 the case of interfaces specified for a particular programming
1786 language, one that is widely used among developers working in that
1789 The "System Libraries" of an executable work include anything,
1790 other than the work as a whole, that (a) is included in the normal
1791 form of packaging a Major Component, but which is not part of that
1792 Major Component, and (b) serves only to enable use of the work
1793 with that Major Component, or to implement a Standard Interface
1794 for which an implementation is available to the public in source
1795 code form. A "Major Component", in this context, means a major
1796 essential component (kernel, window system, and so on) of the
1797 specific operating system (if any) on which the executable work
1798 runs, or a compiler used to produce the work, or an object code
1799 interpreter used to run it.
1801 The "Corresponding Source" for a work in object code form means all
1802 the source code needed to generate, install, and (for an executable
1803 work) run the object code and to modify the work, including
1804 scripts to control those activities. However, it does not include
1805 the work's System Libraries, or general-purpose tools or generally
1806 available free programs which are used unmodified in performing
1807 those activities but which are not part of the work. For example,
1808 Corresponding Source includes interface definition files
1809 associated with source files for the work, and the source code for
1810 shared libraries and dynamically linked subprograms that the work
1811 is specifically designed to require, such as by intimate data
1812 communication or control flow between those subprograms and other
1815 The Corresponding Source need not include anything that users can
1816 regenerate automatically from other parts of the Corresponding
1819 The Corresponding Source for a work in source code form is that
1822 2. Basic Permissions.
1824 All rights granted under this License are granted for the term of
1825 copyright on the Program, and are irrevocable provided the stated
1826 conditions are met. This License explicitly affirms your unlimited
1827 permission to run the unmodified Program. The output from running
1828 a covered work is covered by this License only if the output,
1829 given its content, constitutes a covered work. This License
1830 acknowledges your rights of fair use or other equivalent, as
1831 provided by copyright law.
1833 You may make, run and propagate covered works that you do not
1834 convey, without conditions so long as your license otherwise
1835 remains in force. You may convey covered works to others for the
1836 sole purpose of having them make modifications exclusively for
1837 you, or provide you with facilities for running those works,
1838 provided that you comply with the terms of this License in
1839 conveying all material for which you do not control copyright.
1840 Those thus making or running the covered works for you must do so
1841 exclusively on your behalf, under your direction and control, on
1842 terms that prohibit them from making any copies of your
1843 copyrighted material outside their relationship with you.
1845 Conveying under any other circumstances is permitted solely under
1846 the conditions stated below. Sublicensing is not allowed; section
1847 10 makes it unnecessary.
1849 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
1851 No covered work shall be deemed part of an effective technological
1852 measure under any applicable law fulfilling obligations under
1853 article 11 of the WIPO copyright treaty adopted on 20 December
1854 1996, or similar laws prohibiting or restricting circumvention of
1857 When you convey a covered work, you waive any legal power to forbid
1858 circumvention of technological measures to the extent such
1859 circumvention is effected by exercising rights under this License
1860 with respect to the covered work, and you disclaim any intention
1861 to limit operation or modification of the work as a means of
1862 enforcing, against the work's users, your or third parties' legal
1863 rights to forbid circumvention of technological measures.
1865 4. Conveying Verbatim Copies.
1867 You may convey verbatim copies of the Program's source code as you
1868 receive it, in any medium, provided that you conspicuously and
1869 appropriately publish on each copy an appropriate copyright notice;
1870 keep intact all notices stating that this License and any
1871 non-permissive terms added in accord with section 7 apply to the
1872 code; keep intact all notices of the absence of any warranty; and
1873 give all recipients a copy of this License along with the Program.
1875 You may charge any price or no price for each copy that you convey,
1876 and you may offer support or warranty protection for a fee.
1878 5. Conveying Modified Source Versions.
1880 You may convey a work based on the Program, or the modifications to
1881 produce it from the Program, in the form of source code under the
1882 terms of section 4, provided that you also meet all of these
1885 a. The work must carry prominent notices stating that you
1886 modified it, and giving a relevant date.
1888 b. The work must carry prominent notices stating that it is
1889 released under this License and any conditions added under
1890 section 7. This requirement modifies the requirement in
1891 section 4 to "keep intact all notices".
1893 c. You must license the entire work, as a whole, under this
1894 License to anyone who comes into possession of a copy. This
1895 License will therefore apply, along with any applicable
1896 section 7 additional terms, to the whole of the work, and all
1897 its parts, regardless of how they are packaged. This License
1898 gives no permission to license the work in any other way, but
1899 it does not invalidate such permission if you have separately
1902 d. If the work has interactive user interfaces, each must display
1903 Appropriate Legal Notices; however, if the Program has
1904 interactive interfaces that do not display Appropriate Legal
1905 Notices, your work need not make them do so.
1907 A compilation of a covered work with other separate and independent
1908 works, which are not by their nature extensions of the covered
1909 work, and which are not combined with it such as to form a larger
1910 program, in or on a volume of a storage or distribution medium, is
1911 called an "aggregate" if the compilation and its resulting
1912 copyright are not used to limit the access or legal rights of the
1913 compilation's users beyond what the individual works permit.
1914 Inclusion of a covered work in an aggregate does not cause this
1915 License to apply to the other parts of the aggregate.
1917 6. Conveying Non-Source Forms.
1919 You may convey a covered work in object code form under the terms
1920 of sections 4 and 5, provided that you also convey the
1921 machine-readable Corresponding Source under the terms of this
1922 License, in one of these ways:
1924 a. Convey the object code in, or embodied in, a physical product
1925 (including a physical distribution medium), accompanied by the
1926 Corresponding Source fixed on a durable physical medium
1927 customarily used for software interchange.
1929 b. Convey the object code in, or embodied in, a physical product
1930 (including a physical distribution medium), accompanied by a
1931 written offer, valid for at least three years and valid for
1932 as long as you offer spare parts or customer support for that
1933 product model, to give anyone who possesses the object code
1934 either (1) a copy of the Corresponding Source for all the
1935 software in the product that is covered by this License, on a
1936 durable physical medium customarily used for software
1937 interchange, for a price no more than your reasonable cost of
1938 physically performing this conveying of source, or (2) access
1939 to copy the Corresponding Source from a network server at no
1942 c. Convey individual copies of the object code with a copy of
1943 the written offer to provide the Corresponding Source. This
1944 alternative is allowed only occasionally and noncommercially,
1945 and only if you received the object code with such an offer,
1946 in accord with subsection 6b.
1948 d. Convey the object code by offering access from a designated
1949 place (gratis or for a charge), and offer equivalent access
1950 to the Corresponding Source in the same way through the same
1951 place at no further charge. You need not require recipients
1952 to copy the Corresponding Source along with the object code.
1953 If the place to copy the object code is a network server, the
1954 Corresponding Source may be on a different server (operated
1955 by you or a third party) that supports equivalent copying
1956 facilities, provided you maintain clear directions next to
1957 the object code saying where to find the Corresponding Source.
1958 Regardless of what server hosts the Corresponding Source, you
1959 remain obligated to ensure that it is available for as long
1960 as needed to satisfy these requirements.
1962 e. Convey the object code using peer-to-peer transmission,
1963 provided you inform other peers where the object code and
1964 Corresponding Source of the work are being offered to the
1965 general public at no charge under subsection 6d.
1968 A separable portion of the object code, whose source code is
1969 excluded from the Corresponding Source as a System Library, need
1970 not be included in conveying the object code work.
1972 A "User Product" is either (1) a "consumer product", which means
1973 any tangible personal property which is normally used for personal,
1974 family, or household purposes, or (2) anything designed or sold for
1975 incorporation into a dwelling. In determining whether a product
1976 is a consumer product, doubtful cases shall be resolved in favor of
1977 coverage. For a particular product received by a particular user,
1978 "normally used" refers to a typical or common use of that class of
1979 product, regardless of the status of the particular user or of the
1980 way in which the particular user actually uses, or expects or is
1981 expected to use, the product. A product is a consumer product
1982 regardless of whether the product has substantial commercial,
1983 industrial or non-consumer uses, unless such uses represent the
1984 only significant mode of use of the product.
1986 "Installation Information" for a User Product means any methods,
1987 procedures, authorization keys, or other information required to
1988 install and execute modified versions of a covered work in that
1989 User Product from a modified version of its Corresponding Source.
1990 The information must suffice to ensure that the continued
1991 functioning of the modified object code is in no case prevented or
1992 interfered with solely because modification has been made.
1994 If you convey an object code work under this section in, or with,
1995 or specifically for use in, a User Product, and the conveying
1996 occurs as part of a transaction in which the right of possession
1997 and use of the User Product is transferred to the recipient in
1998 perpetuity or for a fixed term (regardless of how the transaction
1999 is characterized), the Corresponding Source conveyed under this
2000 section must be accompanied by the Installation Information. But
2001 this requirement does not apply if neither you nor any third party
2002 retains the ability to install modified object code on the User
2003 Product (for example, the work has been installed in ROM).
2005 The requirement to provide Installation Information does not
2006 include a requirement to continue to provide support service,
2007 warranty, or updates for a work that has been modified or
2008 installed by the recipient, or for the User Product in which it
2009 has been modified or installed. Access to a network may be denied
2010 when the modification itself materially and adversely affects the
2011 operation of the network or violates the rules and protocols for
2012 communication across the network.
2014 Corresponding Source conveyed, and Installation Information
2015 provided, in accord with this section must be in a format that is
2016 publicly documented (and with an implementation available to the
2017 public in source code form), and must require no special password
2018 or key for unpacking, reading or copying.
2020 7. Additional Terms.
2022 "Additional permissions" are terms that supplement the terms of
2023 this License by making exceptions from one or more of its
2024 conditions. Additional permissions that are applicable to the
2025 entire Program shall be treated as though they were included in
2026 this License, to the extent that they are valid under applicable
2027 law. If additional permissions apply only to part of the Program,
2028 that part may be used separately under those permissions, but the
2029 entire Program remains governed by this License without regard to
2030 the additional permissions.
2032 When you convey a copy of a covered work, you may at your option
2033 remove any additional permissions from that copy, or from any part
2034 of it. (Additional permissions may be written to require their own
2035 removal in certain cases when you modify the work.) You may place
2036 additional permissions on material, added by you to a covered work,
2037 for which you have or can give appropriate copyright permission.
2039 Notwithstanding any other provision of this License, for material
2040 you add to a covered work, you may (if authorized by the copyright
2041 holders of that material) supplement the terms of this License
2044 a. Disclaiming warranty or limiting liability differently from
2045 the terms of sections 15 and 16 of this License; or
2047 b. Requiring preservation of specified reasonable legal notices
2048 or author attributions in that material or in the Appropriate
2049 Legal Notices displayed by works containing it; or
2051 c. Prohibiting misrepresentation of the origin of that material,
2052 or requiring that modified versions of such material be
2053 marked in reasonable ways as different from the original
2056 d. Limiting the use for publicity purposes of names of licensors
2057 or authors of the material; or
2059 e. Declining to grant rights under trademark law for use of some
2060 trade names, trademarks, or service marks; or
2062 f. Requiring indemnification of licensors and authors of that
2063 material by anyone who conveys the material (or modified
2064 versions of it) with contractual assumptions of liability to
2065 the recipient, for any liability that these contractual
2066 assumptions directly impose on those licensors and authors.
2068 All other non-permissive additional terms are considered "further
2069 restrictions" within the meaning of section 10. If the Program as
2070 you received it, or any part of it, contains a notice stating that
2071 it is governed by this License along with a term that is a further
2072 restriction, you may remove that term. If a license document
2073 contains a further restriction but permits relicensing or
2074 conveying under this License, you may add to a covered work
2075 material governed by the terms of that license document, provided
2076 that the further restriction does not survive such relicensing or
2079 If you add terms to a covered work in accord with this section, you
2080 must place, in the relevant source files, a statement of the
2081 additional terms that apply to those files, or a notice indicating
2082 where to find the applicable terms.
2084 Additional terms, permissive or non-permissive, may be stated in
2085 the form of a separately written license, or stated as exceptions;
2086 the above requirements apply either way.
2090 You may not propagate or modify a covered work except as expressly
2091 provided under this License. Any attempt otherwise to propagate or
2092 modify it is void, and will automatically terminate your rights
2093 under this License (including any patent licenses granted under
2094 the third paragraph of section 11).
2096 However, if you cease all violation of this License, then your
2097 license from a particular copyright holder is reinstated (a)
2098 provisionally, unless and until the copyright holder explicitly
2099 and finally terminates your license, and (b) permanently, if the
2100 copyright holder fails to notify you of the violation by some
2101 reasonable means prior to 60 days after the cessation.
2103 Moreover, your license from a particular copyright holder is
2104 reinstated permanently if the copyright holder notifies you of the
2105 violation by some reasonable means, this is the first time you have
2106 received notice of violation of this License (for any work) from
2107 that copyright holder, and you cure the violation prior to 30 days
2108 after your receipt of the notice.
2110 Termination of your rights under this section does not terminate
2111 the licenses of parties who have received copies or rights from
2112 you under this License. If your rights have been terminated and
2113 not permanently reinstated, you do not qualify to receive new
2114 licenses for the same material under section 10.
2116 9. Acceptance Not Required for Having Copies.
2118 You are not required to accept this License in order to receive or
2119 run a copy of the Program. Ancillary propagation of a covered work
2120 occurring solely as a consequence of using peer-to-peer
2121 transmission to receive a copy likewise does not require
2122 acceptance. However, nothing other than this License grants you
2123 permission to propagate or modify any covered work. These actions
2124 infringe copyright if you do not accept this License. Therefore,
2125 by modifying or propagating a covered work, you indicate your
2126 acceptance of this License to do so.
2128 10. Automatic Licensing of Downstream Recipients.
2130 Each time you convey a covered work, the recipient automatically
2131 receives a license from the original licensors, to run, modify and
2132 propagate that work, subject to this License. You are not
2133 responsible for enforcing compliance by third parties with this
2136 An "entity transaction" is a transaction transferring control of an
2137 organization, or substantially all assets of one, or subdividing an
2138 organization, or merging organizations. If propagation of a
2139 covered work results from an entity transaction, each party to that
2140 transaction who receives a copy of the work also receives whatever
2141 licenses to the work the party's predecessor in interest had or
2142 could give under the previous paragraph, plus a right to
2143 possession of the Corresponding Source of the work from the
2144 predecessor in interest, if the predecessor has it or can get it
2145 with reasonable efforts.
2147 You may not impose any further restrictions on the exercise of the
2148 rights granted or affirmed under this License. For example, you
2149 may not impose a license fee, royalty, or other charge for
2150 exercise of rights granted under this License, and you may not
2151 initiate litigation (including a cross-claim or counterclaim in a
2152 lawsuit) alleging that any patent claim is infringed by making,
2153 using, selling, offering for sale, or importing the Program or any
2158 A "contributor" is a copyright holder who authorizes use under this
2159 License of the Program or a work on which the Program is based.
2160 The work thus licensed is called the contributor's "contributor
2163 A contributor's "essential patent claims" are all patent claims
2164 owned or controlled by the contributor, whether already acquired or
2165 hereafter acquired, that would be infringed by some manner,
2166 permitted by this License, of making, using, or selling its
2167 contributor version, but do not include claims that would be
2168 infringed only as a consequence of further modification of the
2169 contributor version. For purposes of this definition, "control"
2170 includes the right to grant patent sublicenses in a manner
2171 consistent with the requirements of this License.
2173 Each contributor grants you a non-exclusive, worldwide,
2174 royalty-free patent license under the contributor's essential
2175 patent claims, to make, use, sell, offer for sale, import and
2176 otherwise run, modify and propagate the contents of its
2177 contributor version.
2179 In the following three paragraphs, a "patent license" is any
2180 express agreement or commitment, however denominated, not to
2181 enforce a patent (such as an express permission to practice a
2182 patent or covenant not to sue for patent infringement). To
2183 "grant" such a patent license to a party means to make such an
2184 agreement or commitment not to enforce a patent against the party.
2186 If you convey a covered work, knowingly relying on a patent
2187 license, and the Corresponding Source of the work is not available
2188 for anyone to copy, free of charge and under the terms of this
2189 License, through a publicly available network server or other
2190 readily accessible means, then you must either (1) cause the
2191 Corresponding Source to be so available, or (2) arrange to deprive
2192 yourself of the benefit of the patent license for this particular
2193 work, or (3) arrange, in a manner consistent with the requirements
2194 of this License, to extend the patent license to downstream
2195 recipients. "Knowingly relying" means you have actual knowledge
2196 that, but for the patent license, your conveying the covered work
2197 in a country, or your recipient's use of the covered work in a
2198 country, would infringe one or more identifiable patents in that
2199 country that you have reason to believe are valid.
2201 If, pursuant to or in connection with a single transaction or
2202 arrangement, you convey, or propagate by procuring conveyance of, a
2203 covered work, and grant a patent license to some of the parties
2204 receiving the covered work authorizing them to use, propagate,
2205 modify or convey a specific copy of the covered work, then the
2206 patent license you grant is automatically extended to all
2207 recipients of the covered work and works based on it.
2209 A patent license is "discriminatory" if it does not include within
2210 the scope of its coverage, prohibits the exercise of, or is
2211 conditioned on the non-exercise of one or more of the rights that
2212 are specifically granted under this License. You may not convey a
2213 covered work if you are a party to an arrangement with a third
2214 party that is in the business of distributing software, under
2215 which you make payment to the third party based on the extent of
2216 your activity of conveying the work, and under which the third
2217 party grants, to any of the parties who would receive the covered
2218 work from you, a discriminatory patent license (a) in connection
2219 with copies of the covered work conveyed by you (or copies made
2220 from those copies), or (b) primarily for and in connection with
2221 specific products or compilations that contain the covered work,
2222 unless you entered into that arrangement, or that patent license
2223 was granted, prior to 28 March 2007.
2225 Nothing in this License shall be construed as excluding or limiting
2226 any implied license or other defenses to infringement that may
2227 otherwise be available to you under applicable patent law.
2229 12. No Surrender of Others' Freedom.
2231 If conditions are imposed on you (whether by court order,
2232 agreement or otherwise) that contradict the conditions of this
2233 License, they do not excuse you from the conditions of this
2234 License. If you cannot convey a covered work so as to satisfy
2235 simultaneously your obligations under this License and any other
2236 pertinent obligations, then as a consequence you may not convey it
2237 at all. For example, if you agree to terms that obligate you to
2238 collect a royalty for further conveying from those to whom you
2239 convey the Program, the only way you could satisfy both those
2240 terms and this License would be to refrain entirely from conveying
2243 13. Use with the GNU Affero General Public License.
2245 Notwithstanding any other provision of this License, you have
2246 permission to link or combine any covered work with a work licensed
2247 under version 3 of the GNU Affero General Public License into a
2248 single combined work, and to convey the resulting work. The terms
2249 of this License will continue to apply to the part which is the
2250 covered work, but the special requirements of the GNU Affero
2251 General Public License, section 13, concerning interaction through
2252 a network will apply to the combination as such.
2254 14. Revised Versions of this License.
2256 The Free Software Foundation may publish revised and/or new
2257 versions of the GNU General Public License from time to time.
2258 Such new versions will be similar in spirit to the present
2259 version, but may differ in detail to address new problems or
2262 Each version is given a distinguishing version number. If the
2263 Program specifies that a certain numbered version of the GNU
2264 General Public License "or any later version" applies to it, you
2265 have the option of following the terms and conditions either of
2266 that numbered version or of any later version published by the
2267 Free Software Foundation. If the Program does not specify a
2268 version number of the GNU General Public License, you may choose
2269 any version ever published by the Free Software Foundation.
2271 If the Program specifies that a proxy can decide which future
2272 versions of the GNU General Public License can be used, that
2273 proxy's public statement of acceptance of a version permanently
2274 authorizes you to choose that version for the Program.
2276 Later license versions may give you additional or different
2277 permissions. However, no additional obligations are imposed on any
2278 author or copyright holder as a result of your choosing to follow a
2281 15. Disclaimer of Warranty.
2283 THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
2284 APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
2285 COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
2286 WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
2287 INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
2288 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
2289 RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
2290 SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
2291 NECESSARY SERVICING, REPAIR OR CORRECTION.
2293 16. Limitation of Liability.
2295 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
2296 WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES
2297 AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
2298 FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
2299 CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
2300 THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
2301 BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
2302 PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
2303 PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
2304 THE POSSIBILITY OF SUCH DAMAGES.
2306 17. Interpretation of Sections 15 and 16.
2308 If the disclaimer of warranty and limitation of liability provided
2309 above cannot be given local legal effect according to their terms,
2310 reviewing courts shall apply local law that most closely
2311 approximates an absolute waiver of all civil liability in
2312 connection with the Program, unless a warranty or assumption of
2313 liability accompanies a copy of the Program in return for a fee.
2316 END OF TERMS AND CONDITIONS
2317 ===========================
2319 How to Apply These Terms to Your New Programs
2320 =============================================
2322 If you develop a new program, and you want it to be of the greatest
2323 possible use to the public, the best way to achieve this is to make it
2324 free software which everyone can redistribute and change under these
2327 To do so, attach the following notices to the program. It is safest
2328 to attach them to the start of each source file to most effectively
2329 state the exclusion of warranty; and each file should have at least the
2330 "copyright" line and a pointer to where the full notice is found.
2332 ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
2333 Copyright (C) YEAR NAME OF AUTHOR
2335 This program is free software: you can redistribute it and/or modify
2336 it under the terms of the GNU General Public License as published by
2337 the Free Software Foundation, either version 3 of the License, or (at
2338 your option) any later version.
2340 This program is distributed in the hope that it will be useful, but
2341 WITHOUT ANY WARRANTY; without even the implied warranty of
2342 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2343 General Public License for more details.
2345 You should have received a copy of the GNU General Public License
2346 along with this program. If not, see `http://www.gnu.org/licenses/'.
2348 Also add information on how to contact you by electronic and paper
2351 If the program does terminal interaction, make it output a short
2352 notice like this when it starts in an interactive mode:
2354 PROGRAM Copyright (C) YEAR NAME OF AUTHOR
2355 This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
2356 This is free software, and you are welcome to redistribute it
2357 under certain conditions; type `show c' for details.
2359 The hypothetical commands `show w' and `show c' should show the
2360 appropriate parts of the General Public License. Of course, your
2361 program's commands might be different; for a GUI interface, you would
2364 You should also get your employer (if you work as a programmer) or
2365 school, if any, to sign a "copyright disclaimer" for the program, if
2366 necessary. For more information on this, and how to apply and follow
2367 the GNU GPL, see `http://www.gnu.org/licenses/'.
2369 The GNU General Public License does not permit incorporating your
2370 program into proprietary programs. If your program is a subroutine
2371 library, you may consider it more useful to permit linking proprietary
2372 applications with the library. If this is what you want to do, use the
2373 GNU Lesser General Public License instead of this License. But first,
2374 please read `http://www.gnu.org/philosophy/why-not-lgpl.html'.
2380 Node: Introduction
\x7f1976
2381 Node: Configuration files
\x7f3869
2382 Ref: defaults
\x7f5397
2383 Ref: account
\x7f5572
2386 Ref: timeout
\x7f6436
2387 Ref: protocol
\x7f6744
2391 Ref: password
\x7f7920
2392 Ref: ntlmdomain
\x7f8556
2394 Ref: tls_trust_file
\x7f9248
2395 Ref: tls_crl_file
\x7f9644
2396 Ref: tls_key_file
\x7f9983
2397 Ref: tls_cert_file
\x7f10311
2398 Ref: tls_certcheck
\x7f10615
2399 Ref: tls_starttls
\x7f10986
2400 Ref: tls_force_sslv3
\x7f11299
2401 Ref: tls_min_dh_prime_bits
\x7f11509
2402 Ref: tls_priorities
\x7f11930
2403 Ref: auto_from
\x7f12457
2405 Ref: maildomain
\x7f13319
2406 Ref: dsn_notify
\x7f13527
2407 Ref: dsn_return
\x7f14240
2408 Ref: keepbcc
\x7f14754
2409 Ref: logfile
\x7f14924
2410 Ref: syslog
\x7f15146
2411 Node: Invocation
\x7f15422
2412 Ref: --serverinfo
\x7f16912
2413 Ref: --rmqs
\x7f17188
2414 Ref: --auth
\x7f18617
2415 Ref: --user
\x7f18736
2416 Ref: --tls-starttls
\x7f18888
2417 Ref: --tls-trust-file
\x7f18996
2418 Ref: --tls-crl-file
\x7f19103
2419 Ref: --tls-key-file
\x7f19223
2420 Ref: --tls-cert-file
\x7f19319
2421 Ref: --tls-certcheck
\x7f19418
2422 Ref: --tls-force-sslv3
\x7f19545
2423 Ref: --tls-min-dh-prime-bits
\x7f19636
2424 Ref: --tls-priorities
\x7f19775
2425 Ref: --auto-from
\x7f19947
2426 Ref: --from
\x7f20076
2427 Ref: --maildomain
\x7f20476
2428 Ref: --dsn-notify
\x7f20630
2429 Ref: --dsn-return
\x7f20750
2430 Ref: --keepbcc
\x7f20961
2431 Ref: --logfile
\x7f21066
2432 Ref: --syslog
\x7f21147
2433 Ref: Choosing an account
\x7f22010
2435 Ref: Environment
\x7f23450
2436 Node: Transport Layer Security
\x7f24535
2437 Node: Authentication
\x7f28768
2438 Ref: Using the Mac OS X Keychain
\x7f33521
2439 Node: Delivery Status Notifications
\x7f34161
2440 Node: Sendmail mode
\x7f35441
2441 Node: Envelope-from address
\x7f35751
2442 Node: Logging
\x7f36839
2443 Node: Bcc header
\x7f38479
2444 Node: Server information mode
\x7f38836
2445 Node: Remote Message Queue Starting mode
\x7f40280
2446 Node: Examples
\x7f41319
2447 Node: A system wide configuration file
\x7f41583
2448 Node: A user configuration file
\x7f42338
2449 Node: Using msmtp with Mutt
\x7f43238
2450 Node: Using msmtp with mail
\x7f45648
2451 Node: Development
\x7f46011
2452 Node: Copying Information
\x7f46594
2453 Node: GNU Free Documentation License
\x7f46885
2454 Node: GNU GPL
\x7f69290