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

[Khaznadar Georges]

Hello Joathan, have you received my previous reply to your bug report? It was one month ago. If you did not read it, you can find it today at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061155 The title of the present bug report says that crontab -e cannot detect “unsafe” email addresses. However, the example you proposed is the usage of e-mail addresses like a...@example.org, b...@example.com, which can be parsed by the usual regular expressions, as valid e-mail addresses. So, I ask you again for other suggestions about a secure way to distinguish “safe” from “unsafe” e-mail addresses. I suspect that asking a program to be more clever than its users is a waste of energy. For example, if I send this email to no-deb...@jhnc.org, chances are that the e-mail will never be distributed. It is my responsability to send this e-mail to deb...@jhnc.org, isn't it? If you do not mind, I suggest to close this bug report in a few days. Best regards, Georges.