forked from neomutt/neomutt
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- substitute mutt with neomutt - fix openSUSE capitalisation
- Loading branch information
Showing
20 changed files
with
98 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
IMAP/SSL in mutt | ||
IMAP/SSL in neomutt | ||
================ | ||
|
||
Compilation | ||
----------- | ||
If you want to have SSL support in mutt, you need to install OpenSSL | ||
If you want to have SSL support in neomutt, you need to install OpenSSL | ||
(http://www.openssl.org) libraries and headers before compiling. | ||
OpenSSL versions 0.9.3 through 1.0.1c have been tested. | ||
|
||
|
@@ -29,7 +29,7 @@ or | |
mailboxes imaps://localhost/inbox | ||
mailboxes imaps://localhost:994/inbox | ||
|
||
If you get errors about lack of entropy, it means that Mutt was unable | ||
If you get errors about lack of entropy, it means that NeoMutt was unable | ||
to find a source of random data to initialize SSL library with. Should | ||
this happen, you need to generate the data yourself and save it in a | ||
file pointed by $entropy_file or $RANDFILE (environment) variables or | ||
|
@@ -40,10 +40,10 @@ generates unpredictable output, for example 'ps aluxww' in Linux, and | |
calculating the MD5-sum from the output and saving it in a file. | ||
|
||
** Note: The contents of the file pointed by $RANDFILE environment | ||
** variable (or ~/.rnd if unset) will be overwritten every time Mutt | ||
** variable (or ~/.rnd if unset) will be overwritten every time NeoMutt | ||
** is run so don't put anything you can't afford to lose in that file. | ||
|
||
The files Mutt will try to use to initialize SSL library with are files | ||
The files NeoMutt will try to use to initialize SSL library with are files | ||
pointed by $entropy_file and $RANDFILE (or ~/.rnd if unset.) If your | ||
OpenSSL is version 0.9.5 or later, the previous files can also be EGD | ||
sockets (see http://www.lothar.com/tech/crypto/ for more information | ||
|
@@ -66,7 +66,7 @@ can also be saved so that further connections to the server are | |
automatically accepted. | ||
|
||
If OpenSSL was built with support for ServerNameIndication (SNI) and TLS | ||
is used in the negotiation, mutt will send its idea of the server-name | ||
is used in the negotiation, neomutt will send its idea of the server-name | ||
as part of the TLS negotiation. This allows the server to select an | ||
appropriate certificate, in the event that one server handles multiple | ||
hostnames with different certificates. | ||
|
@@ -75,7 +75,7 @@ If your organization has several equivalent IMAP-servers, each of them | |
should have a unique certificate which is signed with a common | ||
certificate. If you want to use all of those servers, you don't need to | ||
save each server certificate on the first connect. Instead, you can get | ||
the signer certificate and save it instead. That way, mutt will | ||
the signer certificate and save it instead. That way, neomutt will | ||
automatically accept all certificates signed with the saved certificate. | ||
|
||
System-wide certificates are by default considered trusted when checking | ||
|
@@ -90,7 +90,7 @@ certificates each time you connect to a server, you have set this | |
variable to some reasonable value. | ||
|
||
For example: | ||
set certificate_file=~/.mutt/certificates | ||
set certificate_file=~/.neomutt/certificates | ||
|
||
|
||
Troubleshooting | ||
|
@@ -119,4 +119,4 @@ [email protected] | |
|
||
Updated by: | ||
Jeremy Katz <[email protected]> | ||
Phil Pennock <mutt[email protected]> | ||
Phil Pennock <neomutt[email protected]> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
USING PGP FROM WITHIN MUTT | ||
USING PGP FROM WITHIN NEOMUTT | ||
|
||
|
||
WARNING: The configuration interface has completely changed as of | ||
|
@@ -9,12 +9,12 @@ WARNING: The configuration interface has completely changed as of | |
USERS' GUIDE | ||
|
||
|
||
How do I use mutt with PGP, PGP5, or GnuPG? | ||
How do I use neomutt with PGP, PGP5, or GnuPG? | ||
------------------------------------------- | ||
|
||
Go to the contrib subdirectory of the source tree. You'll find | ||
three files there, pgp2.rc, pgp5.rc, and gpg.rc. These files | ||
contain ready-to-use configurations for using mutt with pgp2, pgp5, | ||
contain ready-to-use configurations for using neomutt with pgp2, pgp5, | ||
and gpg. | ||
|
||
Include one of these files with your ~/.muttrc, and things should | ||
|
@@ -28,10 +28,10 @@ given to the PGP binaries match your needs. | |
Frequently Asked Questions and Tips | ||
----------------------------------- | ||
|
||
Q: "People are sending PGP messages which mutt doesn't | ||
Q: "People are sending PGP messages which neomutt doesn't | ||
recognize. What can I do?" | ||
|
||
The new way is to leave headers alone and use mutt's | ||
The new way is to leave headers alone and use neomutt's | ||
check-traditional-pgp function, which can detect PGP messages at | ||
run-time, and adjust content-types. | ||
|
||
|
@@ -96,7 +96,7 @@ if (/^$BPGPS/:b && /^$EPGPS/:b) | |
|
||
Q: "I don't like that PGP/MIME stuff, but want to use the | ||
old way of PGP-signing my mails. Can't you include | ||
that with mutt?" | ||
that with neomutt?" | ||
|
||
The old answer to this question used to be this: | ||
|
||
|
@@ -113,7 +113,7 @@ The old answer to this question used to be this: | |
|
||
There's a new answer, though: Set the $pgp_autoinline | ||
configuration variable (it's a quad-option) to something different | ||
from "no" (that's the default). Mutt will then try to use | ||
from "no" (that's the default). NeoMutt will then try to use | ||
application/pgp wherever it makes sense. In particular, it does | ||
not make any sense with multiparts, or non-ASCII or non-text bodies. | ||
In all other cases, PGP/MIME is used unconditionally. | ||
|
@@ -127,7 +127,7 @@ Q: "I don't like all the ^Gs and various other verbosity | |
|
||
Roland Rosenfeld <[email protected]> has found a quite | ||
elegant solution to this problem: PGP has some pretty good foreign | ||
language support. So we just introduce a language called "mutt" | ||
language support. So we just introduce a language called "neomutt" | ||
which contains empty strings for the messages we don't want to see. | ||
To use this, copy either language.txt or language50.txt (depending | ||
on what PGP version you are using) to your $PGPPATH. Make sure the | ||
|
@@ -157,15 +157,15 @@ or exim. | |
Auxiliary Programs | ||
------------------ | ||
|
||
Mutt needs two auxiliary programs for its PGP support: pgpewrap and | ||
NeoMutt needs two auxiliary programs for its PGP support: pgpewrap and | ||
pgpring. | ||
|
||
|
||
1. pgpring | ||
|
||
pgpring is a key ring dumper. It extracts information from PGP's | ||
binary key ring and emits it in an (almost) readable output format | ||
understood by mutt's key selection routines. This output format | ||
understood by neomutt's key selection routines. This output format | ||
mimics the one used by the GNU Privacy Guard (GPG). | ||
|
||
You'll need this program with PGP 2 and PGP 5. | ||
|
@@ -203,14 +203,14 @@ will execute: | |
pgpe file -r a -r b -r c | ||
|
||
This script is needed with PGP 5 and with GPG, since their command | ||
line interfaces can't be properly served by mutt's format mechanism. | ||
line interfaces can't be properly served by neomutt's format mechanism. | ||
|
||
|
||
|
||
The Configuration Interface | ||
--------------------------- | ||
|
||
As usual within mutt, the configuration interface for the PGP | ||
As usual within neomutt, the configuration interface for the PGP | ||
commands relies on printf-like formats. For all PGP commands, the | ||
following %-sequences are defined. | ||
|
||
|
@@ -230,7 +230,7 @@ following %-sequences are defined. | |
configuration variable $pgp_sign_as. You probably need to | ||
use this within a conditional % sequence. | ||
|
||
%r In many contexts, mutt passes key IDs to pgp. %r expands to | ||
%r In many contexts, neomutt passes key IDs to pgp. %r expands to | ||
a list of key IDs. | ||
|
||
The following command formats are defined: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.