There are scenarios where setting up SSL for a mail service would not
provide any security benefit, just complicate things or would be
outright impossible. For example, the unofficial emersion/hydroxide
Protonmail bridge is usually ran on your own computer or a home server,
thus it does not bother with implementing encryption. One might also
have a mail server on LAN where getting a cert is difficult, and is
only accessible to trusted machines.

In the manual settings, a prompt is added where the desired enctyption
method can be chosen. For regular users, sensible defaults are provided
both for encryption and ports that can be selected by pressing Enter.

Room for improvement: it's currently assumed that if SMTP has no TLS
support, the PLAIN authentication method is used. This is written out to
`msmtprc`, because by default it disallows sending password data in
cleartext, and fails if the server does not support GSSAPI. Maybe prompt
the user?

This might also be useful for the official Protonmail bridge, but I do
not know how that handles TLS.

I believe this addresses issue #456 where if you add a protonmail account you get an error.  This is caused by prematurely returning from the case statement that queries whether you have a protonmail account or not.

Co-authored-by: rjl6789 <rlives6789@gmail.com>

I think a recent change tried to send output from crontab to dev/null to avoid messages appearing a) when setting the crontab, b) whenever mailsync is run.  However the redirection was for the string concatenation meaning a null string was piped to cron obliterating the crontab (thank goodness for backups). I have put the redirection in the correct location (similar to a few lines above when removing the mailsync line).  I have also redirected all output of the mailsync (both errors and normal messages) to dev null.

Co-authored-by: rjl6789 <rlives6789@gmail.com>

Let's make crontab a little quiet here, unless for those who set up mail for crontab error handling will be disturbed every few minutes.

* Simple Fixes

* Tweak wording

* Update openfile

* ShellChecked

* Little Fixes

* mutt-wizard works on FreeBSD, also changed mbsync with isync (actual package name)

* Added pgp support

* Added vxempire.xyz to domains.cvs

* Fixed set_folder for vxempire.xyz

According to man page of mbsync, AuthMechs is the correct spelling of the option.

the prefix is not correct at least for Ubuntu distro. Since doc clearly
states the dependencis. We assume msmpt is on the PATH environment.

Co-authored-by: Lingyu Zhu <lynuszhu@gmail.com>

Co-authored-by: chau.bao.long <chau.bao.long@framgia.com>

when u have multiple emails in neomutt at the same time, you can sometimes forget which email u'r currently viewing, so with this addition youll be able to see.
all i did was add the email to the default status bar configuration

* Run serverinfo query based on if proton or not

* If domain is already protonmail don't ask if it is

* Fix protonmail fingerprint extraction

* Update docs re: protonmail bridge timing out

Added new search location for certificates and modified command that caused errors for Protonmail users.

If the password contains single quotes and is not surrounded by quotes,
Mutt removes the single quotes, rendering an incorrect password.

This patch puts the environment variable PREFIX in more use. If
specified, mull-wizard Makefile substitute all instances of prefix with
the provided environment variable.

Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com>

In my [PR 224](https://github.com/LukeSmithxyz/mutt-wizard/pull/224), I
introduced a bug.  While I was catching SIGINT with the trap statement,
I did not actually exit the script and returned into the shell.

Fixes https://github.com/LukeSmithxyz/mutt-wizard/issues/234

The terminal text color  wasn't reset when the user  aborted the wizard
while being prompted for input.
This resolves https://github.com/LukeSmithxyz/mutt-wizard/issues/224

The current test  did not terminate  the script in cases  when the user
already has a private GPG key,  but they'd not initialized the password
store.
This leads to an infinite loop in the `getpass()` function.

The commit fixes https://github.com/LukeSmithxyz/mutt-wizard/issues/204

Checking for a secret key with format `<foo@bar.com>` may not work for
people that store key IDs in .gpg-id. Removing the `<` and `>` makes it
work for both beople that use emails and people that use IDs.