googly.negotiator...@aceecat.org (12024-05-21):
> > The problem with any automation, anyway if with GnuPG or not, is how
> > to enter the passphrase or PIN to get access to the private key.
> Does the gpg-agent help with that? It is supposed to, I think.
Makes it worse. Without gpg-agent, your
Matthias Apitz (12024-05-21):
> I do use GnuPG based on OpenPGP SIM cards even in my Linux telephone
> (Pusim L5) for crypting files, ~350 passwords (password-store) and SSH
> connections (the RSA secret is on the OpenPGP card). All works fine and
> gives access to the secrets by entering a 6
On Tue, May 21, 2024 at 05:57:00PM GMT, Matthias Apitz wrote:
> The problem with any automation, anyway if with GnuPG or not, is how
> to enter the passphrase or PIN to get access to the private key.
Does the gpg-agent help with that? It is supposed to, I think.
--
Ian
El día martes, mayo 21, 2024 a las 10:49:08a. m. +0200, Nicolas George escribió:
> Matthias Apitz (12024-05-21):
> > How could we expand this for signing mails on the fly?
>
> Hi.
>
> ...
>
> - Ditch GPG. GPG has been increasingly incapable of deciding if it is a
> high-level tool or a
Matthias Apitz (12024-05-21):
> How could we expand this for signing mails on the fly?
Hi.
For fine control, I would suggest:
- Build your mail entirely yourself without relying on a MUA like mutt
and inject it directly into the MTA local injector /usr/lib/sendmail.
- Ditch GPG. GPG has been
Hi Matthias,
On 2024-05-21 07:45, Matthias Apitz wrote:
> Hello,
>
> Our Library Management System sends mails to patrons and media vendors
> which are assembled in a shell script with all data (Subject, body, To,
> attachments, etc) by a call to the MUA mutt 2.1.1 which pipes the mail
> to
On 13May2024 10:49, Joe Damato via Mutt-users wrote:
And now when I switch to the netdev directory within mutt (by pressing
c),
I can easily see any messages that mention my email address in any thread
on the list.
Late to the thread, and purely for interest: this is what I use for the
On Mon, May 13, 2024 at 06:51:26AM +0200, Christopher Zimmermann wrote:
> On Sun, May 12, 2024 at 04:49:45PM -0700, Joe Damato via Mutt-users wrote:
> > A follow up question: is there a way to apply this to only specific imap
> > directories?
>
> What you now want to use is a folder hook:
>
>
In days of yore (Sun, 12 May 2024), Joe Damato via Mutt-users thus quoth:
> I am subscribed to some high traffic email lists (linux kernel development
> stuff).
>
> There are two cases I am trying to deal with which are fairly similar:
>
> 1. I am subscribed to a mailing list. I start a
On Sun, May 12, 2024 at 04:49:45PM -0700, Joe Damato via Mutt-users wrote:
A follow up question: is there a way to apply this to only specific
imap directories?
What you now want to use is a folder hook:
http://www.mutt.org/doc/manual/#folder-hook
signature.asc
Description: PGP signature
On Mon, May 13, 2024 at 12:13:47AM +0200, Francesco Ariis wrote:
> Hello Joe,
>
> Il 12 maggio 2024 alle 14:47 Joe Damato via Mutt-users ha scritto:
> > Is there any way to get mutt to highlight/colorize/mark or somehow
> > indicate to me messages which specifically have my email in the TO or CC
Hello Joe,
Il 12 maggio 2024 alle 14:47 Joe Damato via Mutt-users ha scritto:
> Is there any way to get mutt to highlight/colorize/mark or somehow
> indicate to me messages which specifically have my email in the TO or CC
> line so that I don't miss those?
This is what I do. First you add a
On Thu, May 09, 2024 at 05:59:39PM +0200, Dennis Preiser wrote:
On Thu, May 09, 2024 at 04:24:56PM +0100, Chris Green wrote:
I have the following in muttrc so that hitting 'Enter' (the CR key) on
the keyboard sends an E-Mail after composing it:-
bindcompose \n send-message #
On Thu, May 09, 2024 at 06:47:30PM +, Ебрашка wrote:
> Can you tell me how to make the date display in the catalog with letters
> in day/month/year format, i.e. 09/05/2024 I write in muttrc set
> date_format="%d/%m/%Y" and there are no changes.
I think you need to override the default or
On Thu, May 09, 2024 at 05:59:39PM +0200, Dennis Preiser wrote:
> On Thu, May 09, 2024 at 04:24:56PM +0100, Chris Green wrote:
> > I have the following in muttrc so that hitting 'Enter' (the CR key) on
> > the keyboard sends an E-Mail after composing it:-
> >
> > bindcompose \n
On Thu, May 09, 2024 at 04:24:56PM +0100, Chris Green wrote:
> I have the following in muttrc so that hitting 'Enter' (the CR key) on
> the keyboard sends an E-Mail after composing it:-
>
> bindcompose \n send-message # rather than 'y'
>
> This works as intended on the old system
On 9 May 2024 16:24 +0100, from c...@isbd.net (Chris Green):
> I have the following in muttrc so that hitting 'Enter' (the CR key) on
> the keyboard sends an E-Mail after composing it:-
>
> bindcompose \n send-message # rather than 'y'
> On the new system the help line at the
On Sat, Apr 13, 2024 at 11:30:55AM +0200, Laura Orvokki Kursula via Mutt-users
wrote:
> > > I have encountered a strange problem setting up mutt: when I
> > > attach a signature block to my e-mail using `$signature', my PGP
> > > signature is, according to mutt, invalid. E-mails without
> > >
On Sat, Apr 13, 2024 at 07:39:45AM +0200, Sirius via Mutt-users wrote:
> In days of yore (Sat, 13 Apr 2024), Laura Orvokki Kursula via Mutt-users thus
> quoth:
> > Hello all
> >
> > I have encountered a strange problem setting up mutt: when I attach a
> > signature
> > block to my e-mail using
In days of yore (Sat, 13 Apr 2024), Laura Orvokki Kursula via Mutt-users thus
quoth:
> Hello all
>
> I have encountered a strange problem setting up mutt: when I attach a
> signature
> block to my e-mail using `$signature', my PGP signature is, according to mutt,
> invalid. E-mails without
On Thu, Apr 11, 2024 at 02:35:30PM -0700, googly.negotiator...@aceecat.org
wrote:
> On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> - if the mailing list does mess with msgid, it absolutely must do it
> consistently for all copies of the message.
For existing software
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin
> wrote:
>
> > On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> > > Question, what should I write in .muttrc to make my outgoing
> > > mails have the same
On Thu, Apr 11, 2024 at 01:13:52PM +1000, raf via Mutt-users wrote:
> > > Question, what should I write in .muttrc to make my outgoing
> > > mails have the same beautiful message-ID as Yandex mail?
> > The unfathomable thing about this question is why you (or anyone)
> > should care in the
Hello Will,
On 2024-04-10 10:05:50, Will Yardley wrote:
> On Wed, Apr 10, 2024 at 08:22:03PM +0800, Sadeep Madurange wrote:
> > When deleting emails (with d), I get a prompt for purging them. I'd
> > like to silence that prompt with 'no'. And, see the prompt when I
> > change folder, or better
El día miércoles, abril 10, 2024 a las 06:26:23 -0400, Kurt Hackenberg escribió:
> On Wed, Apr 10, 2024 at 10:23:37AM +0200, Matthias Apitz wrote:
>
> > I wasn't aware before, that muttprint exists for my mobile phone as
> > well. I've now installed it and configured it, even with the FreeBSD's
On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin
wrote:
> On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> > Question, what should I write in .muttrc to make my outgoing mails have
> > the same beautiful message-ID as Yandex mail?
>
> The unfathomable thing about this question
On Wed, Apr 10, 2024 at 07:25:11AM +0200, Matthias Apitz wrote:
> El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
>
> > On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> > > I do use on FreeBSD muttprint:
> > >
> > > Name : muttprint Version: 0.73_5 Installed
> > >
On Wed, Apr 10, 2024 at 10:23:37AM +0200, Matthias Apitz wrote:
I wasn't aware before, that muttprint exists for my mobile phone as
well. I've now installed it and configured it, even with the FreeBSD's
Beastie in the right corner.
What? Do you run FreeBSD and Mutt on the phone?
On Wed, Apr 10, 2024 at 08:22:03PM +0800, Sadeep Madurange wrote:
> When deleting emails (with d), I get a prompt for purging them. I'd like
> to silence that prompt with 'no'. And, see the prompt when I change
> folder, or better yet, when I quit mutt.
>
> Is there a way to do this?
If I'm
On Wed, Apr 10, 2024 at 01:05:09PM +0800, Kevin J. McCarthy wrote:
> On Tue, Apr 09, 2024 at 09:33:06AM -0700, Will Yardley wrote:
> > side note: using quotes around the template screws things up, that is,
> > set message_id_format=""
> > vs
> > set message_id_format=
> >
> > results in a broken
On Wed, Apr 10, 2024 at 08:22:03PM +0800, Sadeep Madurange wrote:
> Hello,
>
> When deleting emails (with d), I get a prompt for purging them. I'd like
> to silence that prompt with 'no'. And, see the prompt when I change
> folder, or better yet, when I quit mutt.
>
> Is there a way to do this?
On 2024-04-10, Matthias Apitz wrote:
> El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
>
>> On 04/07/2024 07:42 AM, Matthias Apitz wrote:
>> > I do use on FreeBSD muttprint:
>> >
>> > Name : muttprint
>> > Version: 0.73_5
[...]
>> > WWW:
El día miércoles, abril 10, 2024 a las 07:25:11 +0200, Matthias Apitz escribió:
> I could make it available on my Internet host. About any RPM I don't
> know much. On my Linux mobilephone, running a Debian I see:
>
> $ apt search muttprint
> muttprint/byzantium 0.73-10 all
> Pretty printing of
Thanks everyone for the replies and discussion, something to ponder.
Всем спасибо за ответы и дискуссию, есть над чем поразмышлять.
El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
> On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> > I do use on FreeBSD muttprint:
> >
> > Name : muttprint
> > Version: 0.73_5
> > Installed on : Sun Sep 24 11:32:52 2023 CEST
> > Origin : print/muttprint
On Tue, Apr 09, 2024 at 09:33:06AM -0700, Will Yardley wrote:
side note: using quotes around the template screws things up, that is,
set message_id_format=""
vs
set message_id_format=
results in a broken message-id with the quotes inside the angle brackets
(Message-ID: <"xyz">)
That shouldn't
On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> I do use on FreeBSD muttprint:
>
> Name : muttprint
> Version: 0.73_5
> Installed on : Sun Sep 24 11:32:52 2023 CEST
> Origin : print/muttprint
> Architecture : FreeBSD:14:amd64
> Prefix : /usr/local
> Categories
On 09Apr2024 07:11, Michael Kjörling wrote:
On 9 Apr 2024 07:32 +1000, from c...@cskk.id.au (Cameron Simpson):
_Or_ you could "set sendmail=" to a script of your own to add a
message-id
header - that is what mutt uses to deliver the message to a mail system -
you could add a header there then
Cameron Simpson wrote:
> On 07Apr2024 13:19, Ебрашка wrote:
> > Question, what should I write in .muttrc to make my outgoing mails have
> > the same beautiful message-ID as Yandex mail?
> > For example Message-Id: <43265...@example.com> consisting of random
> > digits and domain name
>
> I
On Tue, Apr 09, 2024 at 09:25:56AM -0700, Will Yardley wrote:
> On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> > If so that feature may not be working correctly...
>
> That is the old format for the mutt version I'm using. The new format
> looks like
>
>
>
> Thought you were
On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> > I think some people mentioned some minor threading issues with the new
> > format?
>
> Is that so? I don't recall noticing anything about that... I'd love a
> pointer to some details, if anyone has that.
It's possible that it was
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails
> have the same beautiful message-ID as Yandex mail?
Talk about bikeshedding :-)
--
Ian
On Tue, Apr 09, 2024 at 11:33:55AM -0400, Derek Martin wrote:
> On Tue, Apr 09, 2024 at 08:05:06AM -0700, Will Yardley wrote:
> > On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> > > The unfathomable thing about this question is why you (or anyone)
> > > should care in the slightest
On Tue, Apr 09, 2024 at 08:05:06AM -0700, Will Yardley wrote:
> On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> > The unfathomable thing about this question is why you (or anyone)
> > should care in the slightest what your message ID looks like.
>
> That's totally true, but I
On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote:
> The unfathomable thing about this question is why you (or anyone)
> should care in the slightest what your message ID looks like.
That's totally true, but I still like the classic Mutt message-id
format. Maybe it's just nostalgia,
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails have
> the same beautiful message-ID as Yandex mail?
The unfathomable thing about this question is why you (or anyone)
should care in the slightest what your message ID
On 9 Apr 2024 07:32 +1000, from c...@cskk.id.au (Cameron Simpson):
> You could (a) turn on "set edit_headers=yes" so the headers are visible in
> your message and (b) have your editor startup make one?
This is what I do in order to have a UUID message-ID, which Mutt
doesn't support natively.
>
On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote:
> Question, what should I write in .muttrc to make my outgoing mails have
> the same beautiful message-ID as Yandex mail?
> For example Message-Id: <43265...@example.com> consisting of random
> digits and domain name
There was a long
On 07Apr2024 13:19, Ебрашка wrote:
Question, what should I write in .muttrc to make my outgoing mails have
the same beautiful message-ID as Yandex mail?
For example Message-Id: <43265...@example.com> consisting of random
digits and domain name
I think it would be enough to supply your own
On 07Apr2024 18:23, Anton Sharonov wrote:
On Sun, Apr 07, 2024 at 09:23:07AM -0600, Charles Cazabon via Mutt-users wrote:
There's a good reason for that; it help to ensure uniqueness, which
prevents
problems with threading. By limiting itself to only digits, Yandex's IDs are
much more likely
On 7 Apr 2024 18:23 +0200, from anton.sharo...@gmail.com (Anton Sharonov):
>>> For example Message-Id: <43265...@example.com> consisting of random
>>> digits and domain name
>>
>> There's a good reason for that; it help to ensure uniqueness, which prevents
>> problems with threading. By limiting
On Sun, Apr 07, 2024 at 09:23:07AM -0600, Charles Cazabon via Mutt-users wrote:
> Ебрашка wrote:
> > my mails have Message-ID: . Question, what
> > should I write in .muttrc to make my outgoing mails have the same beautiful
> > message-ID as Yandex mail?
>
> My first question would be, why do
Ебрашка wrote:
> my mails have Message-ID: . Question, what
> should I write in .muttrc to make my outgoing mails have the same beautiful
> message-ID as Yandex mail?
My first question would be, why do you care what the Message-ID: field
contents look like? Virtually no-one will ever look at
I do use on FreeBSD muttprint:
Name : muttprint
Version: 0.73_5
Installed on : Sun Sep 24 11:32:52 2023 CEST
Origin : print/muttprint
Architecture : FreeBSD:14:amd64
Prefix : /usr/local
Categories : print mail
Licenses : GPLv2
Maintainer :
Hello!
On Wed, Nov 24, 2021 at 05:21:10PM +, Jean Louis wrote:
> * Anders Damsgaard [2021-11-22 12:05]:
> > * Globe Trotter via Mutt-users [2021-11-22 00:47:10
> > +]:
> > > What is the recommended way to pretty-print mutt emails? I found a
> > > sourceforge perl script called
On Sat, Mar 30, 2024 at 11:21:21AM -0700, googly.negotiator...@aceecat.org
wrote:
> ...this type of issue is really tricky because one has to be sure to
> *build* against the packaged (i.e. non-base) libraries, including
> cases like libncurses. IIRC this is far from automatic, some packages
> as
On Sat, Mar 30, 2024 at 09:21:53AM -0400, Derek Martin wrote:
> > "Programs in the OpenBSD base system ignore the locale except for
> > the character encoding..."
> Mutt is not part of the "base system" so the limitation on locale
> should not apply to it, and "except for the character encoding"
Hello Derek,
On 2024-03-30 09:21:53, Derek Martin wrote:
> However I would point out that your own post said that you had left
> LANG unset. Did you try setting LANG (and unsetting all the other
> environment variables, and Mutt's charset variable) as I suggested?
> Did you then also look at the
Sandeep,
On Sat, Mar 30, 2024 at 10:21:30AM +0800, Sadeep Madurange wrote:
> On 2024-03-29 16:47:22, Derek Martin wrote:
> > [*] Except in extremely rare and completely esoteric cases that apply
> > only to experts... and by now should really apply to no one.
>
> Thank you for patiently
Hello Derek,
On 2024-03-29 16:47:22, Derek Martin wrote:
> On Sat, Mar 23, 2024 at 07:41:45PM +0800, Sadeep Madurange wrote:
> > Initially, LANG was unset and LC_CTYPE="C". The character encoding
> > was US-ASCII. I changed these variables (i.e., LANG, LC_CTYPE and
> > locale settings) to
On Fri, Mar 29, 2024 at 03:03:54PM -0700, Bob Crochelt wrote:
> Thank you Derek!
> Bob Crochelt
No problem, glad I could help. I had to figure this stuff all out the
hard way 20 years ago, when I moved to Korea and suddently needed to
be able to type in both English and Korean... I've been
Thank you Derek!
Bob Crochelt
On Fri, Mar 29, 2024, at 13:47, Derek Martin wrote:
> On Sat, Mar 23, 2024 at 07:41:45PM +0800, Sadeep Madurange wrote:
>> Initially, LANG was unset and LC_CTYPE="C". The character encoding was
>> US-ASCII. I changed these variables (i.e., LANG, LC_CTYPE and locale
On Sat, Mar 23, 2024 at 07:41:45PM +0800, Sadeep Madurange wrote:
> Initially, LANG was unset and LC_CTYPE="C". The character encoding was
> US-ASCII. I changed these variables (i.e., LANG, LC_CTYPE and locale
> settings) to en_US.UTF-8. Then the ? changed to ?. So, looks like you
> are on to
On 2024-03-23 12:52:40, Sirius Rayner-Karlsson via Mutt-users wrote:
> In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> > > In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > > > When I view the
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> > In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > > When I view the following email in mutt, I see a bunch of question marks
> > > where the spaces are.
On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > When I view the following email in mutt, I see a bunch of question marks
> > where the spaces are. I checked the codepoints and they all seem to be
> > the normal space
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> Hello,
>
> When I view the following email in mutt, I see a bunch of question marks
> where the spaces are. I checked the codepoints and they all seem to be
> the normal space (0x20) character in the ASCII table.
My initial
Thank you both. I'll be trying this shortly :D
--
People,
I never received a response re the stuff below (so I presume it is not
possible) - but the colourised folder idea also would be helpful to me .
.
Thanks,
Phil.
On 2022-07-13 23:58, p...@pricom.com.au wrote:
People,
In my Maildir structure I have subfolders of subfolders eg
Hi,
void wrote:
> I have various mailing list emails filtered on the server
> by the mail provider going into various imap folders, based
> on various properties of the email, like List-Id: for example.
>
> What I'd like to have within mutt is for it to dynamically
> decide which signature file
On 14 Jan 2024 15:47 +, from v...@f-m.fm (void):
> What I'd like to have within mutt is for it to dynamically
> decide which signature file to use based on what imap
> folder the mail being replied to is in.
You can use a set of folder-hook stanzas to set $signature.
For example:
dm1...@gmail.com wrote:
> Hi all,
>
> Is it possible to display messages (preferably automatically, as soon
> as the messages get in the mailbox) as one thread based on a value of
> a custom header? That is, all the messages that have the X header with
> the same value.
If you have threading
On 4 Jan 2024 18:42 +0800, from kai.we...@glorybox.de (Kai Weber):
> From time to time I have to report a falsly classified message to my
> mail provider so that they can adjust their filters. I am looking
> for a way to automate that:
>
> 1. Forward selected mail as attachement to x...@foo.com
>
Hi,
Kai Weber wrote:
> From time to time I have to report a falsly classified
> message to my mail provider so that they can adjust their
> filters. I am looking for a way to automate that:
>
> 1. Forward selected mail as attachement to x...@foo.com
> 2. Set Subject to "reporting false positive
You can limit to mail less than a certain size, or within a size range.
http://www.mutt.org/doc/manual/#patterns
~z [MIN]-[MAX]
You can make a macro which applies this limit.
You may also get creative with the header format to highlight mail that
is over a certain size.
I'm not sure about
On 30Nov2023 07:09, Tim Chase wrote:
For some reason, the way my brain works, when I have a filter in
place
l myfilter
my lizard-brain wants to use "q" instead of
l .
to turn off the filter. The lizard-brain wins over the conscious
brain (that knows to use `l .`) about half the time.
On Wed, Nov 22, 2023 at 08:12:17PM +0100, David Santinoli wrote:
Hallo,
I could not find a way to pipe a message to an external filter and have
the output replace the original message. As a workaround I open the
message in vim, pipe the whole buffer to the filter, and save it back as
a new
On 22 Nov 2023 20:12 +0100, from da...@santinoli.com (David Santinoli):
> I could not find a way to pipe a message to an external filter and have
> the output replace the original message.
You can set $editor to any script you want and cause
(or or as applicable) to be invoked. Make the
script
On 2023-10-29 14:17, Michael Kjörling wrote:
> On 29 Oct 2023 14:44 +0100, from mutt-users@mutt.org (Jan Eden via
> Mutt-users):
> > for several years, I have used mutt with msmtp, and issues with sending
> > messages were usually returned to mutt and displayed as an error.
> >
> > Recently,
On 29 Oct 2023 14:44 +0100, from mutt-users@mutt.org (Jan Eden via Mutt-users):
> for several years, I have used mutt with msmtp, and issues with sending
> messages were usually returned to mutt and displayed as an error.
>
> Recently, though, mutt displays "Mail sent" even when there is a
Hi,
for several years, I have used mutt with msmtp, and issues with sending
messages were usually returned to mutt and displayed as an error.
Recently, though, mutt displays "Mail sent" even when there is a problem
(and the mail is not sent). I always used a simple msmtp configuration,
and could
On Fri, Oct 20, 2023 at 12:43:42PM +0200, Ralf Hildebrandt via Mutt-users wrote:
> I'm getting a few mails which use "^M" line endings, which mutt
> seems to ignore when displaying the body of the email.
> How can I make mutt properly display the mail.
My immediate reaction is you'll need an
tLabels") | wc -l`
if [ $del -eq 1 ]; then
echo -e "\e[1;31m[$i]\e[0m $label"$'\t'"\e[1;31m(-)\e[0m";
else
echo -e "\e[1;32m[$i]\e[0m $label"$'\t'"\e[1;32m(+)\e[0m";
fi
i=$(($i+1));
done
echo -e "\e[1;31m[c] Clear All\e[0m";
ech
On Wed, Sep 27, 2023 at 02:36:57PM -0500, Tim Chase
wrote:
> Howdy,
>
> RFC-2156[1] specifies ways to use the headers
>
> Importance: {low, normal, high}
> Priority: {normal, non-urgent, urgent}
> Sensitivity: {Personal, Private, Company-Confidential}
>
> and I've also seen the
Il 18 settembre 2023 alle 06:57 Kevin J. McCarthy ha scritto:
> $index_format by default uses the %{} expando: %{%b %d}. This uses the
> locale setting but you can prefix it with a ! to use C, e.g. %{!%b %d}.
>
> $date_format is used for the %d and %D expandos in $index_format, and the %D
>
On Sun, Sep 17, 2023 at 11:27:34PM +0200, Francesco Ariis wrote:
There you have it.
I wonder whether the ignored `!` in date_format is a bug or me
misreading the man page (Mutt 2.2.9). I will wait for a developer’s
reply before filing an issue
$index_format by default uses the %{} expando:
Il 17 settembre 2023 alle 23:19 Matthias Apitz ha scritto:
> $ echo $LANG
> es_ES.UTF-8
> $ date "+%b"
> sept.
> $ LANG=C date "+%b"
> Sep
> $
There you have it.
I wonder whether the ignored `!` in date_format is a bug or me
misreading the man page (Mutt 2.2.9). I will wait for a developer’s
El día domingo, septiembre 17, 2023 a las 11:12:23p. m. +0200, Francesco Ariis
escribió:
> `date_format` is passed to `strftime`. Mine is:
>
> date_format="!%a, %b %d, %Y at %I:%M:%S%p %Z"
> # A bang should mean “C (US English) locale,
> # but on mine it is still Italian.
>
> `date
Hello Matthias,
Il 17 settembre 2023 alle 21:27 Matthias Apitz ha scritto:
> Why the actual month September is abbreviated with 4 letters in the index:
>
>6 may. 28 Simsondoktor Mü (2,5K) Re: Defekte Schwalbe
>
>7 jul. 05 Matthi
On Mon, Aug 07, 2023 at 01:57:04AM +1000, Nemo Thorx wrote:
> Quoting Ed Blackman from 04 Aug (a Friday in 2023) at 1434 hours...
> > Any suggestions for a command line program to select emails for
> > deletion based on command line options? I specifically want one that
> > can remove emails that
Dear Sébastien,
Il 12 settembre 2023 alle 16:07 Sébastien Hinderer ha scritto:
> Dear all,
>
> Here is something I have been wanting for a long time.
>
> For those who don't know, the email notifications sent by GitHub do have
> all the information to unsubscribe from the corresponding thread
I know this is a blast from the past, but I wanted to thank Christian for this
long-ago message! I often put aside messages for when I have time to explore
something that is interesting to me. I am not so good at actually going back
and looking at them later.I had a little time recently
Answering late:
* Ed Blackman , 2023-08-04 14:34:44 Fri:
> Any suggestions for a command line program to select emails for
> deletion based on command line options? I specifically want one
> that can remove emails that were received more than X days ago, but
> can also express "but don't delete
Hi Kevin,
On 2023-09-07 20:07, Kevin J. McCarthy wrote:
> On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote:
> > Thank you for this hint. Unfortunately it does not work for me. Mutt
> > insists in 8bit, maybe depending on my locales. Seems I have to study
> > the source code...
>
>
On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote:
Thank you for this hint. Unfortunately it does not work for me. Mutt
insists in 8bit, maybe depending on my locales. Seems I have to study
the source code...
See if 'unset allow_8bit' helps.
--
Kevin J. McCarthy
GPG Fingerprint:
Hello Ed,
On 2023-09-06 14:46, Ed Blackman wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
> > Can I force Mutt to use quoted-printable or base64 by default for
> > encoding of plain text?
>
> It would be better to fix the DKIM problem, but as I have no idea
> about that,
Hello Raf,
On 2023-09-07 10:31, raf via Mutt-users wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
>
> > Dear Mutt Users
> >
> > recently I experienced DKIM fails that depend on the
> > Content-Transfer-Encoding of messages text part.
> >
> > Being a german I use to
On 2023-09-07, raf via Mutt-users wrote:
> On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote:
>
>> Dear Mutt Users
>>
>> recently I experienced DKIM fails that depend on the
>> Content-Transfer-Encoding of messages text part.
>>
>> Being a german I use to write my messages in german
On Thu, Sep 07, 2023 at 10:31:53AM +1000, raf via Mutt-users wrote:
> Hi, This has come up recently in the Postfix mailing list. MTAs can
> convert 8bit messages when sending to another MTA that doesn't
> advertise that it can accept 8bit. If the DKIM signing happens
> before the conversion,
On Wed, Sep 06, 2023 at 04:28:46PM +0200, f...@igh.de wrote:
> works perfectly if the subject contains any non-ASCII characters.
I think this case is not relevant, because any non-ascii characters
in the Subject are converted to use the RFC-2047 scheme, I guess
already in mutt.
--
Ian
1 - 100 of 40781 matches
Mail list logo
