I missed this instance of file slurping into an Email::MIME-like
object the other week when tearing Email::MIME usage out.
---
t/edit.t | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/t/edit.t b/t/edit.t
index 1a5698f6..4b004c1c 100644
--- a/t/edit.t
+++ b/t/edit.t
@@ -24
The perlop, `readline', and `read' functions will all
retry on EINTR, so there's no need to retry and loop ourselves
with `sysread'.
---
lib/PublicInbox/Spamcheck/Spamc.pm | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/lib/PublicInbox/Spamcheck/Spamc.pm
b/lib/Publi
These aren't really supported and will probably be replaced with
better tools, but PublicInbox::Eml should be readily available
to anybody who already has our source tree.
---
scripts/import_maildir | 7 +++
scripts/import_slrnspool | 4 ++--
2 files changed, 5 insertions(+), 6 deletions(-)
TL;DR: is 50K messages a reasonable IMAP folder size?
So far, the IMAP daemon code shares quite a bit of data and
logic with the NNTP code. NNTP article numbers are reusable as
IMAP UIDs; and for small inboxes, newsgroups can be an IMAP
folder. But that only works for small inboxes...
One major