On 16.05.25 01:31, Kurt Hackenberg wrote:
> If you think this is a mess, you're right. People have tried to fix
> it, but it can't really be fixed. The only good solution is to not use
> mbox, and store mail in other ways instead.
I've yet to see anything to fix, having used mbox format exclusi
On 18.04.25 12:28, Nuno Silva via Mutt-users wrote:
> On 2025-04-17, dvalin--- via Mutt-users wrote:
>
> > On 16.04.25 15:05, Ranjan Maitra via Mutt-users wrote:
> [...]
>
> The message I'm replying to shows without References/In-Reply-To
> here. Does it lack pr
On 16.04.25 15:05, Ranjan Maitra via Mutt-users wrote:
> I tried using `xterm -bg "#ff" -fg '#00' -e mutt`` and that does help
> some, however, I am not sure if there is a better preferred way.
Better? Dunno, but for nigh on 40 years now, I've had eye-friendly
light-on-dark in mutt, vim
On 27.10.24 10:38, Sadeep Madurange wrote:
> Hello,
>
> In some lists, users send replies to the list address while cc-ing my
> email address. So, I get two copies of the same email.
>
> Is there anything I can do so that I only receive/see one copy?
If you use procmail to sort incoming mail
On 05.09.21 17:22, Tom Tunguz wrote:
> I'd like to set a macro to send mail directly from the compose
window using
> vim.
I am writing this post in vim, invoked when I hit 'L' in mutt, as
configured by:
set editor=vim
in .muttrc.
Then it's just :wq back to mutt, and send the post with the M
On 27.08.21 22:22, dva...@internode.on.net wrote:
> This should do it: (In .muttrc)
>
> set tmpdir /tmp
Whoops, shoulda checked exact syntax will work.
In my .muttrc I have:
set tmpdir="~/Desktop"
so you'll need some quotes and '='.
I changed from /tmp, so that if something goes seriously
wro
On 27.08.21 14:34, Fourhundred Thecat wrote:
>
> and strace shows me it is trying to use /var/tmp/
>
> any idea what happened?
> How can I revert this back to using /tmp ?
This should do it: (In .muttrc)
set tmpdir /tmp
To check it has stuck:
:set ? tmpdir
(It's all in the manual on the F1 k
On 29.07.21 09:38, hy...@nasalinux.net wrote:
> Is "fetchmail" still a thing?
The latest release, 6.5.0.beta4, is 3 days old, according to the
fetchmail-announce maillist. It includes a security vulnerability fix,
so is worth installing. You'll need the build-essential package
installed in order
On 09.06.21 12:15, steve wrote:
> Hello,
>
> Nobody for this one?
>
> I found that I could modify the subject with a folder-hook but
that's
> only half of the solution since it doesn't take care of the group
alias
> part.
>
> Any help would be highly appreciated.
I'd try a message-hook with p
