1.8.0 has been released two years ago. I think it's very
reasonable to have a future Mutt release to require that version.
At least by default. If anyone has a valid use-case maybe a fallback
option could support 1.6.0, which is over three years old.
What do you think?
--
ilf
If you upload
lows including attachments in
inline-forwards (i.e. $mime_forward unset, $forward_decode set.)
https://gitlab.com/muttmua/mutt/blob/master/UPDATING
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
signature.asc
Description: PGP signature
won't have problems
if you use both Mutt and GPGME from a distribution. Only if you build a
modern mutt with an antiqated GPGME - in which case, you can also build
a modern GPGME.
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
signature.asc
Description: PGP signature
st version of GPGME that you would still feel
comfortable to depend on - for software developed now, released in
months, and shipped in years?
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
signature.asc
Description: PGP signature
of date.
I don't know much about macOS, but there is gpgme 1.13.0 in Homebrew:
https://formulae.brew.sh/formula/gpgme
Do we really need to still support gpgme 1.4.0 from 2013?
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
signature.asc
Description: PGP signature
as to an users email habits
and activities, which might be undesirable.
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
to be what others like Thunderbird are doing
[2].
1. https://bugzilla.mozilla.org/show_bug.cgi?id=902580
2.
https://dxr.mozilla.org/comm-central/source/comm/mailnews/compose/src/nsMsgCompUtils.cpp#916
Should I open a ticket with this suggestion?
--
ilf
If you upload your address book to "the
Kurt Hackenberg:
I guess msmtp is obsolete for Mutt users anyway, since Mutt now
contains an SMTP client.
No, msmtp is not obsolete for Mutt users. People have different
requirements, and it's good Mutt allows choice. (Mutt is an MUA, not an
MSA afterall. :)
-- sent with msmtp
--
ilf
Maxim Tarasov:
+env->subject = safe_strdup ("Re:");
I agree that this should be the default value.
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
stored
attachments by other users (separate user for libreoffice, separate
user for image viewer,...). Manually calling chmod *each and every
time* is even more security-error-prone than being able to set umask
once for time being.
--
ilf
If you upload your address book to "the clou
ssage each receive new message
identifiers.
https://tools.ietf.org/html/rfc5322#section-3.6.4
If you want URLs to be human-meaningful, don't use Message-ID.
I for one thing Mutt shouldn't invent its own, but just use a random
UUID, like so many other MUAs.
--
ilf
If you upload your ad
Yes, sorry, ""> > foo" and ">>foo" are bad, it should be ">> foo""
Kurt Hackenberg:
What? The last two are the same.
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
'>', but
not after others, I think it's thirty years too late to change that
quoting mechanism. You'd have to change all the mail readers in the
world, and also RFC 3676. We know that won't happen.
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
:
https://mutt.org.ua/download/current/patch-1.13.0.vvv.quote.xz
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
believe in rough consensus and running
code."
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
15 matches
Mail list logo