On 2019-04-14 Magnus Holmgren <holmg...@debian.org> wrote: > fredag 12 april 2019 kl. 19:23:40 CEST skrev du: >> The dlopen localscan patch in exim4 has been nonfunctional in unstable >> for quite some time (4.92~RC2-1/experimental/18 Dec, 4.92~RC3-1 >> unstable/26 Dec and buster/03 Jan). The issue only popped up end of >> March on the upstream user support ML.
>> At this time I opened a tracking bug in exim #925982 and looked at >> sa-exim. It is dead upstream since 2006 and buggy: >> * https://lists.exim.org/lurker/message/20180726.113354.6d03efde.en.html >> * #879687 > I've seen reports of bugs, but I didn't realise it was that bad. > sa-exim hasn't exactly changed; has the way local_scan() is called > changed? It's supposed to get an fd, read a message from it, and > possibly write an altered message back (after piping it through > spamc). What can "Format error in spool file" mean? Hello, Afaiu basically exim has got a new feature and in that case (CHUNKING) the spoolfile looks a little bit differently and sa-exim fails to handle this special case properly. Even in version 4.14 exim's documentation said | The file is open for reading and writing, but updating it is not | recommended which I'd read as "you may keep both pieces if it breaks". :-( I have not tested it but I suspect it might break even more when spool_wireformat is set. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
