BTW, although testing validity of email would indeed be nice,
it is notoriously difficult. For example, this is valid:
http://@jhnc.org;
( https://www.rfc-editor.org/rfc/rfc5322#section-3.4 )
but I believe fails the regex in your link (I can't test properly
without turning off my
Perhaps amusingly, now I look at the code, I see in do_command.c
that if safe_p() determines mailfrom contains spaces or parentheses,
it will error out. However the very next line of code then sets it
to contain both spaces and parentheses! (Yes, I know it is safe.)
My suggestion is to call
Hello Jonathan,I apologize, I had not paid attention to the extra space included in thelist of MAILTO addresses.I suppose that we can sanitize the value of MAILTO, by checking it with a regular _expression_ derived from RFC 5322 Official Standard(see https://emailregex.com/), or do you suggest
Sorry, my mail server does not seem to have received any email
from debian when you sent your email on 2024-01-21. Was I
supposed to have been automatically Bcc'd?
I disagree that the bug is not grave - I believe it meets the
criterion of data being lost (and was in fact lost by the user).
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 athttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061155The title of the present bug report says that crontab -e cannotdetect “unsafe” email
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
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
7 matches
Mail list logo
