------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=846
--- Comment #7 from Johannes Berg <johannes@???> 2009-05-01 09:36:40 ---
(In reply to comment #6)
> Adding extra config to turn on your feature isn't ideal, correct. However, all
> minor revision changes should be backwards compatible or you break systems. As
> I understand it, this is the way Exim updates have always happened. If we were
> moving from Exim 4 to Exim 5 rather than from one version of Exim 4 to another
> then yes, it would be ok, but we're not...
>
> The majority of people don't expect upgrading from 4.69 to 4.70 to require them
> to change their configuration, for things to continue to work as normal.
Exactly. As much as I like the feature and would love to have it, I don't think
there's a chance it can be added soon. I'd rather have it soon with config
option rather than wait (probably forever) until it can be added a little
cleaner.
It's also not always trivial to add header lines after spam scanning, since you
might have code adding header lines in ACLs before DATA, and now you'd have to
rewrite your config to store those in an acl_m_ variable and add them later
${if def:acl_m_...} -- rather complex.
Also, can you explain DKIM considerations? Exim always seems to add header
lines after (or before) all others and afaik DKIM says explicitly which are
signed, so I'm not sure I see the problem?
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
