On 28.12.22 12:55, John Stimson via users wrote:
The machine has bind9 running locally to provide DNS for its own
domain, and uses it for name resolution.
On Wed, 28 Dec 2022, Matus UHLAR - fantomas wrote:
This is the problem:
Bind9 is configured to use OpenDNS and Google as forwarders.
On Wed, 28 Dec 2022, Matus UHLAR - fantomas wrote:
On 28.12.22 12:55, John Stimson via users wrote:
The machine has bind9 running locally to provide DNS for its own domain,
and uses it for name resolution.
This is the problem:
Bind9 is configured to use OpenDNS and Google as forwarders.
On 28.12.22 12:55, John Stimson via users wrote:
The machine has bind9 running locally to provide DNS for its own
domain, and uses it for name resolution.
This is the problem:
Bind9 is configured to use
OpenDNS and Google as forwarders.
BIND does NOT need forwarders and by using it, you mo
On 2022/12/28 15:09:36 Matus UHLAR - fantomas wrote:
> spamassassin service is not needed when you use amavis, you can stop and
> disable it.
Good to know.
On 2022/12/28 15:09:36 Matus UHLAR - fantomas wrote:
> >~amavis/.spamassassin contains a file user.prefs that has only comment
> >lines. Co
On 2022/12/28 12:45:48 Matus UHLAR - fantomas wrote:
have you reloaded amavisd?
On 28.12.22 08:50, John Stimson via users wrote:
I restarted the amavisd-new.service and spamassassin.service after
editing /etc/spamassassin/local.cf
spamassassin service is not needed when you use amavis, you
Updates:
On 2022/12/28 12:45:48 Matus UHLAR - fantomas wrote:
> have you reloaded amavisd?
I restarted the amavisd-new.service and spamassassin.service after
editing /etc/spamassassin/local.cf
> do you have anything set in amavis' home directory?
> usually ~amavis/.spamassassin
~amavis/.spa
