DevHeads.net

Postings by Emmett Culley

SASL auth not working

I am not able to get postfix to authenticate on port 465 or 587 to allow account holders to relay via this server.

Everything else works.

firewalld

I have two VMs, both with firewalld installed.

virtual_mailbox_domains

Recently I've been working on upgrading to Postfix 3 and a rewrite of web-cyradm, and so have been studying the Postfix docs.

firewall-config not functional

I have a number of machines (hardware and VMs) running CentOS 7. I all cases firewall-config is not functional.

First, the service check boxes are not functional. When you click on one, it don't change to "checked", and nothing changes on the firewall.

Firewalld

Yesterday I noticed that I was not able to ping one of our development servers so I logged in via VNC and ran the Firewalld GUI.

To my surprise, except for the interface definition for public and trusted zones, nothing seemed to be configured. That is, none of the services were checked off that we want open at the firewall.

Bind fails to start after update from 7.1 to 7.2

I am seeing these lines for each domain in the systemd journal:

zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found
zone relationship123.com/IN: not loaded due to errors.
_default/relationship123.com./IN: file not found

If I change the zone defs to include the full path:

From

zone "relationships123.com." IN {
type master;
file "relationships123.com.db";
};

To

zone "relationships123.com." IN {
type master;
file "/var/named/chroot/var/named/relationships123.com.db";
};

in the config file, named starts, but then fails to provide DNS rep

Firewalld

I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files.

All servers are up to date.

By "just noticed" I mean that I finally investigated why a newly rebooted VM failed to allow NFS connections. Prior to doing that. I'd been stopping the firewall to get access, then restarting the firewall after setting the eth1 interface to ACCEPT.

Zone file not written to slave DNS server

I have mostly succeeded in getting master and slave DNS servers operational. Mostly, because the zone file is not written when a zone is updated on the master server when the notify and transfer process happens.

The slave DNS server gets the changes to the modified zone, but the slave zone file remains as before.

clamav

Every time I update my system with clamav, it doesn't restart and freshclam no longer works, because of a permission issue on the log directory. Each time I update clamav I have to search the Internet to figure out what there is to do. That NEVER helps so I try different combinations on user and group in amavis-new and clamav configuratio files, until I eventually get them both to work.

I am getting clamav and amavisd update from the epel repo.