Hi, Kalyan!
I've at last configured mail for using gmail.
But my scheme is for general purpose, I mean, I did configuration so
that I can use any MUA to read and write messages, not only VM or gnus
in emacs.
I can recommend you the following scheme:
- receive mail with fetchmail; its runtime config file may looks like
this:
# ~/.fetchmailrc
poll pop.gmail.com protocol POP3 port 995 user "[EMAIL PROTECTED]" password
"Try_to_crack" is "My_linux_login" here ssl
Also, a mail transfer agent deamon should listen port 25 on your
localhost. In case of smail, you should run "smail -bd". MTA will put
all maill in system mail spool (/var/spooll/mail/{$USERNAME}) by
default.
Then you can access this spool mailbox with VM with no problem. I
checked this variant. But I prefer another variant, my ~/.fetchmailrc
file looks like this:
#~/.fetchmailrc
poll pop.gmail.com protocol POP3 port 995 user "[EMAIL PROTECTED]" password
"Try_again" is "My_unix_login" here mda "/usr/bin/procmail -f %F" ssl
The reason is that I found that it is simple to configure sorting mail
with procmail, it places sorted messages in different mboxes under
~/Mail/, also I don't like MTA deamon to engage memory permanently as my
host is not a mail server and even is not connected to internet all the
time.
Roma, out
26.01.2006 19:04, Kalyan Mukherjea (wrote):
Content-Description: message body text
> Hi Roman,
> I tried out your suggestion although the VM info document specifically
> asks that this variable be set. But commenting it out means that
> whenever I type `g' to retrieve mail there is a warning bee,p, doing
> C-e a makes Emacspeak repeat the last message:
> Searching for program no such file or directory stunnel.
> So your suggestion fails with VM. I'll try out using fetchmail
> tomorrow:I have been working on the PC for 4 hours and will
> probably make mistakes if I try configuring fetchmail now!
>
> To send mail to google you have to use smtpmail. I am attaching the
> html documentation of this program in my letter. This also involves
> other security-related additions which I haven't yet tried. If you get
> things working I'd like to know.
>
> Thanks and cheers.
>
> Kalyan
>
Content-Description: documentation
> <html lang="en">
> <head>
> <title>Emacs SMTP Library</title>
> <meta http-equiv="Content-Type" content="text/html">
> <meta name="description" content="Emacs SMTP Library">
> <meta name="generator" content="makeinfo 4.7">
> <link title="Top" rel="top" href="#Top">
> <link href="http://www.gnu.org/software/texinfo/"; rel="generator-home"
> title="Texinfo Homepage">
> <!--
> Copyright (C) 2003, 2004 Free Software Foundation, Inc.
>
> Permission is granted to copy, distribute and/or modify this
> document under the terms of the GNU Free Documentation License,
> Version 1.1 or any later version published by the Free Software
> Foundation; with no Invariant Sections, with the Front-Cover texts
> being "A GNU Manual", and with the Back-Cover Texts as in (a)
> below. A copy of the license is included in the section entitled
> "GNU Free Documentation License" in the Emacs manual.
>
> (a) The FSF's Back-Cover Text is: "You have freedom to copy and
> modify this GNU Manual, like GNU software. Copies published by
> the Free Software Foundation raise funds for GNU development."
>
> This document is part of a collection distributed under the GNU
> Free Documentation License. If you want to distribute this
> document separately from the collection, you can do so by adding a
> copy of the license to the document, as described in section 6 of
> the license.
> -->
> <meta http-equiv="Content-Style-Type" content="text/css">
> <style type="text/css"><!--
> pre.display { font-family:inherit }
> pre.format { font-family:inherit }
> pre.smalldisplay { font-family:inherit; font-size:smaller }
> pre.smallformat { font-family:inherit; font-size:smaller }
> pre.smallexample { font-size:smaller }
> pre.smalllisp { font-size:smaller }
> span.sc { font-variant:small-caps }
> span.roman { font-family: serif; font-weight: normal; }
> --></style>
> </head>
> <body>
> <h1 class="settitle">Emacs SMTP Library</h1>
> <div class="contents">
> <h2>Table of Contents</h2>
> <ul>
> <li><a name="toc_Top" href="#Top">Emacs SMTP Library</a>
> <li><a name="toc_How-Mail-Works" href="#How-Mail-Works">1 How Mail Works</a>
> <li><a name="toc_Emacs-Speaks-SMTP" href="#Emacs-Speaks-SMTP">2 Emacs Speaks
> SMTP</a>
> <li><a name="toc_Authentication" href="#Authentication">3 Authentication</a>
> <li><a name="toc_Queued-delivery" href="#Queued-delivery">4 Queued
> delivery</a>
> <li><a name="toc_Server-workarounds" href="#Server-workarounds">5 Server
> workarounds</a>
> <li><a name="toc_Debugging" href="#Debugging">6 Debugging</a>
> <li><a name="toc_Index" href="#Index">7 Index</a>
> <ul>
> <li><a href="#Index">7.1 Concept Index</a>
> <li><a href="#Index">7.2 Function and Variable Index</a>
> </li></ul>
> </li></ul>
> </div>
>
>
>
> <div class="node">
> <p><hr>
> <a name="Top"></a>Next: <a rel="next" accesskey="n"
> href="#How-Mail-Works">How Mail Works</a>,
> Up: <a rel="up" accesskey="u" href="#dir">(dir)</a>
> <br>
> </div>
>
> <h2 class="unnumbered">Emacs SMTP Library</h2>
>
> <p>Copyright © 2003, 2004 Free Software Foundation, Inc.
>
> <blockquote>
> Permission is granted to copy, distribute and/or modify this document
> under the terms of the GNU Free Documentation License, Version 1.1 or
> any later version published by the Free Software Foundation; with no
> Invariant Sections, with the Front-Cover texts being “A GNU
> Manual”,
> and with the Back-Cover Texts as in (a) below. A copy of the license
> is included in the section entitled “GNU Free Documentation
> License”
> in the Emacs manual.
>
> <p>(a) The FSF's Back-Cover Text is: “You have freedom to copy
> and modify
> this GNU Manual, like GNU software. Copies published by the Free
> Software Foundation raise funds for GNU development.”
>
> <p>This document is part of a collection distributed under the GNU
> Free
> Documentation License. If you want to distribute this document
> separately from the collection, you can do so by adding a copy of the
> license to the document, as described in section 6 of the license.
> </blockquote>
>
> <ul class="menu">
> <li><a accesskey="1" href="#How-Mail-Works">How Mail Works</a>: Brief
> introduction to mail concepts.
> <li><a accesskey="2" href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a>: How
> to use the SMTP library in Emacs.
> <li><a accesskey="3" href="#Authentication">Authentication</a>:
> Authenticating yourself to the server.
> <li><a accesskey="4" href="#Queued-delivery">Queued delivery</a>: Sending
> mail without an internet connection.
> <li><a accesskey="5" href="#Server-workarounds">Server workarounds</a>:
> Mail servers with special requirements.
> <li><a accesskey="6" href="#Debugging">Debugging</a>:
> Tracking down problems.
>
> </li></ul>
> <p>Indices
>
> </p>
> <ul class="menu">
> <li><a accesskey="7" href="#Index">Index</a>: Index over
> variables and functions.
> </ul>
>
> <div class="node">
> <p><hr>
> <a name="How-Mail-Works"></a>Next: <a rel="next" accesskey="n"
> href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a>,
> Previous: <a rel="previous" accesskey="p" href="#Top">Top</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">1 How Mail Works</h2>
>
> <p><a name="index-SMTP-1"></a><a name="index-MTA-2"></a> On the internet,
> mail is sent from mail host to mail host using the
> simple mail transfer protocol (SMTP). To send and receive mail, you
> must get it from and send it to a mail host. Every mail host runs a
> mail transfer agent (MTA) such as Exim that accepts mails and passes
> them on. The communication between a mail host and other clients does
> not necessarily involve SMTP, however. Here is short overview of what
> is involved.
>
> <p><a name="index-MUA-3"></a> The mail program — also called a
> mail user agent (MUA) —
> usually sends outgoing mail to a mail host. When your computer is
> permanently connected to the internet, it might even be a mail host
> itself. In this case, the MUA will pipe mail to the
> <span class="file">/usr/lib/sendmail</span> application. It will take care
> of your mail
> and pass it on to the next mail host.
>
> <p><a name="index-ISP-4"></a> When you are only connected to the
> internet from time to time, your
> internet service provider (ISP) has probably told you which mail host
> to use. You must configure your MUA to use that mail host. Since you
> are reading this manual, you probably want to configure Emacs to use
> SMTP to send mail to that mail host. More on that in the next
> section.
>
> <p><a name="index-MDA-5"></a> Things are different when reading mail.
> The mail host responsible
> for your mail keeps it in a file somewhere. The messages get into the
> file by way of a mail delivery agent (MDA) such as procmail. These
> delivery agents often allow you to filter and munge your mails before
> you get to see it. When your computer is that mail host, this file is
> called a spool, and sometimes located in the directory
> <span class="file">/var/spool/mail/</span>. All your MUA has to do is read
> mail from the
> spool, then.
>
> <p><a name="index-POP3-6"></a><a name="index-IMAP-7"></a> When your
> computer is not always connected to the internet, you
> must get the mail from the remote mail host using a protocol such as
> POP3 or IMAP. POP3 essentially downloads all your mail from the mail
> host to your computer. The mail is stored in some file on your
> computer, and again, all your MUA has to do is read mail from the
> spool.
>
> <p>When you read mail from various machines, downloading mail from the
> mail host to your current machine is not convenient. In that case,
> you will probably want to use the IMAP protocol. Your mail is kept on
> the mail host, and you can read it while you are connected via IMAP to
> the mail host.
>
> <p><a name="index-Webmail-8"></a> So how does reading mail via the web
> work, you ask. In that case,
> the web interface just allows you to remote-control a MUA on the web
> host. Whether the web host is also a mail host, and how all the
> pieces interact is completely irrelevant. You usually cannot use
> Emacs to read mail via the web, unless you use software that parses
> the ever-changing HTML of the web interface.
>
> <div class="node">
> <p><hr>
> <a name="Emacs-Speaks-SMTP"></a>Next: <a rel="next" accesskey="n"
> href="#Authentication">Authentication</a>,
> Previous: <a rel="previous" accesskey="p" href="#How-Mail-Works">How
> Mail Works</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">2 Emacs Speaks SMTP</h2>
>
> <p>Emacs includes a package for sending your mail to a SMTP server and
> have it take care of delivering it to the final destination, rather
> than letting the MTA on your local system take care of it. This can
> be useful if you don't have a MTA set up on your host, or if your
> machine is often disconnected from the internet.
>
> <p>Sending mail via SMTP requires configuring your mail user agent
> (see <a href="emacs.html#Mail-Methods">Mail Methods (emacs)</a>) to use the
> SMTP library. How to do
> this should be described for each mail user agent; for the default
> mail user agent the variable <code>send-mail-function</code> (see <a
> href="emacs.html#Mail-Sending">Mail Sending (emacs)</a>) is used; for the
> Message and Gnus user agents the
> variable <code>message-send-mail-function</code> (see <a
> href="message.html#Mail-Variables">Mail Variables (message)</a>) is used.
>
> <pre class="example"> ;; If you use the default mail user agent.
> (setq send-mail-function 'smtpmail-send-it)
> ;; If you use Message or Gnus.
> (setq message-send-mail-function 'smtpmail-send-it)
> </pre>
> <p>Before using SMTP you must find out the hostname of the SMTP server
> to use. Your system administrator should provide you with this
> information, but often it is the same as the server you receive mail
> from.
>
> <dl>
> <dt><code>smtpmail-smtp-server</code><dd><a
> name="index-smtpmail_002dsmtp_002dserver-9"></a><a
> name="index-SMTPSERVER-10"></a> The variable
> <code>smtpmail-smtp-server</code> controls the hostname of
> the server to use. It is a string with an IP address or hostname. It
> defaults to the contents of the <span class="env">SMTPSERVER</span>
> environment
> variable, or, if empty, the contents of
> <code>smtpmail-default-smtp-server</code>.
>
> <br><dt><code>smtpmail-default-smtp-server</code><dd><a
> name="index-smtpmail_002ddefault_002dsmtp_002dserver-11"></a> The variable
> <code>smtpmail-default-smtp-server</code> controls the
> default hostname of the server to use. It is a string with an IP
> address or hostname. It must be set before the SMTP library is
> loaded. It has no effect if set after the SMTP library has been
> loaded, or if <code>smtpmail-smtp-server</code> is defined. It is usually
> set by system administrators in a site wide initialization file.
> </dl>
>
> <p>The following example illustrates what you could put in
> <span class="file">~/.emacs</span> to set the SMTP server name.
>
> <pre class="example"> ;; Send mail using SMTP via mail.example.org.
> (setq smtpmail-smtp-server "mail.example.org")
> </pre>
> <p><a name="index-Mail-Submission-12"></a>SMTP is normally used on the
> registered “smtp” TCP service port 25.
> Some environments use SMTP in “Mail Submission” mode, which uses
> port 587. Using other ports is not uncommon, either for security by
> obscurity purposes, port forwarding, or otherwise.
>
> <dl>
> <dt><code>smtpmail-smtp-service</code><dd><a
> name="index-smtpmail_002dsmtp_002dservice-13"></a> The variable
> <code>smtpmail-smtp-service</code> controls the port on the
> server to contact. It is either a string, in which case it will be
> translated into an integer using system calls, or an integer.
> </dl>
>
> <p>The following example illustrates what you could put in
> <span class="file">~/.emacs</span> to set the SMTP service port.
>
> <pre class="example"> ;; Send mail using SMTP on the mail submission port
> 587.
> (setq smtpmail-smtp-service 587)
> </pre>
> <div class="node">
> <p><hr>
> <a name="Authentication"></a>Next: <a rel="next" accesskey="n"
> href="#Queued-delivery">Queued delivery</a>,
> Previous: <a rel="previous" accesskey="p"
> href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">3 Authentication</h2>
>
> <p><a name="index-SASL-14"></a><a name="index-CRAM_002dMD5-15"></a><a
> name="index-LOGIN-16"></a><a name="index-STARTTLS-17"></a>Many environments
> require SMTP clients to authenticate themselves
> before they are allowed to route mail via a server. The two following
> variables contains the authentication information needed for this.
> The first variable, <code>smtpmail-auth-credentials</code>, instructs the
> SMTP library to use a SASL authentication step, currently only the
> CRAM-MD5 and LOGIN mechanisms are supported and will be selected in
> that order if the server support both.
>
> <p>The second variable, <code>smtpmail-starttls-credentials</code>,
> instructs
> the SMTP library to connect to the server using STARTTLS. This means
> the protocol exchange may be integrity protected and confidential by
> using TLS, and optionally also authentication of the client. This
> feature uses the elisp package <span class="file">starttls.el</span> (see it
> for more
> information on customization), which in turn require that at least one
> of the following external tools are installed:
>
> <ol type=1 start=1>
> <li>The GNUTLS command line tool <span class="samp">gnutls-cli</span>, you
> can get it from
> <a
> href="http://www.gnu.org/software/gnutls/";>http://www.gnu.org/software/gnutls/</a>.
> This is the recommended
> tool, mainly because it can verify the server certificates.
>
> <li>The <span class="samp">starttls</span> external program, you can get
> it from
> <span class="file">starttls-*.tar.gz</span> from <a
> href="ftp://ftp.opaopa.org/pub/elisp/";>ftp://ftp.opaopa.org/pub/elisp/</a>.
> </ol>
>
> <p>It is not uncommon to use both these mechanisms, e.g., to use STARTTLS
> to achieve integrity and confidentiality and then use SASL for client
> authentication.
>
> <dl>
> <dt><code>smtpmail-auth-credentials</code><dd><a
> name="index-smtpmail_002dauth_002dcredentials-18"></a> The variable
> <code>smtpmail-auth-credentials</code> contains a list of
> hostname, port, username and password tuples. When the SMTP library
> connects to a host on a certain port, this variable is searched to
> find a matching entry for that hostname and port. If an entry is
> found, the authentication process is invoked and the credentials are
> used.
>
> <p>The hostname field follows the same format as
> <code>smtpmail-smtp-server</code> (i.e., a string) and the port field the
> same format as <code>smtpmail-smtp-service</code> (i.e., a string or an
> integer). The username and password fields, which either can be
> <code>nil</code> to indicate that the user is prompted for the value
> interactively, should be strings with the username and password,
> respectively, information that is normally provided by system
> administrators.
>
> <br><dt><code>smtpmail-starttls-credentials</code><dd><a
> name="index-smtpmail_002dstarttls_002dcredentials-19"></a> The variable
> <code>smtpmail-starttls-credentials</code> contains a list of
> tuples with hostname, port, name of file containing client key, and
> name of file containing client certificate. The processing is similar
> to the previous variable. The client key and certificate may be
> <code>nil</code> if you do not wish to use client authentication.
> </dl>
>
> <p>The following example illustrates what you could put in
> <span class="file">~/.emacs</span> to enable both SASL authentication and
> STARTTLS. The
> server name (<code>smtpmail-smtp-server</code>) is <var>hostname</var>, the
> server port (<code>smtpmail-smtp-service</code>) is <var>port</var>, and the
> username and password are <var>username</var> and <var>password</var>
> respectively.
>
> <pre class="example"> ;; Authenticate using this username and password
> against my server.
> (setq smtpmail-auth-credentials
> '(("<var>hostname</var>" "<var>port</var>" "<var>username</var>"
> "<var>password</var>")))
>
> ;; Note that if <var>port</var> is an integer, you must not quote it as a
> ;; string. Normally <var>port</var> should be the integer 25, and the
> example
> ;; become:
> (setq smtpmail-auth-credentials
> '(("<var>hostname</var>" 25 "<var>username</var>"
> "<var>password</var>")))
>
> ;; Use STARTTLS without authentication against the server.
> (setq smtpmail-starttls-credentials
> '(("<var>hostname</var>" "<var>port</var>" nil nil)))
> </pre>
> <div class="node">
> <p><hr>
> <a name="Queued-delivery"></a>Next: <a rel="next" accesskey="n"
> href="#Server-workarounds">Server workarounds</a>,
> Previous: <a rel="previous" accesskey="p"
> href="#Authentication">Authentication</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">4 Queued delivery</h2>
>
> <p><a name="index-Dialup-connection-20"></a>If you connect to the internet
> via a dialup connection, or for some
> other reason don't have permanent internet connection, sending mail
> will fail when you are not connected. The SMTP library implements
> queued delivery, and the following variable control its behaviour.
>
> <dl>
> <dt><code>smtpmail-queue-mail</code><dd><a
> name="index-smtpmail_002dqueue_002dmail-21"></a> The variable
> <code>smtpmail-queue-mail</code> controls whether a simple
> off line mail sender is active. This variable is a boolean, and
> defaults to <code>nil</code> (disabled). If this is non-<code>nil</code>,
> mail is
> not sent immediately but rather queued in the directory
> <code>smtpmail-queue-dir</code> and can be later sent manually by invoking
> <code>smtpmail-send-queued-mail</code> (typically when you connect to the
> internet).
>
> <br><dt><code>smtpmail-queue-dir</code><dd><a
> name="index-smtpmail_002dqueue_002ddir-22"></a> The variable
> <code>smtpmail-queue-dir</code> specifies the name of the
> directory to hold queued messages. It defaults to
> <span class="file">~/Mail/queued-mail/</span>.
> </dl>
>
> <p><a name="index-smtpmail_002dsend_002dqueued_002dmail-23"></a> The
> function <code>smtpmail-send-queued-mail</code> can be used to send
> any queued mail when <code>smtpmail-queue-mail</code> is enabled. It is
> typically invoked interactively with <kbd>M-x
> smtpmail-send-queued-mail RET</kbd> when you are connected to the internet.
>
> <div class="node">
> <p><hr>
> <a name="Server-workarounds"></a>Next: <a rel="next" accesskey="n"
> href="#Debugging">Debugging</a>,
> Previous: <a rel="previous" accesskey="p" href="#Queued-delivery">Queued
> delivery</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">5 Server workarounds</h2>
>
> <p>Some SMTP servers have special requirements. The following variables
> implement support for common requirements.
>
> <dl>
> <dt><code>smtpmail-local-domain</code><dd><a
> name="index-smtpmail_002dlocal_002ddomain-24"></a> The variable
> <code>smtpmail-local-domain</code> controls the hostname sent
> in the first <code>EHLO</code> or <code>HELO</code> command sent to the
> server.
> It should only be set if the <code>system-name</code> function returns a
> name that isn't accepted by the server. Do not set this variable
> unless your server complains.
>
> <br><dt><code>smtpmail-sendto-domain</code><dd><a
> name="index-smtpmail_002dsendto_002ddomain-25"></a> The variable
> <code>smtpmail-sendto-domain</code> makes the SMTP library
> add <span class="samp">@</span> and the specified value to recipients
> specified in the
> message when they are sent using the <code>RCPT TO</code> command. Some
> configurations of sendmail requires this behaviour. Don't bother to
> set this unless you have get an error like:
>
> <pre class="example"> Sending failed; SMTP protocol error
> </pre>
> <p>when sending mail, and the debug buffer (see <a
> href="#Debugging">Debugging</a>)) contains
> an error such as:
>
> <pre class="example"> RCPT TO: <var>someone</var>
> 501 <var>someone</var>: recipient address must contain a domain
> </pre>
> </dl>
>
> <div class="node">
> <p><hr>
> <a name="Debugging"></a>Next: <a rel="next" accesskey="n"
> href="#Index">Index</a>,
> Previous: <a rel="previous" accesskey="p"
> href="#Server-workarounds">Server workarounds</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">6 Debugging</h2>
>
> <p>Sometimes delivery fails, often with the generic error message
> <span class="samp">Sending failed; SMTP protocol error</span>. Enabling one
> or both of
> the following variables and inspecting a trace buffer will often give
> clues to the reason for the error.
>
> <dl>
> <dt><code>smtpmail-debug-info</code><dd><a
> name="index-smtpmail_002ddebug_002dinfo-26"></a> The variable
> <code>smtpmail-debug-info</code> controls whether to print
> the SMTP protocol exchange in the minibuffer, and retain the entire
> exchange in a buffer <span class="samp">*trace of SMTP session to
> </span><var>server</var><span class="samp">*</span>,
> where <var>server</var> is the name of the mail server to which you send
> mail.
>
> <br><dt><code>smtpmail-debug-verb</code><dd><a
> name="index-smtpmail_002ddebug_002dverb-27"></a> The variable
> <code>smtpmail-debug-verb</code> controls whether to send the
> <code>VERB</code> token to the server. The <code>VERB</code> server
> instructs the
> server to be more verbose, and often also to attempt final delivery
> while your SMTP session is still running. It is usually only useful
> together with <code>smtpmail-debug-info</code>. Note that this may cause
> mail delivery to take considerable time if the final destination
> cannot accept mail.
>
> </dl>
>
> <div class="node">
> <p><hr>
> <a name="Index"></a>Previous: <a rel="previous" accesskey="p"
> href="#Debugging">Debugging</a>,
> Up: <a rel="up" accesskey="u" href="#Top">Top</a>
> <br>
> </div>
>
> <h2 class="chapter">7 Index</h2>
>
> <h3 class="section">7.1 Concept Index</h3>
>
> <ul class="index-cp" compact>
> <li><a href="#index-CRAM_002dMD5-15">CRAM-MD5</a>: <a
> href="#Authentication">Authentication</a></li>
> <li><a href="#index-Dialup-connection-20">Dialup connection</a>: <a
> href="#Queued-delivery">Queued delivery</a></li>
> <li><a href="#index-IMAP-7">IMAP</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-ISP-4">ISP</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-LOGIN-16">LOGIN</a>: <a
> href="#Authentication">Authentication</a></li>
> <li><a href="#index-Mail-Submission-12">Mail Submission</a>: <a
> href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a></li>
> <li><a href="#index-MDA-5">MDA</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-MTA-2">MTA</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-MUA-3">MUA</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-POP3-6">POP3</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-SASL-14">SASL</a>: <a
> href="#Authentication">Authentication</a></li>
> <li><a href="#index-SMTP-1">SMTP</a>: <a href="#How-Mail-Works">How Mail
> Works</a></li>
> <li><a href="#index-STARTTLS-17">STARTTLS</a>: <a
> href="#Authentication">Authentication</a></li>
> <li><a href="#index-Webmail-8">Webmail</a>: <a href="#How-Mail-Works">How
> Mail Works</a></li>
> </ul><h3 class="section">7.2 Function and Variable Index</h3>
>
>
>
> <ul class="index-fn" compact>
> <li><a
> href="#index-smtpmail_002dauth_002dcredentials-18"><code>smtpmail-auth-credentials</code></a>:
> <a href="#Authentication">Authentication</a></li>
> <li><a
> href="#index-smtpmail_002ddebug_002dinfo-26"><code>smtpmail-debug-info</code></a>:
> <a href="#Debugging">Debugging</a></li>
> <li><a
> href="#index-smtpmail_002ddebug_002dverb-27"><code>smtpmail-debug-verb</code></a>:
> <a href="#Debugging">Debugging</a></li>
> <li><a
> href="#index-smtpmail_002ddefault_002dsmtp_002dserver-11"><code>smtpmail-default-smtp-server</code></a>:
> <a href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a></li>
> <li><a
> href="#index-smtpmail_002dlocal_002ddomain-24"><code>smtpmail-local-domain</code></a>:
> <a href="#Server-workarounds">Server workarounds</a></li>
> <li><a
> href="#index-smtpmail_002dqueue_002ddir-22"><code>smtpmail-queue-dir</code></a>:
> <a href="#Queued-delivery">Queued delivery</a></li>
> <li><a
> href="#index-smtpmail_002dqueue_002dmail-21"><code>smtpmail-queue-mail</code></a>:
> <a href="#Queued-delivery">Queued delivery</a></li>
> <li><a
> href="#index-smtpmail_002dsend_002dqueued_002dmail-23"><code>smtpmail-send-queued-mail</code></a>:
> <a href="#Queued-delivery">Queued delivery</a></li>
> <li><a
> href="#index-smtpmail_002dsendto_002ddomain-25"><code>smtpmail-sendto-domain</code></a>:
> <a href="#Server-workarounds">Server workarounds</a></li>
> <li><a
> href="#index-smtpmail_002dsmtp_002dserver-9"><code>smtpmail-smtp-server</code></a>:
> <a href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a></li>
> <li><a
> href="#index-smtpmail_002dsmtp_002dservice-13"><code>smtpmail-smtp-service</code></a>:
> <a href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a></li>
> <li><a
> href="#index-smtpmail_002dstarttls_002dcredentials-19"><code>smtpmail-starttls-credentials</code></a>:
> <a href="#Authentication">Authentication</a></li>
> <li><a href="#index-SMTPSERVER-10"><code>SMTPSERVER</code></a>: <a
> href="#Emacs-Speaks-SMTP">Emacs Speaks SMTP</a></li>
> </ul>
> <div class="contents">
> <h2>Table of Contents</h2>
> <ul>
> <li><a name="toc_Top" href="#Top">Emacs SMTP Library</a>
> <li><a name="toc_How-Mail-Works" href="#How-Mail-Works">1 How Mail Works</a>
> <li><a name="toc_Emacs-Speaks-SMTP" href="#Emacs-Speaks-SMTP">2 Emacs Speaks
> SMTP</a>
> <li><a name="toc_Authentication" href="#Authentication">3 Authentication</a>
> <li><a name="toc_Queued-delivery" href="#Queued-delivery">4 Queued
> delivery</a>
> <li><a name="toc_Server-workarounds" href="#Server-workarounds">5 Server
> workarounds</a>
> <li><a name="toc_Debugging" href="#Debugging">6 Debugging</a>
> <li><a name="toc_Index" href="#Index">7 Index</a>
> <ul>
> <li><a href="#Index">7.1 Concept Index</a>
> <li><a href="#Index">7.2 Function and Variable Index</a>
> </li></ul>
> </li></ul>
> </div>
>
> </body></html>
>
> _______________________________________________
> Oralux mailing list
> [email protected]
> http://lists.freearchive.org/mailman/listinfo/oralux
_______________________________________________
Oralux mailing list
[email protected]
http://lists.freearchive.org/mailman/listinfo/oralux
