Package: cron Version: 3.0pl1-182 Severity: grave Justification: causes non-serious data loss
Dear Maintainer, * What led up to the situation? 1. A user ran "crontab -e" 2. He added the line (note the space): MAILTO=a...@example.org, b...@example.com 3. He saved and exited 4. No errors were reported to the user. * What was the outcome of this action? Subsequently, jobs ran but output was discarded. /var/log/syslog contains "UNSAFE MAIL" messages which the user cannot see. * What outcome did you expect instead? At step 4, crontab should have reported an error to the user and not applied the update. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-91-generic (SMP w/1 CPU thread) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cron depends on: ii cron-daemon-common 3.0pl1-182 ii init-system-helpers 1.66 ii libc6 2.37-13 ii libpam-runtime 1.5.2-9.1 ii libpam0g 1.5.2-9.1+b1 ii libselinux1 3.5-1+b2 ii sensible-utils 0.0.20 Versions of packages cron recommends: ii exim4-daemon-heavy [mail-transport-agent] 4.97-4+b1 Versions of packages cron suggests: pn anacron <none> pn checksecurity <none> ii logrotate 3.21.0-2 Versions of packages cron is related to: pn libnss-ldap <none> pn libnss-ldapd <none> pn libpam-ldap <none> pn libpam-mount <none> pn nis <none> pn nscd <none> -- no debconf information
