You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ponymail.apache.org by GitBox <gi...@apache.org> on 2021/06/09 11:30:45 UTC

[GitHub] [incubator-ponymail-foal] Humbedooh commented on issue #44: DKIM-ID is incompatible with stdin mode archiving

Humbedooh commented on issue #44:
URL: https://github.com/apache/incubator-ponymail-foal/issues/44#issuecomment-857617272


   >  If `archiver.py` is used in stdin mode then it typically receives an email before the mailing list manager has added the `List-Id` and other such headers, and before it may have made any of the other DKIM changes listed in [RFC 6377 § 3.3](https://datatracker.ietf.org/doc/html/rfc6377#section-3.3).
   
   What leads you to believe this? From what I can tell, from experience, the vast majority of use cases out in the wild, probably 9 out of 10, are using stdin mode for archiving by subscribing the archiver as a standard consumer. In such cases, it would get the emails with the final headers appended/munged, and there would be no problem. In which cases are you seeing otherwise?
   
   I can see the argument that we perhaps should note that the place we hook into the email infrastructure can have a say on the ID consistency, but I don't see this as a very common case.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org