Spam detection software, running on the system "master.squid-cache.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: Em 13/12/2022 19:46, ngtech1...@gmail.com escreveu: > Hey,
> > What is the content of: > /etc/resolv.conf > ? > > It could be something
related to default systemd dns services. > > Eliezer > ---- > El [...]
Content analysis details: (5.6 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
[171.171.0.194 listed in zen.spamhaus.org]
1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
valid
-0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from
envelope-from domain
-0.0 T_SCC_BODY_TEXT_LINE No description available.
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
-0.0 NICE_REPLY_A Looks like a legit reply (A)
0.0 NO_FM_NAME_IP_HOSTN No From name + hostname using IP address
--- Begin Message ---
Em 13/12/2022 19:46, ngtech1...@gmail.com escreveu:
Hey,
What is the content of:
/etc/resolv.conf
?
It could be something related to default systemd dns services.
Eliezer
----
Eliezer Croitoru
NgTech, Tech Support
Mobile: +972-5-28704261
Email: ngtech1...@gmail.com
Web: https://ngtech.co.il/
My-Tube: https://tube.ngtech.co.il/
Yep, I had the same issues when I upgraded from 4 to 5, because I also
upgraded the distro version along with it, and systemd-resolved is
enabled by default in some, such as Fedora and Ubuntu. It stopped
resolving local domain names for some reason.
Instead of struggling to make it work on the new model, I simply
disabled systemd-resolved and went back to old resolv.conf style.
I'll quote the solution I followed here:
https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
====
This method works on the Ubuntu releases 17.04 (Zesty), 17.10 (Artful),
18.04 (Bionic), 18.10 (Cosmic), 19.04 (Disco) and 20.04 (Focal):
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
Then put the following line in the [main] section of your
/etc/NetworkManager/NetworkManager.conf:
dns=default
Delete the symlink /etc/resolv.conf
rm /etc/resolv.conf
Restart NetworkManager
sudo systemctl restart NetworkManager
Also be aware that disabling systemd-resolvd might break name resolution
in VPN for some users. See this bug on launchpad (Thanks, Vincent).
===
--- End Message ---
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
