> Reindl Harald <h.rei...@thelounge.net> kirjoitti 14.11.2017 kello 19.24: > > > > Am 14.11.2017 um 17:46 schrieb Jari Fredriksson: >>> Jari Fredriksson <ja...@iki.fi> kirjoitti 14.11.2017 kello 18.42: >>> >>> >>> >>>> Reindl Harald <h.rei...@thelounge.net> kirjoitti 14.11.2017 kello 15.30: >>>> >>>> >>>> >>>> Am 14.11.2017 um 07:11 schrieb Jari Fredriksson: >>>>> I have a couple of issues with my LAN /w SpamAssassin, >>>>> 1. Wrong resolved used >>>>> Nov 14 07:51:51 whirlwind spamd[4041]: spamd: connection from >>>>> gamecock.fredriksson.dy.fi [192.168.1.123]:59338 to port 783, fd 5 >>>>> Nov 14 07:51:51 whirlwind spamd[4041]: spamd: processing message >>>>> <20171114055150.15886142...@mail.bitwell.biz> for spam:1001 >>>>> Nov 14 07:51:51 whirlwind spamd[4041]: dns: sendto() to [::1]:53 failed: >>>>> Connection refused, failing over to [127.0.0.1]:53 >>>>> Nov 14 07:51:51 whirlwind spamd[4041]: dns: sendto() to [127.0.0.1]:53 >>>>> failed: Connection refused, failing over to [::1]:53 >>>>> $ cat /etc/resolv.conf >>>>> jarif@whirlwind:~$ cat /etc/resolv.conf >>>>> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by >>>>> resolvconf(8) >>>>> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN >>>>> # 127.0.0.53 is the systemd-resolved stub resolver. >>>>> # run "systemd-resolve --status" to see details about the actual >>>>> nameservers. >>>>> nameserver 127.0.0.53 >>>>> search fredriksson.dy.fi >>>> >>>> horrible idea on a server to begin with >>> >>> It is actually a dual boot Ubuntu / Windows 10 workstation. Acts as an >>> additional spamd when on Linux mode. > > spam-detection after the MX which can't reject is worthless but taht's a > different topic
My MX can (bitwell.(fi|biz)) using postcreen, clams-milter and spamass-milter). ja...@iki.fi is a bit problematic as the mail comes to me from a iki.fi forwarding service which I joined some 1995. The purpose of that service is to offer an ever valid email-address that will be forwarded to whichever the real mailbox happens to be. It’s a bit outdated concept these days, but there it is). My MX rejects those still but not by postscreen. I think my postscreen setup was made specifically after YOUR advice. If that is so, then thank You. It works like charm. br. jarif > >> .. and 127.0.0.53 is the NetworkDamager and it’s companion DNSMasq. I hate >> those, but will not once again remove them just the get them back as I >> upgrade that Ubuntu > > than Ubuntu is crap but why don't you do your homework then learn how to > prevent it touching /etc/resolv.conf or just protect the file with "chattr +i > /etc/resolv.conf”? If I wanted that I could do it. If I find out that dnsmasq does not honor dhcp then I will. Give him a sack. > > [root@srv-rhsoft:~]$ touch /etc/resolv.conf > touch: setting times of '/etc/resolv.conf': Operation not permitted > > [root@srv-rhsoft:~]$ chattr -i /etc/resolv.conf > > [root@srv-rhsoft:~]$ touch /etc/resolv.conf > > [root@srv-rhsoft:~]$ chattr +i /etc/resolv.conf > > [root@srv-rhsoft:~]$ touch /etc/resolv.conf > touch: setting times of '/etc/resolv.conf': Operation not permitted Kludge.
signature.asc
Description: Message signed with OpenPGP
