It looks like this is indeed an exim issue that was fixed in a recent update. exim bug report can be found at: https://bugs.exim.org/show_bug.cgi?id=2886
It looks like this is indeed an exim issue that was fixed in a recent update. exim bug report can be found at: https:/ /bugs.exim. org/show_ bug.cgi? id=2886