OS X Server Mail - Alias Debugging, Open Directory Setup & ClamAV Update
Status: 2020 - my testing notes collected from Apple Community Support discussion
Status: 2023 - add Open Directory tips as this is a critical part of mail setup
Status: 2024 - add ClamAV update tip so mail virus scanning remains current
Apple have retired OS X Server and integrated some of the functions back into base MacOS, while others such as its integrated Postfix mail implementation have been put out to pasture and Apple has published suggestions for alternate replacements.
The now retired mail server still runs on OS X High Sierra and has some nice pre-integration with Open Directory and anti-spamming filtering, so it is still usable for small self-hosted mail system. One area of mail systems administration that got a bit confusing was setting up mail alias, so here is info that I put together from my Apple Community support discussion
The OS X Server email is based on Postfix mail transfer agent (MTA), Dovecot pop / imap and SpamHaus anti-spam filter and so if you are inclined you can bring together these parts on any Linux server.
For its directory service OS X Server provided "OpenDirector" which was based on OpenLDAP. For my OS X mail setup I have all the users defined in OpenDirector, so I am including tips on this as well.
Postfix - base OS X vs Server OS X
The base base OS X provides a Postfix (MTA) installation as part of base software. The configuration files for base OS X are installed at: /etc & /etc/postfix
This install has the following aliases & main files included:
- "/etc/aliases" - which is actually a soft link to "postfix/aliases"
- "/etc/aliases.db" - which is the hash map created from "/etc/aliases" source file
- "/etc/postfix/main.cf" - is the main postfix startup configuraton (which by default has all alias configuration items commented out
On installing OS X Server an additional and duplicate Postfix configuration file area is created at: /Library/Server/Mail/Config/postfix
- This results in duplicate aliases files: "aliases" & "aliases.db"
- Main startup configuration file: "main.cf"
- And installs daemon startup plist: "/System/Library/LaunchDaemons/com.postfix.master.plist" which you can look at to see details startup command line and configuration files
Mail Configuration
As there are now multiple postfix configuration areas it (those from base & those from Server) it is easy to get the configuration wrong, for example if you do a "postconf config_directory" command it might tell you that postfix is using the config in "/etc/postfix", when in fact it is not...
To check which configuration file is being used do: "ps -ax | grep postfix" and you can see the configuation file flag indicated via "master -c" process:
$ ps -ax | grep postfix
264 ?? 0:00.80 master -c /Library/Server/Mail/Config/postfix
5878 ?? 0:00.06 /usr/bin/perl /Applications/Server.app/Contents/ServerRoot/usr/libexec/postfix/greylist.pl
5889 ttys000 0:00.01 grep postfixSo by default with OS X Server mail (I know this is true for Server 3 & 4) the config used is the one in "/Library/Server/Mail/Config/postfix"
Aliases Configuration
Having identified the location of configuration files location to managed your aliases the key items to look for in "main.cf" are:
- "alias_maps = hash:/" - this will tell you the location of the ".db" file
- "alias_database = hash:/" - this will tell you the location of the "aliases" file used to generate the hash/db file above
- "local_recipient_maps = proxy:unix:passwd.byname $alias_maps" - this command is very important
... it is what causes the mail server to trivially reject mail undefined/invalid users. This looks at the known login user ids (via proxy) and
the $alias_maps - which are as per item 2 above... - "virtual_alias_maps = $virtual_maps hash:/ - if you are hosting multiple mail domains within a single server
This now gives you flexibility to:
- Put traditional "aliases" & "aliases.db" at any location you would like and manage then in standard way
- Have aliases which are by fully qualified domain names as "virtual_users"
- Use Server Users administration interface via the "Advanced Options..." to create aliases that are held within "Open Directory"
NOTE 1: If have setup email accounts via "Open Directory" master and then replicate this to the mail host, then these user should be flagged as being able to login in order for them to be visible as local recipient (as per item 3. "local_recipient_maps" above).
Testing your configuration
Having created your aliases you will likely need to test then if some thing is not working. A critical configuration item in: "/Library/Server/Mail/Config/postfix/main.cf" to avoid your mail accepting email for undefined address is:
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
This forces postfix mail server to verify that the mail recipient is a known user and is essential to avoid mail to unknown user entering into mail system and then replying with a "cannot deliver message" back to the "from/reply-to" identity which could be a false one and hence your mail system becomes a target for spam relay via return to sender messages.
To test the behaviour you will get you can use the "postmap" command.
For example to test the aliases an alias in the /etc/aliases.db file you can use the following command:
# postmap -q <TEST_NAME> -c /Library/Server/Mail/Config/postfix hash:/<aliases>
---
--- here is example
---
# sudo postmap -q frog -c /Library/Server/Mail/Config/postfix hash:/etc/aliases
hopperIf the alias is found it will provide the destination identity... such as "hopper" in above example.
For recipients that are know local user identities you can test via:
# postmap -q <LOCAL_NAME> -c /Library/Server/Mail/Config/postfix proxy:unix:passwd.byname
---
--- here is example
---
sudo postmap -q hopper -c /Library/Server/Mail/Config/postfix proxy:unix:passwd.byname
hopper:********:521:20:Big Frog:/Users/hopper:/bin/bashIf the user is found you will get the shadow passwd line as response. Postfix does not look at details of the response, just if I gets something or nothing and if it gets something then it will accept mail to that receipient.
So now for the three ways you can add aliases
- Via the <aliases>.db file which must be in the location specified by $alias_maps = hash:/<location> directive in main.cf
- Via the "Advanced Options..." aliases list that available from "Server" application "Account/Users" function
- Via the "Email Addresses:" that is available from the "Edit User.." function from "Server" application "Account/Users" function
I have tested 1 & 2 and the behaviour is that:
- If you use & .db mechanism then the recipient is returned via hash:/ test
- If you use "Advance Options" aliases list then the recipient is returned via proxy:unix:passwd.byname
If you use option 3 then the result is that that mail address will be added in the /Library/Server/Mail/Config/postfix/virtual_users file and you can then test this by doing:
postmap -q NAME@DOMAIN.COM -c /Library/Server/Mail/Config/postfix #hash:/Library/Server/Mail/Config/postfix/virtual_usersThe response should be the local id that this maps to...
Setting up standard file locations
To make using OS X postfix server a bit simpler and consistent with standard configuration.
Thus for me, I keep my files as follows:
/etc/aliases -> postfix/aliases -- soft link to file in /etc/postfix/aliases
/etc/postfix/aliases -- the actual aliases file I use
/etc/aliases.db -- the generated hash file
/Library/Server/Mail/Config/postfix/aliases -> /etc/postfix/aliases -- again link to the master aliases file
/Library/Server/Mail/Config/postfix/aliases.db -> /etc/aliases.db -- again link to the hash file
and my alias directives in /Library/Server/Mail/Config/postfix/main.cf are:
...
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
virtual_alias_maps = $virtual_maps hash:/Library/Server/Mail/Config/postfix/virtual_users
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
...
As you can see I have updated the /Server/Library/Mail/Config/postfix alias related files and config to point back to the standard /etc/aliases area...This is more paranoia rather than necessity.
Generating hash database
To update the aliases.db hash table...
Based on above configuration (symbolic links etc)
# cd /etc
---
--- generate hash file
---
# sudo postalias -c /Library/Server/Mail/Config/postfix aliases
---
--- or
---
# sudo newaliases -c /Library/Server/Mail/Config/postfix aliases
---
--- notes new aliases is just link to postfix Sendmail compatibility interface
---
--- to reload mail server after updating alias db
---
# sudo postfix -c /Library/Server/Mail/Config/postfix reloadDovecot - IMAP Server Configuration
With the lastest IOS updates, which has "push" mail notification enabled as default have found that mail fetching does not work consistently.
The sympton is that the "mail" icon shows there is new unread mail, but when you open the mail app to read it, is does not show the new mail.
On iPad when you go to collect mail, you can get the following error message being returned by mail server:
- "Maximum number of connections from user+IP exceeded (mail_max_userip_connections=20)" - this appears to occur with more recent iOS version, which open up more connections to server
Depending on how you have your email server setup (in particular when you have email server behind firewall with port forwarding) it might be that your multiple email clients are all hitting the email server from the same IP address.
For macOS Server email, the "dovecot" open source IMAP / POP mail collection agent is used. So if you are getting this error you can increase the value of the maximum "userip" configuration.
The dovecot configuration files are in: "/Library/Server/Mail/Config/dovecot"
You can see the current configuration values using the dovecotd:
---
--- Let look at configuration for running dovecot server
---
admin$ /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd -a
# 2.2.30.2 (c0c463e): /Library/Server/Mail/Config/dovecot/dovecot.conf
# Pigeonhole version 0.4.18 (29cc74d)
# OS: Darwin 17.7.0 x86_64 hfs
# NOTE: Send doveconf -n output instead when asking for help.
aps_topic =
auth_anonymous_username = anonymous
auth_cache_negative_ttl = 1 hours
...
...
...
protocol imap {
mail_max_userip_connections = 40
mail_plugins = quota zlib acl fts fts_sk imap_acl imap_quota imap_zlib
}
protocol pop3 {
mail_max_userip_connections = 6
}Using "grep" you can see the relavant configuration items:
---
--- grep is our friend to find configuration items
---
admin$ /Applications/Server.app/Contents/ServerRoot/usr/sbin/dovecotd -a | grep userip
mail_max_userip_connections = 10
mail_max_userip_connections = 40
mail_max_userip_connections = 6
As I only use IMAP and not POP, I change the configuration in: "/Library/Server/Mail/Config/dovecot/conf.d/20-imap.conf" to increase "mail_max_userip_connections = 40".
There is also global and POP specific configuration items.
Open Directory - Configuration and Use
Open Direcotory has a number of components including:
- Microsoft Acticve Directory - including support to act as Primary Domain Controller
- Passwork and Authentication Services - including Kerberos & single sign-on support and
- OpenLDAP Directory Server - the main LDAP implemenation.
The Apple OS X Server vision was sophisticated capabilities with ease of use. However sometimes things go wrong and you need to look past the simple adminstration ui.
I only use the LDAP and Authentication components which requires:
- Open Directory LDP - main and replica server
- Client Replicas - for each server that is using the LDAP (mail, jabber etc)
The main adminstration task I need to use is that sometimes the primary server loses its replicas and so I need to restablish the replication.
Stopping and Starting the Server
Assuming everything is working nicely then you can stop / start the Open Directory service from the OS X Server Admin GUI.
On OS X / MacOS launchd provides framework for running deamons and agents. To control the status of these you can use the "launchctl" tool (in termnal). So to find status of Open Directory:
---
--- 1. find daemon
---
$ sudo launchctl list | grep irectory
91 0 com.apple.opendirectoryd
---
--- 2. Get detail configuration
---
$ sudo launchctl list com.apple.opendirectoryd
{
"EnableTransactions" = true;
"LimitLoadToSessionType" = "System";
"MachServices" = {
"com.apple.system.opendirectoryd.libinfo" = mach-port-object;
"com.apple.system.DirectoryService.libinfo_v1" = mach-port-object;
"com.apple.system.opendirectoryd.api" = mach-port-object;
"com.apple.private.opendirectoryd.rpc" = mach-port-object;
"com.apple.system.opendirectoryd.membership" = mach-port-object;
"com.apple.system.DirectoryService.membership_v1" = mach-port-object;
};
"Label" = "com.apple.opendirectoryd";
"TimeOut" = 30;
"OnDemand" = false;
"LastExitStatus" = 0;
"PID" = 91;
"Program" = "/usr/libexec/opendirectoryd";
};And similiarly to see status of OpenLDAP:
---
--- 1. find daemon
---
$ sudo launchctl list | grep slap
- 1 org.openldap.slapd
---
--- 2. Get detail configuration
---
$ sudo launchctl list org.openldap.slapd
{
"LimitLoadToSessionType" = "System";
"Label" = "org.openldap.slapd";
"TimeOut" = 30;
"OnDemand" = true;
"LastExitStatus" = 256;
"Program" = "/usr/libexec/slapd";
"ProgramArguments" = (
"/usr/libexec/slapd";
"-d";
"0";
"-h";
"ldap:/// ldapi://%2Fvar%2Frun%2Fldapi";
);
};This shows how the OpenLDAP is started and the command line arguments: "/usr/libexec/slapd -d 0 -h ldap:/// ldapi://var/run/run/ldapi"
Some useful commands for "fixing" Open Directory
- Stop Open Directory LDAP: "sudo launchctl stop org.openldap.slapd"
- Stop Open Directory: "sudo launchctl stop com.apple.opendirectoryd"
- Disable Open Directory: "sudo launchctl disable system/com.apple.opendirectoryd"
- Enable Open Directory: "sudo launchctl enable system/com.apple.opendirectoryd"
Another set of command line utilities are what is provided by "Server Admin" tool. This also provides a view on the status of Open Directory:
$ sudo serveradmin fullstatus dirserv
Password:
dirserv:ldapSearchBase = "dc=machine2,dc=domain,dc=com"
dirserv:readWriteSettingsVersion = 1
dirserv:LDAPServerType = "replica"
dirserv:kdcHostedRealm = "MASTER.XX.DOMAIN.COM"
dirserv:logPaths:opendirectorydLog = "/var/log/opendirectoryd.log"
dirserv:logPaths:ldapLog = "/var/log/slapd.log"
dirserv:logPaths:passwordServiceServerLog = "/Library/Logs/PasswordService/ApplePasswordServer.Server.log"
dirserv:logPaths:passwordServiceErrorLog = "/Library/Logs/PasswordService/ApplePasswordServer.Error.log"
dirserv:logPaths:kdcLog = "/var/log/krb5kdc/kdc.log"
dirserv:logPaths:slapconfigLog = "/Library/Logs/slapconfig.log"
dirserv:isRelayServer = no
dirserv:state = "RUNNING"And you can enable & start Open Directory using: "sudo serveradmin start dirserv"
To start your diagnosis on openldap, first see what it thinks it is.
On Open Directory Replica:
$ sudo slapconfig -getstyle
6.1 - hosting replica LDAP directory serverAs expected...
On Open Directory Master:
$ sudo slapconfig -getstyle
Password:
1.1 - hosting a master LDAP directory serverAnd full status on the master via "serveradmin":
sudo serveradmin fullstatus dirserv
dirserv:logPaths:opendirectorydLog = "/var/log/opendirectoryd.log"
dirserv:logPaths:ldapLog = "/var/log/slapd.log"
dirserv:logPaths:passwordServiceServerLog = "/Library/Logs/PasswordService/ApplePasswordServer.Server.log"
dirserv:logPaths:passwordServiceErrorLog = "/Library/Logs/PasswordService/ApplePasswordServer.Error.log"
dirserv:logPaths:kdcLog = "/var/log/krb5kdc/kdc.log"
dirserv:logPaths:slapconfigLog = "/Library/Logs/slapconfig.log"
dirserv:LDAPServerType = "master"
dirserv:state = "RUNNING"
dirserv:ldapSearchBase = "dc=HOST,dc=DOMAIN,dc=com"
dirserv:kdcHostedRealm = "MASTER.XX.DOMAIN.COM"
dirserv:readWriteSettingsVersion = 1For both master & replica the location of the OpenLDAP Berkeley DB is: "/var/db/openldap/openldap-data/".
When the replica fails due to it losing the "replica list", which is most common issue and seems to get triggered when all of Master and Replica's are being rebooted. The you will need to:
- Destroy the replica (on replica machine)
- Remove replica entry on the master machine
- Check that removal has occurred on master and has has propagated to other replicas
- Recreate replica on the replica machine
Step 1 - Destroy Replica:
---
--- 1. Stop Directory Server
---
---
$ sudo serveradmin stop dirserv
dirserv:state = "STOPPED"
---
---
--- 2. Destroy the Replica
---
---
$ sudo slapconfig -destroyldapserver
2024-04-06 02:29:03 +0000 slapconfig -destroyldapserver
2024-04-06 02:29:03 +0000 CopyReplicaArray: ldap_search_ext_s failed
2024-04-06 02:29:03 +0000 Error retrieving replica array
2024-04-06 02:29:03 +0000 Deleting Cert Authority related data
2024-04-06 02:29:03 +0000 OPENDIRECTORY_ROOT_CA_IDENTITY not found, unable to determine rootCA name from OPENDIRECTORY_ROOT_CA_CERTIFICATE, defaulting to configured value of CA-DOMAIN-NAME
2024-04-06 02:29:03 +0000 Could not find root CA certificate in system keychain
2024-04-06 02:29:03 +0000 command: /usr/sbin/xscertadmin add --reason 5 --issuer CA-DOMAIN-NAME --serial 19
CopyCARecordByName: get ldapi node code = 2100 description = Connection failed to node '/LDAPv3/ldapi://%2Fvar%2Frun%2Fldapi'
No such issuer - failed to revoke certificate
2024-04-06 02:29:23 +0000 Not deleting hostname cert as signed by IntermediateCA_MASTER.XX.DOMAIN.COM_20
2024-04-06 02:29:23 +0000 Not deleting hostname cert as signed by THIS-MACHINE.DOMAIN.COM
2024-04-06 02:29:23 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertd.plist
2024-04-06 02:29:23 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertd-helper.plist
2024-04-06 02:29:23 +0000 command: /bin/launchctl unload -w /System/Library/LaunchDaemons/com.apple.xscertadmin.plist
2024-04-06 02:29:24 +0000 Stopping LDAP server (slapd)
2024-04-06 02:29:24 +0000 Stopping password server
2024-04-06 02:29:25 +0000 Removed all service principals from keytab for realm THIS-MACHINE.DOMAIN.COM
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.001.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.002.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.003.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.004.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.005.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/__db.006.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/altSecurityIdentities.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-config-realname.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-generateduid.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-memberguid.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-nestedgroup.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-group-realname.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-hwuuid.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-locale-subnets.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/apple-realname.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/cn.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/DB_CONFIG.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/dn2id.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/entryCSN.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/entryUUID.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/gidNumber.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/givenName.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/id2entry.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/ipHostNumber.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/log.0000000145.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/log.0000000146.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/macAddress.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/mail.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/memberUid.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/objectClass.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/ou.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/sn.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/street.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/uid.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/openldap-data/uidNumber.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.001.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.002.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.003.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.004.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.005.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/__db.006.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/alock.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/authdata.ldif.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/authGUID.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/DB_CONFIG.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/dn2id.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/draft-krbPrincipalAliases.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/draft-krbPrincipalName.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/entryCSN.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/entryUUID.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/id2entry.bdb.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/log.0000000780.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/log.0000000781.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/openldap/authdata/objectClass.bdb.
2024-04-06 02:29:25 +0000 Removed directory at path /var/db/openldap/authdata.
2024-04-06 02:29:25 +0000 Removed file at path /etc/openldap/slapd_macosxserver.conf.
2024-04-06 02:29:25 +0000 Removed file at path /etc/openldap/slapd.conf.
2024-04-06 02:29:25 +0000 Removed file at path /etc/openldap/rootDSE.ldif.
2024-04-06 02:29:25 +0000 Removed file at path /var/db/dslocal/nodes/Default/groups/com.apple.access_dsproxy.plist.
2024-04-06 02:29:25 +0000 Removed directory at path /etc/openldap/slapd.d/cn=config.
2024-04-06 02:29:25 +0000 Removed file at path /etc/openldap/slapd.d/cn=config.ldif.
2024-04-06 02:29:25 +0000 Removed directory at path /etc/openldap/slapd.d.
2024-04-06 02:29:25 +0000 Removed directory at path /etc/openldap/slapd.d.backup/cn=config.
2024-04-06 02:29:25 +0000 Removed file at path /etc/openldap/slapd.d.backup/cn=config.ldif.
2024-04-06 02:29:25 +0000 Removed directory at path /etc/openldap/slapd.d.backup.
2024-04-06 02:29:28 +0000 Stopping password server
2024-04-06 02:29:28 +0000 Removed file at path /Library/Preferences/com.apple.openldap.plist.
---
---
--- 3. Get Status again
---
---
$ sudo serveradmin fullstatus dirserv
dirserv:logPaths:opendirectorydLog = "/var/log/opendirectoryd.log"
dirserv:logPaths:ldapLog = "/var/log/slapd.log"
dirserv:logPaths:passwordServiceServerLog = "/Library/Logs/PasswordService/ApplePasswordServer.Server.log"
dirserv:logPaths:passwordServiceErrorLog = "/Library/Logs/PasswordService/ApplePasswordServer.Error.log"
dirserv:logPaths:kdcLog = "/var/log/krb5kdc/kdc.log"
dirserv:logPaths:slapconfigLog = "/Library/Logs/slapconfig.log"
dirserv:LDAPServerType = "standalone"
dirserv:state = "STOPPED"
dirserv:readWriteSettingsVersion = 1Step 2 - Remove Replica Entry from Master
On the Master machine:
$ sudo slapconfig -removereplica REP-HOST.DOMAIN.COM diradmin
2024-04-06 02:57:46 +0000 slapconfig -removereplica
2024-04-06 02:57:46 +0000 command: /usr/bin/kdestroy --credential=ldap/REP-HOST.DOMAIN.COM@MASTER.XX.DOMAIN.COMStep 3 - Check Replica Removal
While "Step 2" to remove the replica entry on the master machine completes with out error. Going into the Server admin app still shows the entry for the removed replica.
I have found that you can just proceed to "Step 4" and while the creation of new replacement entry fails the process continues and new replica is established correctly.
Step 4 - Recreate Replica
This can be done via Server Admin UI or via command line.
On host you wish to create new replica:
sudo slapconfig -createreplica MASTER-HOST.XX.DOMAIN.COM diradminUpdating ClamAV to supported version
The basis components of macOS Server mail are:
Postfix is a very old and stable SMTP server, but ClamAV need to keep up with neverending new virus releases. This is done via downloadable virus definitions files. To keep ClamAV currently the older version of ClamAV virus feeds get shutdown and you need to move to new version of ClamAV and its newer virus definitions feed. The final version of ClamAV with macOS Server was 0.99.2 and this no longer has available feed.
The resut can be seen on your virus scan log in Server Admin with the following repeating entry:
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.net
WARNING: getpatch: Can't download daily-26096.cdiff from database.clamav.netSo you have the option of having out of date virus scanner or upgrade the ClamAV via source. The blog "Updating ClamAV on OS X Server >= 10.5.6" while out of date, can be used as guideance to updating ClamAV, in a way that maintains compatability with macOS Server Admin GUI.
References & Links:
Apple Community Support - where I posted setup and testing information orginally
Open Directory Administration (Version 10.6 Snow Leopard) - Mac OS X Server documentation, provide here in case you can't find it)
Others have problems - pointers on the process to fix a specific Open Directory issue
slap recovery - more tips on recovering OpenLDAP
Berkerly DB Recovery Tip - OpenLDAP uses berkerly db under the covers, so db_recover tool might help with recovery of corrupted DB
"Updating ClamAV on OS X Server >= 10.5.6" - macOS is no longer supported and the last version used clamav 0.99.2, which has now had its virus update feed shutdown, resulting in repeating feed update failure. To keep macOS Server mail secure you should update the clamav version by building new one from source. This blog post provides guidance to build & install new ClamAV version from source.