Author r.david.murray
Recipients Eric Lafontaine, Henning.von.Bargen, maciej.szulik, r.david.murray
Date 2016-12-19.19:46:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482176809.14.0.449330157037.issue28879@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation is all in the Doc subdirectory of the checkout.

So, this should teach me to rely on vague memory instead of reading the code.  I've probably still missed something because I don't have enough time to read it properly.

Yes, you are correct, the Resent headers need to be added by the user.  So adding a Resent-Date header is the only question, and we can assume that it should go before the first Resent-X header we find.

Here is my reconstruction of why I made that restriction and comment:  There is no specified order to the Resent- block headers.  So how do we know where the first block ends and the next begins?  It will almost always be at the Resent-Date header...but we can't assume that that will *always* be true.

For sendmail/send_message, I'm not going to look at a youtube video, so you'll have to make your argument in text :)  But you may not want to bother, it is indeed too late: we can't change the signature for backward compatibility reasons.  In any case IMO the signature is optimal as it is: the only required argument is msg, and that, therefore, has to come first.  Otherwise the arguments are already in the same order as they are for sendmail.

I spent a lot of time reading RFCs while working on these libraries, but it has been a while since my head was buried in that space :)
History
Date User Action Args
2016-12-19 19:46:49r.david.murraysetrecipients: + r.david.murray, maciej.szulik, Henning.von.Bargen, Eric Lafontaine
2016-12-19 19:46:49r.david.murraysetmessageid: <1482176809.14.0.449330157037.issue28879@psf.upfronthosting.co.za>
2016-12-19 19:46:49r.david.murraylinkissue28879 messages
2016-12-19 19:46:48r.david.murraycreate