Re: Is LDAP+SSL supported?
July 25, 2020 2:26 PM, "Éloi Rivard" wrote: >> In my opinion, table-ldap from extras is doomed as it relies on a lib >> that >> is barely maintained and doing LDAP asynchronously is painful. > > Are you saying the support for table-ldap may stop in a near future? > Nope, the table API has been fairly stable for a long time so there is no extra work for me to leave it as is, it won't stop in a near future but I won't invest time in it as... I don't use it. >> I doubt the >> code will go much further than it currently does. > > However, would you still accept patches for ldaps support? > Yes, but I won't test these patches, I'll only review them and it will be easier to get them in if you find a couple users willing to test. >> If the table-procexec work I documented on my blog gets pushed to >> OpenBSD, >> then it will ease the writing of a table-ldap with a modern library. > > I will keep an eye on this then.
Re: smtp-out: Address family mismatch
Hi,
I don't know what this error entails but I took a peek at the source and
found this in mta.c around lines 1575:
if ((c->source->sa &&
c->source->sa->sa_family !=
mx->host->sa->sa_family) ||
(l->family && l->family != mx->host->sa->sa_family)) {
log_debug("debug: mta-routing: skipping host
%s: AF mism
atch",
mta_host_to_text(mx->host));
family_mismatch = 1;
continue;
}
notice there is a DEBUG level log with a conversion indicating which
host it has problems with. Not saying you need to run it in debug mode,
but you can to see this message.
Best Regards,
-peter
On 2020-07-23 09:45, Harald Dunkel wrote:
The Network error on destination MX has been resolved.
The Address family mismatch is still open.
smtpctl show queue gives me
a9f755dd88e88083|inet4|mta||u...@example.com|cont...@bugs.debian.org|cont...@bugs.debian.org|1595227438|1595227438|0|27|pending|29446|Address
family mismatch on destination MXs
ebbe485d057fa820|inet4|mta||u...@example.com|xxx...@bugs.debian.org|xxx...@bugs.debian.org|1595227386|1595227386|0|27|pending|29394|Address
family mismatch on destination MXs
Please note the "inet4" and
% host bugs.debian.org
bugs.debian.org has address 140.211.166.212
bugs.debian.org has address 209.87.16.39
bugs.debian.org has IPv6 address 2605:bc80:3010:b00:0:deb:166:212
bugs.debian.org has IPv6 address 2607:f8f0:614:1::1274:39
bugs.debian.org mail is handled by 10 buxtehude.debian.org.
% host buxtehude.debian.org.
buxtehude.debian.org has address 209.87.16.39
buxtehude.debian.org has IPv6 address 2607:f8f0:614:1::1274:39
buxtehude.debian.org mail is handled by 10 mailly.debian.org.
buxtehude.debian.org mail is handled by 10 muffat.debian.org.
Currently telnet 140.211.166.212 smtp fails with Connection refused, but
where is the address family mismatch between inet4 and 209.87.16.39 ?
Regards
Harri
Re: smtp-out: Address family mismatch
The Network error on destination MX has been resolved. The Address family mismatch is still open. smtpctl show queue gives me a9f755dd88e88083|inet4|mta||u...@example.com|cont...@bugs.debian.org|cont...@bugs.debian.org|1595227438|1595227438|0|27|pending|29446|Address family mismatch on destination MXs ebbe485d057fa820|inet4|mta||u...@example.com|xxx...@bugs.debian.org|xxx...@bugs.debian.org|1595227386|1595227386|0|27|pending|29394|Address family mismatch on destination MXs Please note the "inet4" and % host bugs.debian.org bugs.debian.org has address 140.211.166.212 bugs.debian.org has address 209.87.16.39 bugs.debian.org has IPv6 address 2605:bc80:3010:b00:0:deb:166:212 bugs.debian.org has IPv6 address 2607:f8f0:614:1::1274:39 bugs.debian.org mail is handled by 10 buxtehude.debian.org. % host buxtehude.debian.org. buxtehude.debian.org has address 209.87.16.39 buxtehude.debian.org has IPv6 address 2607:f8f0:614:1::1274:39 buxtehude.debian.org mail is handled by 10 mailly.debian.org. buxtehude.debian.org mail is handled by 10 muffat.debian.org. Currently telnet 140.211.166.212 smtp fails with Connection refused, but where is the address family mismatch between inet4 and 209.87.16.39 ? Regards Harri
Re: opensmtpd appears to be IPv4-only
Hi Slavik, On 2020-07-22 18:26, Slavik Svyrydiuk wrote: I do not have any issues with IPv6. It works for me. Ubuntu == opensmtpd 6.0.3p1-1ubuntu0.2 smtpd.conf lines: listen on 0.0.0.0 port 25 listen on ::0 port 25 $ netstat -lnt | grep ':25' tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp6 0 0 :::25 :::*LISTEN Nice hint, but AFAIU your smtpd is listening on all interfaces. Thats not the case on my host. Regards Harri
