Re: pipe-message

2025-07-31 Thread Jason Stewart via Mutt-users
> myGUIMailViewer /dev/stdin < "$TMPFILE" The reason for this weirdness (instead of myGUIMailViewer "$TMPFILE") is that it's a flatpak program that can't access the normal system $TMPDIR, without taking many detours, so that is kind-of a hack. > Your diagnostics is wrong, it has nothing to do wit

Re: pipe-message

2025-07-31 Thread Nicolas George
Jason Stewart via Mutt-users (HE12025-07-31): > Are there any timeouts related to ? When I pipe to a > simple program (like `less`), everything works as expected. When I pipe > to a program with a longer startup time, (like `thunderbird` or > `chrome`), there is nothing to read from /dev/stdin.

Re: Mailbox browser doesn't trigger mail check

2025-07-27 Thread googly . negotiator862
On Wed, Jun 04, 2025 at 03:00:15AM +0200, Nickolai Dobrynin wrote: > I would like to press 'y' (), leave the mutt > session idle, and still be notified of new mail. Is this possible? ... > Entering a mailbox (any mailbox) does get me notified, but not until > I leave the mailbox browser. AFAIK

Re: ping

2025-07-27 Thread Nickolai Dobrynin
>> Sorry for the ping email folks. I just want to check if this list >> is still functional, or there's an OSUOSL issue. > > Thanks everyone for the ping reply messages! I got the ping message all right. As a side note, I would really appreciate if someone could answer my question from 2025-06-04

Re: ping

2025-07-27 Thread José María Mateos
On Sun, Jul 27, 2025 at 09:09:58AM +0100, Nuno Silva via Mutt-users wrote: On 2025-07-27, Kevin J. McCarthy wrote: On Sun, Jul 27, 2025 at 01:39:04PM +0800, Kevin J. McCarthy wrote: Sorry for the ping email folks. I just want to check if this list is still functional, or there's an OSUOSL iss

Re: ping

2025-07-27 Thread Nuno Silva via Mutt-users
On 2025-07-27, Kevin J. McCarthy wrote: > On Sun, Jul 27, 2025 at 01:39:04PM +0800, Kevin J. McCarthy wrote: >> Sorry for the ping email folks. I just want to check if this list >> is still functional, or there's an OSUOSL issue. > > Thanks everyone for the ping reply messages! (Those were not s

Re: ping

2025-07-26 Thread Kevin J. McCarthy
On Sun, Jul 27, 2025 at 01:39:04PM +0800, Kevin J. McCarthy wrote: Sorry for the ping email folks. I just want to check if this list is still functional, or there's an OSUOSL issue. Thanks everyone for the ping reply messages! -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 53

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

2025-06-02 Thread Sébastien Hinderer
Hello, Cameron Simpson (2025/06/02 11:31 +1000): > On 28May2025 08:49, Sébastien Hinderer > wrote: > > Kurt Hackenberg (2025/05/18 23:45 -0400): > > > 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 > > > >

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

2025-06-01 Thread Cameron Simpson
On 28May2025 08:49, Sébastien Hinderer wrote: Kurt Hackenberg (2025/05/18 23:45 -0400): 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 t

Re: decoding quoted-printable for iso-2022-jp fails sometimes

2025-05-29 Thread Kevin J. McCarthy
On Thu, May 29, 2025 at 09:53:33PM +0900, Kenichi Asai wrote: I suspect there may be a change in behavior with iconv between BigSur and Sequoia. It would be helpful if I could have an example to work with. Would you be willing to provide an mbox with the problematic email to me, or to attach it

Re: Mailing lists

2025-05-29 Thread googly . negotiator862
On Thu, May 29, 2025 at 02:05:52AM -0400, Kurt Hackenberg wrote: > So tell us, how does neomutt handle mailing lists? I don't think there's a difference in the commands explicitly related to lists, it's just that there are more ways to search in general. IIRC. It has been a while. -- Ian

Re: decoding quoted-printable for iso-2022-jp fails sometimes

2025-05-29 Thread Kenichi Asai
> Might this be a newly introduced Mac keyboard input problem? Thank you. I will look into it. I do use Karabiner Elements... > I suspect there may be a change in behavior with iconv between BigSur and > Sequoia. It would be helpful if I could have an example to work with. > Would you be willi

Re: decoding quoted-printable for iso-2022-jp fails sometimes

