> 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?
Kevin J. McCarthy writes:
> $forward_attachments,
lilydjwg writes:
> I've switched to OAuth because I don't want to enable 2FA (which means
> if I lost all my devices, I would lose access to my Google account).
How did you get your OAuth tokens? I tried following
https://github.com/google/gmail-oauth2-tools/wiki/OAuth2DotPyRunThrough
and
Tavis Ormandy writes:
> Not exactly what was asked, but I use this mailcap to view image
> attachments:
>
> image/png; img2sixel -- %s | less -r; nametemplate=%s.png; needsterminal
Related question: is there a way to view several attachments at once?
For example, someone sends five photos of a
The recent discussion on counting attachments was a revelation --
what a fantastic feature, which I hadn't realized mutt could do!
I set up an attachments definition:
attachments +A */.*
attachments -A text/.*
attachments -I */.*
and then set up a color for index lines with one or more non-text
Derek Martin writes:
> Your only option for this which would have widespread support would
> be HTML. It is *possible* to generate such messages and send them
> with Mutt. It's just not very easy or user-friendly.
I agree (and the thread you reference is very worthwhile reading).
But be warned
> > On Sat, Apr 25, 2020 at 09:46:48PM -0500, David Engel wrote:
> > > I've given up politely asking people to remember to send email as
> > > either both text/html and text/plain or just text/plain when sending
> > > to me. It's a losing battle. :(
Since I don't have to deal with PGP,
Felix Finch writes:
> On 20200405, Sam Kuper wrote:
> > In the meantime, you can just reply to the message (which, after all,
> > was sent as an email): "Thanks, I accept your invitation to the meeting
> > at 5pm PDT on 5th May 2020."
>
> Now that's an idea I hadn't considered! I was thinking
> Regarding the following, written by "Derek Martin" on 2019-10-31 at 15:39 Uhr
> -0500:
> > And FWIW, I *was* discussing (very limited, completely text-based)
> > support for HTML messages in Mutt. I want it, have wanted it for a long
> > time, because all of the available options for dealing
Matthias Apitz writes:
> So, run mutt in an unicode-rxvt terminal. It presents URLs underlined
> and click-able. I do so and sometimes I do hate it: you click into your
Definitely not by default. I'm using rxvt-unicode, and I've tried
the "matcher" and "selection" extensions but neither one
Pankaj Jangid writes:
> On Sat, Jul 27, 2019 at 12:41:21PM -0400, Jude DaShiell wrote:
> > I have getmail working pulling email from my gmail account using imap
> > and it only grabs the new mail for me each time I run it and I open up
> > mutt and go through the email then mutt purges what I
tech-lists writes:
> But inline quoting has its own issues. Multiple inline quotes from multiple
> messages can get messy. IMOHO messier than just bottom posting, which is at
> least logically chronological.
Agreed -- sometimes I wish there was a flag to differentiate the
"> " characters somehow.
Jon LaBadie writes:
> Another example of this: I typically bottom/in-line
> respond even private emails. As most of you may
> note I have a lot of personal info in my standard
> signature. Yet even people with whom I've had many
> exchanges will ask my address or phone number.
Some email
Brian Salter-Duke writes:
> My partner reads gmail on her phone or tablet. [ ... ]
> If I had bottom posting, she would never have read my message, thinking
> that some how she had got her email back again.
If that's true, you're not trimming enough. The idea isn't to quote
the other person's
> On Tue, Apr 10, 2018 at 03:57:53PM +0800, Yubin Ruan wrote:
> >
> > Can anyone share some approaches for reading HTML emails.
> > Currenlty I use w3m:
> >
> > text/html; w3m -I %{charset} -T text/html; copiousoutput;
> >
> > But sometimes I receive some HTML mails which can not be handled
Kevin J. McCarthy writes:
> On Wed, Feb 28, 2018 at 09:28:41AM -0700, Akkana Peck wrote:
> > But the example in the manual doesn't work for me in 1.9.3 [ ... ]
> > subjectrx '\[[^\]]*\]? *' '%L%R'
>
> Looks like the example might be wrong in the manual, unless there
Todd Zullinger writes:
> http://www.mutt.org/doc/manual/#display-munging
>
> subjectrx was added in 1.8.0, it seems.
That's wonderful! Something I've been wishing for for a long time.
But the example in the manual doesn't work for me in 1.9.3
(on Debian testing, but I think that's back to being
> On Mon, Aug 28, 2017 at 11:34:49 -0600, Akkana Peck wrote:
> > fcc-save-hook "(~t that_fri...@somewhere.no | ~c that_fri...@somewhere.no |
> > ~f that_fri...@somewhere.no)" =friend_sent
> >
> > I wish there was a more compact way to specify it [ ... ]
Na
Salve Håkedal writes:
> I use mutt with fetchmail and procmail.
>
> When recieving mail (with fetchmail) from some people I put it in one single
> directory with this in .procmailrc and the rest goes in innboks.
[ ... ]
> How can I make mutt place my reply in the that_friend folder?
I'm not sure
18 matches
Mail list logo
