1 \input texinfo @c -*-texinfo-*-
2 @setfilename ../info/smtpmail
3 @settitle Emacs SMTP Library
6 Copyright @copyright{} 2003, 2004 Free Software Foundation, Inc.
9 Permission is granted to copy, distribute and/or modify this document
10 under the terms of the GNU Free Documentation License, Version 1.1 or
11 any later version published by the Free Software Foundation; with no
12 Invariant Sections, with the Front-Cover texts being ``A GNU Manual'',
13 and with the Back-Cover Texts as in (a) below. A copy of the license
14 is included in the section entitled ``GNU Free Documentation License''
17 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
18 this GNU Manual, like GNU software. Copies published by the Free
19 Software Foundation raise funds for GNU development.''
21 This document is part of a collection distributed under the GNU Free
22 Documentation License. If you want to distribute this document
23 separately from the collection, you can do so by adding a copy of the
24 license to the document, as described in section 6 of the license.
30 * SMTP: (smtpmail). Emacs library for sending mail via SMTP.
34 @title{Emacs SMTP Library}
35 @subtitle{An Emacs package for sending mail via SMTP}
36 @author{Simon Josefsson, Alex Schroeder}
38 @vskip 0pt plus 1filll
46 @top Emacs SMTP Library
52 * How Mail Works:: Brief introduction to mail concepts.
53 * Emacs Speaks SMTP:: How to use the SMTP library in Emacs.
54 * Authentication:: Authenticating yourself to the server.
55 * Queued delivery:: Sending mail without an internet connection.
56 * Server workarounds:: Mail servers with special requirements.
57 * Debugging:: Tracking down problems.
61 * Index:: Index over variables and functions.
65 @chapter How Mail Works
69 On the internet, mail is sent from mail host to mail host using the
70 simple mail transfer protocol (SMTP). To send and receive mail, you
71 must get it from and send it to a mail host. Every mail host runs a
72 mail transfer agent (MTA) such as Exim that accepts mails and passes
73 them on. The communication between a mail host and other clients does
74 not necessarily involve SMTP, however. Here is short overview of what
78 The mail program --- also called a mail user agent (MUA) ---
79 usually sends outgoing mail to a mail host. When your computer is
80 permanently connected to the internet, it might even be a mail host
81 itself. In this case, the MUA will pipe mail to the
82 @file{/usr/lib/sendmail} application. It will take care of your mail
83 and pass it on to the next mail host.
86 When you are only connected to the internet from time to time, your
87 internet service provider (ISP) has probably told you which mail host
88 to use. You must configure your MUA to use that mail host. Since you
89 are reading this manual, you probably want to configure Emacs to use
90 SMTP to send mail to that mail host. More on that in the next
94 Things are different when reading mail. The mail host responsible
95 for your mail keeps it in a file somewhere. The messages get into the
96 file by way of a mail delivery agent (MDA) such as procmail. These
97 delivery agents often allow you to filter and munge your mails before
98 you get to see it. When your computer is that mail host, this file is
99 called a spool, and sometimes located in the directory
100 @file{/var/spool/mail/}. All your MUA has to do is read mail from the
105 When your computer is not always connected to the internet, you
106 must get the mail from the remote mail host using a protocol such as
107 POP3 or IMAP. POP3 essentially downloads all your mail from the mail
108 host to your computer. The mail is stored in some file on your
109 computer, and again, all your MUA has to do is read mail from the
112 When you read mail from various machines, downloading mail from the
113 mail host to your current machine is not convenient. In that case,
114 you will probably want to use the IMAP protocol. Your mail is kept on
115 the mail host, and you can read it while you are connected via IMAP to
119 So how does reading mail via the web work, you ask. In that case,
120 the web interface just allows you to remote-control a MUA on the web
121 host. Whether the web host is also a mail host, and how all the
122 pieces interact is completely irrelevant. You usually cannot use
123 Emacs to read mail via the web, unless you use software that parses
124 the ever-changing HTML of the web interface.
126 @node Emacs Speaks SMTP
127 @chapter Emacs Speaks SMTP
129 Emacs includes a package for sending your mail to a SMTP server and
130 have it take care of delivering it to the final destination, rather
131 than letting the MTA on your local system take care of it. This can
132 be useful if you don't have a MTA set up on your host, or if your
133 machine is often disconnected from the internet.
135 Sending mail via SMTP requires configuring your mail user agent
136 (@pxref{Mail Methods,,,emacs}) to use the SMTP library. How to do
137 this should be described for each mail user agent; for the default
138 mail user agent the variable @code{send-mail-function} (@pxref{Mail
139 Sending,,,emacs}) is used; for the Message and Gnus user agents the
140 variable @code{message-send-mail-function} (@pxref{Mail
141 Variables,,,message}) is used.
144 ;; If you use the default mail user agent.
145 (setq send-mail-function 'smtpmail-send-it)
146 ;; If you use Message or Gnus.
147 (setq message-send-mail-function 'smtpmail-send-it)
150 Before using SMTP you must find out the hostname of the SMTP server
151 to use. Your system administrator should provide you with this
152 information, but often it is the same as the server you receive mail
156 @item smtpmail-smtp-server
157 @vindex smtpmail-smtp-server
159 The variable @code{smtpmail-smtp-server} controls the hostname of
160 the server to use. It is a string with an IP address or hostname. It
161 defaults to the contents of the @env{SMTPSERVER} environment
162 variable, or, if empty, the contents of
163 @code{smtpmail-default-smtp-server}.
165 @item smtpmail-default-smtp-server
166 @vindex smtpmail-default-smtp-server
167 The variable @code{smtpmail-default-smtp-server} controls the
168 default hostname of the server to use. It is a string with an IP
169 address or hostname. It must be set before the SMTP library is
170 loaded. It has no effect if set after the SMTP library has been
171 loaded, or if @code{smtpmail-smtp-server} is defined. It is usually
172 set by system administrators in a site wide initialization file.
175 The following example illustrates what you could put in
176 @file{~/.emacs} to set the SMTP server name.
179 ;; Send mail using SMTP via mail.example.org.
180 (setq smtpmail-smtp-server "mail.example.org")
183 @cindex Mail Submission
184 SMTP is normally used on the registered ``smtp'' TCP service port 25.
185 Some environments use SMTP in ``Mail Submission'' mode, which uses
186 port 587. Using other ports is not uncommon, either for security by
187 obscurity purposes, port forwarding, or otherwise.
190 @item smtpmail-smtp-service
191 @vindex smtpmail-smtp-service
192 The variable @code{smtpmail-smtp-service} controls the port on the
193 server to contact. It is either a string, in which case it will be
194 translated into an integer using system calls, or an integer.
197 The following example illustrates what you could put in
198 @file{~/.emacs} to set the SMTP service port.
201 ;; Send mail using SMTP on the mail submission port 587.
202 (setq smtpmail-smtp-service 587)
206 @chapter Authentication
212 Many environments require SMTP clients to authenticate themselves
213 before they are allowed to route mail via a server. The two following
214 variables contains the authentication information needed for this.
215 The first variable, @code{smtpmail-auth-credentials}, instructs the
216 SMTP library to use a SASL authentication step, currently only the
217 CRAM-MD5 and LOGIN mechanisms are supported and will be selected in
218 that order if the server support both.
220 The second variable, @code{smtpmail-starttls-credentials}, instructs
221 the SMTP library to connect to the server using STARTTLS. This means
222 the protocol exchange may be integrity protected and confidential by
223 using TLS, and optionally also authentication of the client. This
224 feature uses the elisp package @file{starttls.el} (see it for more
225 information on customization), which in turn require that at least one
226 of the following external tools are installed:
230 The GNUTLS command line tool @samp{gnutls-cli}, you can get it from
231 @url{http://www.gnu.org/software/gnutls/}. This is the recommended
232 tool, mainly because it can verify the server certificates.
235 The @samp{starttls} external program, you can get it from
236 @file{starttls-*.tar.gz} from @uref{ftp://ftp.opaopa.org/pub/elisp/}.
239 It is not uncommon to use both these mechanisms, e.g., to use STARTTLS
240 to achieve integrity and confidentiality and then use SASL for client
244 @item smtpmail-auth-credentials
245 @vindex smtpmail-auth-credentials
246 The variable @code{smtpmail-auth-credentials} contains a list of
247 hostname, port, username and password tuples. When the SMTP library
248 connects to a host on a certain port, this variable is searched to
249 find a matching entry for that hostname and port. If an entry is
250 found, the authentication process is invoked and the credentials are
253 The hostname field follows the same format as
254 @code{smtpmail-smtp-server} (i.e., a string) and the port field the
255 same format as @code{smtpmail-smtp-service} (i.e., a string or an
256 integer). The username and password fields, which either can be
257 @code{nil} to indicate that the user is prompted for the value
258 interactively, should be strings with the username and password,
259 respectively, information that is normally provided by system
262 @item smtpmail-starttls-credentials
263 @vindex smtpmail-starttls-credentials
264 The variable @code{smtpmail-starttls-credentials} contains a list of
265 tuples with hostname, port, name of file containing client key, and
266 name of file containing client certificate. The processing is similar
267 to the previous variable. The client key and certificate may be
268 @code{nil} if you do not wish to use client authentication.
271 The following example illustrates what you could put in
272 @file{~/.emacs} to enable both SASL authentication and STARTTLS. The
273 server name (@code{smtpmail-smtp-server}) is @var{hostname}, the
274 server port (@code{smtpmail-smtp-service}) is @var{port}, and the
275 username and password are @var{username} and @var{password}
279 ;; Authenticate using this username and password against my server.
280 (setq smtpmail-auth-credentials
281 '(("@var{hostname}" "@var{port}" "@var{username}" "@var{password}")))
282 ;; Use STARTTLS without authentication against the server.
283 (setq smtpmail-starttls-credentials
284 '(("@var{hostname}" "@var{port}" nil nil)))
287 @node Queued delivery
288 @chapter Queued delivery
290 @cindex Dialup connection
291 If you connect to the internet via a dialup connection, or for some
292 other reason don't have permanent internet connection, sending mail
293 will fail when you are not connected. The SMTP library implements
294 queued delivery, and the following variable control its behaviour.
297 @item smtpmail-queue-mail
298 @vindex smtpmail-queue-mail
299 The variable @code{smtpmail-queue-mail} controls whether a simple
300 off line mail sender is active. This variable is a boolean, and
301 defaults to @code{nil} (disabled). If this is non-@code{nil}, mail is
302 not sent immediately but rather queued in the directory
303 @code{smtpmail-queue-dir} and can be later sent manually by invoking
304 @code{smtpmail-send-queued-mail} (typically when you connect to the
307 @item smtpmail-queue-dir
308 @vindex smtpmail-queue-dir
309 The variable @code{smtpmail-queue-dir} specifies the name of the
310 directory to hold queued messages. It defaults to
311 @file{~/Mail/queued-mail/}.
314 @findex smtpmail-send-queued-mail
315 The function @code{smtpmail-send-queued-mail} can be used to send
316 any queued mail when @code{smtpmail-queue-mail} is enabled. It is
317 typically invoked interactively with @kbd{M-x
318 smtpmail-send-queued-mail RET} when you are connected to the internet.
320 @node Server workarounds
321 @chapter Server workarounds
323 Some SMTP servers have special requirements. The following variables
324 implement support for common requirements.
328 @item smtpmail-local-domain
329 @vindex smtpmail-local-domain
330 The variable @code{smtpmail-local-domain} controls the hostname sent
331 in the first @code{EHLO} or @code{HELO} command sent to the server.
332 It should only be set if the @code{system-name} function returns a
333 name that isn't accepted by the server. Do not set this variable
334 unless your server complains.
336 @item smtpmail-sendto-domain
337 @vindex smtpmail-sendto-domain
338 The variable @code{smtpmail-sendto-domain} makes the SMTP library
339 add @samp{@@} and the specified value to recipients specified in the
340 message when they are sent using the @code{RCPT TO} command. Some
341 configurations of sendmail requires this behaviour. Don't bother to
342 set this unless you have get an error like:
345 Sending failed; SMTP protocol error
348 when sending mail, and the debug buffer (@pxref{Debugging})) contains
352 RCPT TO: @var{someone}
353 501 @var{someone}: recipient address must contain a domain
362 Sometimes delivery fails, often with the generic error message
363 @samp{Sending failed; SMTP protocol error}. Enabling one or both of
364 the following variables and inspecting a trace buffer will often give
365 clues to the reason for the error.
369 @item smtpmail-debug-info
370 @vindex smtpmail-debug-info
371 The variable @code{smtpmail-debug-info} controls whether to print
372 the SMTP protocol exchange in the minibuffer, and retain the entire
373 exchange in a buffer @samp{*trace of SMTP session to @var{server}*},
374 where @var{server} is the name of the mail server to which you send
377 @item smtpmail-debug-verb
378 @vindex smtpmail-debug-verb
379 The variable @code{smtpmail-debug-verb} controls whether to send the
380 @code{VERB} token to the server. The @code{VERB} server instructs the
381 server to be more verbose, and often also to attempt final delivery
382 while your SMTP session is still running. It is usually only useful
383 together with @code{smtpmail-debug-info}. Note that this may cause
384 mail delivery to take considerable time if the final destination
392 @section Concept Index
396 @section Function and Variable Index
404 arch-tag: 6316abdf-b366-4562-87a2-f37e8f894b6f