Intermittent reconnection failure
Having intermittent trouble with mutt 2.2.12 on debian stable. It uses an imap server (dovecot) over a wireguard VPN. When my laptop resumes from suspend, a few seconds elapse before the VPN becomes available and mutt usually reconnects automatically. Sometimes, about one time in 5, it doesn't. In those cases I make mutt reconnect by opening a folder. It's not a grave problem but I'd prefer mutt to try a little harder to reconnect, if that can be done. I'm attaching two extracts from .muttdebug0, running with '-d 2'. reconn-ok.txt shows mutt reconnecting after running my preconnect script. reconn-failed.txt shows mutt failing to reconnect and without running my preconnect script. I obscured one folder name with for privacy. Why does mutt sometimes fail to reconnect? Thanks -- Nick Asunción 08:36 PYT ► 21°C ◆ cielo claro ◆ 11Km/h SSE ◆ 66% HR [2024-04-17 19:44:00] 4< * STATUS Junk (RECENT 2 UIDNEXT 335 UIDVALIDITY 1519640566 UNSEEN 0) [2024-04-17 19:44:00] 4< a3058 OK Status completed (0.001 + 0.000 secs). [2024-04-17 19:44:00] 4< * STATUS *** (RECENT 0 UIDNEXT 1551 UIDVALIDITY 1519640578 UNSEEN 0) [2024-04-17 19:44:00] 4< a3059 OK Status completed (0.001 + 0.000 secs). [2024-04-18 05:41:01] 4> a3060 NOOP [2024-04-18 05:41:12] tls_socket_read (Error in the pull function.) [2024-04-18 05:41:16] imap_cmd_step: Error reading server response. [2024-04-18 05:41:16] A fatal error occurred. Will attempt reconnection. [2024-04-18 05:41:16] imap_exec: command failed: [2024-04-18 05:41:16] Trying to reconnect... [2024-04-18 05:41:16] Reading imaps://rolly.vpn/INBOX... [2024-04-18 05:41:16] Executing preconnect: wait-for-ping -v -l ~/.local/logs/mutt-preconnect.log rolly.vpn 20 [2024-04-18 05:41:16] Preconnect result: 0 [2024-04-18 05:41:16] Looking up rolly.vpn... [2024-04-18 05:41:16] Connecting to rolly.vpn... [2024-04-18 05:41:18] SSL/TLS connection using TLS1.3 (ECDHE-RSA/AES-256-GCM/AEAD) [2024-04-18 05:41:18] Connected to rolly.vpn:993 on fd=4 [2024-04-18 05:41:18] 4< * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot (Debian) ready. [2024-04-18 05:41:18] imap_authenticate: Using any available method. [2024-04-18 05:41:18] imap_auth_gsasl: using mech PLAIN [2024-04-18 05:41:18] Authenticating (PLAIN)... [2024-04-18 07:55:25] 4< * STATUS Junk (RECENT 2 UIDNEXT 335 UIDVALIDITY 1519640566 UNSEEN 0) [2024-04-18 07:55:25] 4< a5509 OK Status completed (0.001 + 0.000 secs). [2024-04-18 07:55:25] 4< * STATUS *** (RECENT 0 UIDNEXT 1551 UIDVALIDITY 1519640578 UNSEEN 0) [2024-04-18 07:55:25] 4< a5510 OK Status completed (0.001 + 0.000 secs). [2024-04-18 08:26:31] 4> a5511 NOOP [2024-04-18 08:26:34] 4< * BYE Disconnected for inactivity. [2024-04-18 08:26:34] Handling BYE [2024-04-18 08:26:34] Disconnected for inactivity. [2024-04-18 08:26:36] A fatal error occurred. Will attempt reconnection. [2024-04-18 08:26:36] imap_exec: command failed: * BYE Disconnected for inactivity. [2024-04-18 08:26:36] Trying to reconnect... [2024-04-18 08:26:36] Reading imaps://rolly.vpn/alert... [2024-04-18 08:26:36] Selecting alert... [2024-04-18 08:26:36] 5> a0292 STATUS "Drafts" (MESSAGES) a0293 SELECT "alert" [2024-04-18 08:26:36] tls_socket_read (Error in the pull function.) [2024-04-18 08:26:40] imap_cmd_step: Error reading server response. [2024-04-18 08:26:40] Reconnect failed. Mailbox closed. [2024-04-18 08:26:40] mutt_socket_close: Attempt to close closed connection.
Re: Can't sign if I sign
On Sat, Apr 13, 2024 at 07:39:45AM +0200, Sirius via Mutt-users wrote: > In days of yore (Sat, 13 Apr 2024), Laura Orvokki Kursula via Mutt-users thus > quoth: > > Hello all > > > > I have encountered a strange problem setting up mutt: when I attach a > > signature > > block to my e-mail using `$signature', my PGP signature is, according to > > mutt, > > invalid. E-mails without signature blocks yield valid PGP signatures. If I > > go > > back and replace the automatic signature with something else, the PGP > > signature > > checks out too. Is this a known issue? Is there something I can do about it? > > That is odd. I do not see that at all (just tested, mutt-2.2.13 on > Debian). For a gpg signature to be invalid, what is signed has to have > changed in some way. > > You are doing effectively this in muttrc: > set signature="~/.mutt/signature" > yes? And there is nothing in the signature that could be altered after it > is pulled into the message and the GnuPG signature is applied, right? After some more testing, I figured out this issue had nothing at all to do with signature blocks, or mutt. The culprit was the silly `X-Clacks-Overhead' header I had configured postfix to add ages ago. How I came to think it had a correlation with whether or not I use a `$signature' remains a mystery; my bet is on a lack of sleep. Thank you for your time. > My questions would be: > - mutt gnupg configuration, is it changed in any way from distribution > default? > - version of mutt and what distribution/version are you running? > > My suggestion would be to run mutt with -d1 or -d2 and look at the debug > output (crank the debug level higher if need be, it goes up to five) to > work out what happens. > > -- > Kind regards, > > /S -- Laura signature.asc Description: PGP signature
Re: Can't sign if I sign
In days of yore (Sat, 13 Apr 2024), Laura Orvokki Kursula via Mutt-users thus quoth: > Hello all > > I have encountered a strange problem setting up mutt: when I attach a > signature > block to my e-mail using `$signature', my PGP signature is, according to mutt, > invalid. E-mails without signature blocks yield valid PGP signatures. If I go > back and replace the automatic signature with something else, the PGP > signature > checks out too. Is this a known issue? Is there something I can do about it? That is odd. I do not see that at all (just tested, mutt-2.2.13 on Debian). For a gpg signature to be invalid, what is signed has to have changed in some way. You are doing effectively this in muttrc: set signature="~/.mutt/signature" yes? And there is nothing in the signature that could be altered after it is pulled into the message and the GnuPG signature is applied, right? My questions would be: - mutt gnupg configuration, is it changed in any way from distribution default? - version of mutt and what distribution/version are you running? My suggestion would be to run mutt with -d1 or -d2 and look at the debug output (crank the debug level higher if need be, it goes up to five) to work out what happens. -- Kind regards, /S signature.asc Description: PGP signature
Can't sign if I sign
Hello all I have encountered a strange problem setting up mutt: when I attach a signature block to my e-mail using `$signature', my PGP signature is, according to mutt, invalid. E-mails without signature blocks yield valid PGP signatures. If I go back and replace the automatic signature with something else, the PGP signature checks out too. Is this a known issue? Is there something I can do about it? Thank you all in advance -- Laura signature.asc Description: PGP signature
Re: Question about message id
On Tue, Apr 09, 2024 at 10:53:41AM -0400, Derek Martin wrote: > On Sun, Apr 07, 2024 at 01:19:09PM +, Ебрашка wrote: > > Question, what should I write in .muttrc to make my outgoing mails have > > the same beautiful message-ID as Yandex mail? > > The unfathomable thing about this question is why you (or anyone) > should care in the slightest what your message ID looks like. It's an > esoteric detail about e-mail transfer, the specific contents of which > have no value to users, who in most cases won't even ever see the > message ID, since most mail clients hide that detail from you by > default. You have no practical reason to care what it is as long as > everything is working correctly. It's literally not for you--it's for > your MUA software. The link to a kernel mailing list message that was provided earlier in this discussion said that the choice to use base64 results in the possibility of / characters being included in the message id which causes problems for their archived messages accessible via a web browser. So it seems that there is a reason to care about this. Although one could argue that the mailing list archiving system should accept the responsibility of munging message ids to suit its own needs. I've certainly seen mailing list archives on the web that did munge the message id (but to replace @ characters, I think). cheers, raf > -- > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. Replying to it will result in > undeliverable mail due to spam prevention. Sorry for the inconvenience. >
Re: pretty-print mutt emails
On Wed, Apr 10, 2024 at 07:25:11AM +0200, Matthias Apitz wrote: > El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió: > > > On 04/07/2024 07:42 AM, Matthias Apitz wrote: > > > I do use on FreeBSD muttprint: > > > > > > Name : muttprint Version: 0.73_5 Installed > > > on : Sun Sep 24 11:32:52 2023 CEST Origin : > > > print/muttprint Architecture : FreeBSD:14:amd64 Prefix > > > : /usr/local Categories : print mail Licenses : > > > GPLv2 Maintainer : g...@unixarea.de WWW: > > > http://muttprint.sourceforge.net/ Comment: Utility to > > > print mail for most any mail client > > > > > > Started from ~/.muttrc as: > > > > > > $ grep muttprint .muttrc set print_cmd="muttprint --printer > > > pdf --paper A4 --rem_sig " > > > > > > The result is nice and attached. > > > > > > matthias > > > > > I would like to try muttprint for my installation of neomutt on > > CentOS 7. When I visit the sourceforge page above, the latest > > version for download is 0.72d, not 0.73_5 as you listed above. > > 0.72d was released 2007-01-08... > > The "_5" in "0.73_5" is FreeBSD'ish. i.e. the version of the > change of the port. The history is here: > https://www.freshports.org/print/muttprint/#history. I don't know > why the 0.73 source is not available. I have it in my build > server: > > [guru@jet /usr/ports/distfiles]$ ls -l muttprint-0.73.tar.gz > -rw-r--r-- 1 root wheel 361268 Dec 26 2008 muttprint-0.73.tar.gz > > I could make it available on my Internet host. About any RPM I > don't know much. On my Linux mobilephone, running a Debian I see: > > $ apt search muttprint muttprint/byzantium 0.73-10 all Pretty > printing of mails > > muttprint-manual/byzantium 0.73-10 all Manual for muttprint > > HIH > > matthias > If something is available in debian, debian will ship a '.orig' as well as all the patches they are using. Looks as if sid is now on their 11th revision: https://packages.debian.org/sid/muttprint ĸen -- I used to farm cats, and let me tell you, their eggs don't taste nearly as chocolatey as they look. -- Milton Jones, Mock the Week
Re: How to delete message with purge=no?
On Wed, Apr 10, 2024 at 08:22:03PM +0800, Sadeep Madurange wrote: > Hello, > > When deleting emails (with d), I get a prompt for purging them. I'd like > to silence that prompt with 'no'. And, see the prompt when I change > folder, or better yet, when I quit mutt. > > Is there a way to do this? There are a lot of possibilities for deleting mails and empying the trash, see http://www.mutt.org/doc/manual/ Here mutt does like you want to have. I looked into my .muttrc but found no clue how it works. KR, //meine
Re: pretty-print mutt emails
On 2024-04-10, Matthias Apitz wrote: > El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió: > >> On 04/07/2024 07:42 AM, Matthias Apitz wrote: >> > I do use on FreeBSD muttprint: >> > >> > Name : muttprint >> > Version: 0.73_5 [...] >> > WWW: http://muttprint.sourceforge.net/ >> > Comment: Utility to print mail for most any mail client [...] >> I would like to try muttprint for my installation of neomutt on >> CentOS 7. When I visit the sourceforge page above, the latest >> version for download is 0.72d, not 0.73_5 as you listed above. 0.72d >> was released 2007-01-08... > > The "_5" in "0.73_5" is FreeBSD'ish. i.e. the version of the change of the > port. The history is here: > https://www.freshports.org/print/muttprint/#history. > I don't know why the 0.73 source is not available. I have it in my > build server: It is available on SourceForge (project page) but not on the muttprint (sourceforge-hosted?) website: https://sourceforge.net/projects/muttprint/files/ lists 0.73 as the latest, https://sourceforge.net/projects/muttprint/files/muttprint/muttprint-0.73/ https://sourceforge.net/p/muttprint/code/HEAD/tree/trunk/muttprint/CHANGES > [guru@jet /usr/ports/distfiles]$ ls -l muttprint-0.73.tar.gz > -rw-r--r-- 1 root wheel 361268 Dec 26 2008 muttprint-0.73.tar.gz [...] -- Nuno Silva
Re: Question about message id
Ебрашка wrote: > my mails have Message-ID: . Question, what > should I write in .muttrc to make my outgoing mails have the same beautiful > message-ID as Yandex mail? My first question would be, why do you care what the Message-ID: field contents look like? Virtually no-one will ever look at it. > For example Message-Id: <43265...@example.com> consisting of random > digits and domain name There's a good reason for that; it help to ensure uniqueness, which prevents problems with threading. By limiting itself to only digits, Yandex's IDs are much more likely to collide. If you absolutely must do this, have a look at the `message_id_format` variable. Charles -- --- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ ---
Re: Mutt showing ? in place of space
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth: > On 2024-03-23 11:10:11, Sirius via Mutt-users wrote: > > In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth: > > > When I view the following email in mutt, I see a bunch of question marks > > > where the spaces are. I checked the codepoints and they all seem to be > > > the normal space (0x20) character in the ASCII table. > > > > My initial guess is that this is not a mutt problem but rather a display > > problem related to your environment. What does your LANG and LC variables > > look like and what are your locale settings? If at all possible, run with > > UTF-8. > > Initially, LANG was unset and LC_CTYPE="C". The character encoding was > US-ASCII. I changed these variables (i.e., LANG, LC_CTYPE and locale > settings) to en_US.UTF-8. Then the ? changed to �. So, looks like you > are on to something. I will check this with OpenBSD community as well. For reference, in my Debian Bookworm, I have the following: sirius�~�$�locale LANG=sv_SE.UTF8 LANGUAGE= LC_CTYPE="sv_SE.UTF8" LC_NUMERIC="sv_SE.UTF8" LC_TIME="sv_SE.UTF8" LC_COLLATE="sv_SE.UTF8" LC_MONETARY="sv_SE.UTF8" LC_MESSAGES="sv_SE.UTF8" LC_PAPER="sv_SE.UTF8" LC_NAME="sv_SE.UTF8" LC_ADDRESS="sv_SE.UTF8" LC_TELEPHONE="sv_SE.UTF8" LC_MEASUREMENT="sv_SE.UTF8" LC_IDENTIFICATION="sv_SE.UTF8" LC_ALL= I run this in a WSL on Win11, but have this config replicated across Fedora, RHEL and Debian VMs and physical systems. In my .mutt/muttrc, I have the following set: set ascii_chars=yes set assumed_charset="utf-8:iso-8859-1:us-ascii" set charset="utf-8" set config_charset="utf-8" It may be that you just need to pop in the "set charset="utf-8"" in your mutt config and you are good to go. > In Xdefaults, I have set XTerm*utf-8 setting to true as well. > > > It could also be related to the font used in Xterm, so worth trying > > another font (preferably one that has a decent portion of the UTF-8 > > glyphs). > > Unlikely to be a problem with the font. I'm using DejaVu Sans Mono, > which I used on Linux in the past without any problem. That should be a good font. If you are in the market for some other good fonts, take a look at Monafont. > -- > Sadeep Madurange > PGP: 103BF9E3E750BF7E -- Kind regards, /S
Re: Mutt showing ? in place of space
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth: > Hello, > > When I view the following email in mutt, I see a bunch of question marks > where the spaces are. I checked the codepoints and they all seem to be > the normal space (0x20) character in the ASCII table. My initial guess is that this is not a mutt problem but rather a display problem related to your environment. What does your LANG and LC variables look like and what are your locale settings? If at all possible, run with UTF-8. It could also be related to the font used in Xterm, so worth trying another font (preferably one that has a decent portion of the UTF-8 glyphs). > This happens fairly often. Usually with git patches or emails hat > contain the output of commands like ifconfig that has indented blocks. > > Any ideas? I'm using OpenBSD and Xterm. > > - Forwarded message - > > Index: 75.html > === > RCS file: /cvs/www/75.html,v > retrieving revision 1.10 > diff -u -p -r1.10 75.html > --- 75.html 22 Mar 2024 11:08:09 -?? 1.10 > +++ 75.html 22 Mar 2024 15:22:40 - > @@ -408,6 +408,7 @@ to 7.5. > JDK 8u402, 11.0.22, 17.0.10 and 21.0.2 > KDE Applications 23.08.4 > KDE Frameworks 5.115.0 > +?? KDE Plasma 5.27.10 > Krita 5.2.2 > LLVM/Clang 13.0.0, 16.0.6 and 17.0.6 > LibreOffice 24.2.1.2 > > - End forwarded message - > > -- > Sadeep Madurange > PGP: 103BF9E3E750BF7E -- Kind regards, /S
Re: Cascading directory display + Colourised folders after using "c" to indicate folders with mail newer than x hours
People, I never received a response re the stuff below (so I presume it is not possible) - but the colourised folder idea also would be helpful to me . . Thanks, Phil. On 2022-07-13 23:58, p...@pricom.com.au wrote: People, In my Maildir structure I have subfolders of subfolders eg they look like this: /home/phr/Maildir /home/phr/Maildir/.00 /home/phr/Maildir/.00.0 /home/phr/Maildir/.00.2045_ru /home/phr/Maildir/.00.3dcontenth /home/phr/Maildir/.00.3scale_net /home/phr/Maildir/.00.4mation_co /home/phr/Maildir/.00.ChurchOfPe /home/phr/Maildir/.00.FreeWillsO /home/phr/Maildir/.00.MeTA1_org . . Is there a way to display like structure like this: /home/phr/Maildir +/home/phr/Maildir/.00 where clicking on the '+' can expand the subdirectories? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: p...@pricom.com.au
Re: Re: Profiles and mutt-notmuch
On 2023-10-29 14:17, Michael Kjörling wrote: > On 29 Oct 2023 14:44 +0100, from mutt-users@mutt.org (Jan Eden via > Mutt-users): > > for several years, I have used mutt with msmtp, and issues with sending > > messages were usually returned to mutt and displayed as an error. > > > > Recently, though, mutt displays "Mail sent" even when there is a problem > > (and the mail is not sent). I always used a simple msmtp configuration, > > and could not identify any major changes in the msmtp docs related to > > exit codes. > > What's your $sendmail_wait? Thank you, that caused the problem! I experimented with msmtpq a while ago and set sendmail_wait to -1. When returning the config files to their previous state, I obviously forgot to remove that setting. Thanks again! - Jan signature.asc Description: PGP signature
Re: Profiles and mutt-notmuch
Hi, for several years, I have used mutt with msmtp, and issues with sending messages were usually returned to mutt and displayed as an error. Recently, though, mutt displays "Mail sent" even when there is a problem (and the mail is not sent). I always used a simple msmtp configuration, and could not identify any major changes in the msmtp docs related to exit codes. Has anyone else experienced something similar, and did anything change on mutt's end? .muttrc contains the following: set sendmail = "/opt/homebrew/bin/msmtp -a profile1 --read-envelope-from" Cheers, Jan signature.asc Description: PGP signature
^M line endings
Hi! I'm getting a few mails which use "^M" line endings, which mutt seems to ignore when displaying the body of the email. How can I make mutt properly display the mail. Using Mutt 2.1.4 (2021-12-11) Using these pager settings: set pager=builtin set pager_context = 3 set pager_stop The XMailer header of the "^M"-mail program is X-Mailer: Bp Event 11.0n88 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Setting X-Priority/Priority/Important headers more easiliy?
On Wed, Sep 27, 2023 at 02:36:57PM -0500, Tim Chase
wrote:
> Howdy,
>
> RFC-2156[1] specifies ways to use the headers
>
> Importance: {low, normal, high}
> Priority: {normal, non-urgent, urgent}
> Sensitivity: {Personal, Private, Company-Confidential}
>
> and I've also seen the non-standard
>
> X-Priority: 1 (Highest)
> X-MSMail-Priority: High
>
> (with X-Priority ranging from 1 (Highest) to 5 (lowest)) in the
> wild to convey meta-information about the message.
>
> Does anyone have any suggestions/mappings that might make it easier
> to add/manage add/manage these headers rather than hand-entering
> them with {edit-headers} in the message-compose menu? Preferrably
> picking from a list rather than remembering the exact text/number
> for each header.
>
> Thanks!
>
> -tkc
>
> [1] https://datatracker.ietf.org/doc/html/rfc2156
You can define a macro that uses my_hdr for each such header.
Then each one can be a single keystroke.
cheers,
raf
Re: DKIM fails depending on Content-Transfer-Encoding
On 2023-09-07, raf via Mutt-users wrote: > On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote: > >> Dear Mutt Users >> >> recently I experienced DKIM fails that depend on the >> Content-Transfer-Encoding of messages text part. >> >> Being a german I use to write my messages in german with UTF-8 >> encoding. I prefer plain text. My e-mails are DKIM signed. I have >> checked DKIM to be set up correctly twice. >> >> By default Mutt does 8bit encoding for text/plain. Now I found that >> several (most) of the recipient systems fail to check DKIM. >> >> If I force Mutt to change the encoding from 8bit to 7bit, base64, or >> quoted-printable (using ^E in the compose menu), the DKIM checks >> succeed. >> >> Can I force Mutt to use quoted-printable or base64 by default for >> encoding of plain text? >> >> Does anyone have similar experiences? Is there an explanation for this? >> May there be any interference with the MTA? >> >> Interestingly DKIM checks do not fail if I use non-ASCII characters in >> the subject. Also attachements do not cause DKIM to fail. >> >> Best Regards >> >> T. Finke >> >> -- >> >> T. Finke >> f...@igh.de >> > > Hi, This has come up recently in the Postfix mailing list. > MTAs can convert 8bit messages when sending to another MTA > that doesn't advertise that it can accept 8bit. If the DKIM > signing happens before the conversion, then subsequent DKIM > checks will fail. Work is being done in Postfix to address > this. I don't know about other MTAs. It seems unlikely that > there are any MTAs that can't accept 8bit messages, but perhaps > there are some that are misconfigured and don't advertise the > fact to other MTAs. Has AOL/Yahoo/Verizon/...'s server software been finally fixed from its eternal dance between two different failure modes? (Either replacing non-ascii with ? or messing up the encoding); I think it also misadvertised 8-bit support to MUAs... But maybe that really just affects client connections and does not damage messages received from other servers? -- Nuno Silva
Re: DKIM fails depending on Content-Transfer-Encoding
On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote: > Dear Mutt Users > > recently I experienced DKIM fails that depend on the > Content-Transfer-Encoding of messages text part. > > Being a german I use to write my messages in german with UTF-8 > encoding. I prefer plain text. My e-mails are DKIM signed. I have > checked DKIM to be set up correctly twice. > > By default Mutt does 8bit encoding for text/plain. Now I found that > several (most) of the recipient systems fail to check DKIM. > > If I force Mutt to change the encoding from 8bit to 7bit, base64, or > quoted-printable (using ^E in the compose menu), the DKIM checks > succeed. > > Can I force Mutt to use quoted-printable or base64 by default for > encoding of plain text? > > Does anyone have similar experiences? Is there an explanation for this? > May there be any interference with the MTA? > > Interestingly DKIM checks do not fail if I use non-ASCII characters in > the subject. Also attachements do not cause DKIM to fail. > > Best Regards > > T. Finke > > -- > > T. Finke > f...@igh.de > Hi, This has come up recently in the Postfix mailing list. MTAs can convert 8bit messages when sending to another MTA that doesn't advertise that it can accept 8bit. If the DKIM signing happens before the conversion, then subsequent DKIM checks will fail. Work is being done in Postfix to address this. I don't know about other MTAs. It seems unlikely that there are any MTAs that can't accept 8bit messages, but perhaps there are some that are misconfigured and don't advertise the fact to other MTAs. cheers, raf
Re: DKIM fails depending on Content-Transfer-Encoding
On 2023-09-06 13:33, f...@igh.de wrote: > Dear Mutt Users > > recently I experienced DKIM fails that depend on the > Content-Transfer-Encoding of messages text part. > > Being a german I use to write my messages in german with UTF-8 > encoding. I prefer plain text. My e-mails are DKIM signed. I have > checked DKIM to be set up correctly twice. > > By default Mutt does 8bit encoding for text/plain. Now I found that > several (most) of the recipient systems fail to check DKIM. > > If I force Mutt to change the encoding from 8bit to 7bit, base64, or > quoted-printable (using ^E in the compose menu), the DKIM checks > succeed. > > Can I force Mutt to use quoted-printable or base64 by default for > encoding of plain text? In my experience, mutt chooses the simplest encoding required for each message, and it is usually better not to intervene. > Does anyone have similar experiences? Is there an explanation for this? > May there be any interference with the MTA? At what point do you apply the DKIM signature? If the DKIM signature is calculated for the complete message (as created by mutt), there should be no mismatch/DKIM failure. - Jan signature.asc Description: PGP signature
Re: Re: Avoiding S/MIME
On 2023-09-01 16:15, Todd Zullinger wrote: > Hi, > > Jan Eden wrote: > > my configuration sets a PGP default key: > > > > set pgp_default_key = ... > > > > and outgoing messages are signed accordingly. But every time I reply > > to a message signed using S/MIME, mutt tries to add an S/MIME signature, > > too (which fails, as there is no S/MIME key available via GPGME). > > > > How can I prevent this behavior? > > You may want to check the crypt_auto* and crypt_reply* > variables to see how they are set. My first thought would > be disabling crypt_autosmime, e.g.: > > set crypt_autosmime=no Thanks, Todd, that worked. - Jan signature.asc Description: PGP signature
Avoiding S/MIME
Hi, my configuration sets a PGP default key: set pgp_default_key = ... and outgoing messages are signed accordingly. But every time I reply to a message signed using S/MIME, mutt tries to add an S/MIME signature, too (which fails, as there is no S/MIME key available via GPGME). How can I prevent this behavior? Thanks, Jan signature.asc Description: PGP signature
Re: Why Mail-Followup-To header for a non-list address?
On Sun, Aug 20, 2023 at 06:25:57PM +0800, "Kevin J. McCarthy" wrote: > On Sun, Aug 20, 2023 at 03:53:09PM +1000, raf via Mutt-users wrote: > > I don't have any "lists" commands. I do have a "subscribe" command > > which refers to mailing lists by their aliases. One of the aliases > > is "debian" and the email address in question does contain "+debian" > > but that shouldn't matter. > > Hi raf, > > 'lists' and 'subscribe' specify regular expressions to match against email > addresses, not aliases. That's most certainly why you are seeing this > behavior. Try tightening the regular expression in the 'subscribe' > command(s). > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA Hi Kevin, Thanks! I'm surprised it's taken this long for a problem to get noticed! :-) cheers, raf
Why Mail-Followup-To header for a non-list address?
Hi, Someone recently emailed me. Technically it was a reply to an old email of mine. Since then, a few emails have gone back and forth between us. All of my outgoing mails to this one address have had a Mail-Followup-To header added. I have no idea why. The address isn't mentioned in any "subscribe" or "lists" commands. I don't have any "lists" commands. I do have a "subscribe" command which refers to mailing lists by their aliases. One of the aliases is "debian" and the email address in question does contain "+debian" but that shouldn't matter. I've fixed it with a send-hook that does "set followup_to = no" for that address, but I don't understand why I needed to. Can anyone think what I might have done to cause this? Linux ook 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64 GNU/Linux mutt-2.2.9-1+b1 cheers, raf
Re: Re: [OT] Terminal redraw issues / isync launchctl job in macOS 13.5
On 2023-08-14 14:16, Will Yardley wrote: > On Mon, Aug 07, 2023 at 03:47:53PM +0200, Jan Eden via Mutt-users wrote: > > I recently upgraded to macOS 13.5, and for the first time, there are > > redraw issues in the Terminal with mutt (2.2.10, installed via > > Homebrew). Also, the launchctl job for isync/mbsync (1.4.4, also > > installed via Homebrew) fails since the upgrade. > > I am observing this as well (at least with 2.2.7) -- both before and > after recompiling. This can be fixed by using a newer ncurses version, as Dennis suggested on this list. - Jan signature.asc Description: PGP signature
Re: Re: Re: Re: [OT] Terminal redraw issues / isync launchctl job in macOS 13.5
On 2023-08-10 09:37, Dennis Preiser wrote:
> On Thu, Aug 10, 2023 at 08:14:23AM +0200, Jan Eden via Mutt-users wrote:
> > On 2023-08-07 19:18, Dennis Preiser wrote:
> >> Not surprising. You must somehow tell homebrew that for mutt
> >> --with-curses=PATH/TO/HOMEBREW/ROOT is necessary.
> >
> > Tried that, and it worked (up to a point). Compiling mutt with the
> > following options
> >
> > ./configure --enable-hcache --with-curses=/opt/homebrew/opt/ncurses
> > --with-tokyocabinet=/opt/homebrew/opt/tokyo-cabinet
> >
> > eliminates the redraw issue (using the current ncurses version), but
> > when I try to add gpgme –
>
> It would be worth a try to change the mutt formula locally.
>
> | brew edit mutt
>
> Then add
>
> depends_on "ncurses"
>
> where the depends are and add
>
> "--with-curses=#{Formula["ncurses"].opt_prefix}"
>
> to the configure options. Save and reinstall mutt
>
> brew reinstall mutt
>
> This should install mutt with the edited, locally cached formula. Since
> I don't use homebrew myself I don't know if this is lost in a brew
> update.
Thank you! I had to create a copy of
/opt/homebrew/opt/mutt/.brew/mutt.rb because my changes to the original
file were overwritten. But then I could execute
brew install --build-from-source mutt.rb
to get a working mutt binary. Thanks again, your help is much
appreciated.
- Jan
signature.asc
Description: PGP signature
Re: Re: Re: [OT] Terminal redraw issues / isync launchctl job in macOS 13.5
On 2023-08-07 19:18, Dennis Preiser wrote: > On Mon, Aug 07, 2023 at 06:16:39PM +0200, Jan Eden via Mutt-users wrote: > > On 2023-08-07 16:29, Dennis Preiser wrote: > >> Maybe it is sufficient to install a newer ncurses with homebrew. > > > > Even with ncurses 6.4 installed, homebrew delivers a mutt version linked > > against ncurses 5.7. > > Not surprising. You must somehow tell homebrew that for mutt > --with-curses=PATH/TO/HOMEBREW/ROOT is necessary. Tried that, and it worked (up to a point). Compiling mutt with the following options ./configure --enable-hcache --with-curses=/opt/homebrew/opt/ncurses --with-tokyocabinet=/opt/homebrew/opt/tokyo-cabinet eliminates the redraw issue (using the current ncurses version), but when I try to add gpgme – ./configure --enable-gpgme --enable-hcache --with-curses=/opt/homebrew/opt/ncurses --with-tokyocabinet=/opt/homebrew/opt/tokyo-cabinet --with-gpgme-prefix=/opt/homebrew/opt/gpgme --with-libgpg-error-prefix=/opt/homebrew/opt/libgpg-error – the compilation results in a fatal error: In file included from crypt-gpgme.c:47: /opt/homebrew/Cellar/gpgme/1.21.0/include/gpgme.h:30:10: fatal error: 'gpg-error.h' file not found #include ^ 1 error generated. So I would need to compile gpgme and libgpg-error myself (and probably other components). I use homebrew to avoid this stuff, and will have to live with the redraw bug for now.Nevertheless: Thanks for your suggestion! - Jan signature.asc Description: PGP signature
Re: Re: [OT] Terminal redraw issues / isync launchctl job in macOS 13.5
On 2023-08-07 15:59, Claus Assmann wrote: > On Mon, Aug 07, 2023, Jan Eden via Mutt-users wrote: > > I recently upgraded to macOS 13.5, and for the first time, there are > > redraw issues in the Terminal with mutt (2.2.10, installed via > > "Terminal" broke screen handling for me in MacOS 13.5 with various > programs - even vi. Maybe file a bug with Apple? > > Others suggested I should switch to iTerm2 which doesn't seem > to have the problem. Thanks for the suggestion – I will try iTerm2 then. - Jan signature.asc Description: PGP signature
Re: Re: [OT] Terminal redraw issues / isync launchctl job in macOS 13.5
On 2023-08-07 16:29, Dennis Preiser wrote: > On Mon, Aug 07, 2023 at 03:47:53PM +0200, Jan Eden via Mutt-users wrote: > > I recently upgraded to macOS 13.5, and for the first time, there are > > redraw issues in the Terminal with mutt (2.2.10, installed via > > Homebrew). Also, the launchctl job for isync/mbsync (1.4.4, also > > installed via Homebrew) fails since the upgrade. > > > > Has anyone else experienced similar issues with macOS 13.5? > > With homebrew, mutt is linked against the ncurses supplied with macOS. > This version is relatively old. > > | % /usr/bin/ncurses5.4-config --version --abi-version > | 5.7.20081102 > | 5.4 > > I don't use homebrew but I use mutt with a self-installed ncursesw and > have no issues. > > | % mutt -v | grep 'Mutt 2\|ncurses' > | Mutt 2.2.10 (2023-03-25) > | ncurses: ncurses 6.4.20230603 (compiled with 6.4) > > Maybe it is sufficient to install a newer ncurses with homebrew. Even with ncurses 6.4 installed, homebrew delivers a mutt version linked against ncurses 5.7. - Jan signature.asc Description: PGP signature
[OT] Terminal redraw issues / isync launchctl job in macOS 13.5
Hi, I recently upgraded to macOS 13.5, and for the first time, there are redraw issues in the Terminal with mutt (2.2.10, installed via Homebrew). Also, the launchctl job for isync/mbsync (1.4.4, also installed via Homebrew) fails since the upgrade. Has anyone else experienced similar issues with macOS 13.5? - Jan signature.asc Description: PGP signature
Re: Scheduling deferred sending of emails
Hello Sébastian, I remember replying to a similar post on Unix Stackexchange in the past: https://unix.stackexchange.com/a/554369/85046 Best, JJ On 2023-07-29 12:07, Sébastien Hinderer wrote: Dear all, I would like to be able to respond to emails quickly to have it done but defer the actual sending of the response to slow down conversations. Ideally at the moment of sending I would specify a date and time after which I am fine with the mail being sent. For example, I respond to an email on Friday afternoon but can express that I want it to be actually sent anytime after next Monday 9pm. That could be by adding a special header to the email or by responding to questions at send time, I don't mind and it's not really the usesr interface I'd like to discuss here. What I rather would like to discuss is rather whether and how this could be implemented in the MUA/MTA framework mutt belongs to. I believe that more integrated solutions like Thunderbird do have such scheduled deferred sending features, but I have no idea how this can be achieved in presence of both an MUA and an MTA because the feature seems to be at the interface between the two: there needs to be a way for the MUA to tell the MTA about the deferred sending and of course the MTA does not only need to undestand it, it also needs to actually implement it. I had a superficial look to exim4 which I use as an MTA but didn't find anything related, but perhaps my search has been too shallow. I also considered adding another MTA between mutt and Exim4 which would keep the deferred mails until the scheduled date and pass them to Exim4 only at that moment but it felt a bit a pity to have to use one dedicated software component just for that as, I assume, it would widely resemble a traditional MTA, having a lot in common with it. Any idea will be more than welcome. Best wishes, Seb. signature.asc Description: PGP signature
Re: INBOX message count in sidebar
On 24-07-2023 21:41, Will Yardley wrote: > On Mon, Jul 24, 2023 at 10:18:37PM +0200, Mikhail Nidze via Mutt-users wrote: > > The problem was in *folder* and *spoolfile* variables incorrectly set. > > The correct ones are: > > > > set folder = "imaps://imap.mail.me.com:993" > > set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX" > > BTW, Kevin's response may have hinted at this a bit, but you can use + > or = before so that you don't have to repeat the imaps:// part, e.g., > > set folder="imaps://imap.example.com/" > set spoolfile=+INBOX > set postponed=+Drafts Thanks, I tried that too. In this case $spoolfile will be expanded to "imaps://imap.mail.me.com:993/INBOX", i.e. without *my_account* part and that doesn't work. In fact, fetching mail will still work as it used to, but sidebar will show "INDEX 0". The only solution I've found so far is to set $folder without *my_account* part and $spoolfile with one. -- Best regards, Mikhail.
Re: INBOX message count in sidebar
On 25-07-2023 10:53, Kevin J. McCarthy wrote: > I see you solved your problem, but also note the mailboxes command doesn't > use an assignment syntax. The '=' will be interpreted as a mailbox shortcut > for $folder. Just use: > > mailboxes -label "INBOX" "imaps://my_acco...@imap.mail.me.com/INBOX" Oh, my mistake! Thank you, Kevin! Fixed that. Haven't noticed it since the mail still worked. Can it be because $folder is set *after* the mailboxes command in my config (my guess)? -- Best regards, Mikhail.
Re: INBOX message count in sidebar
Update: The problem was in *folder* and *spoolfile* variables incorrectly set. The correct ones are: set folder = "imaps://imap.mail.me.com:993" set spoolfile = "imaps://my_acco...@imap.mail.me.com/INBOX" Now INBOX shows message count correctly in sidebar. Problem solved. -- Best regards, Mikhail.
INBOX message count in sidebar
Hi all. My mutt is configured to fetch mail from single IMAP account with several folders set with *mailboxes ...*. All folders are shown in sidebar: sidebar_format = '%B%?F? [%F]?%* %?N?%N/?%S' The problem is INBOX folder doesn't show message count in sidebar "%S" column after program start, i.e. when I start mutt INBOX always shows "INBOX 0" (of course, INBOX is not empty and all messages are shown in index/main window). Other folders show correct number of messages in sidebar. If I re-enter INBOX (press y, then select INBOX) the message count for INBOX appears correctly. What can be a problem here? Can this be solved? I use Mutt 2.2.10. My mailboxes are set like this: mailboxes = -label "INBOX""imaps://my_acco...@imap.mail.me.com/INBOX" mailboxes = -label "SENT" "imaps://my_acco...@imap.mail.me.com/Sent Messages" mailboxes = -label "DRAFTS" "imaps://my_acco...@imap.mail.me.com/Drafts" mailboxes = -label "JUNK" "imaps://my_acco...@imap.mail.me.com/Junk" mailboxes = -label "ARCHIVE" "imaps://my_acco...@imap.mail.me.com/Archive" mailboxes = -label "TRASH""imaps://my_acco...@imap.mail.me.com/Deleted Messages" Variables are: set folder = "imaps://my_acco...@imap.mail.me.com:993" set spoolfile = "+INBOX" set postponed = "+Drafts" set record = "+Sent Messages" set trash = "+Deleted Messages" -- Best regards, Mikhail.
Behavior After Sending an Email Not Consistent
Hello. I am scratching my head. Please help. After replying to an email, Mutt does one of three things: ⋅ It returns to the pager, showing the email to which the reply was made. ⋅ It returns to the index, selecting the email to which the reply was made. ⋅ It returns to the index, selecting the second-oldest unread email. This happens frequently and is the most annoying of the three. Please note that I am able to reproduce the inconsistency even after running “unhook *”. However, while I am ABLE to reproduce the inconsistency with the following configuration... set sort = "threads" set sort_aux = "last-date-received" ... I am UNABLE to reproduce the inconsistency after changing “sort” to “reverse-threads”. Is there a way to debug this? Mutt 2.2.9 (2022-11-12) Linux 6.3.8-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 15 02:15:40 UTC 2023 x86_64 GNU/Linux Thank you.
Re: Is there any way to view text/html inline *only if* we think text/plain is not right?
On Thu, May 18, 2023 at 07:53:50PM -0400, José María Mateos wrote: > Hi everybody, > > Lately I've been receiving mail in which the text/plain part and the > text/html part are at odds. This is typically caused by generator software > that ignores text/plain, or uses some old version, etc. > > Today I changed my settings to view text/html first via w3m, but I'm not > entirely comfortable with this. > > What I'd really like to do is: > > 1. Display text/plain by default. > 2. If I'm not convinced by that version, press some key and then text/html > is displayed inline (using w3m, lynx, links, or whatever in the ~/.mailcap > file). > 3. If that's still not good enough, use a macro I already have to run > mutt_bgrun and display that mail using Firefox directly. > > I don't know if point 2 is a possibility, to be honest. Does anyone know if > this can be done? > > Thanks a lot, > > -- > José María (Chema) Mateos || https://rinzewind.org I think you can setup two ways of handling an attachment, one for "viewing" and one for "printing". You can make the "view" command treat it as text/plain and make the "print" command treat it as text/html, but I don't remember the details on how to do this. Does anyone else remember? cheers, raf
Re: unset email address for reply
Quoting steve (dl...@bluewin.ch): > This only happens for particular folders, not all. So this probably is a folder-hook somewhere. You'd start by grep'ing for 'hook' or 'my_hdr From' in your configs. I have a set of folder-hooks, but the first one is always: | folder-hook . unmy_hdr From: And following that are specific folder hooks e.g.: | folder-hook .lists.mutt-users my_hdr From: Sander Smeenk The "." matches any folder i think, so it always unsets the header, unless a specific match is found and it sets the header again. I believe this is how it should work. ;) HTH, -Sndr. -- | [ $[$RANDOM % 6] = 0 ] && rm -rf ~ || echo "You win!" | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
Re: How do I see the text/html version of an email?
Jude DaShiell writes: > If the mail is going to be illegible thanks to html, maybe it's > appropriate to automate an illegible email rejected filter that adds a > short message and bounces it back to the sender. If enough of these > senders keep getting rejected messages maybe they'll clean up their acts > but count on any start toward this taking at least 10 years from the time > rejected email starts hitting their inboxes. This is pointless when you're dealing with automated emails generated by some bought-in software/portal. I *think* zoom support emails were like that, too, but I might not remember it correctly, it was years ago.
Re: How do I see the text/html version of an email?
José María Mateos writes: > On Sun, Apr 23, 2023 at 02:56:35PM +, Alan Mackenzie wrote: > >Some considerate organisation has been sending me MIME mails with > >content in a text/html section and a wholly blank text/plain version. > >What I see in mutt is the blank text/plain. Who on Earth thought a > >blank text/plain section was somehow a good idea? > > I've seen a worse version of this: the text version and the html version > are completely different. I can better that, regularly spotted in the corporate environment: the text/plain part is also in html.
Re: Re: Forward with attachments
On 2023-04-22 14:58, Akkana Peck wrote: > > On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote: > > > Is there a configuration that will make mutt's forwarding behavior more > > > like other clients I have used: body is quoted in the message, and > > > attachments are automatically attached? > > Kevin J. McCarthy writes: > > $forward_attachments, added in Mutt 1.12.0, will prompt to attach non > > text-decodable attachments. However, Mutt considers autoview types to be > > text decodable. $honor_disposition can override this. > > Thanks: I'd also been trying to find a way to forward with attachments, and > $forward_attachments helps as long as there's no HTML part. > > But it still doesn't forward html parts, and setting honor_disposition > doesn't change that. Is there a way to forward the same MIME structure as the > original message, including html parts? Like what bounce does, except that it > makes me the sender and gives me a chance to add a comment? Isn't this what the mime_forward variable is for? - Jan signature.asc Description: PGP signature
Re: [ext] Re: top and bottom margin
* Claus Assmann : > On Wed, Mar 29, 2023, Mark E. Mallett wrote: > > > to add and implement a couple of muttrc variables to set a top and > > bottom margin, since I like to break up any wall of solid text. As I > > "Back then" I had my own patches to do that. Chiming in -- the old farts are back (me included) :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: How do I make mutt send my mails to a remote MSA?
On Mon, Jan 30, 2023 at 04:22:43AM +0200, e wrote: > On Mon, Jan 30, 2023 at 04:10:45AM +0200, e wrote: > > > > Is it possible to use mutt without having an MTA on your own machine? I > > have read that some MUA's use "Message submission" (rfc 2476) > > to send the mail to an MSA that can be on the same network for example. How > > can I do this with mutt? > > Is $smtp_url the situation where a MUA is using "Message submission" and it > sends to an MSA? I expect so. The manpage says the syntax is: smtp[s]://[user[:pass]@]host[:port] If the port isn't provided, it presumably uses port 25, but in that case, the user and password probably aren't helpful (authentication is often not offered on port 25). Your MUA host would have to be considered as local by the MTA server. That might not be possible. If the port is supplied as 465 or 587, it presumably knows the difference (i.e, TLS or STARTTLS, respectively), and the user and password are necessary. Actually, you probably need "smtps:" for port 465 and "smtp:" for port 587. mutt might not handle that for you. So the following would be best: smtps:user:pass@server:465 smtp:user:pass@server:587 These last two might work, but only if the MTA server offers authentication on port 25, or if it trusts your MUA host, respectively. smtp:user:pass@server smtp:server Also note that, when using "smtp:" rather than "smtps:", mutt still encrypts the traffic by default, because $ssl_starttls is yes by default. But you might want to set ssl_force_tls=yes as well. cheers, raf
Profiles and mutt-notmuch
Hi, I configured notmuch for my mail stores, and use mutt-notmuch according to the man page[1]: macro index "unset wait_key~/bin/mutt-notmuch --prompt search~/.cache/mutt_results" mutt is started with the -F parameter, and each parameter (work, personal etc) refers to a different mail store. Ideally, I would like to pass different values for notmuch's --config parameter to mutt-notmuch within the respective mutt configuration file, but this is obviously not possible. Has anyone configured mutt (with mutt-notmuch) such that different notmuch profiles are used depending on the mutt profile? - Jan [1] https://upsilon.cc/~zack/blog/posts/2011/01/how_to_use_Notmuch_with_Mutt/mutt-notmuch.1.html signature.asc Description: PGP signature
Re: multiple IMAP accounts on one server?
On Sun, Jan 15, 2023 at 08:58:19PM +0100, Matěj Cepl wrote:
> Hi,
>
> I am looking for the terminal-based MUA which would be able to
> work with my email needs. However, for various reasons I really
> need all my emails stay on multiple IMAP accounts (no local
> emails if possible). I have started with mutt as it is the
> client I know best, but I am not married to it, if you know
> about anything better (Alpine?, notmuch?, anything else) which
> could help me, then I am all ears.
Have a look at neomutt. It's based on mutt, and might or might
not be different in relation to account hooks.
> account-hook .*localhost 'set imap_user=matej imap_pass=secret1 \
> from="Matěj Cepl "
> folder=imap://localhost.localdomain \
> trash=+Trash postponed=+Drafts'
> # account-hook mcepl 'set imap_user=mc...@cepl.eu imap_pass="secret2" \
> # from="Matěj Cepl " \
> # folder=imaps://redcrew.org trash=+Trash postponed=+Drafts'
> account-hook .*redcrew.org 'set imap_user="ma...@ceplovi.cz" \
> imap_pass= "secret3" \
> from="Matěj Cepl " \
> folder=imaps://redcrew.org trash=+Trash postponed=+Drafts'
> account-hook .*suse.de 'set imap_user=mcepl@Thunderbird \
> imap_pass= "secret4" \
> postponed=+INBOX/Drafts from="Matěj Cepl " \
> trash=+INBOX/Trash'
>
> The problem is obviously mc...@cepl.eu account.
>
> * Is it possible to have two account hooks directed against one
> IMAP server?
Kind of. I found this:
[mutt] Multiple email accounts using hooks
https://nixtricks.wordpress.com/2010/05/20/mutt-multiple-email-accounts-using-hooks/
It has an initial account-hook matching . that unsets things,
followed by other account-hooks that sets them depending on
the account.
So, multiple account-hook directives can match the same account.
It just depends on the regular expressions used. But that might
not be useful to you. I'm not sure why you want different
account-hooks for the same account.
If you want two different sets of parameters for the same account
(does that even make sense?), then you might need to put them in
different rc files, and perhaps create key bindings to load the one
you want when you want to change.
> * What EXACTLY are possible values of the first parameter of
> account-hook. Does it have to be domain name of the server, or
> could it be some random string (as shown here in the commented
> out account-hook)?
Good question. It's not clear from just the account-hook entry in
muttrc(5). From the webpage mentioned above, it looks like the
regexp needs to match the imap URI
(e.g., 'imaps://us...@imap.gmail.com/').
> * Is there some patch somewhere, which would support some more
> grown-up version of the accounts settings? I would like to have
> something like
>
> account work { \
> imap_server = imap.suse.de \
> imap_user = mcepl@Thunderbird \
> imap_pass = secret4 \
> ... { any other mutt settings }
> }
>
> account floss { \
> imap_server = redcrew.org \
> imap_user = mc...@cepl.eu \
> imap_pass = secret2 \
> ... { any other mutt settings }
> }
>
> and then I would run
>
> $ mutt -C work
>
> (C as aCcount)
>
> and when inside of mutt I could refer to the other account with
> something like
>
> #floss/INBOX/somewhere
>
> Anybody heard about something like this?
No, but the same thing can be achieved with alternate muttrc files
and the -F option. When you run "mutt -F work" or "mutt -F floss",
the work and floss rc files can contain their specific imap settings,
and then source a common rc file with everything else.
For saving to the other account, macros would help.
If you really like your config syntax above, you could probably
write a little tool that "compiled" it into muttrc syntax.
> Best,
> Matěj
cheers,
raf
Re: Search patterns for multiples address in to or cc
On Sun, Dec 18, 2022 at 09:22:33PM -0300, Marcelo Laia wrote: > I know and I use the ~C, ~b and ~B pattern for a specific search. > > How ever, I would like to search multiples address in to or cc header. Like > this: > > to: someo...@domain1.edu.au, someo...@domain1.edu.au, ... > cc: someo...@domain2.edu.au, someo...@domain10.edu.au, ... > > In fact, I would like to search messages that there are more than one > address in to or cc header. > > This is more a regex that mutt, I think. > > Have you a time to helpe me? > > Thank you so much! > > -- > Marcelo Perhaps you just need '~C @.+,.+@'. That should match two addresses with a comma between them. But I just tried it and it doesn't work. :-( Perhaps ~C matches individual recipients rather than the complete To: and Cc: headers. Replacing ~C with ~h works but it might match other headers. This seems to work: ~h ^(To|Cc):.*@.+,.+@ Of course comments that contain "@" and "," will match as well, but they should be rare. cheers, raf
PGP signed messages and MS Outlook
Hi, a couple of days ago, people using MS Outlook started complaing that my messages looked "strange". I asked for an example and received this: > > Subject: Re: Finanzierung > > > > MIME-Version: 1.0 > > Content-Type: multipart/signed; micalg=pgp-sha512; > > protocol="application/pgp-signature"; boundary="Zd5+bFLIq/fPSfy5" > > > > --Zd5+bFLIq/fPSfy5 > > Content-Type: text/plain; charset=utf-8 > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > > > Lieber x, > > > > vielen Dank. Wenn wir die Parallelit=C3=A4t ... The headers below the Subject header are visible to the recipient, and the quoted-printable content is not unquoted by the client. The message in question is PGP signed and properly displayed in mutt (of course) and Apple Mail. The source of the message (as received via MS Exchange) looks like this: > Subject: Re: Finanzierung > Message-ID: > References: > > Content-Type: multipart/signed; micalg=pgp-sha512; > protocol="application/pgp-signature"; boundary="Zd5+bFLIq/fPSfy5" > Content-Disposition: inline > In-Reply-To: > Return-Path: my.addr...@hs-duesseldorf.de > X-MS-Exchange-Organization-Network-Message-Id: > eededcf1-f439-486e-1257-08dad6c4c55a > X-MS-Exchange-Organization-AuthSource: zvexch6.IT.lan > X-MS-Exchange-Organization-AuthAs: Internal > X-MS-Exchange-Organization-AuthMechanism: 07 > X-Originating-IP: [10.5.7.121] > X-ClientProxiedBy: zvexch6.IT.lan (10.5.7.76) To zvexch6.IT.lan (10.5.7.76) > X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0 > X-MS-Exchange-Organization-Recipient-P2-Type: Bcc > X-MS-Exchange-Transport-EndToEndLatency: 00:00:00.3281613 > X-MS-Exchange-Processed-By-BccFoldering: 15.01.2507.016 > MIME-Version: 1.0 > X-TUID: pVjn50NSefgW > > --Zd5+bFLIq/fPSfy5 > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Lieber , > > vielen Dank. Wenn wir die Parallelit=C3=A4t ... The issue only occurs with signed messages – sending the very same (plain text) message without the signature works fine for Outlook-using recipients. I have signed my messages for several months now, without any negative feedback – is anyone aware of recent changes in Outlook which might have caused this? - Jan signature.asc Description: PGP signature
Re: don't fetch attachments from imap by default
> Is it possible to configure mutt to not fetch the whole > message, but only the text part, so that opening multi-megabyte messages > gets faster and using less bandwidth ? I also wonder if Mutt can partially fetch message when opening pager view, and stop at "Content-Disposition: attachment". Here I found related discussion in 2009: https://www.mail-archive.com/mutt-users@mutt.org/msg38194.html -- 謝晉凡 Hsieh Chin Fan | https://topo.tw/about signature.asc Description: PGP signature
Re: Understanding message deletion model
> Are "purging" and "deleting" not the same thing? True, based on http://www.mutt.org/doc/manual/#index-map: delete the current entry, bypassing the trash folder > I already checked my trash folder, and it's not there. Based on http://www.mutt.org/doc/manual/#trash: If set, this variable specifies the path of the trash folder where the mails marked for deletion will be moved, instead of being irremediably purged. Did you realy set $trash ? Use the following command to take a look: :set ?trash -- 謝晉凡 Hsieh Chin Fan | https://topo.tw/about signature.asc Description: PGP signature
Re: Understanding message deletion model
On Thu, Nov 10, 2022 at 08:47:44PM -0500, Jason Franklin wrote: > Now, if I re-open mutt, the message is gone... completely. I'm confused > as to why the message was removed even though I typed 'n' at the prompt > for whether or not to proceed with the purge. > > Where did this message go? I already checked my trash folder, and it's > not there. Unfortunately, I've been re-writing my configs, so the trash > folder is not named yet. Did you read the message? Maybe it is moved to $mbox. -- 謝晉凡 Hsieh Chin Fan | https://topo.tw/about signature.asc Description: PGP signature
Re: Apple displays flowed text
> > And the question is? > > I guess Kurt's message should have referenced another of Kurt's > messages, . I still > have that older message flagged, too. :-) my apologies. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Apple displays flowed text
* Kurt Hackenberg : > 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. It also rotates when you turn the phone > sideways. > > The Macintosh mail reader also displays flowed text correctly, and rewraps > on the fly when you change the size of the window. And the question is? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: in search of OAuth2 tokens for Microsoft Office 365
I too have a university email account that uses Office 365 (Microsoft Exchange) with OAuth2. Nor do they allow any client but Outlook. I asked IT to allow app passwords, which would allow both my existing mutt and fetchmail+procmail clients access to the email, https://support.microsoft.com/en-us/account-billing/using-app-passwords-with-apps-that-don-t-support-two-step-verification-5896ed9b-4263-e681-128a-a6f2979a7944 but they refused. My solution: Since I'm a long-time Mac user, I configured my university account to send copies of all my email to my Apple iCloud mail, which does support app passwords. https://support.apple.com/en-us/HT202304 https://forums.freebsd.org/threads/mutt-with-icloud-mail.44264/ It works well. I had a bit of work to extract mail messages that Microsoft Exchange rejects with error status codes, e.g., SPF validation error, to many hops, sender's DMARC policy. I wrote a short Perl script to extract and restore the attachment containing the original message. It's processed thousands of rejected messages with no problems. As an aside, check out the book https://www.amazon.com/Hacking-Multifactor-Authentication-Roger-Grimes/dp/1119650798 Most 2FA isn't nearly as secure as many think! Jon On Tue, Oct 25, 2022 at 06:13:42PM -0500, Greg Marks wrote: >Dear Mutt Developers, > >This is not exactly a question about Mutt--more about OAuth2 >authentication with Microsoft Office 365--but I wonder if anyone >can advise. > >I've been trying to configure Mutt for continued access to my university >e-mail account, which uses the IMAP/SMTP server outlook.office365.com. >I have successfully configured Mutt for my G-Mail account using one >of the official gitlab.com Python scripts to generate OAuth2 tokens. >But when I tried to do the same for my university e-mail account, I >found that I lacked permissions to create an "app registration" after >logging in to my account through a Web browser. When I created an "app >registration" by setting up a private Outlook account, the credentials >were not accepted. > >I was able to get Thunderbird to access my university e-mail account with >OAuth2 authentication, and I had some hopes that as a workaround I could >paste the credentials generated by Thunderbird into the Mutt script. >Unfortunately, a grep search through the ~/.thunderbird directory >for "client_id," "client_secret," and "redirect_uri" yielded nothing. >(I presume Thunderbird is storing the relevant credentials in encrypted >form, making them appropriately hard to access.) This might not work >anyway; it seems possible that the Office 365 only recognizes Thunderbird >as an authorized "application." My recollection is that Thunderbird >initially created OAuth2 tokens with a call to a Web browser to log >in to my e-mail account and grant access; since then, any necessary >refreshed tokens are apparently generated automatically. > >Having now used Thunderbird in lieu of Mutt for this account over the >past couple weeks, I am reminded of the considerable superiority of Mutt, >because of the security of text-only access, because when composing >e-mails with Mutt I can use countless vi macros that I've created over >the years, and because I can easily move IMAP e-mail into local mbox >files on my computer. > >I raised this issue with my university IT department (see below) and >received a singularly unhelpful response (see below). My impression is >that I need to make a very clear and specific request for appropriate >permissions to create OAuth2 tokens. Is the least intrusive way to >proceed to request that my Azure account associated with my university >e-mail be granted permission in the Azure Active Directory in the Azure >AD role of "Application developer"? > >Any other ideas or suggestions would be most welcome. > >Sincerely, >Greg Marks > >- > >My message to university IT department: > > I have been using the e-mail client Mutt to access my > SLU e-mail account, and this stopped working on Oct. 12; > apparently, the office365 accounts that SLU uses now require > OAuth2 authentication. I am trying to configure Mutt to > authenticate using OAuth2 following the instructions here: > > > https://gitlab.com/muttmua/mutt/-/blob/master/contrib/mutt_oauth2.py.README > > I followed their instructions: "End users who aren't able to > get to the app registration screen within portal.azure.com for > their work/school account can temporarily use an incognito > browser window to create a free outlook.com account and use > that to create the app registration." At the stage when I > ran the command > > ./
Re: [ext] Re: Display info about S/MIME signature
* ckeader via Mutt-users : > gpgsm --list-keys ralf.hildebra...@charite.de > > would give you all information about the key, including ID (which is the > last part of the fingerprint), serial etc. Yeah, that's awesome. Exactly what I need! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Display info about S/MIME signature
> certificate b43f1e2c.0 (foo) for firstname.lastn...@charite.de added. > > But what *IS* "b43f1e2c"? Is it a serial number, a part of the fingerprint? It looks like an openssl hash, the type c_rehash generates. Like, what you may find under /etc/ssl/certs. > > Also check the config options `crypt_verify_sig`, and > > `smime_verify_command`, `smime_verify_opaque_command` > > I'll have a look at those. > > > When receiving a smime signed mail, mutt tells me if the signature is > > valid or not. > > Well yes, but in some cases (please don't ask) my moron users have > more than one valid certifcate in use and I'd like to know which one > that is (because they don't know). I do not seem to have this problem. Maybe using S/MIME support via gpgme makes this all a bit easier to handle? gpgsm --list-keys ralf.hildebra...@charite.de would give you all information about the key, including ID (which is the last part of the fingerprint), serial etc.
Re: [ext] Re: Display info about S/MIME signature
* Bastian : > Try ^K, which is the default keybind for `extract-keys`. > This command extracts the public key and adds is to your keyring > (smime_keys). Yes, but this only displays precious little info. Enter label: Found 1 certificate chains Processing chain: subject=C = DE, ST = Berlin, L = Berlin, O = Charite- Universitaetsmedizin Berlin, SN = Lastname, GN = Firstname, CN = Firstname Lastname Certificate: /home/hildeb-adm/.smime/certificates/6ab64010.0 already installed. ==> about to verify certificate of b43f1e2c.0 /home/hildeb-adm/.smime/certificates/b43f1e2c.0: OK ==> checking purpose flags for b43f1e2c.0 S/MIME signing : Yes S/MIME encryption : Yes certificate b43f1e2c.0 (foo) for firstname.lastn...@charite.de added. But what *IS* "b43f1e2c"? Is it a serial number, a part of the fingerprint? > Also check the config options `crypt_verify_sig`, and > `smime_verify_command`, `smime_verify_opaque_command` I'll have a look at those. > When receiving a smime signed mail, mutt tells me if the signature is > valid or not. Well yes, but in some cases (please don't ask) my moron users have more than one valid certifcate in use and I'd like to know which one that is (because they don't know). -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Display info about S/MIME signature
Hi! when receiving an S/MIME signed mail, how can I extract information about the certificate / public key that was sent along with the signature? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Re: Re: Viewing HTML message with Firefox
On 2022-10-10 08:42, José María Mateos wrote: > On Mon, Oct 10, 2022 at 12:27:52PM +0200, Jan Eden via Mutt-users wrote: > > The problem was related to the target dir (/tmp/mutt_attach). Although > > it was accessible by the current user, Firefox was not able to display > > files at file:///tmp/mutt_attach/file.html – while Epiphany was. > > > > Whatever the reason, I changed the script to store HTML files in > > /home/jan/mutt_attach, and Firefox successfully opens > > file:///home/jan/mutt_attach/file.html. > > What version of Firefox are you using? I started seeing exactly the same > problem when I upgraded my Ubuntu installation to 22.04, where Firefox is > handled by snap, and the filepaths it can access seems to be somewhat > restricted. I ended up using a solution similar to yours: placing the > temporary file in a folder within my user folder. Firefox 105.0.3 on Ubuntu 22.04. It seems the switch to snap has many disadvantages. - Jan signature.asc Description: PGP signature
Re: Re: Viewing HTML message with Firefox
On 2022-10-10 08:58, Cameron Simpson wrote: > On 09Oct2022 09:35, Jan Eden via Mutt-users wrote: > > Yes, I did use Chris Green's helper script, and it does work with > > Epiphany, but not with Firefox. > > Maybe it would prefer a "file:///path/to/file.html" URL? > > Try some things by hand with the "open" command, see what works. You're > aware that "open" (MacOS command) accepts a "-a appname" argument to select > which application gets asked to open the target? You can do comparisons that > way, or force a preference. [...] Um, your error log suggests you're on > Linux. IIRC its "open" command is rather different. Anyway, experiment by > hand rather than indirectly through the mailcap. The problem was related to the target dir (/tmp/mutt_attach). Although it was accessible by the current user, Firefox was not able to display files at file:///tmp/mutt_attach/file.html – while Epiphany was. Whatever the reason, I changed the script to store HTML files in /home/jan/mutt_attach, and Firefox successfully opens file:///home/jan/mutt_attach/file.html. Thanks again for all your help, Jan signature.asc Description: PGP signature
Re: Mailcap and MS Word documents
On 2022-10-09 10:20, Jan Eden wrote: > Hi, > > after Chris Green's and Cameron Simpson's helpful advice regarding HTML > messages, I dare to post another mailcap question. > > My mailcap contains the following lines: > > application/vnd.openxmlformats-officedocument.wordprocessingml.document; > ~/.mutt/view_attachment %s "-" > application/vnd.openxmlformats-officedocument.wordprocessingml.document; > pandoc --from docx --to markdown %s; copiousoutput > > where view_attachment is a modified version of Chris' script. .muttrc > contains > > auto_view text/html > application/vnd.openxmlformats-officedocument.wordprocessingml.document > > to take advantage of the mailcap search order[1]. The idea is to display > the pandoc-generated markdown with view-attach and open LibreOffice with > view-mailcap. > > But Word attachments are always opened with LibreOffice. Is there any > way to achieve the intended (different) behavior for view-attach and > view-mailcap? Update: There was an error in my configuration, and now Markdown versions of Word documents are displayed inline ([-- Autoview using pandoc --from docx --to markdown --]). view-attach und view-mailcap still use the same mailcap entry (opening the attachment with LibreOffice), but at least auto_view has the desired effect. - Jan signature.asc Description: PGP signature
Mailcap and MS Word documents
Hi,
after Chris Green's and Cameron Simpson's helpful advice regarding HTML
messages, I dare to post another mailcap question.
My mailcap contains the following lines:
application/vnd.openxmlformats-officedocument.wordprocessingml.document;
~/.mutt/view_attachment %s "-"
application/vnd.openxmlformats-officedocument.wordprocessingml.document; pandoc
--from docx --to markdown %s; copiousoutput
where view_attachment is a modified version of Chris' script. .muttrc
contains
auto_view text/html
application/vnd.openxmlformats-officedocument.wordprocessingml.document
to take advantage of the mailcap search order[1]. The idea is to display
the pandoc-generated markdown with view-attach and open LibreOffice with
view-mailcap.
But Word attachments are always opened with LibreOffice. Is there any
way to achieve the intended (different) behavior for view-attach and
view-mailcap?
A related question: On a macOS system with mutt installed via Homebrew,
the mime.types file missing, and mutt would display Word attachments as
text ("No matching mailcap entry found. Viewing as text."). I fixed this
by copying ~/.mime.types from another system, but according to the mutt
docs, a mime.types file is supposed to be provided with mutt[2]. Why
wasn't it present in my case?
- Jan
[1]: http://mutt.org/doc/manual/#advanced-mailcap
[2]: http://mutt.org/doc/manual/#mime-types
signature.asc
Description: PGP signature
Re: Re: Viewing HTML message with Firefox
On 2022-10-09 08:18, Cameron Simpson wrote: > On 08Oct2022 21:55, Jan Eden via Mutt-users wrote: > > Thank you! This works well with Epiphany, but Firefox still fails (which > > I do not care about, as long as I have a working browser option). > > My recollection is that this is a timing issue. To run the viewer mutt goes: > - make a temp file containing the message or html > - run the mailcap command > - remove the temp file > > Your command is "open", which tells firefox (your default browser) to open > the file for viewing. That message takes little time. By the time firefox > gets around to opening the file (probably after making the new browser > window) the file has been removed by step 3 above. > > This is why helper scripts like Chris Green's one take a copy of the file. > They tell the browser to view the copy, which does not get removed. Yes, I did use Chris Green's helper script, and it does work with Epiphany, but not with Firefox. The (slightly modified) script creates a file in /tmp/mutt_attach, which is then passed to the respective browser, and while Epiphany handles it properly, Firefox still displays "File not found" along with several error messages: >>update.go:85: cannot change mount namespace according to change mount >>(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none >>bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission >>denied >>update.go:85: cannot change mount namespace according to change mount >>(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none >>bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied >>update.go:85: cannot change mount namespace according to change mount >>(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help >>none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": >>permission denied >>update.go:85: cannot change mount namespace according to change mount >>(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none >>bind,ro 0 0): cannot open directory "/var/lib": permission denied >>/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) >>Gtk-Message: 09:22:48.907: Failed to load module "canberra-gtk-module" >>Gtk-Message: 09:22:48.921: Failed to load module "canberra-gtk-module" >>ATTENTION: default value of option mesa_glthread overridden by environment. >>ATTENTION: default value of option mesa_glthread overridden by environment. >>ATTENTION: default value of option mesa_glthread overridden by environment. >>Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs >>[2022-10-09T07:22:51Z ERROR glean_core::metrics::ping] Invalid reason code >>startup for ping background-update >>^CExiting due to channel error. >>Exiting due to channel error. >>Exiting due to channel error. >>Exiting due to channel error. >>Exiting due to channel error. >>Exiting due to channel error. >>Press any key to continue... >>/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) >>Gtk-Message: 09:24:29.485: Failed to load module "canberra-gtk-module" >>Gtk-Message: 09:24:29.487: Failed to load module "canberra-gtk-module" >>ATTENTION: default value of option mesa_glthread overridden by environment. >>ATTENTION: default value of option mesa_glthread overridden by environment. >>ATTENTION: default value of option mesa_glthread overridden by environment. >>Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs >>[2022-10-09T07:24:31Z ERROR glean_core::metrics::ping] Invalid reason code >>startup for ping background-update Interesting enough, opening URLs from mutt with Firefox is possible. > My personal process, which is by no means seamless, is a macro bond to my > "V" key: > > macro index,pager V "mail-open-attachments" "extract > attachments to temp dir and open" > macro attach V "qVv" "extract attachments to temp dir and open" > > and the associated script is here: > > https://github.com/cameron-simpson/css/blob/main/bin/mail-open-attachments > > Like Chris' script, it makes a copy. > > It unpacks everything in the message into a directory, then opens the Finder > on that directory. Then I can use preview on the HTML or open it in Firefox. > Etc etc for whatever other attachments there may have been. Nice, thank you! - Jan signature.asc Description: PGP signature
Re: Re: Re: Viewing HTML message with Firefox
On 2022-10-08 11:52, Chris Green wrote:
> On Sat, Oct 08, 2022 at 12:06:52PM +0200, Jan Eden via Mutt-users wrote:
> > On 2022-10-08 09:34, Chris Green wrote:
> > > On Sat, Oct 08, 2022 at 10:25:29AM +0200, Jan Eden via Mutt-users wrote:
> > > > Hi,
> > > >
> > > > I recently configured mutt on a Linux system, and cannot display HTML
> > > > messages in the default browser. mailcap contains the following lines:
> > > >
> > > > text/html; open %s;
> > > > text/html; w3m -I %{charset} -T text/html; copiousoutput
> > > > application/pdf; open %s; copiousoutput
> > > >
> > > > w3m is used automatically (auto_view text/html), and PDF documents are
> > > > opened correctly in evince.
> > > >
> > > > But when I try to open an HTML message manually, Firefox displays either
> > > > a permission denied error (with AppArmor enabled), or a file not found
> > > > error – both pointing to the message's filename.
> > > >
> > > > How can I allow Firefox to access and display the message?
> > > >
> > > I no longer use Firefox on my xubuntu system (I've moved to Vivaldi)
> > > but I seem to remember that Firefox's security paranoia means that you
> > > now have to explicitly configure to allow access to files on the local
> > > system.
> >
> > With AppArmor disabled, Firefox tries to display the message, but cannot
> > find the message file in /var/tmp/ – %s seems to point to that
> > directory.
> >
> > In Firefox' settings, I did not find any parameter to keep the browser
> > from accessing local files.
> >
> > > By 'manually' I presume you mean v[iew] the message parts and then
> > > m[view-mailcap] the html.
> >
> > Yes.
> >
> When I view an HTML message like this the address is like:-
>
> file:///srv/mutt/mutt-esprimo-1000-151542-10027422769961820949.html
>
> I use a script (called via mailcap) to store the HTML message in that
> directory.
>
> So, in mailcap I have:-
>
> [...]
>
> You don't need the bit for remote viewing from my laptop, just the "running
> locally"
> bit.
Thank you! This works well with Epiphany, but Firefox still fails (which
I do not care about, as long as I have a working browser option).
- Jan
signature.asc
Description: PGP signature
Re: Re: Viewing HTML message with Firefox
On 2022-10-08 09:34, Chris Green wrote:
> On Sat, Oct 08, 2022 at 10:25:29AM +0200, Jan Eden via Mutt-users wrote:
> > Hi,
> >
> > I recently configured mutt on a Linux system, and cannot display HTML
> > messages in the default browser. mailcap contains the following lines:
> >
> > text/html; open %s;
> > text/html; w3m -I %{charset} -T text/html; copiousoutput
> > application/pdf; open %s; copiousoutput
> >
> > w3m is used automatically (auto_view text/html), and PDF documents are
> > opened correctly in evince.
> >
> > But when I try to open an HTML message manually, Firefox displays either
> > a permission denied error (with AppArmor enabled), or a file not found
> > error – both pointing to the message's filename.
> >
> > How can I allow Firefox to access and display the message?
> >
> I no longer use Firefox on my xubuntu system (I've moved to Vivaldi)
> but I seem to remember that Firefox's security paranoia means that you
> now have to explicitly configure to allow access to files on the local
> system.
With AppArmor disabled, Firefox tries to display the message, but cannot
find the message file in /var/tmp/ – %s seems to point to that
directory.
In Firefox' settings, I did not find any parameter to keep the browser
from accessing local files.
> By 'manually' I presume you mean v[iew] the message parts and then
> m[view-mailcap] the html.
Yes.
- Jan
signature.asc
Description: PGP signature
Viewing HTML message with Firefox
Hi,
I recently configured mutt on a Linux system, and cannot display HTML
messages in the default browser. mailcap contains the following lines:
text/html; open %s;
text/html; w3m -I %{charset} -T text/html; copiousoutput
application/pdf; open %s; copiousoutput
w3m is used automatically (auto_view text/html), and PDF documents are
opened correctly in evince.
But when I try to open an HTML message manually, Firefox displays either
a permission denied error (with AppArmor enabled), or a file not found
error – both pointing to the message's filename.
How can I allow Firefox to access and display the message?
Thanks,
Jan
signature.asc
Description: PGP signature
Re: Flowed text with Emacs
On Tue, Sep 27, 2022 at 12:31:09AM -0400, Kurt Hackenberg wrote: > 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: > <https://www.panix.com/~kh/mutt-flowed-text/> > > Try it, let me know how it works for you. I'm not an emacs user, but thanks. I think it's important to support $edit_headers for this. I always need the option of editing headers. cheers, raf
Re: Recognizing alternative reply prefixes
Hi Jaron, On 2022-09-21 15:53, Jaron Kent-Dobias via Mutt-users wrote: > Hello, > > I am frequently exchanging emails with Italians, whose mail clients often > use the format 'R: [Subject]' in replies instead of 'Re: [Subject]'. Mutt > in my locale does not recognize the leading 'R:' as a reply prefix and > proposes the subject line 'Re: R: [Subject]'. > > Can mutt be configured to recognize other reply prefixes automatically? reply_regexp should to the trick, e.g. set reply_regexp='^(re([\[0-9\]+])*|aw|Antwort):[ \t]*' - Jan signature.asc Description: PGP signature
Recognizing alternative reply prefixes
Hello, I am frequently exchanging emails with Italians, whose mail clients often use the format 'R: [Subject]' in replies instead of 'Re: [Subject]'. Mutt in my locale does not recognize the leading 'R:' as a reply prefix and proposes the subject line 'Re: R: [Subject]'. Can mutt be configured to recognize other reply prefixes automatically? Cheers, Jaron
Re: Re: Loading several intialisation files at startup
On 2022-09-15 08:27, Cameron Simpson wrote: > On 13Sep2022 16:50, Sébastien Hinderer > wrote: > > I would like to have a nice way to deal with several accounts in mutt. I > > am talking just about the .muttrc file aspect here. > > > > My present configuration is that each account has its own muttrc file > > which sources a common one. > > I thought the common approach was what you next outline: a single muttrc > which sources the appropriate account-specific muttrc. > > [...] > reply-hook . "my_hdr BCC: $my_cs" An indirect version of this reply-hook does not work for me reply-hook '~C "^mutt-users@mutt.org$"' 'source ~/.mutt/mutt-users.cf' where mutt-users.cf sets an address and sources reset.cf: # reset.cf set from=$my_address unmy_hdr * my_hdr Bcc: $my_address According to the docs, the BCC header is set before reply-hooks are evaluated[1], and the above configuration does not change this header (unlike the From header): > my_hdr processing for To, Cc, Bcc, Subject headers. > Prompts for To, Cc, Bcc, Subject headers. See $askcc, $askbcc, $fast_reply. > From header setting. Note: this is so send-hooks below can match ~P, but From > is re-set further below in case a send-hook changes the value. > reply-hook > send-hook > From header setting. > my_hdr processing for From, Reply-To, Message-ID and user-defined headers. > The To, Cc, Bcc, Subject, and Return-Path headers are ignored at this stage. How did you manage to change the BCC header with your reply hook? - Jan [1] http://mutt.org/doc/manual/#compose-flow signature.asc Description: PGP signature
Re: Re: Re: Re: Loading several intialisation files at startup
On 2022-09-15 21:23, Sébastien Hinderer wrote: > Jan, > > I think I got it. > > Am I correct that, for each account, you have actually two files: one > that you use in your alias and one that you use in your macro. Is that > right? More or less: For three of my accounts, there is only a single address, but for the fourth account, I have five additional files to use in my macros. > I think what I described in the first e-mail would allow you to have > only one file per account and to not repeat the line, no? Right, I misread your initial request. Sorry! - Jan signature.asc Description: PGP signature
Re: Re: Re: Loading several intialisation files at startup
Hi Sébastien, On 2022-09-15 20:26, Sébastien Hinderer wrote: > Hello Jan, thanks a lot for your response and the link! > > Jan Eden via Mutt-users (2022/09/15 11:42 +0200): > > I defined aliases for my accounts in .zshrc, because I do not mind > > restarting mutt when switching to a different account: > > > > alias m1='cd ~/Downloads && /opt/homebrew/bin/mutt -F ~/.mutt/account1.cf > > && cd' > > alias m2='cd ~/Downloads && /opt/homebrew/bin/mutt -F > > ~/.mutt/account2.cf && cd' > > That's what I am doing currently, yse. But then, am I correct that each > of your account.cf file needs to source the main configuration file to > get the default values in? Precisely, it's the repetition of this line > that I wanted to avoid. Yes, that line is repeated in each account configuration. > Plus, that way, when you change configuraiton > interactively, all the common settings are read in again useessly. It's > cheap of course but I'de still like to avoid it. Not really, because I only re-set a few parameters interactively (i.e. I do not source a complete account configuration, but an address configuration): macro generic \e1 ":source ~/.mutt/default_address.cf\r" # default_address.cf set my_address = "x...@eden.one" set my_pgp_key = '257A9B6F3DEDCA11319000877CD4656792A3A1F4' source '~/.mutt/set_address.cf' # set_address.cf set from=$my_address set pgp_default_key = $my_pgp_key set status_format="-%r $my_address: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---" unmy_hdr * my_hdr Bcc: $my_address Each macro sources only six lines of configuration. To use a different account, I restart mutt (or rather, I have four terminal tabs running mutt for different accounts). - Jan signature.asc Description: PGP signature
Re: Re: Loading several intialisation files at startup
On 2022-09-15 10:23, Sébastien Hinderer wrote: > Hello, > > Many thanks for your reponse! > > Cameron Simpson (2022/09/15 08:27 +1000): > > I thought the common approach was what you next outline: a single muttrc > > which sources the appropriate account-specific muttrc. > > [...] > > For files that define different thisgs yes, that works. But for > accounts, which have different values for the smae variables, I think > you don't want to include all them simultaneously, because then the last > one would win, but you want to source exactly one of them. And then if > you wnat to change accout without leaving mutt you just source another > one... I defined aliases for my accounts in .zshrc, because I do not mind restarting mutt when switching to a different account: alias m1='cd ~/Downloads && /opt/homebrew/bin/mutt -F ~/.mutt/account1.cf && cd' alias m2='cd ~/Downloads && /opt/homebrew/bin/mutt -F ~/.mutt/account2.cf && cd' For switching e-mail addresses, PGP keys etc within an account, I adopted a suggestion by Cos: http://lists.mutt.org/pipermail/mutt-users/Week-of-Mon-20220905/003863.html I also bind the source commands used in the solution above to message-hooks: message-hook '~C ^a...@eden.one$' 'source ~/.mutt/default.cf' message-hook '~C ^x...@eden.one$' 'source ~/.mutt/alternative_address1.cf' - Jan signature.asc Description: PGP signature
Re: Re: Two doubts about POP3 and IMAP
On 2022-09-12 13:37, Kurt Hackenberg wrote: > 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. You can do this with offlineimap or isync/mbsync by syncing just the inbox and moving messages to different folders locally. - Jan signature.asc Description: PGP signature
Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP
On 2022-09-12, Mihai Lazarescu wrote: >> Mihai Lazarescu wrote on Mon, 12 Sep 2022 at >> 15:07:37 EDT in : >> >> > Only Microsoft (outlook.com, hotmail.com) seem to filter the whole >> > IP block, but I am too lazy to ask the provider to fix or change >> > provider altogether. [...] > 1. [...] For work contacts on > Microsoft servers I use the work email (also on Microsoft). [...] > That being said, I found at work that Microsoft uses a very crude spam > filtering (kind of 1980s database-driven). E.g., it indiscriminately > junks all messages from almost any mailing list I join. Moreover, if I > un-junk the messages, Outlook behind the scenes whitelists the *sender > address*, not the list address/ID. Thus: > > - I've got myself a never ending job to move legit messages out of the > spam folder for every new sender seen on lists > > - I end up with a huge whitelist of people I don't personally know > > - if I go and clear the Outlook-built whitelist, the spam filter > behavior resets: all messages from the lists are junked, etc. (hence > my strong feeling that it's db.whitelist-driven). > > Besides, at the switch to Microsoft systems the sysadmins strongly > advised to carefully check the junk folder for important messages. And > I also found that Microsoft junked its own automated notifications, > e.g., for OneDrive shares. Go figure… > > In 2022 I find astonishing how much of Microsoft's antispam seems to > rely on lists (addresses, IP blocks…). Leading to annoying false > positives, with rates well higher than Google's. Microsoft's antispam > filters may very well include some well hidden adaptive smartness, > though. ;-) They do, at least for domains which have bought MS's email "protection" service or the full cloud-based MS e-mail hosting. Microsoft calls it SmartScreen[1], and, with this, emails can get silently dropped - accepted but not shown anywhere in the recipient's mailbox, not even in the Junk folder. These dropped messages get sent to a separate "quarantine" feature. While non-admin users can access this and (at least from what I've read) see their quarantined messages[2], users have to know about this feature first. [1] https://www.nerd-quickies.net/2020/10/20/microsoft-silently-dropping-emails-a-sad-but-true-story/ [2] https://guides.downstate.edu/c.php?g=654922=4870487 -- Nuno Silva
Re: Re: Handling multiple From addresses
On 2022-09-13 20:07, Robert wrote: > Hi there, > > On 2022-09-04 17:17, Jan Eden via Mutt-users wrote: > > - Can I define multiple From addresses to select them from a list? > > - Can mutt be configured to switch the default BCC address to a changed > > From address? > > - If there is only a single PGP private key for each address – is it > > possible to have that key selected automatically (or with a single > > keystroke) according to the current From address? > > I had the exact same problems and did a bit of an over-engineering approach: > my profiles are defined in a yaml file and a python script generates the > necessary (neo)mutt rc files. > > The details, as well as the python script are available here: > https://spacepanda.se/neomutt-pt7.html Nice – I have a knack for over-engineering. :) Cos had already suggested a similar approach to your "tedious and annoying" version which I adapted (http://lists.mutt.org/pipermail/mutt-users/Week-of-Mon-20220905/003863.html) to manually select the desired identity. Using reply-hooks is a better solution, but unfortunately, they are executed too late in the composition workflow to change the Bcc header (http://mutt.org/doc/manual/#compose-flow). Some of my addresses have more than one recipient, so the correct Bcc header is crucial. Defining a message-hook works in most cases (if I open/view a message before replying to it), but sometimes I want to reply to a message right from the index after starting mutt. Do you have any suggestion on how to change the Bcc header automatically? Thanks, Jan signature.asc Description: PGP signature
Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP
> In 2022 I find astonishing how much of Microsoft's antispam seems > to rely on lists (addresses, IP blocks…). Leading to annoying > false positives, with rates well higher than Google's. Those "false positives" are clearly made on purpose to boycott independent mail providers, it doesn't matter if an IP sends less than 10 emails per day on average during years and has never been black listed in any public list, it will stay on Microsoft blacklist forever and there is no easy/cheap way to remove it. And of course, they will never tell you WHY they have blacklisted you in the first place. The way to overcome that is to have several mail servers and domains, one way or other you always overpass Hotmail censorship.
Re: Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP
On 2022-09-12 21:59, bastian-muttu...@t6l.de wrote: > On 12Sep22 21:07+0200, Mihai Lazarescu wrote: > > Given the cheap VPS, I can mirror the setup on a second VPS from a different > > provider with quick DNS switch in case of issues. > > I just did that approx half a year ago. Before, everything was rolling > just fine (for more than 10 yrs). No dead ends of my outgoing mails. > After transferring the domain over to the new hoster, some destinations > did not receive my mails. Either filtered into spam, some got denied > (where I got a nice SMTP error reply) and some just got silently > dropped. > This took me some time to figure out with each destination, why is that > happening. And sometimes also just guessing. At least the > mail-tester.com rate is 10/10, so it is not about my setup per se. Now that this thread has steered off-topic already, I dare to hijack it some more: My own setup had a score below 10/10, because my PTR record pointed to eden.one, while my mailserver's hostname was mail.eden.one. I changed the hostname (and the Dovecot/Postfix config) to eden.one, but subsequently found a couple of serverfault threads (related to the MxToolbox warning "Reverse DNS is not a valid Hostname") advising against this setup: https://serverfault.com/questions/711600/reverse-dns-is-not-a-valid-hostname-error-from-mxtoolbox/ https://serverfault.com/questions/599712/best-practices-for-fqdn-for-standalone-domain-is-a-two-part-domain-tld-okay/599725#599725 While I did run into a problem initially (overlapping mydestination and mailbox_virtual_domains in the Postfix configuration disrupted email delivery to Dovecot virtual mailboxes), the new setup now works quite well (and delivers a 10/10 score at mail-tester.com). Do you consider a PTR record pointing to a bare domain (eden.one) a serious issue? Or are there any downsides to pointing the PTR record to mail.eden.one? According to Cloudflare, reverse DNS lookups are mainly used for mailservers anyway – but are they relevant for other services (nginx etc) running on the same server at all? > The IP and/or subnet my VPS was in had a bad reputation at some > denylist services. Question was then, how to get removed from them. > Sometimes via automated forms and sometimes through personal > mail-conversation with other mail operators (t-online.de was very nice > and responsive to my surprise). I had exactly the same impression of the postmaster team at T-Online.de just two weeks ago: https://eden.one/2022/8/schwarzgelistet :) Thanks, Jan signature.asc Description: PGP signature
Re: [Mutt] Is linewrap dead?
On Mon, Sep 12, 2022 at 09:07:37PM +0200, Mihai Lazarescu wrote: > On Monday, September 12, 2022 at 15:15:55 +, Nacho via Mutt-users wrote: > > > > What you describe is becoming more and more history, which I regret. > > > Let me give you the link of an article that should interest you. > > > > > > https://cfenollosa.com/blog/after-self-hosting-my-email-for-twenty-three-years-i-have-thrown-in-the-towel-the-oligopoly-has-won.html > > > > I don't agree with that article, it has some technical errors I will not > > discuss > > here because of lack of time and it being off topic. > > > > But in short, today it's just a matter of money and time to have your own > > email system working perfectly, of course the cost have increased wildly in > > the > > last few years and will keep doing so, but at least for me makes all the > > sense > > to pay for it. > > I tend to concur. I run just fine for several years now my own SMTP/IMAP > servers + Let's Encrypt certificate on a cheap VPS (< $20/year). > > It took some work to set it up, but that's it. Surely not a mass solution, > yet feasible and stable. > > Messages sent to Google accounts tick all green boxes. > > Only Microsoft (outlook.com, hotmail.com) seem to filter the whole IP block, > but I am too lazy to ask the provider to fix or change provider altogether. > > Given the cheap VPS, I can mirror the setup on a second VPS from a different > provider with quick DNS switch in case of issues. > > HTH. > > Mihai I haven't noticed any cost increases with my VPS (but I am paying more than $20/year). I've only had two mail receivability problems. It turns out that spamhaus doesn't realise that someone might only have one IPv6 address, so if any of my neighbour VPSs sends spam over IPv6, the whole network block is tainted, so I had to stop my mail server from sending from its IPv6 address. Luckily, the same strange idea doesn't seem to apply to IPv4 (at least for spamhaus). Also, Microsoft once didn't like my IPv4 address so I temporarily routed mail to there via some third party service, but when I asked them to fix it, they did (but they couldn't explain why they didn't like it). Apart from that, it all seems fine (unless I'm deluded). :-) cheers, raf
Re: Is linewrap dead?
> What you describe is becoming more and more history, which I regret. > Let me give you the link of an article that should interest you. > > https://cfenollosa.com/blog/after-self-hosting-my-email-for-twenty-three-years-i-have-thrown-in-the-towel-the-oligopoly-has-won.html I don't agree with that article, it has some technical errors I will not discuss here because of lack of time and it being off topic. But in short, today it's just a matter of money and time to have your own email system working perfectly, of course the cost have increased wildly in the last few years and will keep doing so, but at least for me makes all the sense to pay for it. You can even give email accounts to people you want to comunicate with. many are more than happy to have a nice alternative to their gmail/hotmail/yahoo accounts.
Re: Two doubts about POP3 and IMAP
John Hawkinson wrote: > [ I want to preface this by saying the recent discussions about POP3 that > suggest it is a reasonable approach or a viable alternative are quite > concerning to me, becauase as a practical matter, my understanding is that > basically "nobody should still be using POP3" and it is a moribund and > technically inadequate protocol with a lot of problems, I'm not sure where you read/heard that. POP3 and IMAP4 are really aimed at different use cases - POP3 is basically just used to pull messages from a server when the machine you're on doesn't receive mail by SMTP. Yes, it can be used in more complex environments, and can be used as a live store of mail accessed remotely by a client - but that really isn't its forte. IMAP4 *is* designed as a live remote store of mail, providing features that a full MUA needs to be able to provide a reasonable approximation of "normal email" service when the mailstore is remote. For what it's designed to do, POP3 is still fully capable of serving those needs. "No one should be using POP3" is a religious argument, not a technical one. If POP3 serves your needs, use it. If it doesn't, or you don't want to, use IMAP4. But you needn't be "concerned" about other people using POP3 - it's a perfectly valid thing to do. Charles -- --- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ ---
[help] Disabling email notification not working
Hello, > 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 notification for a new email, yet, I do. I receive a notification about 20 seconds after I sent myself an email with another email address. With mail_check, I should get the notification only after 10 minutes. How come? And with -nonotify and -nopoll, I should not even get the notification. I tried unmailboxes $spoolfile and I still get the notification and hear noise.mp3. I tried running mutt with the -n option, still doesn't work. (I have mutt 2.2.7) And and I do get "Reading configuration file '~/.mutt.rc'" in the debug log file. Hope somebody has a little time to help me out. Sent with [Proton Mail](https://proton.me/) secure email.
Re: Re: Handling multiple From addresses
On 2022-09-07 08:04, Cameron Simpson wrote: > On 06Sep2022 09:26, Jan Eden via Mutt-users wrote: > > Thank you! This is exactly what I needed. I tweaked your version a bit > > to use the standard parameters for setting the required values: > > > > set from="x...@eden.one" > > set pgp_default_key = '0x20F7FHD80EC4C17294434A0220D37B3CE755FE8A' > > set status_format="-%r x...@eden.one: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? > > Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? > > %l?]---(%s/%S)-%>-(%P)---" > > unmy_hdr * > > my_hdr Bcc: t...@eden.one > > I've got a slightly tweaked $status_format which begins: > > set status_format="$my_account_email .." > > because I've parameterised the email address, since it gets used in a few > places. FWIW, my final setup looks like this: # .muttrc source ~/.mutt/default_address.cf macro generic \e1 ":source ~/.mutt/default_address.cf\r" macro generic \e2 ":source ~/.mutt/alternative_address1.cf\r" macro generic \e3 ":source ~/.mutt/alternative_address2.cf\r" macro generic \e4 ":source ~/.mutt/alternative_address3.cf\r" # default_address.cf set my_address = "x...@eden.one" set my_pgp_key = '257A9B6F3DEDCA11319000877CD4656792A3A1F4' source '~/.mutt/set_address.cf' # set_address.cf set from=$my_address set pgp_default_key = $my_pgp_key set status_format="-%r $my_address: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---" unmy_hdr * my_hdr Bcc: $my_address - Jan signature.asc Description: PGP signature
Re: Is linewrap dead?
On Mon, Sep 05, 2022 at 10:45:09PM -0400, Kurt Hackenberg wrote: > 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 program, or script that runs > two programs -- rather than be done later by Mutt itself. That is, Mutt > could farm out the whole job, rather than have the external program do half > and Mutt do half. > > I would guess that it's split just because it was made for vim, and vim > can't do the space-stuffing. I don't know the history, though. I expect it is done in mutt because it must be done (for transport), and it would be a mistake to assume that it will be done by the editor, whatever editor it is. I don't think that mutt makes any assumptions about which editor is used. Also, vim could do it. Vim can do anything to text, and it can be automated, but of course, it needs to configured to do so. Not necessarily with formatoptions settings, but perhaps with filetype-based autocommands. But I think the real problem with format=flowed, and possibly the reason why the large corporate web-based mail providers don't support it is that it's not sufficiently trivial to make it happen. So maybe it just isn't used by enough people. It seems that vim makes it fairly easy, but that's just one editor. Although the real reason might just be a preference for html email. cheers, raf
Re: Problems sending mail
You'll need to set up the authentication for msmtp. Snippet from msmtprc: defaults account david-email host mx1.dreamhost.com port 25 protocol smtp auth on user youru...@fake.domain.com password yoursecretpassword On Mon, Sep 05, 2022 at 03:49:59PM -0500, David Bryant wrote: Hi. I'm new to this group. I'm looking for some help. I recently built a Linux from Scratch system. I don't have any kind of graphical interface set up there yet. I would like to use mutt to send and receive email using a tty terminal. Mainyly for educational purposes. I'm composing this message with KMail2, on a Gentoo system. I have built mutt from the tarball, and I've done some configuration stuff. In particular, I set up msmtp as my SMTP server locally. That looked like it's easier to configure than sendmail is. I believe I got all the necessary configuration variables set correctly. But I can't send email. Everything goes fine until I'm ready to send an email message. I say "y" to send the message, and mutt replies "Error sending message, child exited 65 (Data format error)" msmtp issues three error messages: msmtp: recipient address da...@davidcbryant.net not accepted by the server msmtp: server message 554 5.7.1 Recipient address rejected. Access denied. msmtp could not send mail (account default from /home/dbryant/.msmtprc) Any idea how I can get around this? I tried sending messages without going through an external server, and that didn't seem to work either. Oh -- here's the message from the "postponed" file. = Date: Mon, 5 Sep 2022 18:26:53 + From: David Bryant To: da...@davidcbryant.net Cc: davidbry...@gvtc.com Subject: This is a test Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mutt-Fcc: ~/sent This is a test. This is only a test. = Any and all suggestions will be accepted gladly. Thanks! -- David Bryant Canyon Lake, Texas https://davidcbryant.net -- Dan Ciprus [ curl -L http://git.io/unix ] signature.asc Description: PGP signature
Re: Re: Handling multiple From addresses
On 2022-09-05 19:16, Ofer Inbar wrote: > What I did for this was select a few esc-capital hotkey combos > and define macros like this in my muttrc: > > macro generic \eF ":source ~/.mutt/headers.f...\r" > macro generic \eH ":source ~/.mutt/headers.h...\r" > > And so on. (I replaced the actual filenames with "...") > > Each .mutt/headers... file looks somewhat like this: > -- > unmy_hdr * > my_hdr X-URL: ... > my_hdr From: Ofer Inbar > set status_format="-%r- %f: cos@somedomain ---[Msgs:%?M?%M/?%m%?n?New:%n?%?d? > Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? > Inc:%b?%l]---(%s%?S?/%S?)-%>-(%P)---" > set signature="..." > -- > > So in the index I can hit esc-F, esc-H, etc., and it loads the set of > headers I want, and also sets my status line to show me which header > set I currently have loaded. Thank you! This is exactly what I needed. I tweaked your version a bit to use the standard parameters for setting the required values: set from="x...@eden.one" set pgp_default_key = '0x20F7FHD80EC4C17294434A0220D37B3CE755FE8A' set status_format="-%r x...@eden.one: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---" unmy_hdr * my_hdr Bcc: t...@eden.one Thanks again, Jan signature.asc Description: PGP signature
Re: Re: Is linewrap dead?
On Sun, Sep 04, 2022 at 05:39:05PM +0200, Jan Eden via Mutt-users wrote: > On 2022-09-04 20:37, Cameron Simpson wrote: > > On 04Sep2022 15:34, raf via Mutt-users wrote: > > > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson > > > wrote: > > > > > The `md2html` script is my personal script, which wraps `pandoc` > > > > and post munges the HTML to indent the code blocks, which > > > > `pandoc`'s HTML does not please my eye. It's here: > > > > https://github.com/cameron-simpson/css/blob/main/bin-cs/md2html if > > > > anyone wants a starting point. > > > > > > Thanks, Cameron. It's odd that there isn't an md2html program out > > > there already. I had to create one too (using python's markdown > > > module). > > There is a python script provided with mutt > (share/doc/mutt/samples/markdown2html), which can also be found at > https://fossies.org/linux/mutt/contrib/markdown2html . This one also > uses pandoc. > > - Jan Thanks. cheers, raf
Re: Is linewrap dead?
On Mon, Sep 05, 2022 at 08:36:54AM +1000, Cameron Simpson wrote: > On 05Sep2022 08:24, Cameron Simpson wrote: > > On 04Sep2022 11:33, Kurt Hackenberg 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=flowed that it > > > gets back from the editor. > > Aye. I avoid lines commencing with a ">" just because they look quoted to my > eye anyway, so that aside "live" space stuffing in authoring is something > I'd find distracting. > > Cheers, > Cameron Simpson Hmm. I do "From-munging" on arrival. I should probably read rfc3676 properly. :-) cheers, raf
Re: Is linewrap dead?
On Sun, Sep 04, 2022 at 08:37:21PM +1000, Cameron Simpson
wrote:
> On 04Sep2022 15:34, raf via Mutt-users wrote:
> > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson
> > wrote:
> [...]
> > > So I've revisited the manual and found the
> > > `$send_multipart_alternative`
> > > option and its friend `$send_multipart_alternative_filter`. They work
> > > well!
> > >
> > > So now I have a mechanism to send: `format=flowed` MarkDown with a
> > > aparallel
> > > HTML alternative. The HTML should render in a "paragraphy" way for the
> > > HTML
> > > people, and the MarkDown keeps me happy.
> > >
> > > My default setting is now:
> > >
> > > set send_multipart_alternative=no
> > > set send_multipart_alternative_filter='echo text/html; echo; exec
> > > md2html'
> > >
> > > which is the inactive form, and I've added:
> > >
> > > message-hook . 'set send_multipart_alternative=no'
> > > message-hook '%f htmlees' 'set send_multipart_alternative=no'
> >
> > Oops. That should be =yes above.
>
> Whoops indeed. I just sketched this out this morning. Thanks for the catch.
> fix applied.
>
> > > The `md2html` script is my personal script, which wraps `pandoc` and
> > > post
> > > munges the HTML to indent the code blocks, which `pandoc`'s HTML does not
> > > please my eye. It's here:
> > > https://github.com/cameron-simpson/css/blob/main/bin-cs/md2html
> > > if anyone wants a starting point.
> >
> > Thanks, Cameron. It's odd that there isn't an md2html
> > program out there already. I had to create one too
> > (using python's markdown module).
>
> Ah, that might be easier to customise. I just tried a few markdown
> converters and ended up with pandoc.
>
> > I like your indenting of code blocks, but it seems to
> > put an additional blank line after each code block.
> > That might not be intentional.
>
> Not intentional. I just wanted to keep the 4 space indent used to trigger a
> code block for the same visual effect, since I use that instead of the
> triple backticks usually. Pandoc tosses those spaces.
That's correct behaviour for markdown. If you want the
output to be indented four spaces, the markdown source
needs to be indented eight spaces. But for email use,
it's a nice idea to do what you're doing.
If you want to prevent the extra line, the sed command
can be changed to remove theindenyt before the closing
line of the code block:
sed '
s/^\(\)\(.*<\/code><\/pre>\)$/\1\2/
t post_pre_code
/^/,/<\/code><\/pre>$/{
s/^//
s/^\(\)/\1/
s/^\(<\/code><\/pre>\)/\1/
}
:post_pre_code
'
> Pandoc's conversion is a bit clunky (but better than discount and the other
> tool I tried).
>
> > And it looks like it
> > doesn't do titles (which default to "-"). I guess that
> > doesn't matter for email use, except that pandoc
> > whinges about it on stderr.
>
> Aye, annoying. There's no context for a title (eg the subject header), I may
> just have to provide something to shut it up. Or shift sideways to the
> Python module, particularly if that does a better job.
>
> > 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 automatically.
>
> > Perhaps I could just post-process messages with perl
> > in my mutt-editor wrapper script.
>
> Vim can do 99% of it for you on the fly :-)
Thanks again.
> Cheers,
> Cameron Simpson
cheers,
raf
Re: Re: Is linewrap dead?
On 2022-09-04 20:37, Cameron Simpson wrote: > On 04Sep2022 15:34, raf via Mutt-users wrote: > > On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson > > wrote: > > > The `md2html` script is my personal script, which wraps `pandoc` > > > and post munges the HTML to indent the code blocks, which > > > `pandoc`'s HTML does not please my eye. It's here: > > > https://github.com/cameron-simpson/css/blob/main/bin-cs/md2html if > > > anyone wants a starting point. > > > > Thanks, Cameron. It's odd that there isn't an md2html program out > > there already. I had to create one too (using python's markdown > > module). There is a python script provided with mutt (share/doc/mutt/samples/markdown2html), which can also be found at https://fossies.org/linux/mutt/contrib/markdown2html . This one also uses pandoc. - Jan signature.asc Description: PGP signature
Handling multiple From addresses
Hi, I use a couple of From addresses, and currently change the default From address and BCC address manually, and select the matching PGP key for signing afterwards (PGP menu → sign as → [From address] → select key). This can probably be done much more efficiently, so my questions are: - Can I define multiple From addresses to select them from a list? - Can mutt be configured to switch the default BCC address to a changed From address? - If there is only a single PGP private key for each address – is it possible to have that key selected automatically (or with a single keystroke) according to the current From address? I know I could work with different mutt profiles by starting the program with the -F parameter, but I regularly need to switch the From/BCC/PGP key combination while using mutt. Thanks, Jan signature.asc Description: PGP signature
Re: Re: Is linewrap dead?
> I smile, that was me. I agree with your point: email use is getting > relegated to corporate settings, dealing with banks/utilities, some > services (newsletters). It's worse than that: what is being relegated by most people is reading and writing "complex texts" (i.e. more than a few lines), and performing "complex tasks" as attaching a few images to an email or using a paper map; this is going backwards in the development of the Western human psyche, it's a very serious issue, but too much off topic for this list. Apart from that, the big difference between using whatsapp or email is that with email you get independence: I have my own email servers using my own domains that just a court can take away from me, use the OS and MTA of my choice that I can modify and compile from source, set up my spam filters, webmail and everything else just the way I want, and everything works the way I want. It's like being the owner of my own piece of land or just a poor peasant in somebody's else huge land.
Re: Is linewrap dead?
On Sun, Sep 04, 2022 at 01:51:25PM +1000, Cameron Simpson wrote: > Well, this has been quite the read. > > As a plain text person (aren't we all?) I find poor quality mail clients > annoying, as shown by the motivating screenshot of a plain text hard folder > message presenting on a narrow portrait mode mail reader. > > There seem to two approaches available: `format=flowed` which works well if > the mail reader supports it, and HTML which is a PITA to author for us. > > Having just got my `format=flowed` stuff working again after being broken > for a long time, and have been using some Discourse forums recently (via > email) which accept MarkDown, I've been filled with enthusiasm for MarkDown > email. And markdown's a decent source for basic HTML, since it's authoring > overhead is low and it is very readable in its raw form. > > So I've revisited the manual and found the `$send_multipart_alternative` > option and its friend `$send_multipart_alternative_filter`. They work well! > > So now I have a mechanism to send: `format=flowed` MarkDown with a aparallel > HTML alternative. The HTML should render in a "paragraphy" way for the HTML > people, and the MarkDown keeps me happy. > > My default setting is now: > > set send_multipart_alternative=no > set send_multipart_alternative_filter='echo text/html; echo; exec md2html' > > which is the inactive form, and I've added: > > message-hook . 'set send_multipart_alternative=no' > message-hook '%f htmlees' 'set send_multipart_alternative=no' Oops. That should be =yes above. > which will be turning it on for people in my (empty so far) "htmlees" mutt > group. I use a similar pattern (`%htmlers`) for preserring HTML over plain > text for certain messages. > > The `md2html` script is my personal script, which wraps `pandoc` and post > munges the HTML to indent the code blocks, which `pandoc`'s HTML does not > please my eye. It's here: > https://github.com/cameron-simpson/css/blob/main/bin-cs/md2html > if anyone wants a starting point. > > I'm probably going to bind a key to turn this mode on at some point. > > Cheers, > Cameron Simpson Thanks, Cameron. It's odd that there isn't an md2html program out there already. I had to create one too (using python's markdown module). I like your indenting of code blocks, but it seems to put an additional blank line after each code block. That might not be intentional. And it looks like it doesn't do titles (which default to "-"). I guess that doesn't matter for email use, except that pandoc whinges about it on stderr. Do you have any advice for automating spaces at the end of non-final paragraph lines for format=flowed in vim? Perhaps I could just post-process messages with perl in my mutt-editor wrapper script. cheers, raf
Re: Having problems with POP3 setup
On Sat, Sep 03, 2022 at 05:35:31PM -0500, x...@trimaso.com.mx wrote: > What's the current panorama for POP3 nowadays? Is it still used or is it > dying? I heard Yahoo dropped POP3 support since years ago, except for paid > users... > > Thanks again. I don't think POP will go away entirely. I can't imagine dovecot removing support for it. The entities that would want to abandon POP are ones like Yahoo/Gmail/Microsoft who store their users' emails. I have a mail server on a little VM that some family members use. I wouldn't want to store their emails indefinitely, or be responsible for backups, so they all connect via POP to fetch mail, which they delete a week or two later (to give multiple devices a chance to see everything), and they handle their own backups. But I suppose it could disappear from big mail providers. When there are choices, they can pick a favourite and make a choice on behalf of their users rather than letting their users make their own choices. But this is speculation. I don't really know. cheers, raf
Re: Re: Is linewrap dead?
On 2022-09-03 00:46, Derek Martin wrote: > On Wed, Aug 31, 2022 at 07:45:05PM -0400, John Hawkinson wrote: > > Derek Martin wrote on Wed, 31 Aug 2022 > > at 19:35:15 EDT in <20220831233515.gf13...@bladeshadow.org>: > > > > Evaluating the strength of a SHOULD requires looking at pragmatic > > realities. And that reality is that lots of messages are sent > > without hard line wraps. > > That's true but the vast majority of that is HTML mail, which has > entirely different set of formatting rules and display parameters, and > again, not applicable here. While I find this thread quite entertaining, we should accept that we are an increasingly small group of people who care not just about plain text email (and its formatting), but about email in general. Over at gnupg-users, there was a recent discussion about the Washington Post's malformed PGP key, and one participant summarized the situation pretty well: "It would be interesting to see how long the key has been there in such a state. If the answer is “a long time”, that is quite a field report: it means signal and whatsapp (!) are more popular options (way more popular options) than PGP + email for secure communications." (https://lists.gnupg.org/pipermail/gnupg-users/2022-August/066156.html) This is obviously not limited to *secure* communications (as many people do not care about security). Apologies for the digression. - Jan signature.asc Description: PGP signature
Re: Is linewrap dead?
On Thu, Sep 01, 2022 at 08:20:21AM +0200, Angel M Alganza wrote: > On Wed, Aug 31, 2022 at 05:22:48PM -0400, Kurt Hackenberg wrote: > > > Very long lines -- one line per paragraph -- changes the meaning of > > After top posting that is probably the most annoying thing on email. > And from what I can tell reading this thread, there will always be some > nasty software and some people who will insist on doing that. > > So, is there a way to instruct Mutt to wrap received mail with long > lines to wrap them for me at a sane length so that I don't have to suffer > those ridiculous long lines? I have this in ~/.muttrc: set markers = no set wrap = -5 which wraps lines at 5 columns in from the right. You can also use a positive number to specify an absolute amount. Turning markers off means that wrapped lines won't start with a "+" character. HAving the + there might be preferable. I remove them so I can copy and paste multi-line wrapped URLs into another window to be opened locally (the email is read remotely via ssh to a vm). So maybe try something like: set wrap = 72 set smart_wrap There are other muttrc variables to look into: e.g. smart_wrap That looks good. I might add that. It wraps at word boundaries. > Of course I can reduce the with of the frame on Notion (my window > manager) where I run Mutt to force the wrapping, but I'd rather keep the > size I use for everything else and have Mutt wrapping the text for me. > > Cheers. > Ángel cheers, raf
Re: Is linewrap dead?
On Wed, Aug 31, 2022 at 02:48:55PM -0500, Derek Martin wrote: > The bottom line is there is absolutely no reason why hard-wrapped > lines of plain text at 72 characters should ever need to display > unreadably for any desktop user, or even anyone on any reasonable > mobile device which can rotate lines parallel to their longer side, > that doesn't boil down to the choice of the user. Flouting the > standards is a bad habit to be in. They exist for good reason; if you > choose to abandon them you do so at your own peril, and the rest of us > should not be expected to accommodate you. > > -- > Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- I hard wrap at 55 to leave plenty of room for later quoting. I often receive replies from MUAs that wrap quoted text badly (as though they don't know what quoted text is) and so I try to reduce the likelihood of that. Strangely, it seems that some MUAs that treat each line as a paragraph seem to insert an additional newline after each line in what they quote as part of a reply, so I receive replies with a quoted blank line between each original line. It's almost as though they want to think that each line is a separate paragraph on input, but they're not entirely convinced, so for output, they make sure it's a "real" paragraph by adding a blank line between each input "paragraph". It doesn't make a lot of sense. Either a newline marks a paragraph or it doesn't. They can't make up their minds. I sometimes spend time cleaning up this sort of thing (or just removing quote trails), but it would never occur to me to complain to the sender about the formatting of their email. There's no point. Similarly, noone has ever complained about my emails. They might (or might not) have seen them as untidy, but I don't agree that that makes them any less effective as a means of communication. And I wouldn't worry about a recipient thinking that my emails aren't as nice as someone else's. The content of one person's emails would never be the same as the content of someone else's emails, so there is no meaning to any comparison like that. The best definition of technology that I ever heard was: "Anything that doesn't work properly yet". Once technology works properly, we give it a permanent name like chair, or hammer, or pencil. :-) So it's best if everyone just cuts everyone else a lot of slack when it comes to what technology does to our written communications. If someone has too much trouble doing that, for whatever reason (and I'm sure there are valid reasons), and they are receiving emails that do bother them to read, they could consider not reading emails on phones. There are many other reasons to not read email on phones. This might just be another one. Even excluding the whole short attention-span dopamine training thing, I know someone who is often very frustrated with the mail app on their iphone for often not being able to display emails that it composed and sent, complaining that the sender created a malformed email (a bug people have complained about for 10+ years that shows no sign of every being fixed), or emails from one person that are displayed with a different person altogether as the sender). In the grand scheme of things, lines that aren't all the same length seems unimportant. But it's obviously fun to talk about. :-) It would have been great if all of the obvious suspects had been willing at any point in the last 20+ years to pay just one of their many thousands of programmers to spend a little time to implement format=flowed. That would be the best solution to this "problem". But it seems they really really don't want that solution to exist for some reason best known only to themselves. I don't think it's fair or reasonable to blame the senders of emails for a problem caused by the company that created the deliberately limited MUA that the recipient uses, let alone expect those senders to all individually solve the problem. I'd use format=flowed if there was any point, but it doesn't seem that there is. It never makes sense to expect a large number of entities to each solve a problem that could be solved by a tiny number of (more powerful) entities. It's just not efficient or practical or likely to work reliably. cheers, raf
Re: Postponing and forwarding
On 2022-08-31, X Tec wrote: > When composing an email, I decided to postpone instead of immediately > send. It got saved in Drafts folder, but when deciding to send it, I > opened the draft, but there's no "send" option; just the usual > respond, new email, and the other options when opening any other > message. Then how am I supposed to "send" drafts, without having to, > say, use the "respond" option again? If you try composing another email, does mutt ask if you want to edit the postponed one? (It does here, but that might depend on some changed setting?) -- Nuno Silva
Re: Postponing and forwarding
On 2022-08-31 11:51, X Tec wrote: When composing an email, I decided to postpone instead of immediately send. It got saved in Drafts folder, but when deciding to send it, I opened the draft, but there's no "send" option; just the usual respond, new email, and the other options when opening any other message. Then how am I supposed to "send" drafts, without having to, say, use the "respond" option again? If there are drafts and you hit m to create a new message, you will be asked whether you want to edit one of the drafts. Also, how can I *forward* messages to other users? Just hit f while the message is selected in the pager. - Jan signature.asc Description: PGP signature
Re: Re: Is linewrap dead?
On 2022-08-30 14:58, Kurt Hackenberg wrote: 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, but the indentation obviously gets messed up with text_flowed=yes [mutt] and formatoptions=ntwcql [vim]. 1. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. 2. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. It would get messed up only if spaces were added at the ends of lines. Your sample numbered paragraphs above did not have those spaces in your message, and don't in this message, even though this message is text/plain format=flowed. The numbered paragraphs should be displayed undisturbed. (This paragraph, however, has those spaces, and should be filled and word-wrapped to fit the window width, by any mail reader that understands format=flowed. For example, Mutt with reflow_text=yes and reflow_wrap=0.) Right. I created the numbered paragraphs above without the format=flowed support in vim (fo=ntcql), as opposed to the following (fo=nwtcql): 1. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. 2. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. I don't use vim, but just tried it a little with formatoptions=aw, and textwidth set, so it wrapped automatically. fo=w tells vim to recognize as a soft line break, but vim didn't insert those spaces automatically. Is there some other option to make it insert them? Or do you have to type them by hand? vim (9.0) does insert the spaces for me with fo=w (as illustrated in the second version of the numbered paragraphs). - Jan signature.asc Description: PGP signature
Re: Re: Is linewrap dead?
On 2022-08-29 19:07, Tavis Ormandy wrote: > On 2022-08-29, Logan Rathbone wrote: > > On Mon, Aug 29, 2022 at 10:43:45AM EDT, Tavis Ormandy wrote: > >> 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. > > > > FWIW, the solution/compromise I ended up using was to compose > > multipart/alternative mails with mutt, sending a very simple HTML mail > > and a standard hard-wrapped text-based mail as well. So mobile > > mailreaders can read it perfectly, and desktop users can read the > > plaintext version correctly as well. > > > > Hmm thanks, that does work - I don't like the idea of sending html > parts, but clearly a compromise is necessary somewhere! 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, but the indentation obviously gets messed up with text_flowed=yes [mutt] and formatoptions=ntwcql [vim]. 1. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. 2. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. Creating HTML mail with mutt feels more like a surrender. :) Apart from the known drawbacks of HTML mail, the markdown2html script has a couple of requirements to further complicate my (already overly complex) mailstack. - Jan signature.asc Description: PGP signature
Re: Visualising contents of a Maildir
Regarding the following, written by "Victor Goff" on 2022-08-18 at 20:09 Uhr -0400: I have used https://tmate.io for those on Windows and those with a small amount of experience with computers in general. Since you can share a browser, and they can either type with you or not, and they do not necessarily need to even generate ssh keys, this is a point of allowing that to happen easily. Nice, but this isn't going to be a live presentation, so it really has to be a PDF. -- @martinkrafft | https://matrix.to/#/#madduck:madduck.net in the beginning was the word, and the word was content-type: text/plain spamtraps: madduck.bo...@madduck.net
