Hi Magnus, On 05-05-2019 23:42, Magnus Holmgren wrote: > after some investigation, I believe I have the issues in sa-exim under > control. The broken spool files were due to a memory corruption that could > easily be worked around. The issue with CHUNKING was mainly that SpamAssassin > uses CRLF to terminate header lines when the input message uses CRLF line > endings, and the CR needs to be stripped. With this taken care of, I don't > think SA-Exim is so buggy that it needs be removed from Debian. It does have a > couple of advantages over the built-in spam ACL conditions, as outlined in > README.Debian. I expect that for your package to remain useful the exim maintainers will have to drop the changes that are currently in unstable, am I right? Please align that with them. Also make sure you can help them moving forward with their unblock request, by making sure your *targeted* fixes are available in unstable. sa-exim would need to be unblocked first or at the same time, so don't add unnecessary changes to your package and file an unblock request when your package lands in unstable. If your changes are acceptable and accepted your package won't be dropped from buster, but until that happens, autoremoval may still remove your package and we may remove your package if fixing it stalls the release process. Please keep the ball rolling. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature