From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Wong <e@80x24.org>
Cc: Alyssa Ross <hi@alyssa.is>, meta@public-inbox.org
Subject: Re: Do I need multiple publicinbox.<name>.address values?
Date: Thu, 10 Oct 2019 05:56:01 -0500 [thread overview]
Message-ID: <877e5c50ou.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20191010083132.GA14886@ailurophile> (Eric Wong's message of "Thu, 10 Oct 2019 08:31:32 +0000")
Eric Wong <e@80x24.org> writes:
> "Eric W. Biederman" <ebiederm@xmission.com> wrote:
>> Eric Wong <e@80x24.org> writes:
>>
>> > "Eric W. Biederman" <ebiederm@xmission.com> wrote:
>> >> my $tracker = PublicInbox::IMAPTracker->new();
>> >
>> > Thanks. What's PublicInbox::IMAPTracker?
>>
>> Something that keeps the last fetched UID in an sqlite database.
>> I will follow up with a patch for that as well.
>
> Thanks!
>
>> I haven't been brave enough to let this script delete any mail
>> yet so I need to track what has been fetched. Something that
>> will be rolled back if the email message isn't commited into git.
>>
>> I have a companion script that will delete mail.
>
> Yup. I also don't trust and don't want somebody trusting my
> code when it comes to deleting stuff.
>
> So I've also been considering a script which deletes mail from
> my Maildirs/IMAP folders if a ContentId matches what's in a
> known public-inbox, perhaps after a certain time...
Interesting.
Partly I have been leaving things up so I could restart the process
if the script fails.
I like the idea of a verifier/deleter.
I have a delete up to my imap tracker script. A verifier will probably
share a lot of logic with the imap importer script, but since it only
has to confirm something is stable before deleting, it isn't quite the
same.
Time permitting I will play with that next.
Eric
next prev parent reply other threads:[~2019-10-10 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 22:13 Do I need multiple publicinbox.<name>.address values? Alyssa Ross
2019-10-08 0:10 ` Eric Wong
2019-10-08 12:18 ` Eric W. Biederman
2019-10-08 12:23 ` [PATCH] Config.pm: Add support for mailing list information Eric W. Biederman
2019-10-08 22:11 ` Do I need multiple publicinbox.<name>.address values? Eric Wong
2019-10-08 22:24 ` Eric W. Biederman
2019-10-08 22:41 ` Eric Wong
2019-10-09 7:58 ` Eric W. Biederman
2019-10-09 8:15 ` [PATCH 0/4] Various bits to support import_imap_mailbox Eric W. Biederman
2019-10-09 8:16 ` [PATCH 1/4] PublicInbox::Import Smuggle a raw message into add Eric W. Biederman
2019-10-15 20:26 ` Eric Wong
2019-10-15 23:05 ` Eric W. Biederman
2019-10-09 8:17 ` [PATCH 2/4] PublicInbox::Config: Process mailboxes in sorted order Eric W. Biederman
2019-10-10 9:43 ` Eric Wong
2019-10-10 11:05 ` Eric W. Biederman
2019-10-09 8:23 ` [PATCH 3/4] Config.pm: Add support for looking up repos by their directories Eric W. Biederman
2019-10-09 8:25 ` [PATCH 4/4] IMAPTracker: Add a helper to track our place in reading imap mailboxes Eric W. Biederman
2019-10-10 19:08 ` ibx->{listid} autoviv fixup [was: [PATCH 0/4] Various bits to support import_imap_mailbox] Eric Wong
2019-10-10 21:23 ` Eric W. Biederman
2019-10-10 8:31 ` Do I need multiple publicinbox.<name>.address values? Eric Wong
2019-10-10 10:56 ` Eric W. Biederman [this message]
2019-10-09 11:59 ` Alyssa Ross
2019-10-10 10:06 ` 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: http://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=877e5c50ou.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=e@80x24.org \
--cc=hi@alyssa.is \
--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).