-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refine and document Envelope fields #31
Comments
My reading of the spec is different at least for As for the others, I worry that servers might not correctly implement some of these things, leading the parser to choke on things that could still usefully be returned to the caller. I'll see if I can check this against my personal mail archive, at least. |
Ah, yes, I think you're right about Yeah, that's probably a good idea as a sanity check. We could of course implement the fallback inside |
@djc did you have a chance to try to run against your mail archive? |
Nope, not yet -- ran into some problems getting my mailsync code to run with the latest compiler/dependencies and it's been very busy. 😞 |
RFC 3501 section 7.4.2 has a lot to say about envelopes that would be handy to include in the docs for
Envelope
. Beyond that though, there are some observations there that I think affectEnvelope
's types. Specifically:Implies that
Envelope::date
should not be anOption
.Implies the same for
Envelope::in_reply_to
andEnvelope::message_id
.Implies the same for
Envelope::from
,Envelope::sender
, andEnvelope::reply_to
.The text was updated successfully, but these errors were encountered: