Re: Mailing lists

On 2025/05/29 00:35, googly.negotiator...@aceecat.org wrote: This is also an area where neomutt has some extra features, so it may be worth looking at. I'm biased because I contributed code to neomutt. So tell us, how does neomutt handle mailing lists?

Re: Mailing lists

On Wed, May 28, 2025 at 08:47:16AM +0200, Sébastien Hinderer wrote: Separately from all that, I think it would be straightforward and useful to make the $index_format expandos that identify a message as coming from a list (%L, %T, %Z), also look at List-ID:. ... To push this even a bit further

Re: mutt mbox format for new mailboxes

On Thu, May 22, 2025 at 08:12:13AM -0400, Rich Kulawiec wrote: I think a better approach is to figure out what needs to be changed/ fixed/added to RFC 4155 so that it covers the variants that arisen, and to create a superseding RFC that updates it. This won't fix all the problems that have aris

Re: Discourse emails not recognized as coming from a mailing-list

On Sat, May 17, 2025 at 12:18:53PM +0200, Sébastien Hinderer wrote: In my understanding, a consequence of what you say is that a message will not be detected as coming from a list if it is sent in Bcc to that list, even if you are subscribed to this list. Yes, I think that's right. Out of cur

Re: Mailing lists

On Sun, May 11, 2025 at 08:47:40AM +0100, Chris Green wrote: It sure would be a lot simpler to: Eliminate commands "(un)subscribe" and "(un)lists" Eliminate $auto_subscribe Identify messages from lists by List-ID: Make only send to List-Post:, and fail if it's absent There

Re: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 02:29:13PM -0700, Will Yardley wrote: Though then it's even more odd that mbox(5) which ships with mutt _does_ (now) mention MBOXCL2, but also still leaves in all the text about From_ escaping / quoting. Wouldn't it be nice if there was only one version of mbox, and it