2025-05-29 Thread Kevin J. McCarthy
On Thu, May 29, 2025 at 11:09:31AM +0900, Kenichi Asai wrote: This phenomenon did not occur when I was using MacOS BigSur 11.6.7. The mutt version I am using is 2.2.11 (2023-08-18) for BigSur and 2.2.14 (2025-05-03) for Sequoia. However, today, I recompiled the old 2.2.11 on Sequoia and the same

Re: Mailing lists

2025-05-29 Thread Sébastien Hinderer
Kurt Hackenberg (2025/05/29 00:15 -0400): > Patterns have > ~l ("messages addressed to a known mailing list") > ~u ("messages addressed to a subscribed mailing list") > > Apparently those also work by comparing To: and CC: to commands "lists" and > "subscribe", and to $auto_subscribe. They

Re: decoding quoted-printable for iso-2022-jp fails sometimes

2025-05-29 Thread Rory Campbell-Lange
On 29/05/25, Kenichi Asai (a...@is.ocha.ac.jp) wrote: > After I started to use MacOS Sequoia 15.5, Japanese characters encoded > in iso-2022-jp and quoted-printable are sometimes garbled. It seems > what is happening is: ... Might this be a newly introduced Mac keyboard input problem? https://g

Re: Mailing lists

2025-05-28 Thread Kurt Hackenberg
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

2025-05-28 Thread googly . negotiator862
On Thu, May 29, 2025 at 12:15:07AM -0400, Kurt Hackenberg wrote: > Patterns have > ~l ("messages addressed to a known mailing list") > ~u ("messages addressed to a subscribed mailing list") > Apparently those also work by comparing To: and CC: to commands > "lists" and "subscribe", and to

Re: Mailing lists

2025-05-28 Thread Kurt Hackenberg
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: Mailing lists

2025-05-28 Thread Sébastien Hinderer
Dear Kurt, Many thanks for this response, I find it very helpful. Kurt Hackenberg (2025/05/18 23:42 -0400): > 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

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

2025-05-27 Thread Sébastien Hinderer
Kurt Hackenberg (2025/05/18 23:45 -0400): > 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 subscribe

Re: Mailing lists

2025-05-27 Thread Sébastien Hinderer
Thank you Ian, I find it reassuring that others also have thought about using scripts and actually even went further than just thinking about it! Seb. googly.negotiator...@aceecat.org (2025/05/18 10:49 -0700): > On Sat, May 17, 2025 at 12:49:16PM +0200, Sébastien Hinderer wrote: > > > One final

Re: Mailing lists

2025-05-27 Thread Sébastien Hinderer
Nuno Silva via Mutt-users (2025/05/18 10:21 +0100): > On 2025-05-17, Sébastien Hinderer wrote: > > > As I understand it, knowing whether a user is subscribed to a list or > > not is also very helpful to make sure we do not get responses twice. I > > do not knowwhether I am wrong or right but I alw

Re: mutt mbox format for new mailboxes

2025-05-22 Thread Kurt Hackenberg
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: mutt mbox format for new mailboxes

2025-05-22 Thread Rory Campbell-Lange
On 22/05/25, Rich Kulawiec (r...@gsp.org) wrote: > On Fri, May 16, 2025 at 05:26:25PM -0400, Kurt Hackenberg wrote: > > Nope, sorry. RFC 4155 has a problem. Its default format, the only one it > > defines, defines the From_ line rigidly, forbids ">From " escaping, and does > > not use a length. It

Re: mutt mbox format for new mailboxes

2025-05-22 Thread Rich Kulawiec
On Fri, May 16, 2025 at 05:26:25PM -0400, Kurt Hackenberg wrote: > Nope, sorry. RFC 4155 has a problem. Its default format, the only one it > defines, defines the From_ line rigidly, forbids ">From " escaping, and does > not use a length. It says messages should be found by recognizing the whole >

Re: Mailing lists

2025-05-20 Thread Mark E. Mallett
On Mon, May 19, 2025 at 02:23:20PM -0700, Will Yardley wrote: > On Sun, May 18, 2025 at 11:42:08PM -0400, Kurt Hackenberg wrote: > > Mutt needs to know what addresses are mailing lists to generate the > > header Mail-Followup-To:, which asks recipients not to send duplicate > > messages to you. >

Re: Mail-Followup-To header; was: Mailing lists

