Re: format=flowed

On 1/5/19 5:48 PM, Samir Benmendil wrote: I stopped using format=flowed because not much besides Mutt supports it, and particularly not GMail and Outlook. That's interesting. I've been using format=flowed for ages now, never really checked how it looked in other MUA. It worked in Mutt and I

Re: Hide a message?

On 12/13/18 10:05 PM, Patrick Shanahan wrote: mbox still serves my needs and has never failed me. why would I want to invest time and effort to change to something (anything) else? maildir does not "work better" as I can see. If mbox works for the way you use it, there's no need to change.

Re: Hide a message?

On 12/13/18 11:15 AM, Victor Sudakov wrote: Dan Ritter wrote: That doesn't happen in Maildir storage. Is it reasonable to switch from mbox to maildir? An interesting idea! In my opinion, it's always a good idea to convert from mbox to something that works better. On Unix systems, maildir

Re: Hide a message?

On 12/13/18 11:46 AM, Ian Zimmerman wrote: On 2018-12-13 23:15, Victor Sudakov wrote: I have over 400 mboxes in my ~/Mail directory, some of them being mailing list archives, others being Usenet groups archives, or mboxes inherited from my decommissioned CommuniGate server. My dovecot

Re: Hide a message?

On 12/15/18 1:01 AM, Erik Christiansen wrote: On 13.12.18 13:05, Kurt Hackenberg wrote: You may want to preserve message attributes -- things like, this message has been read, this message has been replied to, this message has been flagged, this message has been assigned the keyword "b

Re: OT: culprit in MIME recoding and breaking signatures

On 11/23/18 1:40 AM, Ian Zimmerman wrote: The winner appears to be Perl, namely the Mail::Audit module (and whatever other modules it relies on). I had a couple of scripts that did gentle transformations of incoming mails. The transformations were supposed to only ever touch the headers, but

Re: Compiling a newer version than the latest .deb package

On 2019-06-07 07:22, Cameron Simpson wrote: Are you looking in mbox files or in other places. [...] Hmm, my maildir message files also have From_ lines. If fetchmail's delivering to a programme, nothing prevents that being an arbitrary script to premangle a leading From_ line. Hmm. I've got

Re: Compiling a newer version than the latest .deb package

On 2019-06-07 05:08, Frank Watt wrote: When I look at the headers of most mail, I see an mbox-style From line. Where do we make use of the 'reformat -f0' and "Return-Path" advice? In the stream of data that ends up on the standard input of the delivery agent (procmail, maildrop, whatever).

Re: Compiling a newer version than the latest .deb package

On 2019-06-08 00:41, Cameron Simpson wrote: Well, the From_ isn't just a delimiter for mbox lines, it also historically contains the envelope address from the mail system - the address used for this delivery (versus whatever may be in the headers). It's the envelope sender address, who SMTP

Re: Compiling a newer version than the latest .deb package

On 2019-06-07 05:08, Frank Watt wrote: | However, fetchmail has a -m option, which can probably deliver directly | to procmail, bypassing the local mail system entirely. Looks like that's not as simple as I'd hoped. I'm sort of jumping in blind here -- don't know exactly what you're trying to

Re: Inbox folder doesn't work anymore

On 2019-05-07 12:13, Luciano ES wrote: Does the Inbox folder contain the standard maildir style directories: cur, new, tmp ? Unread messages should be inside 'new', read messages inside 'cur'. Hi. There used to be cur, new, tmp. There shouldn't be because it is all MH. So I decided to delete

Re: Inbox folder doesn't work anymore

On 2019-05-07 17:11, Luciano ES wrote: I don't remember how I converted it. It was a very long time ago. Oh. But the problem just started a day or two ago? Then two questions: Did something change just before the problem started? If so, what? And, maybe you could show us the contents of

Re: Inbox folder doesn't work anymore

On 2019-05-07 15:21, Luciano ES wrote: Why does mutt show files rather than browse folders on every first attempt? It doesn't make sense. Because when you converted your inbox from maildir to MH format, you didn't do it right. That's my current guess, anyway. How did you convert it,

Re: How do I set up a gmail account?

On 2019-05-07 22:56, Luciano ES wrote: folder-hook gmail 'set folder = "imaps://imap.gmail.com:993"' folder-hook gmail 'set spoolfile = "$HOME/Mail/gmail"' That looks backward to me. Really, read the manual.

Re: Inbox folder doesn't work anymore

On 2019-05-07 19:00, Luciano ES wrote: I pasted the output of ls -AR here: https://pastebin.com/DihPtit2 Nothing jumps out at me as obviously invalid MH format, but it's clearly been modified and reused at least a couple times. There's extra stuff that's not normally present in MH format.

Re: File locking of mboxrd-format mbox file

On 2019-06-28 23:24, Frank Watt wrote: I'm looking at the getmail documentation... BTW, Is "mbox" the standard abbreviation of Mboxrd or is it something else? Mbox is not a single file format; it's a family of related formats, all partially incompatible. The original form, and many

Re: marking a message as "read"

On 2019-09-06 10:50, Kevin J. McCarthy wrote: Both "new" and "old" are "unread".  "read" means neither new nor old. That sounds familiar. I think that goes back about 40 years, long before Mutt, to how spooling of incoming messages was implemented, and the introduction of the non-standard

Re: File locking of mboxrd-format mbox file

On 2019-06-30 01:23, Frank Watt wrote: So does that mean I don't have to be concerned about lock settings when it's only a single user system? No. A single-user system still has multiple processes. You need file locking to use mbox.

Re: Creating HTML emails with mutt

Sorry, I'm coming into this late. Early on, Kevin McCarthy said: Native support for multipart/alternative composition isn't in my todo list. Too bad -- that would be conceptually clean, to generate multipart/alternative as part of composition. Mutt runs an external text editor to compose

Re: How [Mutt] to send links from Firefox

On 2019-10-14 19:46, José María Mateos wrote: I think the problem was that my desktop environment was doing something funky with the way it passed arguments to the mutt executable. After reading your e-mail I fixed it by telling Firefox to call a script for mailto: links, and the script is

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

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

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: 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

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,

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: 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

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=141634350915839 ... Maildrop is a popular alternative. Some more delivery agents are listed in the Wikipedia article below. They may not all

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

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: 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

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_

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

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

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: 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: 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

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: 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

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: 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

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: 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/blob/mas

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

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.

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

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: 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'

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?

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: 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.

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

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

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 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,

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

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

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

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

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

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

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

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

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:

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.

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

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

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: 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

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: [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 soon. Now I've

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,

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

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 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

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

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

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?