Mechiel Lukkien d2f7d59fce for dns resolve errors likely due to a missing name server in /etc/resolv.conf, point user to man page of systemd-resolved, the likely cause ... it seems linux machines with systemd-resolved don't always set up /etc/resolv.conf correctly. there may be no "nameserver" entry, causing Go's net resolver to fallback to 127.0.0.1 and ::1. Systemd-resolved is listening on 127.0.0.53, so users will likely get a "connection refused". So point users to the systemd-resolved manual page. for issue #38 by ArnoSen		2023-06-12 14:53:07 +02:00
..
dns.go	when logging email addresses with IDNA domain and/or special characters or utf8 in localpart, log both native utf8 form and form with escape localpart and ascii-only domain	2023-03-09 20:18:34 +01:00
dns_test.go	mox!	2023-01-30 14:27:06 +01:00
ipdomain.go	when logging email addresses with IDNA domain and/or special characters or utf8 in localpart, log both native utf8 form and form with escape localpart and ascii-only domain	2023-03-09 20:18:34 +01:00
mock.go	fix sending to address where the domain does not have an mx record (but where we should connect directly to the host, or follow cname records)	2023-04-24 10:34:19 +02:00
resolver.go	for dns resolve errors likely due to a missing name server in /etc/resolv.conf, point user to man page of systemd-resolved, the likely cause	2023-06-12 14:53:07 +02:00