From: Eric Wong <e@80x24.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: meta@public-inbox.org
Subject: Re: public-index-{watch,mda}
Date: Mon, 2 Apr 2018 18:04:08 +0000 [thread overview]
Message-ID: <20180402180408.GA32637@80x24.org> (raw)
In-Reply-To: <20180402083615.3edf34ed@lwn.net>
Jonathan Corbet <corbet@lwn.net> wrote:
> I have a question on public-index-watch v. public-index-mda; sending to
> the list since I might not be the only one. I've seen a couple of times
> that you recommend public-index-watch for maintaining a mirror of a
> mailing list whose home is elsewhere. But I would rather use
> public-inbox-mda since that doesn't require keeping a duplicate maildir
> around that's just wasted space.
I've been thinking along the same lines. For now:
find $MAILDIR -type f -ctime +1 | xargs rm -f
is reasonably good at not removing files.
> So I'm wondering: is there a reason *not* to use public-inbox-mda for this
> use case beyond the rather aggressive filtering that it does? If not,
> would you entertain a patch to make that filtering optional?
The big reason is -watch is safer in case of bugs in our code and
can recover with readdir scans (instead of bouncing and making
other mail admins unhappy).
I also expect -watch to be more useful for people who do not run
their own MTA.
I'm open to accepting patches to make -mda more configurable and
perhaps being able to share configuration with -watch; but the
defaults need to remain for compatibility.
I think time would be better spent giving -watch an optional new
feature which provides the following three options:
1) move-to-another-Maildir-on-import
2) mark-message-as-trash-on-import (add 'T' to filename flag)
3) unlink-on-successful-import (needs to be delayed
until fast-import is done writing (im->checkpoint or im->done)
Thanks.
prev parent reply other threads:[~2018-04-02 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 14:36 public-index-{watch,mda} Jonathan Corbet
2018-04-02 18:04 ` Eric Wong [this message]
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=20180402180408.GA32637@80x24.org \
--to=e@80x24.org \
--cc=corbet@lwn.net \
--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.
Code repositories for project(s) associated with this public 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).