Re: [exim] converting from debian package to source

2022-01-09 Thread Zakaria via Exim-users
It seems you are right indeed. Compatibility has to be taken into consideration, using OpenDMARC library version that is accessible from headers, I guess a mere of an if statement should handle two code blocks for post to 1.3.2 and up to 1.3.2, in relation to this specific " few

Re: [exim] converting from debian package to source

2022-01-09 Thread Andreas Metzler via Exim-users
On 2022-01-09 Zakaria via Exim-users wrote: >> On 9 Jan 2022, at 11:44, Jeremy Harris via Exim-users >> wrote: >> On 08/01/2022 18:30, Edwin Balani via Exim-users wrote: >>> Can't you rely on OPENDMARC_LIB_VERSION? It's defined in dmarc.h: >> Quite possibly. Now, is the changed API

Re: [exim] converting from debian package to source

2022-01-09 Thread Zakaria via Exim-users
Also, the EXIM reference of opendmarc_policy_store_dkim its in https://github.com/Exim/exim/blob/e3e281ccf9d8777d0df98ddd644720573e0343d1/src/src/dmarc.c “ libdm_status = opendmarc_policy_store_dkim(dmarc_pctx, US sig->domain, dkim_result, US""); " While following new OpenDMARC method

Re: [exim] converting from debian package to source

2022-01-09 Thread Zakaria via Exim-users
I spent an amount of time trying to get latest DMARC work against master EXIM, over last few weeks. It was only one method DMARC has refactored, with extra parameter, and EXIM integration isn’t it taking into account. I found this bug issue opened on

Re: [exim] converting from debian package to source

2022-01-09 Thread Jeremy Harris via Exim-users
On 08/01/2022 18:30, Edwin Balani via Exim-users wrote: Can't you rely on OPENDMARC_LIB_VERSION?  It's defined in dmarc.h: Quite possibly. Now, is the changed API documented? Or are we supposed to inspect the libdmarc code and watch for API-breaking changes, evermore? And *guess* from the

Re: [exim] converting from debian package to source

2022-01-08 Thread Sabahattin Gucukoglu via Exim-users
On 8 Jan 2022, at 14:07, Julian Bradfield via Exim-users wrote: > My mail servers run, and have run for decades, on Debian, and I've > always used the Debian package for exim4, though I don't use debconf > for my own additions, but just edit the conf.template file as if it > were a .conf file. >

Re: [exim] converting from debian package to source

2022-01-08 Thread Heiko Schlittermann via Exim-users
Hi Julian, Julian Bradfield via Exim-users (Sa 08 Jan 2022 15:07:01 CET): > My mail servers run, and have run for decades, on Debian, and I've > always used the Debian package for exim4, though I don't use debconf > for my own additions, but just edit the conf.template file as if it > were a

Re: [exim] converting from debian package to source

2022-01-08 Thread Jasen Betts via Exim-users
On 2022-01-08, Odhiambo Washington via Exim-users wrote: > On Sat, Jan 8, 2022 at 5:26 PM Julian Bradfield via Exim-users < > exim-users@exim.org> wrote: > >> My mail servers run, and have run for decades, on Debian, and I've >> always used the Debian package for exim4, though I don't use debconf

Re: [exim] converting from debian package to source

2022-01-08 Thread Julian Bradfield via Exim-users
On 2022-01-08, Slavko (tblt) via Exim-users wrote: >>So I suppose the question is: if I drop the master-source-built binary >>on top of the Debian one, what can I expect to break? > AFAIK spfquery is used in debian's exim for years, thus i am confused, why it > is problem for you right now,

Re: [exim] converting from debian package to source

2022-01-08 Thread Evgeniy Berdnikov via Exim-users
Hello. On Sat, Jan 08, 2022 at 03:27:45PM +, Julian Bradfield via Exim-users wrote: > Specifically, I don't like the idea of installing an external tool > spfquery and using the slightly clunky config snippet to use it, > rather than using the built-in spf - I like things in the exim4

Re: [exim] converting from debian package to source

2022-01-08 Thread Edwin Balani via Exim-users
On Sat, Jan 08, 2022 at 05:02:10PM +, Jeremy Harris via Exim-users wrote: The dmarc library project appears to have changed their API in a incompatible fashion. It's difficult to tell, because there is no visible documentation and no obvious way to discover the library version at build

Re: [exim] converting from debian package to source

