Bug#1061155: cron: "crontab -e" does not report "unsafe" mail and so job output can be lost

Hello, Thank you for your bug report. I shall lower the severity of your bug report, since it "causes non-serious data loss" a...@example.org would be parsed as a valid e-mail address if one uses regexp matching. What improvement would you suggest? Should "crontab -e" send an e-mail to

Bug#1061155: cron: "crontab -e" does not report "unsafe" mail and so job output can be lost

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