From: Konstantin Ryabitsev <email@example.com> To: firstname.lastname@example.org Subject: Re: watch a simple dir Date: Fri, 26 Feb 2021 14:29:43 -0500 [thread overview] Message-ID: <CAMwyc-SmvBoVOs+vCMNaWOWPT3TCB-7rJ_0bp43QB+pjzbNvemail@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, 26 Feb 2021 at 09:38, Konstantin Ryabitsev <email@example.com> wrote: > - it's a simple flat dir of numeric files corresponding to the number of the > message in the index > - each message is a valid rfc2822 document -- in fact, if I copy them into the > "new" folder of any maildir, I can read them with mutt > - however, if I use symlink trickery to make mlmmj deliver into "new" or "cur" > of a maildir monitored by public-inbox-watch, they are ignored -- so things > are not as easy as that. :) Probably, it expects to have more complex > filenames instead of just a number, but I didn't dig too deep. Ah, looks like this was only a limitation of v1.6.1 -- master doesn't require that filenames in new/ contain a :2 (which is not a requirement for maildir files in "new/" -- they merely need to be unique; the :2, part is required for cur/ entries for adding flags). So, this will work out just fine as long as this behaviour doesn't go back to what is in 1.6.1 (which it shouldn't). Simply symlinking /var/spool/mlmmj/<listname>/archive to <some-maildir-elsewhere>/new is sufficient to automatically add mlmmj messages to the public-inbox archive and, as an added bonus, this will properly respect control/noarchive settings. Me pleased. -K
next prev parent reply other threads:[~2021-02-26 19:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-26 14:38 Konstantin Ryabitsev 2021-02-26 19:29 ` Konstantin Ryabitsev [this message] 2021-02-26 19:38 ` Eric Wong
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 List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAMwyc-SmvBoVOs+vCMNaWOWPT3TCB-7rJ_0bp43QB+pjzbNvfirstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: watch a simple dir' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).