I recently upgraded two of my servers from Debian Jessie to Debian
Buster, and now the two "new" servers no longer send status messages
during the monthly mdadm resynch check. Ordinarily, as mdadm does a
redundancy check of each array on a system, it sends a status message as
the check completes another 20% of each array, and then the overall
result of the redundancy check when it finishes each array. This is no
longer happening.
I did have quite a bit of trouble getting email to work on the
servers since sSMTP is no longer supported and the change to msmtp was
not successful, but I eventually ironed out all the issues with msmtp (I
think). I then had trouble with mdadm working at all with msmtp, but I
also ironed that out. Now mdadm faithfully sends an email every morning
at 07:35 if one of the arrays is degraded. It sends a message
immediately if an array undergoes a change in status. It also sends an
email when one sends a test message via the monitor function in mdadm.
I have sent queries to the linux-raid list, and in point of fact it
is likely this may be an issue with the version of mdadm, but I am not
completely comfortable with the email setups on these servers.
The "new" servers are running mdadm v4.1 under Debian Buster with
kernel version 4.19.0-6-amd64 and msmtp version 1.8.3
/etc/msmtprc:
# Example for a system wide configuration file
# A system wide configuration file is optional.
# If it exists, it usually defines a default account.
# This allows msmtp to be used like /usr/sbin/sendmail.
account default
# The SMTP smarthost
host outbound.att.net
# Use TLS on port 465
port 465
tls on
tls_starttls off
# Construct envelope-from addresses of the form "user@oursite.example"
#auto_from on
#maildomain att.net
from xxxxx...@att.net
user xxxxx...@att.net
auth on
password xxxxxxxxxxx
# Syslog logging with facility LOG_MAIL instead of the default LOG_USER
syslog LOG_MAIL
The "old" servers are running mdadm v3.3.2 under Debian Jessie with
kernel version 3.16.0-4-amd64 and sSMTP 2.64
