I'm very close to a usable setup for S/MIME. It took a lot of research, the
documentation isn't great and seems a bit outdated in some cases
(https://gitlab.com/muttmua/mutt/-/wikis/MuttGuide/UseSMIME - patch gpgme?),
but the basics work.
Two questions remain now. The first, when using mutt wit
Kevin J. McCarthy writes:
> On Sun, Jun 14, 2020 at 12:20:22PM +0100, isdtor wrote:
> >Two questions remain now. The first, when using mutt with gpgme, are
> >any of the gpg/gpg/certificate/smime related configuration variables
> >still relevant? And if so, which? The ques
Andrew D. Arenson writes:
> My organization is moving to Office365 and have decided, sadly, not to
> support IMAP.
>
> Anyone have insight in how mutt might still be able to connect to
> Office365?
>
> A co-worker has been investigating a project called davmail, which
> provi
> * $smime_default_key is used for self encryption and signing
> * $smime_sign_as overrides $smime_default_key for signing
> * $smime_is_default
> * $smime_self_encrypt
>
> Note the GPGME backend stores certs differently, and does not use the
> same IDs as the traditional backend. The gppsm com
Hi all,
I upgraded my email tool chain recently to the latest versions of
mutt/gpg/gpgme etc. and now S/MIME signing and encrypting no longer works. The
bad part is, going back to the previous executables also no longer works, so
I'm wondering whether gpg has updated some files in an incompatib
> > I'm not familiar with fetchmail. Would you mind saying more about how
> > you use fetchmail and what you did to get davmail to work?
For davmail, I just followed the Linux setup instructions on their web site,
nothing more. For the added bonus, I set it up for imaps with a self-signed
Hi all,
$work moved to a new email system (in-house exchange). I've managed to
configure mutt for it and can successfully access the mailbox for reading. But
I am unable to send, with a message
No authenticators available
What could be the problem here? I have the same settings configured u
isdtor writes:
>
> Hi all,
>
> $work moved to a new email system (in-house exchange). I've managed to
> configure mutt for it and can successfully access the mailbox for reading.
> But I am unable to send, with a message
>
> No authenticators available
>
>
> The --with-gss is actually only used for IMAP authentication. For SMTP,
> Mutt's (simple) implementation relies entirely on SASL. Is it possible you
> don't have the modules installed for SASL's GSSAPI support?
>
> If you're on a Debian derivative, try installing libsasl2-modules-gssapi-mit
> Try running mutt at debug level 2 and see what it prints. There should be a
> message:
> smtp_authenticate: Trying method XXX
> for each method, and then hopefully something inside the SASL authentication
> starting with:
> smtp_auth_sasl:
>
> I don't know what the problem is, but pe
> At this point, I'm just guessing, as I have almost no experience with
> Kerberos. The message above may supply some kind of clue: Server not
> found in Kerberos database. Which GSSAPI library is SASL using? Is it
> possible there is some setup or configuration that library needs to
> fun
Philippe Meunier writes:
> Hello,
>
> I use an IMAPS server for reading email and an STMPS server for sending
> email. Both servers use the same password, which I think is a fairly
> common setup.
>
> I know about imap_pass and smtp_pass but I don't want to write my password
> in my .muttrc for
All,
My S/MIME setup has died one from day to the next and I cannot find out why.
Symptom: trying to send e.g. signed email, the result is
error signing data: No CRL known?
TBH this looks more like a gpg than a mutt problem, and I haven't figured out
how to debug this. Same error for encrypt
> >TBH this looks more like a gpg than a mutt problem, and I haven't
> >figured out how to debug this. Same error for encrypting.
>
> Yes, it sounds like something changed with either the GPGME version, or
> perhaps a configuration file. I can't offer much advice except to check
> those thin
I realize my config has a lot of moving parts and non-default settings, but I
still hope someone can shine a light on this.
I use less instead of the internal pager (note -R option),
set pager="less -eiMR"
and elinks for html display
text/html; /usr/bin/elinks -localhost 1 -no-connect 1 -for
> I think that might be elinks. I'm not sure about what all the relevant
> options are, but document.colors.text (default foreground) may be what
> is giving you light gray text. You probably also want
> document.colors.use_document_colors to be 2 and document.css.enable to
> be enabled (1)?
Tha
> I fear the days where my dayjob requires me to use something else (than
> neo/mutt).
After a corp takeover, my dayjob is fully MS-centric. Yet, I am continuing to
use mutt for everything that is required, including S/MIME, and LDAP/AD based
address completion. Davmail+tb also works fine for
17 matches
Mail list logo
