Re: [exim] Defaults for FreeBSD

Hi! > Unfortunately I don't know right off how to find out who that is. https://www.freshports.org/mail/exim/ has the maintainer listed. This works for all FreeBSD ports, sometimes, it's not a person, but a group. If there's no maintainer, po...@freebsd.org is used. -- p...@opsec.eu

Re: [exim] Issue with Exim on an IPv6-only host

Hi! > My (only) transport included the line: > > hosts_require_auth = $host_address try: hosts_require_auth = <; $host_address otherwise the : from the v6 address is used as list seperator character. -- p...@opsec.eu+49 171 3101372Now what ? -- ## List

Re: [exim] FreeBSD: Moving from BDB5 to BDB18

Hi! > I have deinstalled BDB5 and instead installed BDB18 for the obvious reason. > > Now Exim will not build at all and I am wondering whether it's possible to > build Exim against BDB18. It probably needs some work. The FreeBSD ports community is aware of this problem. No solution right now.

Re: [exim] stuck exim processes

Hi! > I have added the following patch: > > diff --git a/src/src/transports/smtp.c b/src/src/transports/smtp.c > index 6a979a243..f97b0c625 100644 > --- a/src/src/transports/smtp.c > +++ b/src/src/transports/smtp.c > @@ -4800,7 +4800,11 @@ if (sx->send_quit || tcw_done && !tcw) > # ifdef

Re: [exim] stuck exim processes

Hi! > I have a reproducible case on FreeBSD 13.0p7 with exim-4.95_1 from ports > to some recipient. > > What should I test ? Adding commit d2f99aad04 and re-building ? I did that, it did not fix the hung exim outbound process 8-( -- p...@opsec.eu+49 171 3101372

Re: [exim] stuck exim processes

Hi! I have a reproducible case on FreeBSD 13.0p7 with exim-4.95_1 from ports to some recipient. What should I test ? Adding commit d2f99aad04 and re-building ? - Problem: exim outbound, mails hang - those two processes 47118 - IXs 0:00.02 /usr/local/sbin/exim -Mc 1nWfgZ-000CFx-95 47122

Re: [exim] Exim 4.95: growth kern.openfiles

Hi! > No, from FreeBSD port. > > Do you build from source?  If so, please try the attached patch. If you build from port, dropping the patch as /usr/ports/mail/exim/files/patch-debug-openfiles and rebuilding should probably work. I'll try it on my test-box soonish. -- p...@opsec.eu

Re: [exim] Exim 4.95: growth kern.openfiles

Hi! > inum 2327639 - /usr/local/share/certs/ > > # fstat -p 8418 | grep 2327639 -c > 2754 > > It's a bug? Another datapoint: Similar on FreeBSD 14.0, but with /etc/ssl/ instead. -- p...@opsec.eu+49 171 3101372Now what ? -- ## List details at

Re: [exim] Virtual mailboxes not working on new install.

Hi! > What I currently have and need to replicate is as follows. Have a look at https://exim4u.org/, it should cover this. I have not tested it, but the project looks alive enough to be usable. -- p...@opsec.eu+49 171 3101372Now what ? -- ## List details at

Re: [exim] Exim 4.94 Taint issues

> On 2020-07-18 05:22, Andreas Metzler wrote: [...] > I strongly believe it would be very helpful, if the developers would rewrite > some of these configurations and publish it in the documentation. If any of you can provide a patch to the docs, that would help the very busy developers in a big

Re: [exim] de-tainting

Hi! > That fact that string sub-sitution and matching parts don't even work > now is a real problem... > > data = ${expand:"|/command -c ${if match > {$local_part}{.*foo[\-\+]([a-z0-9]+).*}{$1}{}}"} One thing I'll test is if we hand values over to perl, maybe we'll get back untainted

Re: [exim] De-tainting

Hi! > The concept "de-tainting" appears in the index, but not in the manual. Yes, but: Jeremy can't do all the heavy lifting all by himself. We need to help him. Write docs etc. -- p...@opsec.eu+49 171 3101372Now what ? -- ## List details at

Re: [exim] Tainted filename for search in Exim 4.94-1

Hi! Jeremy wrote: > On 18/06/2020 13:43, Vladislav Georgiev | NS1.bg via Exim-users wrote: > > 2020-06-18 15:26:49 Tainted filename for search: '/etc/valiases/domain.com' > > Docs, concept index, de-tainting. Ah, thanks! I'm having the same problems with our config template and this looks like

Re: [exim] tainted string in 4.93

Hi! > After an upgrade to 4.93 from 4.92 (FreeBSD ports), I am getting > > > 2020-02-24 18:13:08 1j67LU-0005vG-1C == a...@ish.com.au R=localuser > T=local_delivery defer (0): Expansion of > "${local_part}${local_part_suffix}@$domain" from command > "/usr/local/libexec/dovecot/dovecot-lda -a >

Re: [exim] How to submit a patch

Hi! > What is the preferred way thse days? Pull request on github? Submit them to https://bugs.exim.org/ -- p...@opsec.eu+49 171 3101372One year to go ! -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at

Re: [exim] Virtual Users

Hi! > I am hoping I am missing something here, but is there a commonly-used > database-based exim management system that controls virtual users and their > domains? I keep finding Postfix solutions, but have no desire to change to > that MTA system. http://exim4u.org -- p...@freebsd.org

Re: [exim] Exim & DANE .. status ?

Hi! > From a practical (i know the theory too) security view DANE "by" > DNSSEC is much less useful then in theory and compared to other > usual / even more modern technologies / standards (which are easier > to deploy at any level, even required with DNSSEC and depend less > from complex trust

Re: [exim] Exim & DANE .. status ?

Hi! > >> the german office of security ( BSI ) has given out a policy, that > >> secure emailserver should have implemented DANE. > > Can you elaborate ? Where / when did BSI say so ? > You can find it here: > >

Re: [exim] Exim & DANE .. status ?

Hi! > the german office of security ( BSI ) has given out a policy, that > secure emailserver should have implemented DANE. Can you elaborate ? Where / when did BSI say so ? -- p...@opsec.eu+49 171 31013722 years to go ! -- ## List details at

Re: [exim] compiling 4.91 under FreeBSD

Hi! > Had someone this error? Using port: Can you provide a make showconfig output ? On what FreeBSD version ? I've testbuilded on current, looks OK. -- p...@opsec.eu+49 171 31013722 years to go ! -- ## List details at

Re: [exim] How to rewrite From: header of offsite forwards only to prevent Amazon SES 554 error

Hi! Now that someone points to ARC as that might be in our future, does anyone already have a ARC implementation for exim ? > https://tools.ietf.org/html/draft-ietf-dmarc-arc-protocol-12 -- p...@opsec.eu+49 171 3101372 2 years to go ! -- ## List details at