that this is *not* the full pathname, but relative to the user's
home directory. Defaults to "mailbox" if FILE is not specified.
---enable-pop
- enable POP3 support
-
---enable-imap
- enable IMAP support
-
--with-gss[=PFX]
Enable GSSAPI authentication to IMAP servers. This should work with
both MIT and Heimdal GSSAPI implementations - others haven't been
--disable-nls
This switch disables mutt's native language support.
---with-included-gettext
- Mutt will be built using the GNU gettext library included in
- the intl/ sub-directory. You may need to use this switch if
- your machine has something which looks like gettext to the
- configure script, but isn't able to cope with mutt's catalog
- files.
-
---with-regex
- use GNU regex instead of local regexp routines. Many systems
- don't have the POSIX compliant regcomp/regexec/regfree
- routines, so this provides a way to support them.
-
--enable-flock
use flock() to lock files.
If you really want to, you can configure Mutt --disable-iconv, but
there will then be no character set conversion.
-
-Platform Notes
-==============
-
-All platforms
-
- There is a bug in most (if not all) S-Lang versions which
- prevents the Meta key from working with mutt. A patch can
- be found in the file contrib/patch.slang-1.2.2.keypad.1 in
- this mutt distribution.
-
-
-Solaris 2.4
-
- The system regcomp() and regexec() routines are very badly
- broken. This should be automatically detected by the
- configure script. If not, use the --with-regex switch when
- configuring mutt.
-
- We are also hearing reports that Solaris 2.4's NLS libraries
- dump core with mutt when using a locale different from "C".
- Use the --with-included-gettext configuration switch if you
- experience this problem.
-
- Color does not work right with Solaris curses. You will
- have to compile with either ncurses or slang to get working
- color support.
-
-Solaris 2.6
-
- There are reports that mutt behaves strangely when linked with
- the system regexp library. Please use the --with-regex switch
- when configuring on this platform.
-
- For the real fix, applying Sun patches # 105490-05 (linker
- patch) and # 105210-17 (libc and malloc patch) from
- sunsolve.sun.com has been reported to stop these problems
- from occurring.
-
-Linux
-
- On recent Linux systems, flock() and fcntl() locks don't mix. If
- you use the --enable-flock switch on such systems, be sure to
- give the --disable-fcntl argument as well.
-
-Sparc Linux
-
- Redhat 4.2 Sparc users reported problems with some system
- include files when building mutt. Configuring mutt with the
- --disable-warnings switch is said to help against this problem.
-
# Test the .tar file by building everything
AM_DISTCHECK_CONFIGURE_FLAGS = --enable-debug --enable-flock --enable-gpgme \
- --enable-mailtool --enable-nfs-fix --enable-notmuch --with-bdb \
+ --enable-nfs-fix --enable-notmuch --with-bdb \
--with-gdbm --with-gnutls --with-gss --with-kyotocabinet --with-lmdb \
--with-mixmaster --with-qdbm --with-sasl --with-tokyocabinet
OpenSSL versions 0.9.3 through 1.0.1c have been tested.
For SSL support to be enabled, you need to run the ``configure''
-script with ``--enable-imap --with-ssl[=PFX]'' parameters. If the
+script with ``--with-ssl[=PFX]'' parameters. If the
OpenSSL headers and libraries are not in the default system search
paths (usually /usr/include and /usr/lib) you can use the optional PFX
argument to define the root directory of your installation. The
<sect1 id="pop">
<title>POP3 Support</title>
- <para>If Mutt is compiled with POP3 support (by running the
- <emphasis>configure</emphasis> script with the
- <emphasis>--enable-pop</emphasis> flag), it has the ability to work with
- mailboxes located on a remote POP3 server and fetch mail for local
+ <para>Mutt has POP3 support and has the ability to work with mailboxes
+ located on a remote POP3 server and fetch mail for local
browsing.</para>
<para>Remote POP3 servers can be accessed using URLs with the
<literal>pop</literal> protocol for unencrypted and
<sect1 id="imap">
<title>IMAP Support</title>
- <para>If Mutt was compiled with IMAP support (by running the
- <emphasis>configure</emphasis> script with the
- <emphasis>--enable-imap</emphasis> flag), it has the ability to work with
- folders located on a remote IMAP server.</para>
+ <para>Mutt has IMAP support and has the ability to work with folders
+ located on a remote IMAP server.</para>
<para>You can access the remote inbox by selecting the folder by its URL
(see
<xref linkend="url-syntax" />for details) using the
<sect1 id="smtp">
<title>SMTP Support</title>
<para>Besides supporting traditional mail delivery through a
- sendmail-compatible program, Mutt supports delivery through SMTP if it
- was configured and built with
- <literal>--enable-smtp</literal>.</para>
+ sendmail-compatible program, Mutt supports delivery through SMTP.</para>
<para>If the configuration variable
<link linkend="smtp-url">$smtp_url</link> is set, Mutt will contact the
given SMTP server to deliver messages; if it is unset, Mutt will use the
and MH, reading the headers from a single file is much faster than
looking at possibly thousands of single files (since Maildir and MH use
one file per message.)</para>
- <para>Header caching can be enabled via the configure script and the
- <emphasis>--enable-hcache</emphasis> option. It's not turned on by
- default because external database libraries are required: one of
- tokyocabinet, kyotocabinet, qdbm, gdbm, lmdb or bdb must be
- present.</para>
+ <para>Header caching can be enabled by configuring one of the database
+ backends. One of tokyocabinet, kyotocabinet, qdbm, gdbm, lmdb or
+ bdb.</para>
<para>If enabled,
<link linkend="header-cache">$header_cache</link> can be used to either
point to a file or a directory. If set to point to a file, one database
<sect2 id="nntp-intro">
<title>Introduction</title>
<para>Reading news via NNTP</para>
- <para>If Mutt is compiled with the
- <emphasis>--enable-nntp</emphasis> option, it can read from a news
- server using NNTP.</para>
+ <para>Mutt can read from a news server using NNTP.</para>
<para>The default news server can be obtained from the
<literal>$NNTPSERVER</literal> environment variable or from the
<literal>/etc/nntpserver</literal> file. Like in other news readers,
projects / neomutt / commitdiff