Only tested with mpop and getmail as far as real-world clients go. mpop is pretty strict and fast, too; getmail was ignoring sequence number bugs :x
...And now I think I know where IMAP inherited horrible message sequence number idea from :P The on-disk storage aspect still has me a little nervous :x over.sqlite3 is totally overkill (and thus slower than optimal) for this, but I don't think it's worth a schema version change, either. Lot more code cleanups and maybe some optimizations on the way. Eric Wong (2): public-inbox-pop3d - a mostly read-only POP3 server pop3: implement IN-USE from RESP-CODES (RFC 2449) Documentation/public-inbox-config.pod | 12 +- Documentation/public-inbox-pop3d.pod | 122 +++++++ Documentation/standards.perl | 12 +- MANIFEST | 5 + lib/PublicInbox/Config.pm | 5 +- lib/PublicInbox/Daemon.pm | 8 +- lib/PublicInbox/Inbox.pm | 10 +- lib/PublicInbox/POP3.pm | 444 ++++++++++++++++++++++++++ lib/PublicInbox/POP3D.pm | 231 ++++++++++++++ script/public-inbox-pop3d | 8 + t/pop3d.t | 254 +++++++++++++++ 11 files changed, 1094 insertions(+), 17 deletions(-) create mode 100644 Documentation/public-inbox-pop3d.pod create mode 100644 lib/PublicInbox/POP3.pm create mode 100644 lib/PublicInbox/POP3D.pm create mode 100755 script/public-inbox-pop3d create mode 100644 t/pop3d.t
