Atualizações não assistidas não enviando notificação por email

0

Eu segui o este tutorial para ativar as notificações por e-mail com o pacote de atualizações autônomas, no entanto, não estou recebendo e-mails quando não atendido upgrades é executado automaticamente, mas quando, mas Se eu executar este comando unattended-upgrade -v -d Eu recebo uma notificação por e-mail para o meu endereço do gmail, Na minha configuração "mail on error" está desabilitado.

Ele está definitivamente atualizando pacotes, mas parece não estar tentando enviar notificações por e-mail de acordo com o log, por exemplo, do outro dia.

2017-10-27 06:49:45,396 INFO Initial blacklisted packages:
2017-10-27 06:49:45,397 INFO Initial whitelisted packages:
2017-10-27 06:49:45,398 INFO Starting unattended upgrades script
2017-10-27 06:49:45,398 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial', 'o=Ubuntu,a=xenial-updates']
2017-10-27 06:49:53,276 INFO Packages that will be upgraded: grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common libgnutls-openssl27 libgnutls30 wget
2017-10-27 06:49:53,277 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
2017-10-27 06:49:59,266 INFO All upgrades installed

Aqui está minha configuração para atualizações autônomas.

// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
        "${distro_id}:${distro_codename}";
        "${distro_id}:${distro_codename}-security";
        // Extended Security Maintenance; doesn't necessarily exist for
        // every release and this system may not have it installed, but if
        // available, the policy for updates is such that unattended-upgrades
        // should also install from here by default.
        "${distro_id}ESM:${distro_codename}";
        "${distro_id}:${distro_codename}-updates";
//      "${distro_id}:${distro_codename}-proposed";
//      "${distro_id}:${distro_codename}-backports";
};

// List of packages to not update (regexp are supported)
Unattended-Upgrade::Package-Blacklist {
//      "vim";
//      "libc6";
//      "libc6-dev";
//      "libc6-i686";
};

// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run
//   dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg "false";

// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGUSR1. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps "true";

// Install all unattended-upgrades when the machine is shuting down
// instead of doing it in the background while the machine is running
// This will (obviously) make shutdown slower
//Unattended-Upgrade::InstallOnShutdown "true";

// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package that provides
// 'mailx' must be installed. E.g. "[email protected]"
Unattended-Upgrade::Mail “[email protected]";

// Set this value to "true" to get emails only on errors. Default
// is to always send a mail if Unattended-Upgrade::Mail is set
//Unattended-Upgrade::MailOnlyOnError "true";

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
//Unattended-Upgrade::Remove-Unused-Dependencies "false";

// Automatically reboot *WITHOUT CONFIRMATION*
//  if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";
// If automatic reboot is enabled and needed, reboot at the specific
// time instead of immediately
//  Default: "now"
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";

// Use apt bandwidth limit feature, this example limits the download
// speed to 70kb/sec
Acquire::http::Dl-Limit "1000";

Qualquer ajuda seria muito apreciada, pesquisei muito no Google e não consigo encontrar uma resposta para o motivo de isso não estar funcionando. Eu também tenho heirloom-mailx instalado e um trabalho .mailrc.

Obrigado!

    
por Damien White 28.10.2017 / 19:41

1 resposta

1

Verifique o /var/log/mail.log para ver o que está errado, geralmente é o campo "from:" que é bloqueado pelo servidor SMTP upstream.

    
por Stuggi 24.02.2018 / 01:39