------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1142
--- Comment #7 from Phil Pennock <pdp@???> 2011-09-03 13:21:40 ---
Breaking mails arbitrarily, in the middle of MIME structure? While passing on
the message, including DKIM signatures (since that read data will have been
verified)?
We're talking about making Exim deliberately corrupt a mail, and providing a
hook to corrupt mail where we assume that postmasters will be wise enough to
always configure the backing to catch the corruption.
While I understand that it's nicer all around when patches are accepted
upstream, sometimes needed functionality just has to live locally and be
patched in as needed.
If this we going to be accepted into Exim main, then we'd need some stronger
safety checks, such as a new mode for delivery (like "verify") which tastes
Routers and the Router needs to set accept_incomplete to take the message, and
no Router without that flag would accept Routing it. Also, authentication
headers relating to DKIM would then need to be renamed to an X-Incomplete-*
prefix, so that the mails aren't just rejected elsewhere. I know, the current
intent is only for Submission, but the features are often used in ways other
than that which the original requester envisioned, whether for good or ill.
That's a lot more to take on than adjusting a couple of additions as the
current patch does -- it's a good clean patch, nothing wrong in the code, only
in the result. For the one group who need it, is it that onerous to maintain?
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
