Closed
Bug 278414
Opened 20 years ago
Closed 19 years ago
Cannot add 'cc' notification for Flags when using emailsuffixes
Categories
(Bugzilla :: Email Notifications, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: peterkayatwork, Assigned: LpSolit)
Details
Attachments
(2 files)
|
2.30 KB,
patch
|
Wurblzap
:
review+
|
Details | Diff | Splinter Review |
|
2.25 KB,
patch
|
Wurblzap
:
review+
|
Details | Diff | Splinter Review |
When using e-mail suffixes to append @host.com to e-mail addresses, one cannot add an e-mail address (email@host.com) to the CC list for a Flag. One gets the error: <bright red> The e-mail address you entered (email@host.com) didn't pass our syntax checking for a legal email address. Enter only the username (the @host.com will be appended). It must also not contain any of these special characters: \ ( ) & < > , ; : " [ ], or any whitespace. </bright red> in editflagtypes.cgi, sub validateCCList, there's the line: foreach my $address (@addresses) { CheckEmailSyntax($address) } CheckEmailSyntax checks against the parameter "emailregexp", which rejects "email@host.com". According to the documentation, we allow arbitrary CC lists for Flags, so "email@host.com" should be valid. If we allow arbitrary CC lists for Flags (why *do* we do that for flags but not for normal CC lists?) then we will need a seperate way to validate the CC e-mail addresses.
| Assignee | ||
Comment 1•20 years ago
|
||
Marc, I reassign this bug to you. I will let you set the correct flags (if necessary) and confirm this bug. CC'ing kiko who reviewed your patch in bug 277389.
Comment 2•20 years ago
|
||
Removing dependency because it doesn't exist :) CheckEmailSyntax is named incorrectly. Its name should be CheckLoginSyntax. We need a real CheckEmailSyntax which doesn't care about emailregexp (which should be called loginregexp -- but this change is imo out of scope of this bug).
Comment 3•20 years ago
|
||
I'm not currently working on this... I'll take it if/when I do. Until then, it's up to grabs.
Assignee: wurblzap → nobody
Updated•19 years ago
|
Flags: blocking2.22?
Comment 4•19 years ago
|
||
I'd like to see this fixed in 2.20 also, but I don't think it's severe enough to block the 2.22 release. We've lived with it OK in 2.20. People who use emailsuffix should only rarely have a need to CC somebody on a flag who isn't inside the company.
Severity: normal → major
Flags: blocking2.22? → blocking2.22-
Comment 5•19 years ago
|
||
The effect of this bug is that installations using emailsuffix can't use the CC feature of flags at all.
Flags: blocking2.22- → blocking2.22?
Comment 6•19 years ago
|
||
Oh, OK. In that case, it makes more sense to block 2.22 on it.
Flags: blocking2.22? → blocking2.22+
| Assignee | ||
Comment 7•19 years ago
|
||
| Assignee | ||
Updated•19 years ago
|
Target Milestone: --- → Bugzilla 2.20
| Assignee | ||
Comment 8•19 years ago
|
||
Attachment #205587 -
Flags: review?(wurblzap)
Updated•19 years ago
|
Attachment #205586 -
Flags: review?(wurblzap) → review+
Updated•19 years ago
|
Attachment #205587 -
Flags: review?(wurblzap) → review+
Updated•19 years ago
|
Flags: approval?
Flags: approval2.20?
Comment 9•19 years ago
|
||
Frédéric filed bug 319953 to follow up.
Updated•19 years ago
|
Flags: approval?
Flags: approval2.20?
Flags: approval2.20+
Flags: approval+
| Assignee | ||
Comment 10•19 years ago
|
||
tip: Checking in editflagtypes.cgi; /cvsroot/mozilla/webtools/bugzilla/editflagtypes.cgi,v <-- editflagtypes.cgi new revision: 1.30; previous revision: 1.29 done Checking in template/en/default/global/user-error.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/global/user-error.html.tmpl,v <-- user-error.html.tmpl new revision: 1.144; previous revision: 1.143 done 2.20: Checking in editflagtypes.cgi; /cvsroot/mozilla/webtools/bugzilla/editflagtypes.cgi,v <-- editflagtypes.cgi new revision: 1.19.4.1; previous revision: 1.19 done Checking in template/en/default/global/user-error.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/global/user-error.html.tmpl,v <-- user-error.html.tmpl new revision: 1.115.2.9; previous revision: 1.115.2.8 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•