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: Wed, 09 Oct 2019 02:58:45 -0500 Message-ID: <87h84ibb9m.fsf@x220.int.ebiederm.org> (raw) In-Reply-To: <20191008224104.GA24142@dcvr> (Eric Wong's message of "Tue, 8 Oct 2019 22:41:04 +0000") 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. 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. I mostly sent it so that there is some idea what I am working with. In context of this discussion I don't remember how often I am looking at the "Delivered-To:" header. That is almost gone but I know for a while I was using that as well. >> for (;;imap_sleep()) { >> # Run fetch_mail in it's own separate process so >> # that if something goes wrong the process exits >> # and everything cleans up properly. >> # >> # Running fetch_mail in an eval block is not enough >> # to prevent leaks of locks and other resources. > > I was thinking along the same lines :) > > The rest looked good and it's definitely something I can work > with to get supportable in a way that reuses git's credential > system and configs. I think fundamentally the script sucks because it is one email message at a time (not using IMAPs overlapping), the script is polling (NOT using IMAP idle), and I have magic to go from the server that I need to fetch to the actual domain. But in practice the script seems to be working reliably even in the event of an error right now. Eric
next prev parent reply other threads:[~2019-10-09 7:59 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-07 22:13 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 [this message] 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 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: 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=87h84ibb9m.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
user/dev discussion of public-inbox itself This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \ meta@public-inbox.org public-inbox-index meta Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.io/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/public-inbox.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git