Github messages for mblaze
 help / color / mirror / Atom feed
From: hills <hills@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: The proper way to delete mails?
Date: Thu, 30 Mar 2023 16:02:00 +0200	[thread overview]
Message-ID: <20230330140200.nWm9CJVYxu3l5IXRi2wJjHMrnC8_X3SWJEY7jxaDtSI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-236@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

New comment by hills on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/236#issuecomment-1490361071

Comment:
Thanks for such a quick reply.

I don't think my IMAP server automatically does this (though there's a command at my client, alpine, to "purge")

> (modulo usual quoting issues)

I suppose that's another good reason for a dedicated command (could be equivalent of rm or even xargs for mails): ensure one message per-line and have a safety check that the filename (and possibly first block of content) looks like a mail message.

In the spirit of community, shall I see if I can patch the docs so people don't need to ask again.

The existing example:

`mdirs ~/Maildir | xargs minc | mthread | mless`

there's no consideration for pathnames with spaces. So should I just follow in the spirit of it being an example, with a simple xargs again:

`mlist ~/Maildir | mpick -t 'mtime < "-365d"' | xargs rm`

Because the full example gets cluttered and is probably only moving the goalposts:

`mlist ~/Maildir | mpick -t 'mtime < "-365d"' | xargs -d '\n' -r rm



  parent reply	other threads:[~2023-03-30 14:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:39 [ISSUE] " hills
2023-03-30 13:43 ` leahneukirchen
2023-03-30 14:02 ` hills [this message]
2023-03-30 14:06 ` leahneukirchen
2023-03-30 14:06 ` leahneukirchen
2023-03-30 14:13 ` hills
2023-10-27  7:32 ` Anachron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230330140200.nWm9CJVYxu3l5IXRi2wJjHMrnC8_X3SWJEY7jxaDtSI@z \
    --to=hills@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).