Bug#486437: exim4: Make source compatible with libdkim-1.0.19

[Russell Stuart]

On Mon, 2008-06-16 at 18:58 +0200, Andreas Metzler wrote:
> I was of the opinion that exim was not supposed to be buildable
> against the (yet) released libdkim, since exim required additionial
> stuff in liblibdkim. - This seems to be the point of the libdkim in
> experimental.
> http://packages.qa.debian.org/libd/libdkim/news/20080517T221723Z.html

I wasn't aware of dkim in experimental.  I submitted an 
identical patch to 30_extra_fields.dpatch in 
libdkim_1.0.19-1exp1+eximdkim, only to have Magnus
make the same point.

It doesn't fix the problem entirely though.  Although I 
have not tried, I don't think exim4-4.69-5 would compile 
against libdkim_1.0.19-1exp1+eximdkim without this patch.
The issue is libdkim's upstream decided to gratuitously 
rename some fields in a structure as of libdkim-1.0.19.  
The exim4 source has to be modified to use the new field 
names.  I presume upstream will do this in due course.

I know this is really upstream's problem.  The only reason 
I submitted this (and the libdkim patch for that matter), 
is it would be nice to have exim4 in lenny compile cleanly
with dkim support - even though it is not enabled by
default.  I am sure there are quite a few people who, like 
me who will want to enable it for exim4-daemon-custom.  
I think exim4 + this patch + libdkim in experimental is 
the cleanest way to achieve that goal.