Re: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 04:04:35PM -0400, Rich Kulawiec wrote: We referred to them as "mboxes" back in the day; the term was so common that some programs used "mbox" as a default filename. (Can't recall offhand, but maybe the early BSD version of the "mail" command, AKA "ucbmail"?) I think t

Re: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 04:30:53PM +0100, Rory Campbell-Lange wrote: I assume the "Content-Length" (and possibly also "Lines"?) was, as Kurt suggests, a way of efficiently reading emails out of a larger mbox file. No. It was invented so it wouldn't have to do "&g

Re: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 08:05:25PM +0100, Rory Campbell-Lange wrote: I'm on mutt 2.2.13-1. Is the following what you expected? --- /tmp/test.maildir/cur/1747420397.M988463P24699Q1.rain.cave:2,S 2025-05-16 19:33:17.0 +0100 +++ /tmp/test.mbox 2025-05-16 20:00:52.063481577 +0100 @@

Re: ReRe: mutt mbox format for new mailboxes: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 02:46:07PM -0400, Mark E. Mallett wrote: One case in point: the bit about only quoting "From_" lines if preceded by a blank line. That's one heuristic (if I dare to use the word) that was pretty randomly followed in the past. It mostly is now, but has not always been. T

Re: ReRe: mutt mbox format for new mailboxes: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 02:09:16PM -0500, Tim Chase wrote: And if program Y "properly" escapes them when storing (indenting again): >From me with no prefix >>From me with one prefix >>>From me with two prefixes From me with three prefixes program X will only un-mung the first one (corr

Re: ReRe: mutt mbox format for new mailboxes: mutt mbox format for new mailboxes

On Fri, May 16, 2025 at 08:37:01AM +, dvalin--- via Mutt-users wrote: I've yet to see anything to fix, having used mbox format exclusively since the 1980s, with mutt since the late 90s. It just effortlessly works with complete reliability - never a hiccup. If you use only Mutt, only with m

Re: mutt mbox format for new mailboxes

On Thu, May 15, 2025 at 11:26:00PM -0700, Will Yardley wrote: On Fri, May 16, 2025 at 01:31:27AM -0400, Kurt Hackenberg wrote: Mboxcl2 does it the other way. Instead of using a marker, it uses a length, stored in the non-standard header Content-Length:. Software reads the message header

Re: mutt mbox format for new mailboxes

On Thu, May 15, 2025 at 09:18:53PM -0700, Will Yardley wrote: > It's interesting that in replies, Mutt uses >From escaping, though in > the actual raw mbox file, it's not present. No, you're confusing two different uses of '>' at the beginning of a line. ... Yes, I understand how quote mark

Re: mutt mbox format for new mailboxes

On Thu, May 15, 2025 at 02:25:44PM -0700, Will Yardley wrote: It's interesting that in replies, Mutt uses >From escaping, though in the actual raw mbox file, it's not present. No, you're confusing two different uses of '>' at the beginning of a line. A reply can quote the original message, an

Re: mutt mbox format for new mailboxes

On Thu, May 15, 2025 at 06:40:34AM +0100, Rory Campbell-Lange wrote: I didn't know that. I see on the man page mutt can save as mbox, MMDF, MH or Maildir using the -m flag. I couldn't see any docs about saving in the different mbox formats, which I understand from https://docs.aspose.com/email/n

Re: mutt mbox format for new mailboxes

On Wed, May 14, 2025 at 02:01:11PM +0100, Rory Campbell-Lange wrote: I believe that mutt uses mboxcl2 format for writing new mailboxes. I'd be grateful to know if that is corrrect. I think that's right, with a small addition: since version 1.9.5 (April 2018), Mutt has also written Lines: along

Mailing lists

It turns out that Mutt's mailing list code is old. It was first written before the headers List-*: existed, so originally it didn't use any of them. That explains some things. Most of the headers List-*: were defined by RFC 2369, published in 1998; List-ID: was defined by RFC 2919, published i

Re: Discourse emails not recognized as coming from a mailing-list

On Wed, Mar 19, 2025 at 01:50:35PM +0100, Sébastien Hinderer wrote: I follow a discourse forum but with emails enabled as I am not comfortable with its web interface. For the moment, the emails I receive for forum posts appear as addressed to me (with a + flag) rather than coming from a mailing

Re: Threading/references (was: Re: using a light theme with xterm

On Fri, Apr 18, 2025 at 12:18:42PM +, dvalin--- via Mutt-users wrote: Regrettably, the web-based MUA provided by my ISP, after ceasing to accept smtp from users, is rather deficient, not least in that regard. (It's a PITA to use too.) In another thread, Ken Moffat wrote: I turned out t

Mailing lists [was: using a light theme...]

may not need `folder-hook .` >anymore, but I haven't changed or tested it in several >years. I think you don't need it. Looks like you used "folder-hook ." to reset to the default key bindings for messages not from lists, and now you do that with "message-hook ~A"

Re: Mailing lists [was: using a light theme...]

On Thu, Apr 17, 2025 at 04:41:54PM -0400, Todd Zullinger wrote: I checked and it is needed. If you read a list message and then move back to another folder and want to reply to a message without first opening it, you need the folder-hook to reset the default bindings. Otherwise you press 'r' a

Mailing lists [was: using a light theme...]

On Wed, Apr 16, 2025 at 09:07:49PM -0700, Will Yardley wrote: This is also why Mutt has a built in feature to _ignore_ Reply-To when it matches the list address. Well, look at that ($ignore_list_reply_to). Some disagree strongly, but this is probably the "classic" post about the subject: htt

Re: using a light theme with xterm (that has black background)

On Wed, Apr 16, 2025 at 08:07:47PM -0500, Ranjan Maitra via Mutt-users wrote: Have you tried ? Does it do what you want? (You don't have to send the reply, just see what Mutt generates in To: and CC:, and then abort the reply.) Yes, it does work, thanks! However, I have to remember that this

Re: using a light theme with xterm (that has black background)

On Wed, Apr 16, 2025 at 06:38:25PM -0500, Ranjan Maitra via Mutt-users wrote: Mutt has a function , by default bound to 'L', that replies to a mailing list. See the manual. Can I set a folder-specific hook for this? All my mutt mailing emails are in a f

Re: Discourse emails not recognized as coming from a mailing-list

On Wed, Apr 16, 2025 at 01:48:43PM +0200, Sébastien Hinderer wrote: Still, as I mentionned in another thread, I am subscribed to a list to which the posters send emails in Bcc and such emails are not recognized as lists by Mutt although, ijust checked, they do have the List-Post header. I don'

Re: using a light theme with xterm (that has black background)

On Wed, Apr 16, 2025 at 06:04:19PM -0500, Ranjan Maitra via Mutt-users wrote: PS: Off-topic to this thread, but I have realized that the mutt mailing list does not have Reply-To set to the mailing list. That's been a worldwide subject of argument for 20 or 30 years. Some people think mailing

Re: Discourse emails not recognized as coming from a mailing-list

On Wed, Mar 19, 2025 at 01:50:35PM +0100, Sébastien Hinderer wrote: I follow a discourse forum but with emails enabled as I am not comfortable with its web interface. For the moment, the emails I receive for forum posts appear as addressed to me (with a + flag) rather than coming from a mailing

Re: Attachment decode issue

On Fri, Mar 28, 2025 at 05:49:24PM -0400, Kurt Hackenberg wrote: Background: I received an e-mail with an attached ZIP file (base64-encoded), where the attachment had the following mime headers: Content-Type: text/plain; name="name.zip" Content-Transfer-Encoding: base64 I thin

Re: Attachment decode issue

On Fri, Mar 28, 2025 at 03:07:15PM -0600, Daniel Carroll wrote: I think I've identified the issue, but my question is: is this a bug or expected behavior? Background: I received an e-mail with an attached ZIP file (base64-encoded), where the attachment had the following mime headers: Con

Re: basic mutt question

On Wed, Feb 26, 2025 at 04:38:33PM -0500, Jude DaShiell wrote: The G key gets pop email. What key is used to download imap email? No key, by default. There's the function , but, by default, there's no key binding to it. I change that, bind G to , since I use IMAP but not POP. Here's an e

Re: Two copies of email when cc-ed in mailing lists

On 2024/12/05 01:08, Rene Kita wrote: I wonder if the argument that modern MUAs make it easy to choose between 'reply' and 'group reply'/'reply all' still holds. Thunderbird makes it easy. It also has a third command, "reply list". (I suppose it recognizes messages from mailing lists by the h

Re: bouncing email and "from" address

On Wed, Jul 24, 2024 at 10:55:26AM -0700, Will Yardley wrote: Correct... mutt's "bounce" feature is more like redirecting / forwarding a message without modifying the other headers. From memory (and from doing a quick test), it uses the person who resent the message's address as the envelope-sen

Re: Newbie Help for multiple signatures

On Sat, Jul 20, 2024 at 10:56:08AM -0700, googly.negotiator...@aceecat.org wrote: On Sat, Jul 20, 2024 at 08:55:24AM GMT, MN Repair wrote: Using Mutt 1.7.2. My manual stops at chapter 10. I need basic help to get started once. Mind sharing chapter 14 ? My manual stops at chapter 10 too. It

Re: Handing on attempt to send

On Thu, Jun 20, 2024 at 11:42:20AM -0700, Will Yardley wrote: If by "the docs" you're referring only to the man pages, vs. the Mutt wiki and other online docs, you're right that they don't explicitly mention that it can refer to a remote mailbox. Obviously the manual was not updated when the I

Re: Handing on attempt to send

On Thu, Jun 20, 2024 at 11:18:48AM -0700, Will Yardley wrote: ...I agree the docs could make it more clear. The docs never mention it, not even once.

Re: Handing on attempt to send

On Thu, Jun 20, 2024 at 10:56:28AM -0700, Will Yardley wrote: The variable spoolfile has nothing to do with IMAP, and does not affect it. I disagree; from what I can see, the _naming_ of $spoolfile is vestigal and comes from before mutt supported IMAP, but it _does_ affect mutt's behavior, and

Re: Handing on attempt to send

On Thu, Jun 20, 2024 at 10:11:36AM -0700, Will Yardley wrote: I believe that's unnecessary, and kind of wrong. That variable spoolfile is for incoming mail delivered into local files on the computer where Mutt runs (eg, /var/mail/freduser, or ~freduser/Maildir). IMAP is entirely different,

Re: Handing on attempt to send

On Wed, Jun 19, 2024 at 11:43:54PM -0400, Andrew D Arenson wrote: Today, after working for years, my IMAP connection to Dreamhost has started hanging when I attempt to send an email, showing a message like: "Sending message... 0K/0.4K (0%)". Sure looks like Dreamhost had a problem. (Does it

Re: pretty-print mutt emails

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?

Re: Scheduling deferred sending of emails

On Sat, Jul 29, 2023 at 12:07:37PM +0200, Sébastien Hinderer wrote: I believe that more integrated solutions like Thunderbird do have such scheduled deferred sending features... Thunderbird does have that (called "send later"), but can only send when it's running, so is probably not what you

Re: FreeBSD ports mail/mutt feature patches

On Fri, May 05, 2023 at 05:58:21PM +, Tim Chase wrote: On 2023-05-05 12:37, Derek Schrock wrote: Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and :raises hand: hoping to get some feedback on option usage and which non-standard features you're using from the port's inc

Re: FreeBSD ports mail/mutt feature patches

On Fri, May 05, 2023 at 12:37:02PM -0400, Derek Schrock wrote: Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and hoping to get some feedback on option usage and which non-standard features you're using from the port's included extra patches. This is mainly the *_PATCH options.

Re: FreeBSD ports mail/mutt feature patches

On Fri, May 05, 2023 at 12:37:02PM -0400, Derek Schrock wrote: >Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and >hoping to get some feedback on option usage and which non-standard >features you're using from the port's included extra patches. This >is mainly the *_PATCH option

Re: why does mutt take so long to load my python folder?

On Sat, Nov 19, 2022 at 02:25:50PM +1100, Cameron Simpson wrote: from https://www.rfc-wiki.org/wiki/RFC2822. Is there a better RFC 2822 page? I used to use a nicely formatted tools.ietf.org URL, but that now redirects to some RFC author editing ... thing. Is this better? (For RFC 5322, success

Re: Apple displays flowed text

On Mon, Oct 31, 2022 at 08:12:23AM +0100, Ralf Hildebrandt via Mutt-users wrote: * Kurt Hackenberg : ... The iPhone mail reader displays flowed text correctly: lines are filled and word-wrapped to fit the screen. It also rotates when you turn the phone sideways. The Macintosh mail reader

Apple displays flowed text

I don't have any Apple hardware, but asked a couple friends to help out. They showed me an iPhone and a Macintosh displaying a test message that I sent them, text/plain format=flowed. The iPhone mail reader displays flowed text correctly: lines are filled and word-wrapped to fit the screen. I

Flowed text with Emacs

All, Remember the thing I posted here a while ago, a way to use Emacs to compose text/plain format=flowed? I've made it easier to use. Now it can be used with or without $edit_headers, and the text format conversions are automatic. It's here: Tr

Re: Two doubts about POP3 and IMAP

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 for IMAP. Fetchmail and getmail do that. There's also some

Re: [help] Disabling email notification not working

On Sun, Sep 11, 2022 at 04:45:55PM -0400, Kurt Hackenberg wrote: This example Woops. I missed a character in copy-paste, and should have given a web reference anyway: <http://mutt.org/doc/manual/#ex-multiaccount>

Re: [help] Disabling email notification not working

On Sun, Sep 11, 2022 at 06:28:30PM +, Charles via Mutt-users wrote: set folder = imap://... set spoolfile = imap://.../INBOX mailboxes -nonotify -nopoll $spoolfile set timeout = 10 set mail_check = 600 set new_mail_command = "/bin/mpv /noise.mp3" With this setup, I should not get a notifi

Re: Is linewrap dead?

On Mon, Sep 05, 2022 at 10:53:15PM -0400, Kurt Hackenberg wrote: Here's an updated version of my Emacs mode for Mutt flowed text... Here's a picture of it in use, with long lines being word-wrapped by Emacs's visual-line-mode.

Re: Is linewrap dead?

Here's an updated version of my Emacs mode for Mutt flowed text, with tweaks: displays quoted text in a different color, handles signature separator lines correctly, has a little more documentation. (defvar mutt-flowed-text-mode-map (let ((map (make-sparse-keymap))) (set-keymap-parent map t

Re: Is linewrap dead?

On Tue, Sep 06, 2022 at 08:54:58AM +1000, Cameron Simpson wrote: I'm not sure we're disagreeing here, except for the conceptual separation of the space-stuffing step. I agree that it's a separate step, or layer. I just think it might better be done within the editor -- or special-purpose prog

Re: Is linewrap dead?

On Mon, Sep 05, 2022 at 07:40:54PM +1000, Cameron Simpson wrote: It seems a little conceptually cleaner to have the editor do the whole job, rather than divide it between the editor and Mutt. But another complication is that you can edit a message more than once... I think space stuffing is e

Re: Is linewrap dead?

On 2022/09/04 18:45, raf via Mutt-users wrote: Hmm. I do "From-munging" on arrival. I should probably read rfc3676 properly. :-) Format=flowed includes a thing to protect the message from being damaged in the future by being written into an mbox file.

Re: Is linewrap dead?

On Mon, Sep 05, 2022 at 08:36:54AM +1000, Cameron Simpson wrote: But not space-stuffing, right? I just reread https://www.rfc-editor.org/rfc/rfc3676#section-4.4 to refresh my brain. Yeah, I don't think I'd want that when writing a message. Which I guess is why Mutt space-stuffs the format=f

Re: Is linewrap dead?

On 2022/09/04 06:37, Cameron Simpson wrote: Do you have any advice for automating spaces at the end of non-final paragraph lines for format=flowed in vim? I use these settings: https://github.com/cameron-simpson/css/blob/main/bin/vim-flowed which autowraps and leaves trailing spaces automatica

Re: Is linewrap dead?

On 2022/09/01 09:31, Mark H. Wood wrote: From my POV, when someone uses one of those MUAs that think a paragraph and a line are the same thing, that person's emails make more work for me, and I find the person annoying. "More work" means, for example, that if I try to quote such a "paragraph",

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 05:43:41PM -0400, John Hawkinson wrote: Very long lines -- one line per paragraph -- changes the meaning of ASCII/Unicode. err, what? I am confused what we are discussing. ASCII was not designed to be automatically word-wrapped. The idea was that a line keeps going

Re: Is linewrap dead?

On 2022/08/31 16:38, John Hawkinson wrote: I don't really think we're flouting the standards. Very long lines -- one line per paragraph -- changes the meaning of ASCII/Unicode. I could live with that if it were labelled, with a new MIME subtype, but I agree that a new subtype probably will

Re: Is linewrap dead?

On Wed, Aug 31, 2022 at 12:39:42PM -0500, Derek Martin wrote: I can't say I know how various MTAs handle lines longer than 998 characters, but I would expect at least a subset would either truncate them or reject your message... or at least that it would be wise to assume so. Mail readers th

Re: Is linewrap dead?

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 displayed properly in mutt with linebreaks, bu

Re: Is linewrap dead?

On 2022/08/29 13:28, Logan Rathbone wrote: Do phone mail readers understand text/plain format=flowed? 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. So now we know about Gmail. What about other common

Re: Is linewrap dead?

On Sun, Aug 28, 2022 at 08:49:50PM -0400, John Hawkinson wrote: I have not shaken the feeling that maybe I should learn how to compose format=flowed messages, but I guess it's not worth the trouble -- or at least I never managed to get it to work right. And yes, I toggle M-x visual-line-mode

Re: Is linewrap dead?

On Mon, Aug 29, 2022 at 12:28:29AM -, Tavis Ormandy wrote: Hello, long time mutt user here - I've always hard wrapped my lines at 72 columns for as long as I can remember. The problem is popular modern mobile and web-based MUAs don't handle this and can make unexpected linewrap decisions. I

Re: setting word/line wrap correctly with mutt and vim

On 2022/08/28 14:15, void wrote: I'm trying to get things so that emails composed and replied to in mutt do not have to be manually edited with hard returns each time. What I want is, if i'm typing in a line and it goes over 72 chars, to newline at that point intelligently. I've tried variat

Re: [RFC] Remove additional spaces when quoting already-quoted lines

On Sun, Jul 31, 2022 at 01:47:06PM -0400, Kurt Hackenberg wrote: >I agree there should not be a space after the '>'. The trouble is, >that space is ambiguous: software can't tell whether it's part of the >quoting or part of the original message. I spoke too s

Re: Key is not bound. Press '?' for help. - keycode

On 2022/07/28 16:23, Chris Narkiewicz via Mutt-users wrote: I configured a shortcut - C- and C- - to naviage the sidebar. It works, but on some terminal, pressing this shortcut yields Key is not bound. Press '?' for help. This is puzzling and I suspect that the terminal sends something else.

Re: file corruption after transmission over email

On 2022/06/01 12:17, Marcelo Laia wrote: tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ ... 1. http://www.jukie.net/bart/blog/lbdb-and-mutt Ah, bash's "process substitution". I forgot about that.

Re: file corruption after transmission over email

On 2022/05/29 12:15, Marcelo Laia wrote: If I send a message using tee >(lbdb-fetchaddr -a)|/usr/bin/msmtp -a gmail $@ the attached file with embedded image got corrupted What is that line intended to do? Is the message intended to be on tee's standard input? If so, how does it get there? T

Re: vs. / vs.

On 2022/03/23 17:29, Cameron Simpson wrote: On 23Mar2022 15:01, Jon Brinkmann wrote: I'm working to extract the original message and send it back through procmail to be properly sorted into my mailboxes. I've mapped this process to the 'E' key: macro index E '5procmail;tail procmail.log' 'e

Re: Unexplained mutt error

On 2022/02/25 10:53, Ranjan Maitra wrote: Regardless, actually I think that all I would be happy with would be a query or something that alerts me to the fact that I am potentially writing to an individual address (or a list) (for when I am on a list, but not in general, because then I start

Re: Unexplained mutt error

On 2022/02/22 18:10, Ranjan Maitra wrote: As an aside, for others: is there, in .muttrc a way to set things such that hitting "r" would automatically switch to reply list ("L") for specific folders? I have seen that for some list mail, "r" responds to list, and for others, to the sender. So

Re: Unexplained mutt error

On Sun, Feb 20, 2022 at 01:10:11PM -0600, Hokan wrote: >Replying to the sender seems to be the default behavior for the list. Do y'all know about the command 'L' ? See the manual:

Re: Are there any good maildir manipulation utilities out there?

On 2021/04/08 03:34, Chris Green wrote: fdm? ... Ah, I maybe wasn't clear, I want to manage E-Mails which have been delivered already. All the maildir messages I want to move around are already in ~/mail as maildirs. I want to rearrange them.

Re: Are there any good maildir manipulation utilities out there?

On 2021/04/07 18:16, Kurt Hackenberg wrote: On 2021/04/07 17:01, Chris Green wrote: I'm looking for a tool which will allow me to search through a large hierarchy of maildir messages and then provide actions to take on the matched messages. fdm? <https://github.com/nicm/fdm/blo

Re: my weekend project: a streaming POP3 fetcher, replacing fetchmail/getmail

On 2021/04/07 18:03, Cameron Simpson wrote: Just tried it on the satellite link with an overnight load of messages, normally a 10 minute exercise with getmail (give or take). 411 messages, 8.5 seconds. Nice. ...regexps...are appalling for email addresses. When testing addresses, my filer doe

Re: Are there any good maildir manipulation utilities out there?

On 2021/04/07 17:01, Chris Green wrote: I'm looking for a tool which will allow me to search through a large hierarchy of maildir messages and then provide actions to take on the matched messages. fdm? Or some other filter-and-deliver program

Re: my weekend project: a streaming POP3 fetcher, replacing fetchmail/getmail

On Wed, Apr 07, 2021 at 09:43:36AM +1000, Cameron Simpson wrote: >My new tool streams the fetches: it issues RETRs for every message up >front at maximum network speed - fully buffered and with no waits. A >parallel worker thread collects the messages as they come in at full >speed (the upstream s

Re: Strange error with mairix and a maildir stored by mutt

On 2021/03/25 16:37, Chris Green wrote: Brilliant! :-) That was it. I've not seen an error like that before but I guess it must be because of when I did something to that message relative to when the mairix index was built. You replied to that message. That's what the R in the filename means

Re: Strange error with mairix and a maildir stored by mutt

On 2021/03/25 14:19, Chris Green wrote: However I'm now getting a rather odd error on one particular message when I search using mairix:- chris@esprimo$ mairix 183493 stat '/home/chris/mail/folder/shopping/food/wine/cur/1612869077.1202519_3.esprimo:2,S': No such file or directory

Re: Quoting character when replying

On 2021/02/14 23:40, Cameron Simpson wrote: [format=flowed] is quite conservations, to minimise the implementation burden. And that frugality is likely where the inflexibility about ">" comes from. I think it's to avoid ambiguity. A line that starts with "> " could have been quoted that way

Re: Is there an easy way to remove empty maildir directories?

On 1/9/21 3:28 PM, Kurt Hackenberg wrote: I know that save_empty doesn't work for maildir... I ask again... Sorry, I was grumpy. That behavior is maybe not perfectly to my taste, but it's a small thing, not worth fussing about.

Re: Is there an easy way to remove empty maildir directories?

On 1/9/21 3:06 PM, Chris Green wrote: I know that save_empty doesn't work for maildir... Huh. Why doesn't it? Because it doesn't, see the documentation! :-) I looked at the documentation before I asked. I ask again: why does $save_empty remove empty mailboxes only of certain types? (It r

Re: Is there an easy way to remove empty maildir directories?

On 1/9/21 7:00 AM, Chris Green wrote: I know that save_empty doesn't work for maildir... Huh. Why doesn't it?

Re: Assigning multiple labels (X-Label) to a message

On 2020-12-16 19:36, David Champion wrote: As Kevin mentioned, I have some patches that work to resolve this stuff * Upcoming code supports X-Label, X-Keywords, X-Mozilla-Keys, and Keywords. * Mutt will read keywords from any of these and, by default, write them back to the same he

Re: Assigning multiple labels (X-Label) to a message

On 2020-12-16 13:05, Kevin J. McCarthy wrote: Mutt's label handling is pretty basic right now.  It expects only a single X-Label header in the email.  When editing the label, Mutt only knows how to write a single X-Label header back. ... The label completion has some code to delimit by ":" or

Re: Is it possible to change/add headers to incoming mail?

On 2020-12-09 05:11, Sam Kuper wrote: procmail is not a good option anymore, and has not been for a while now: https://marc.info/?l=openbsd-ports&m=141634350915839 ... Maildrop is a popular alternative. Some more delivery agents are listed in the Wikipedia article below. They may not all f

Re: A question about mairix, I'm sure there are users here

On 2020-11-26 09:26, Chris Green wrote: Reading the mairix man page it says that the messages found by mairix are symbolic links when using maildir... Yes. Doesn't the symbolic link itself tell you where the original message is? What do you want to do, exactly? Does the "muttjump" that Chri

Re: Sending all mail in IMAP folder from command line

On 2020-11-21 21:31, Cameron Simpson wrote: This then? The draft file is expected to contain just an RFC822 email: headers and a body. Although it is not an mbox file, if an mbox "From " line is present, it will be silently discarded. Good. I'll figure out how to do a *roff n

Re: Sending all mail in IMAP folder from command line

On 2020-11-21 00:10, Cameron Simpson wrote: How about something like this: The draft file is expected to contain just the email. It is not an mbox file. However, if an mbox From_ header is present, it will be accepted. Hmm. Pretty wordy. But not bad. How about: The draft file is ex

Re: Sending all mail in IMAP folder from command line

On 2020-11-19 04:29, Cameron Simpson wrote: ‐H draft Specify a draft file which contains header and body to use to send a message. ... Just a thought: if it needs to have a From_ mbox message header (or if it needs to not have that)... I'm pretty sure no From_ is

Re: Can mutt be persuaded to use a sensible maildir hierarchy?

On 2020-09-23 04:07, Chris Green wrote: I think I might try that second idea, I can run mb2md (as you say) 2354 times and get the layout I want. Then I can try mutt on it and see if it's practical. Does mb2md convert message attributes? (Message has been read, message has been replied to, e

Re: Message threading: reply message and In-Reply-To/References

On 2020-09-23 03:22, Francesco Ariis wrote: Il 23 settembre 2020 alle 13:52 Kevin Shell ha scritto: In mail/news discussion, some reply messages have no In-Reply-To/References headers, what cause reply messages don't have In-Reply-To/References headers? A possible explanation: the sender clic

Re: Can mutt be persuaded to use a sensible maildir hierarchy?

On 2020-09-22 13:30, Chris Green wrote: Does mutt still use the (IMHO silly) maildir hierarchy where mail 'folders' are simply represented by another '.' and name in the maildir directory name? Is there some way I can get to use real directories to represent my hierarchy of mail? Originally

Re: Is there a hook for modifying a To: field?

On 2020-08-26 15:29, Ian Zimmerman wrote: It would be easy if List-Post: was always present and the other was sometimes there. Right, in my case the List-Post is consistent and is the only address "subscribed" in mutt. If the List-Post is _not_ consistent, I'd really call it a buggy list and

Re: Is there a hook for modifying a To: field?

On Tue, Aug 25, 2020 at 01:46:52PM +0100, Chris Green wrote: >Here's the headers, rather verbose I'm afraid:- ... >From: NWY6 ... >To: "'David Eyre'" , > "'ixion'" ... >List-Post: Two different addresses for the list. Which one is correct? Do all m

Re: Going GUI...er

On 2020-04-07 22:18, Derek Martin wrote: Then again, maybe I should just move everything to gmail and be done with it. Please remember that Google reads your mail.

Re: Going GUI...er

On 2020-04-04 03:41, Vegard Svanberg wrote: Currently I'm running Mutt from a machine which I ssh into from 5 other computers I use frequently (IMAP backend - self-hosted). Suggestions? What does everyone else do? Meaning Mutt runs on the same computer that runs your IMAP server, and you us

  1   2   >