måndag 15 april 2019 kl. 19:46:14 CEST skrev Andreas Metzler: > 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.
So it has BDAT lines in it? > 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". :-( Well, now that I look closer (it's been too long since I did that) I realise that of couse the headers are available and manipulated through the header_line structs in memory and that it's only the body that's read from and written to the fd, so there should be no problems if SARewriteBody is set to 0 in sa-exim.conf (which is the default). > I have not tested it but I suspect it might break even more when > spool_wireformat is set. Isn't it the case that if CHUNKING has been offered AND spool_wireformat is set, then the body files are in an alternate format? read_message_bdat_smtp() looks like it is like the good old read_message_data_smtp() but for CHUNKING. And the documentation for spool_wireformat says "If this option is set, Exim may for some messages use an alternative format for data-files in the spool which matches the wire format. Doing this permits more efficient message reception and transmission. Currently it is only done for messages received using the ESMTP CHUNKING option." So it seems that everything should work unless spool_wireformat=true *and* SARewriteBody: 1. How do I detect in sa-exim whether wire format is used for a given body file though? -- Magnus Holmgren holmg...@debian.org Debian Developer
signature.asc
Description: This is a digitally signed message part.
