On 2024-09-09 11:32, Christian Brabandt wrote:
> On Mo, 09 Sep 2024, Jan Eden via Mutt-users wrote:
> > The filename created for this reply looks like this –
> >
> > "/var/folders/ps/4v3k3hwj1jd9bdyq8sc4kptrgn/T/mutt-snafu-501-5821-14318527686633908551"
>
On 2024-09-09 00:41, Akshay Hegde via Mutt-users wrote:
> On 2024-09-09 08:42 +0200, Jan Eden via Mutt-users wrote:
> > Hi,
> >
> > this is a little off-topic, but maybe other mutt users are affected,
> > too: Since upgrading to vim 9.1.700 this morning via homebrew,
Hi,
this is a little off-topic, but maybe other mutt users are affected,
too: Since upgrading to vim 9.1.700 this morning via homebrew, the
filetype is not set automatically anymore when calling vim from mutt.
I worked around this by setting the filetype explicitly in .muttrc –
set editor='/opt/
On 2024-07-24 17:49, Ofer Inbar wrote:
> On Wed, Jul 24, 2024 at 09:17:13PM +0100,
> Peter Flynn wrote:
> > >However .. when I use the "bounce" feature, mutt is not using my From:
> > >header. It's generating a From: address using the actual name of the
> > >individual host, hy...@alfred.nasali
On 2024-06-21 10:34, Michael Kjörling wrote:
> On 21 Jun 2024 09:52 +0200, from mutt-users@mutt.org (Jan Eden via
> Mutt-users):
> >> I noticed that non-ascii characters in recipient names become garbled
> >> recently (in Mutt 2.2.13, installed via Homebrew
On 2024-06-21 09:44, Jan Eden via Mutt-users wrote:
> Hi,
>
> I noticed that non-ascii characters in recipient names become garbled
> recently (in Mutt 2.2.13, installed via Homebrew):
>
> "Basi´c, P."
>
> becomes
>
> "Basi´c, P."
>
>
Hi,
I noticed that non-ascii characters in recipient names become garbled
recently (in Mutt 2.2.13, installed via Homebrew):
"Basi´c, P."
becomes
"Basi´c, P."
The effect is not visible when composing the message in mutt, but in the
sent message (in the Sent mailbox), so it is not caused furt
On 2024-06-19 15:31, Will Yardley wrote:
> On Tue, Jun 18, 2024 at 07:25:48AM +0200, Jan Eden via Mutt-users wrote:
> > text/html; w3m -dump -I %{charset} -T text/html -o display_link_number=1
> > %s; copiousoutput;
>
> Aside from the lynx suggestion that someone posted,
On 2024-06-20 01:20, Andrew D Arenson wrote:
> Just to add -- I have, indeed, tried both port 587 and port 465 -- same
> results.
>
> Point about this being SMTP and not IMAP is noted. Thanks!
Could it be that the SMTP server's certificate changed, so the TLS
connection fails because mutt refers
On 2024-06-18 05:59, Michael Kjörling wrote:
> On 18 Jun 2024 07:25 +0200, from mutt-users@mutt.org (Jan Eden via
> Mutt-users):
> > Is there any way to display the links inline (e.g.
> > Markdown-style) with w3m (or lynx)?
>
> lynx has -dump -list_inline which looks us
Hi,
I currently use the following entry in my mailcap to display HTML
messages in mutt:
text/html; w3m -dump -I %{charset} -T text/html -o display_link_number=1 %s;
copiousoutput;
This works well for me - with a numbered list of links at the end of the
parsed message - but replying to such mess
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 send
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.
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 2023-09-06 13:33, 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 with UTF-8
> encoding. I prefer plain text. My e-mails are DKIM signed. I
On 2023-09-01 16:15, Todd Zullinger wrote:
> Hi,
>
> Jan Eden wrote:
> > my configuration sets a PGP default key:
> >
> > set pgp_default_key = ...
> >
> > and outgoing messages are signed accordingly. But every time I reply
> > to a message signed using S/MIME, mutt tries to add an S/MIME sign
Hi,
my configuration sets a PGP default key:
set pgp_default_key = ...
and outgoing messages are signed accordingly. But every time I reply
to a message signed using S/MIME, mutt tries to add an S/MIME signature,
too (which fails, as there is no S/MIME key available via GPGME).
How can I preven
On 2023-08-14 14:16, Will Yardley wrote:
> On Mon, Aug 07, 2023 at 03:47:53PM +0200, Jan Eden via Mutt-users wrote:
> > I recently upgraded to macOS 13.5, and for the first time, there are
> > redraw issues in the Terminal with mutt (2.2.10, installed via
> > Homebrew). Al
On 2023-08-10 09:37, Dennis Preiser wrote:
> On Thu, Aug 10, 2023 at 08:14:23AM +0200, Jan Eden via Mutt-users wrote:
> > On 2023-08-07 19:18, Dennis Preiser wrote:
> >> Not surprising. You must somehow tell homebrew that for mutt
> >> --with-curses=PATH/TO
On 2023-08-07 19:18, Dennis Preiser wrote:
> On Mon, Aug 07, 2023 at 06:16:39PM +0200, Jan Eden via Mutt-users wrote:
> > On 2023-08-07 16:29, Dennis Preiser wrote:
> >> Maybe it is sufficient to install a newer ncurses with homebrew.
> >
> > Even with ncurses 6.4
On 2023-08-07 15:59, Claus Assmann wrote:
> On Mon, Aug 07, 2023, Jan Eden via Mutt-users wrote:
> > I recently upgraded to macOS 13.5, and for the first time, there are
> > redraw issues in the Terminal with mutt (2.2.10, installed via
>
> "Terminal" broke scree
On 2023-08-07 16:29, Dennis Preiser wrote:
> On Mon, Aug 07, 2023 at 03:47:53PM +0200, Jan Eden via Mutt-users wrote:
> > I recently upgraded to macOS 13.5, and for the first time, there are
> > redraw issues in the Terminal with mutt (2.2.10, installed via
> > Homebrew). Al
Hi,
I recently upgraded to macOS 13.5, and for the first time, there are
redraw issues in the Terminal with mutt (2.2.10, installed via
Homebrew). Also, the launchctl job for isync/mbsync (1.4.4, also
installed via Homebrew) fails since the upgrade.
Has anyone else experienced similar issues with
On 2023-04-22 14:58, Akkana Peck wrote:
> > On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> > > Is there a configuration that will make mutt's forwarding behavior more
> > > like other clients I have used: body is quoted in the message, and
> > > attachments are automatically attached?
>
Hi,
I configured notmuch for my mail stores, and use mutt-notmuch
according to the man page[1]:
macro index "unset
wait_key~/bin/mutt-notmuch --prompt
search~/.cache/mutt_results"
mutt is started with the -F parameter, and each parameter (work,
personal etc) refers to a different mail store.
Hi,
a couple of days ago, people using MS Outlook started complaing that my
messages looked "strange". I asked for an example and received this:
> > Subject: Re: Finanzierung
> >
> > MIME-Version: 1.0
> > Content-Type: multipart/signed; micalg=pgp-sha512;
> > protocol="application/pgp-signat
On 2022-10-10 08:42, José María Mateos wrote:
> On Mon, Oct 10, 2022 at 12:27:52PM +0200, Jan Eden via Mutt-users wrote:
> > The problem was related to the target dir (/tmp/mutt_attach). Although
> > it was accessible by the current user, Firefox was not able to display
> >
On 2022-10-10 08:58, Cameron Simpson wrote:
> On 09Oct2022 09:35, Jan Eden via Mutt-users wrote:
> > Yes, I did use Chris Green's helper script, and it does work with
> > Epiphany, but not with Firefox.
>
> Maybe it would prefer a "file:///path/to/file.html&quo
On 2022-10-09 10:20, Jan Eden wrote:
> Hi,
>
> after Chris Green's and Cameron Simpson's helpful advice regarding HTML
> messages, I dare to post another mailcap question.
>
> My mailcap contains the following lines:
>
> application/vnd.openxmlformats-officedocument.wordprocessingml.document;
>
Hi,
after Chris Green's and Cameron Simpson's helpful advice regarding HTML
messages, I dare to post another mailcap question.
My mailcap contains the following lines:
application/vnd.openxmlformats-officedocument.wordprocessingml.document;
~/.mutt/view_attachment %s "-"
application/vnd.openxml
On 2022-10-09 08:18, Cameron Simpson wrote:
> On 08Oct2022 21:55, Jan Eden via Mutt-users wrote:
> > Thank you! This works well with Epiphany, but Firefox still fails (which
> > I do not care about, as long as I have a working browser option).
>
> My recollection is that t
On 2022-10-08 11:52, Chris Green wrote:
> On Sat, Oct 08, 2022 at 12:06:52PM +0200, Jan Eden via Mutt-users wrote:
> > On 2022-10-08 09:34, Chris Green wrote:
> > > On Sat, Oct 08, 2022 at 10:25:29AM +0200, Jan Eden via Mutt-users wrote:
> > > > Hi,
> > > &
On 2022-10-08 09:34, Chris Green wrote:
> On Sat, Oct 08, 2022 at 10:25:29AM +0200, Jan Eden via Mutt-users wrote:
> > Hi,
> >
> > I recently configured mutt on a Linux system, and cannot display HTML
> > messages in the default browser. mailcap contains the followin
Hi,
I recently configured mutt on a Linux system, and cannot display HTML
messages in the default browser. mailcap contains the following lines:
text/html; open %s;
text/html; w3m -I %{charset} -T text/html; copiousoutput
application/pdf; open %s; copiousoutput
w3m is used automatically (auto_vi
Hi Jaron,
On 2022-09-21 15:53, Jaron Kent-Dobias via Mutt-users wrote:
> Hello,
>
> I am frequently exchanging emails with Italians, whose mail clients often
> use the format 'R: [Subject]' in replies instead of 'Re: [Subject]'. Mutt
> in my locale does not recognize the leading 'R:' as a reply
On 2022-09-15 08:27, Cameron Simpson wrote:
> On 13Sep2022 16:50, Sébastien Hinderer
> wrote:
> > I would like to have a nice way to deal with several accounts in mutt. I
> > am talking just about the .muttrc file aspect here.
> >
> > My present configuration is that each account has its own mut
On 2022-09-15 21:23, Sébastien Hinderer wrote:
> Jan,
>
> I think I got it.
>
> Am I correct that, for each account, you have actually two files: one
> that you use in your alias and one that you use in your macro. Is that
> right?
More or less: For three of my accounts, there is only a single
Hi Sébastien,
On 2022-09-15 20:26, Sébastien Hinderer wrote:
> Hello Jan, thanks a lot for your response and the link!
>
> Jan Eden via Mutt-users (2022/09/15 11:42 +0200):
> > I defined aliases for my accounts in .zshrc, because I do not mind
> > restarting mutt when swi
On 2022-09-15 10:23, Sébastien Hinderer wrote:
> Hello,
>
> Many thanks for your reponse!
>
> Cameron Simpson (2022/09/15 08:27 +1000):
> > I thought the common approach was what you next outline: a single muttrc
> > which sources the appropriate account-specific muttrc.
>
> [...]
>
> For files
On 2022-09-12 13:37, Kurt Hackenberg wrote:
> On Mon, Sep 12, 2022 at 01:32:25PM +0200, meine wrote:
>
> > on the POP3: it is my favourite because mails are on my own hard disk
> > after downloading -- both for security and archiving. I have to dive
> > into the possibilities of having the same fo
On 2022-09-13 20:07, Robert wrote:
> Hi there,
>
> On 2022-09-04 17:17, Jan Eden via Mutt-users wrote:
> > - Can I define multiple From addresses to select them from a list?
> > - Can mutt be configured to switch the default BCC address to a changed
> > From addres
On 2022-09-12 21:59, bastian-muttu...@t6l.de wrote:
> On 12Sep22 21:07+0200, Mihai Lazarescu wrote:
> > Given the cheap VPS, I can mirror the setup on a second VPS from a different
> > provider with quick DNS switch in case of issues.
>
> I just did that approx half a year ago. Before, everything
On 2022-09-07 08:04, Cameron Simpson wrote:
> On 06Sep2022 09:26, Jan Eden via Mutt-users wrote:
> > Thank you! This is exactly what I needed. I tweaked your version a bit
> > to use the standard parameters for setting the required values:
> >
> > set from="x...@e
On 2022-09-05 19:16, Ofer Inbar wrote:
> What I did for this was select a few esc-capital hotkey combos
> and define macros like this in my muttrc:
>
> macro generic \eF ":source ~/.mutt/headers.f...\r"
> macro generic \eH ":source ~/.mutt/headers.h...\r"
>
> And so on. (I replaced the actual fi
On 2022-09-04 20:37, Cameron Simpson wrote:
> On 04Sep2022 15:34, raf via Mutt-users wrote:
> > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson
> > wrote:
> > > The `md2html` script is my personal script, which wraps `pandoc`
> > > and post munges the HTML to indent the code blocks, w
Hi,
I use a couple of From addresses, and currently change the default From
address and BCC address manually, and select the matching PGP key for
signing afterwards (PGP menu → sign as → [From address] →
select key). This can probably be done much more efficiently, so my
questions are:
- Can I de
On 2022-09-03 00:46, Derek Martin wrote:
> On Wed, Aug 31, 2022 at 07:45:05PM -0400, John Hawkinson wrote:
> > Derek Martin wrote on Wed, 31 Aug 2022
> > at 19:35:15 EDT in <20220831233515.gf13...@bladeshadow.org>:
> >
> > Evaluating the strength of a SHOULD requires looking at pragmatic
> > rea
On 2022-08-31 11:51, X Tec wrote:
When composing an email, I decided to postpone instead of immediately send. It got saved in Drafts folder,
but when deciding to send it, I opened the draft, but there's no "send" option; just the usual
respond, new email, and the other options when opening any
On 2022-08-30 14:58, Kurt Hackenberg wrote:
On Tue, Aug 30, 2022 at 09:09:34AM +0200, Jan Eden via Mutt-users wrote:
I would consider f=f an acceptable compromise, because while it looks
nicer on (some) mail clients, it breaks automatic list indentation
created in vim (fo-n). The following is
On 2022-08-29 19:07, Tavis Ormandy wrote:
> On 2022-08-29, Logan Rathbone wrote:
> > On Mon, Aug 29, 2022 at 10:43:45AM EDT, Tavis Ormandy wrote:
> >> No, format=flowed sounds like the perfect solution but I've tested and
> >> as far as I can tell it's ignored by gmail on Android, for example.
> >
50 matches
Mail list logo
