Re: [OT-ish] Want command line program to selectively delete emails
Answering late: * Ed Blackman , 2023-08-04 14:34:44 Fri: > Any suggestions for a command line program to select emails for > deletion based on command line options? I specifically want one > that can remove emails that were received more than X days ago, but > can also express "but don't delete if they're flagged". [...] > > When I recently upgraded to Debian 12, I found that archivemail has > been removed from Debian because it's an unmaintained Python 2 > program. I went through the same realization some time ago. Checking my configuration, I see that I have replaced archivemail with mail-expire: https://manpages.debian.org/bookworm/mail-expire/mail-expire.1.en.html It does not seem to support your requirement to avoid deleting flagged messages, sadly, but this might be useful to others looking to move off archivemail. -- David Haguenauer
Re: DKIM fails depending on Content-Transfer-Encoding
Hi Kevin, On 2023-09-07 20:07, Kevin J. McCarthy wrote: > On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote: > > Thank you for this hint. Unfortunately it does not work for me. Mutt > > insists in 8bit, maybe depending on my locales. Seems I have to study > > the source code... > > See if 'unset allow_8bit' helps. YES! That solved my problem - thanks a lot and best regards Torsten > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA -- Torsten Finke f...@igh.de
Re: DKIM fails depending on Content-Transfer-Encoding
On Thu, Sep 07, 2023 at 11:57:09AM +0200, f...@igh.de wrote: Thank you for this hint. Unfortunately it does not work for me. Mutt insists in 8bit, maybe depending on my locales. Seems I have to study the source code... See if 'unset allow_8bit' helps. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: DKIM fails depending on Content-Transfer-Encoding
Hello Ed, On 2023-09-06 14:46, Ed Blackman wrote: > On Wed, Sep 06, 2023 at 01:33:30PM +0200, f...@igh.de wrote: > > Can I force Mutt to use quoted-printable or base64 by default for > > encoding of plain text? > > It would be better to fix the DKIM problem, but as I have no idea > about that, I'll tell you how I force q-p encoding: include a > non-ASCII space in my signature. > The space between my first and last name in my signature is a > non-breaking space, eg in HTML. In vim I used > to insert it. The non-ASCII character in the > message body tickles mutt to send the message encoded as > quoted-printable. Thank you for this hint. Unfortunately it does not work for me. Mutt insists in 8bit, maybe depending on my locales. Seems I have to study the source code... Best Regards Torsten > Ed Blackman -- Torsten Finke f...@igh.de
Re: DKIM fails depending on Content-Transfer-Encoding
Hello Raf, On 2023-09-07 10:31, 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. ... > 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. that's a good hint. I also suspected some MTA. So I should do further investigation on them. Best Regards Torsten -- Torsten Finke f...@igh.de
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
