For reference, here's the RFC: https://tools.ietf.org/html/rfc5064
Side note, mbox is really not supposed to be used for a mail backend. You'll need to read the whole archive on startup, and all write operations will require you to rewrite the whole file. Also, things like flags are not supported.
Some people configure their server to send automated (e.g. out-of-office) replies.
Auto-Submittedheader fields can help detecting those.
We probably shouldn't forward out-of-office-like emails.
Microsoft Outlook has its own set of non-standard header fields, of course: https://www.jitbit.com/maxblog/18-detecting-outlook-autoreplyout-of-office-emails-and-x-auto-response-suppress-header/
Here's a build failure I've received:
mrsh/alpine.yml #77433: FAILED in 36s [6770e0d](https://git.sr.ht/~sircmpwn/mrsh/commit/6770e0de0ae18cb976e3b3bdb7e115432949952e) — [Drew DeVault](mailto:firstname.lastname@example.org) <pre>Add configure script and Makefile </pre> https://builds.sr.ht/~sircmpwn/job/77433 ✓ setup ✓ build-gcc ✓ build-clang ✗ test-gcc - test-clang
Annotations containing things like
"to": "#L14"won't correctly link to the current file.
Yes, this is how it should be implemented. POP isn't supported anyway so we can just skip that.
net.LookupSRVcan be used to retrieve those SRV records.
pullstag for PRs,
This allows to export a badge just for commits (instead of having a failing badge when a PR's build fails).
Some folder names that cause the error: All Mail, INBOX, Sent, Folders/x.
That's pretty weird. It would be useful to have a debug log of the TCP communication.