söndag 21 april 2019 kl. 19:55:10 CEST skrev Magnus Holmgren: > But now that I look closer, it looks like the "spool format error" message > is only triggered by malformed header files, and Thomas in https:// > lists.exim.org/lurker/message/20180726.174108.0620f3c0.en.html had narrowed > it down to multiple messages being received over the same connection. I > still haven't been able to reproduce it though. It might be stochastic.
Okay, so as I reported on the exim-dev list, I figured out that primary_hostname, which has been being expanded once and the pointer kept in static memory since forever, is now being overwritten although allocated from the permanent pool. My plan is to change this to expand it anew for each run; that solved the problem when I tested. I'm also going to add an unrelated patch that disables body rewriting when the spool file is in wire format and which handles CRLF line endings when scanning headers. Do you think that you can then re-enable local_scan for the release? -- Magnus Holmgren holmg...@debian.org Debian Developer
signature.asc
Description: This is a digitally signed message part.