2022-01-08 Thread Andreas Barth via Exim-users
* Julian Bradfield via Exim-users (exim-users@exim.org) [220108 16:36]: > However, I also don't like fiddling with systems more than necessary - > sysadmin is not my job, it's just what I have to do to make things > work. If I have to go the trouble of building my own Debian package, I > might as

Re: [exim] converting from debian package to source

2022-01-08 Thread Andrew C Aitchison via Exim-users
On Sat, 8 Jan 2022, Julian Bradfield via Exim-users wrote: On 2022-01-08, Andreas Barth via Exim-users wrote: * Julian Bradfield via Exim-users (exim-users@exim.org) [220108 15:18]: The pain of dealing with Debian's antiquated versions (4.92) and gratuitous messing around with upstream's

Re: [exim] converting from debian package to source

2022-01-08 Thread Jeremy Harris via Exim-users
On 08/01/2022 16:31, Slavko (tblt) via Exim-users wrote: new version of DMARC lib, which fails to build with exim The dmarc library project appears to have changed their API in a incompatible fashion. It's difficult to tell, because there is no visible documentation and no obvious way to

Re: [exim] converting from debian package to source

2022-01-08 Thread Zakaria via Exim-users
Hi Julian, I installed exim from source, and here is my input. Expect to start with all configuration being set in one file when you install from source. I used Dovecot as IMAP server, for security purposes disabled startttls in port 587 for smtp in exim and 143 + startttls for

Re: [exim] converting from debian package to source

2022-01-08 Thread Slavko (tblt) via Exim-users
Dňa 8. januára 2022 15:27:45 UTC používateľ Julian Bradfield via Exim-users napísal: >So I suppose the question is: if I drop the master-source-built binary >on top of the Debian one, what can I expect to break? IMO nothing will break, except two things: + many ACL & routers presets, which

Re: [exim] converting from debian package to source

2022-01-08 Thread Jeremy Harris via Exim-users
On 08/01/2022 15:27, Julian Bradfield via Exim-users wrote: (Tainting is the main thing I'm aware of as a risk.) It's also a major benefit, because it shows up places in your config where you have coded in a manner vulnerable to attack. -- Cheers, Jeremy -- ## List details at

Re: [exim] converting from debian package to source

2022-01-08 Thread Jeremy Harris via Exim-users
On 08/01/2022 15:27, Julian Bradfield via Exim-users wrote: I like things in the exim4 manual to work in my installation! The manuals for old releases are available on the Exim website. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim

Re: [exim] converting from debian package to source

2022-01-08 Thread Julian Bradfield via Exim-users
On 2022-01-08, Andreas Barth via Exim-users wrote: > * Julian Bradfield via Exim-users (exim-users@exim.org) [220108 15:18]: >> The pain of dealing with Debian's antiquated versions (4.92) and >> gratuitous messing around with upstream's configuration (most recent >> annoyance, not supporting

Re: [exim] converting from debian package to source

2022-01-08 Thread Odhiambo Washington via Exim-users
On Sat, Jan 8, 2022 at 5:26 PM Julian Bradfield via Exim-users < exim-users@exim.org> wrote: > My mail servers run, and have run for decades, on Debian, and I've > always used the Debian package for exim4, though I don't use debconf > for my own additions, but just edit the conf.template file as

Re: [exim] converting from debian package to source

2022-01-08 Thread Jeremy Harris via Exim-users
On 08/01/2022 14:07, Julian Bradfield via Exim-users wrote: I wonder if anybody on this list has done such a conversion recently, and would have time to share the chief gotchas they encountered. Not directly, but: ALWAYS read the ChangeNotes file when changing versions. It's there for good

Re: [exim] converting from debian package to source

2022-01-08 Thread Andreas Barth via Exim-users
* Julian Bradfield via Exim-users (exim-users@exim.org) [220108 15:18]: > The pain of dealing with Debian's antiquated versions (4.92) and > gratuitous messing around with upstream's configuration (most recent > annoyance, not supporting built-in SPF) is prompting me to think about > switching to

[exim] converting from debian package to source

2022-01-08 Thread Julian Bradfield via Exim-users
My mail servers run, and have run for decades, on Debian, and I've always used the Debian package for exim4, though I don't use debconf for my own additions, but just edit the conf.template file as if it were a .conf file. The pain of dealing with Debian's antiquated versions (4.92) and