Mail and mbox adapter (fixes #89) #104
Conversation
FliegendeWurst
force-pushed
the
mail-adapter
branch
2 times, most recently
from
81f636a to
e9c5cd4
Compare
FliegendeWurst
force-pushed
the
mail-adapter
branch
from
e9c5cd4 to
4c64bfc
Compare
|
Hey. I'm a bit late here but if you would rebase this I would be happy to merge it. Maybe not too easy because adapters are async now.. |
|
Hi, thanks for the response. I'm actually working on an |
|
uh good luck with that. i tried writing an mbox parser in Rust a few years ago but apparently the mbox format has different incompatible versions that differ in how the "from " line is escaped and I couldn't even find docs about how the mbox format that Firefox uses works |
FliegendeWurst
force-pushed
the
mail-adapter
branch
from
ca0191c to
6ae1fb3
Compare
FliegendeWurst
changed the title
Oh just splitting on "\nFrom " seems to work for mbox files saved by Thunderbird. I think most mbox variantions forbid "\nFrom " in mail content. |
Seems tree_magic does not know about this format
|
|
||
| let mut content = Vec::new(); | ||
| let s = stream! { | ||
| inp.read_to_end(&mut content).await?; |
There was a problem hiding this comment.
reading the whole file into RAM is not good because it may be many gigabytes in size (e.g. firefox mailbox files?)
The new
MboxAdapterprovides the mail content to other extractors (this resolves #89).