2025-05-20 Thread Michael Kjörling
On 19 May 2025 14:23 -0700, from mutt-us...@veggiechinese.net (Will Yardley): > As best I understand, M-F-T is a draft from 1997 that expired in > 1998(?), never made progress towards becoming a standard (and is only > implemented by a handful of other clients other than Mutt, none of which > are s

Re: Mailing lists

2025-05-19 Thread Will Yardley
On Sun, May 18, 2025 at 11:42:08PM -0400, Kurt Hackenberg wrote: > Mutt needs to know what addresses are mailing lists to generate the > header Mail-Followup-To:, which asks recipients not to send duplicate > messages to you. As best I understand, M-F-T is a draft from 1997 that expired in 1998(?)

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

2025-05-18 Thread Kurt Hackenberg
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

2025-05-18 Thread Kurt Hackenberg
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

2025-05-18 Thread Nemo Thorx
Quoting Rory Campbell-Lange from 15 May (a Thursday in 2025) at 0640 hours... > > 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.a

Re: Mailing lists

2025-05-18 Thread googly . negotiator862
On Sun, May 18, 2025 at 10:49:02AM -0700, googly.negotiator...@aceecat.org wrote: > Here is what I do. Like Chris, I use a generator script to start from > a unified config file (which is JSON5 in my case). There are two > significant outputs: Sorry for self-follow-up: I forgot to mention that I

Re: Mailing lists

2025-05-18 Thread googly . negotiator862
On Sat, May 17, 2025 at 12:49:16PM +0200, Sébastien Hinderer wrote: > One final note: I don't now how other muttusers go about archiving > their emails but I continue to have dedicated mailboxes (maildirs, > to be precise) for mailing lists and this, too, requires a quantity > of configuration tha

Re: Mailing lists

2025-05-18 Thread Nuno Silva via Mutt-users
On 2025-05-17, Sébastien Hinderer wrote: > As I understand it, knowing whether a user is subscribed to a list or > not is also very helpful to make sure we do not get responses twice. I > do not knowwhether I am wrong or right but I always foundMutt's way of > dealing with the situation superior t

Re: Mailing lists

2025-05-18 Thread Nuno Silva via Mutt-users
On 2025-05-17, Will Yardley wrote: > On Sat, May 17, 2025 at 08:05:13PM +0100, Chris Green wrote: >> On Sat, May 17, 2025 at 07:21:17PM +0200, Sébastien Hinderer wrote: > >> > When I suggested to share I was more thinking about e.g. adding your >> > work to Mutt's repo, if there is a contrib direc

Re: Mailing lists

2025-05-17 Thread Will Yardley
On Sat, May 17, 2025 at 08:05:13PM +0100, Chris Green wrote: > On Sat, May 17, 2025 at 07:21:17PM +0200, Sébastien Hinderer wrote: > > When I suggested to share I was more thinking about e.g. adding your > > work to Mutt's repo, if there is a contrib directory, say. > Yes, I guess that somewhere

Re: Mailing lists

2025-05-17 Thread Chris Green
On Sat, May 17, 2025 at 07:21:17PM +0200, Sébastien Hinderer wrote: > Thanks alot, Chris! > > When I suggested to share I was more thinking about e.g. adding your > work to Mutt's repo, if there is a contrib directory, say. Or maybe if > the manual has a "Useful links" section there could be a lin

Re: Mailing lists

2025-05-17 Thread Sébastien Hinderer
Thanks alot, Chris! When I suggested to share I was more thinking about e.g. adding your work to Mutt's repo, if there is a contrib directory, say. Or maybe if the manual has a "Useful links" section there could be a link to a public repository or so, so that your contribution receives the attenti

Re: Mailing lists

2025-05-17 Thread Chris Green
On Sat, May 17, 2025 at 04:39:07PM +0200, Sébastien Hinderer wrote: > Hello Chris, thanks a lot for your feedback! > > Chris Green (2025/05/17 14:39 +0100): > > On Sat, May 17, 2025 at 12:49:16PM +0200, Sébastien Hinderer wrote: > > > For instance here is the configuration I have for this list: >

Re: Mailing lists

2025-05-17 Thread Sébastien Hinderer
Hello Chris, thanks a lot for your feedback! Chris Green (2025/05/17 14:39 +0100): > On Sat, May 17, 2025 at 12:49:16PM +0200, Sébastien Hinderer wrote: > > For instance here is the configuration I have for this list: > > > > subscribe mutt-users@mutt.org > > fcc-hook '~t mutt-users@mutt.org|~c m

Re: Mailing lists

2025-05-17 Thread Chris Green
On Sat, May 17, 2025 at 12:49:16PM +0200, Sébastien Hinderer wrote: > For instance here is the configuration I have for this list: > > subscribe mutt-users@mutt.org > fcc-hook '~t mutt-users@mutt.org|~c mutt-users@mutt.org' '=list/mutt-users/' > save-hook '~t mutt-users@mutt.org|~c mutt-users@mutt

Re: Mailing lists

2025-05-17 Thread Sébastien Hinderer
Dear Kurt, all, A bunch of thanks for the detective work. I do not have much to add, especially given I donot see myself doing more than participating to feature design. To be ven more precise, I do not see myself code anything, partly because I start to be rather involved in understanding accessi

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

2025-05-17 Thread Sébastien Hinderer
Hello Kurt and a lot of gratitude for you re-visiting the topic and apparently even taking the time to read Mutt's sources! Kurt Hackenberg (2025/05/10 17:25 -0400): > Sébastien, I'm sorry, I gave a bad answer back then, because I misunderstood > Mutt's mailing list code. I

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Kurt Hackenberg
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

2025-05-16 Thread Will Yardley
On Fri, May 16, 2025 at 02:43:50PM -0400, Kurt Hackenberg wrote: > 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: > > Right, totally understand all of this, but where I'm confused is that if > > the claim is that M

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Kurt Hackenberg
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

2025-05-16 Thread Rich Kulawiec
On Thu, May 15, 2025 at 02:25:44PM -0700, Will Yardley wrote: > https://www.loc.gov/preservation/digital/formats/fdd/fdd000386.shtml > mentions MBOXCL and MBOXCL2 dating back to SYSVr4. So, if that's the > case, that may have been the widely understood "mbox" used well before > Mutt was first writt

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Rory Campbell-Lange
On 16/05/25, Kurt Hackenberg (k...@panix.com) wrote: > 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 inv

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Kurt Hackenberg
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 ">From " escaping, which damages

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Kurt Hackenberg
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

2025-05-16 Thread Kurt Hackenberg
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

2025-05-16 Thread Kurt Hackenberg
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

2025-05-16 Thread Mark E. Mallett
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. Oh this is kind of interesting. I have a set of patches that I apply to mutt, like for when new versions come out. One of them is a fix to

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Rory Campbell-Lange
On 16/05/25, Kurt Hackenberg (k...@panix.com) wrote: > All right, I just made a maildir for this test. Tar file is attached. Save > the tar file, extract the maildir from it (it's named test.maildir), do > > mutt -f test.maildir > > have Mutt save the message to a new mbox file, cat that mbox

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

2025-05-16 Thread Tim Chase
On 2025-05-16 08:37, Mutt list wrote: > 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 an

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

2025-05-16 Thread Tim Chase
On 2025-05-16 14:46, Mark E. Mallett wrote: > PS: just to babble on, here's part of the body of a message that I use > in one of the test scripts for my mail delivery agent. > [snip] > I've left-padded all the lines here with spaces so they won't get > quoted. I hope. If you're looking for more tr

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Rory Campbell-Lange
On 16/05/25, Mark E. Mallett (m...@schmem.com) wrote: > Just to wade into the bikeshedding.. ... > PS: just to babble on, here's part of the body of a message that I use > in one of the test scripts for my mail delivery agent. The test files > are used in testing different formats (mbox and maildir

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

2025-05-16 Thread Kurt Hackenberg
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: ReRe: mutt mbox format for new mailboxes: mutt mbox format for new mailboxes

2025-05-16 Thread Mark E. Mallett
On Fri, May 16, 2025 at 08:37:01AM +, dvalin--- via Mutt-users wrote: > 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 oth

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Kurt Hackenberg
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 section

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

2025-05-16 Thread googly . negotiator862
On Fri, May 16, 2025 at 10:47:15AM -0700, Will Yardley 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 fi

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

2025-05-16 Thread Will Yardley
On Fri, May 16, 2025 at 08:37:01AM +, dvalin--- via Mutt-users wrote: > 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 oth

Re: mutt mbox format for new mailboxes

2025-05-16 Thread Rory Campbell-Lange
On 16/05/25, Kurt Hackenberg (k...@panix.com) wrote: > > I was just confused because the earlier post had seemed > > to imply that this was not done / needed for MBOXCL2. > > It's not, because that variant has Content-Length:. > > Let's say you want to put multiple variable-length chunks of text

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Will Yardley
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 section and in there finds the length of the message body, > and th

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Kurt Hackenberg
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

2025-05-15 Thread Will Yardley
On Thu, May 15, 2025 at 08:57:56PM -0400, Kurt Hackenberg wrote: > 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

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Kurt Hackenberg
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

2025-05-15 Thread Kurt Hackenberg
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

2025-05-15 Thread Will Yardley
On Thu, May 15, 2025 at 06:40:34AM +0100, Rory Campbell-Lange wrote: > On 14/05/25, Kurt Hackenberg (k...@panix.com) wrote: > > 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 kno

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Rory Campbell-Lange
On 15/05/25, Christian Brabandt (cbli...@256bit.org) wrote: > On Thu, 15 May 2025, Rory Campbell-Lange wrote: > > I tested > > > > mutt -R -f test.mbox -m Maildir > > > > I tagged all and saved to a new destination, and that worked as you > > suggested. > A long time ago¹, I wrote a guide (

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Christian Brabandt
On Thu, 15 May 2025, Rory Campbell-Lange wrote: > My plan for "mailboxoperator" > (https://github.com/rorycl/mailboxoperator) is to provide a general > mailbox/maildir parser which might be useful for e.g. legal discovery. > My post here was because of the problem with the protonmail go mbox > pa

Re: mutt mbox format for new mailboxes

2025-05-15 Thread Rory Campbell-Lange
On 15/05/25, Dan Ritter (d...@randomstring.org) wrote: > Rory Campbell-Lange wrote: > > I'm going to start with the postmark line (I can't really read C but > > is_from in from.c makes interesting reading.) I'll then work to decode > > the different mbox types, starting with MBOXCL/MBOXCL2, as nee

Re: mutt mbox format for new mailboxes

2025-05-14 Thread Rory Campbell-Lange
On 14/05/25, Kurt Hackenberg (k...@panix.com) wrote: > 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: si

Re: mutt mbox format for new mailboxes

2025-05-14 Thread Kurt Hackenberg
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

Re: Mailing lists

2025-05-11 Thread Chris Green
On Sat, May 10, 2025 at 05:27:51PM -0400, Kurt Hackenberg wrote: [snip] > > 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 i

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

2025-05-10 Thread Kurt Hackenberg
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: A mailing list not being recognized as such

2025-04-24 Thread Sébastien Hinderer
googly.negotiator...@aceecat.org (2025/04/16 21:11 -0700): > On Sat, Apr 05, 2025 at 10:35:32AM -0700, googly.negotiator...@aceecat.org > wrote: > > > Can I make this a feature request? > > https://gitlab.com/muttmua/mutt/-/issues/499 Awesome, thanks! Seb.

Re: Use mutt with several accounts on same server

2025-04-23 Thread Paul Tansom
On 18/04/2025 12:50, Erwan David wrote: I use mutt with sevreal accounts on different servers through folder-hook, account-hook, etc. But now I need to use it with two different accounts on same server. I do not succeed in differentiating them since folders are names imap://server, and

Re: Use mutt with several accounts on same server

2025-04-23 Thread Erwan David
On Wed, Apr 23, 2025 at 01:44:22PM CEST, Paul Tansom said: > On 18/04/2025 12:50, Erwan David wrote: > > I use mutt with sevreal accounts on different servers through > > folder-hook, account-hook, etc. > > But now I need to use it with two different accounts on same server. > > I do not succ

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

2025-04-21 Thread Derek Martin
On Mon, Apr 21, 2025 at 11:26:48AM -0700, googly.negotiator...@aceecat.org wrote: > So they have to be on different machines in the case of using X remotely: > .Xresources on the server, .Xdefaults on the client. Eh... I didn't really want to dive too deep into the X init process, since it's esot

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

2025-04-21 Thread googly . negotiator862
On Mon, Apr 21, 2025 at 10:01:13AM -0400, Derek Martin wrote: > Like most of the programs that came with the original X Window > System, xterm relies on "X resources" for configuration. On most > modern Linux systems, you can create a file in your home directory > called .Xresources, and then def

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

2025-04-21 Thread Derek Martin
On Wed, Apr 16, 2025 at 03:05:15PM -0500, Ranjan Maitra via Mutt-users wrote: > Hi, > > So, I like to have my email window to have a light theme and > everything else to have a dark theme (to distinguish things easily > and sort of intuitively). ... > I tried using `xterm -bg "#ff" -fg '#000

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

2025-04-18 Thread José María Mateos
On Fri, Apr 18, 2025 at 01:58:24PM -0400, Kurt Hackenberg wrote: Fastmail is a large mail service with a good reputation. It's not expensive -- looks like base price is $5 / month. Another happy Fastmail customer here. Very good IMAP support, responsive staff, plus you can download your contac

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

2025-04-18 Thread Kurt Hackenberg
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

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

2025-04-18 Thread dvalin--- via Mutt-users
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 proper threading on the mailing

Re: Threading/references

2025-04-18 Thread Christian Ebert
* Nuno Silva via Mutt-users on Friday, April 18, 2025 at 12:28:12 +0100: 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 proper threading on the mail

Threading/references (was: Re: using a light theme with xterm (that has black background))

2025-04-18 Thread Nuno Silva via Mutt-users
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 proper threading on the mailing list side too, or is there something amiss on Gmane's side? -- Nuno S

Re: Anyone used mutt to sub or unsub to linux kerrel lists ?

2025-04-18 Thread Ken Moffat via Mutt-users
On Fri, Apr 11, 2025 at 04:13:15PM -0700, Akshay Hegde via Mutt-users wrote: > On 2025-04-11 22:55 +0100, Ken Moffat via Mutt-users wrote: > > I just send an empty body when I ubscribe/subscribe. And yes, to answer > your initial question, I use mutt to send the (un)subscribe email. > > You shoul

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

2025-04-18 Thread Sébastien Hinderer
Kurt Hackenberg (2025/04/17 21:42 -0400): > 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 >

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

2025-04-17 Thread Kurt Hackenberg
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

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

2025-04-17 Thread Todd Zullinger
Kurt Hackenberg wrote: >>I had `folder-hook '=lists/'` too, but `message-hook` has >>replaced that for me. I 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

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

2025-04-17 Thread Todd Zullinger
Ranjan Maitra via Mutt-users wrote: > Yes, my problem is that when I respond, I do not remember > to check at the top especially for the longer mesages when > it goes off the screen. > > I will look into message hooks to set this (as suggested > by Kurt): I was thinking that someone may have done

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

2025-04-17 Thread Todd Zullinger
Ranjan Maitra via Mutt-users wrote: > On Wed Apr16'25 04:54:08PM, Todd Zullinger wrote: >> Testing with pull request #13 does look decent. So it seems >> like the issue may be largely that the theme choice uses a >> bit of a dark background by default, but you can adjust it >> to suite your tastes

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

2025-04-17 Thread dvalin--- via Mutt-users
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

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

2025-04-17 Thread Ranjan Maitra via Mutt-users
On Wed Apr16'25 09:21:28PM, googly.negotiator...@aceecat.org wrote: > From: googly.negotiator...@aceecat.org > Date: Wed, 16 Apr 2025 21:21:28 -0700 > To: mutt-users@mutt.org > Subject: Re: using a light theme with xterm (that has black background) > > On Wed, Apr 16, 2

Re: A mailing list not being recognized as such

2025-04-17 Thread googly . negotiator862
On Sat, Apr 05, 2025 at 10:35:32AM -0700, googly.negotiator...@aceecat.org wrote: > Can I make this a feature request? https://gitlab.com/muttmua/mutt/-/issues/499 -- Ian

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

2025-04-16 Thread googly . negotiator862
On Wed, Apr 16, 2025 at 08:07:47PM -0500, Ranjan Maitra via Mutt-users wrote: > Yes, it does work, thanks! However, I have to remember that this is > a list and use that then. I am bound to forget this (as I was about > to do right now) and therefore it would be better if I had one "r" > set which

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

2025-04-16 Thread Will Yardley
On Wed, Apr 16, 2025 at 07:16:53PM -0400, Kurt Hackenberg wrote: > 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

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

2025-04-16 Thread Kurt Hackenberg
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)

2025-04-16 Thread Ranjan Maitra via Mutt-users
On Wed Apr16'25 07:59:34PM, Kurt Hackenberg wrote: > From: Kurt Hackenberg > Date: Wed, 16 Apr 2025 19:59:34 -0400 > To: mutt-users@mutt.org > Subject: Re: using a light theme with xterm (that has black background) > > On Wed, Apr 16, 2025 at 06:38:25PM -0500, Ranjan Mait

  1   2   3   4   5   6   7   8   9   10   >