From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: watch a simple dir
Date: Fri, 26 Feb 2021 09:38:06 -0500 [thread overview]
Message-ID: <20210226143806.6hu2775yroqaqynj@chatter.i7.local> (raw)
Hello:
I'm playing around with using public-inbox as the archiving subsystem for
mlmmj. I know it's possible to simply configure a local address to deliver to
public-inbox-mda [1], but I wonder if there's a way to reduce complexity and
simply configure public-inbox-watch to monitor mlmmj's "archive" directory for
any new files, similar to how it would monitor a maildir:
- 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.
So, any way to make this work either by tricking public-inbox-watch to
recognize these as valid maildir entries, or by teaching it to monitor simple
additions to a dir as parallel scheme to maildir:?
-K
[1] adding an extra hop to deliver to public-inbox-mda, or to a maildir
monitored by public-inbox-watch adds another entry into the postfix queue,
bloats the headers by adding more Received: lines and generally seems like an
inefficient way to basically copy a file that already exists on the filesystem
next reply other threads:[~2021-02-26 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 14:38 Konstantin Ryabitsev [this message]
2021-02-26 19:29 ` watch a simple dir Konstantin Ryabitsev
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=20210226143806.6hu2775yroqaqynj@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).