[Pkg-exim4-users] Compiling Debian exim4 with dmarc support

ian-exim4 at zsd.co.za ian-exim4 at zsd.co.za
Wed May 11 10:32:15 BST 2022

On 5/10/22 22:36, Adam D. Barratt wrote:
> On Tue, 2022-05-10 at 15:11 -0400, Ian Kelling wrote:
>> ian-exim4 at zsd.co.za writes:
>>> But this is not viable on a long term basis, we have many servers
>>> to
>>> support and there will be security and other updates to deal with
>>> going
>>> forward. So I am looking forward for this to getting resolved
>>> somewhere
>>> upstream.
>> Thank you Ian for working on this. I think the Debian exim maintain
>> is
>> not especially active, someone else may need to take the initiative.
> The upload history of the package doesn't particularly suggest that,
> IMO.
> In any case, upstream are aware - see
> https://bugs.exim.org/show_bug.cgi?id=2728

I can't complain about the Debian Exim maintenance team. It is a complex 
package and e-mail is a complex and changing environment. Managing new 
developments without breaking millions of e-mail deliveries on existing 
servers is a minefield. My experience is that their track record over 
many years has been pretty good. My only wish would be for better, up to 
date, documentation of the debian packaging features and issues.

I am not sure if packaging dependency rules could be crafted to make a 
specific version of exim4 source package depend on a specific version of 
the dmarc library?

If dmarc (and internal spf) support was included in exim4-daemon-heavy, 
I suspect it maybe easier to manage the dependencies. Perhaps it is time 
to review that policy?



More information about the Pkg-exim4-users mailing list