Open
Bug 266148
Opened 21 years ago
Updated 12 years ago
Adding non-existent/invalid CC: to a flag type incompatible with restricted bugs
Categories
(Bugzilla :: Attachments & Requests, defect)
Bugzilla
Attachments & Requests
Tracking
()
NEW
People
(Reporter: kiko, Unassigned)
References
Details
We currently do no validation of flag type CC lists. Since we do a check for the
CC: list when we have restricted attachments or a restricted bug, an invalid CC
list will be kicked silently out without warning. This triggers things like bug
266147.
I think we should require the CC: added to be a valid Bugzilla account.
Comment 1•20 years ago
|
||
The purpose of the CC list is to send messages to mailing lists like
reviewers@bugzilla.org, and such mailing lists often don't and generally
shouldn't have Bugzilla accounts. It may be worth validating the addresses on
the list for conformity with email address standards, but we shouldn't be
requiring them to be valid Bugzilla account addresses.
| Reporter | ||
Comment 2•20 years ago
|
||
Well, unless they are valid Bugzilla accounts, we won't be able to validate if
they can receive email or not; in that case we'll just need to kick that check
off Flag.pm:notify(). I however don't think that is the right thing to do.
I generally think that it simplifies things a lot if anyone that gets email from
Bugzilla should have a Bugzilla account; it's *really* easy to create one and
disable it if you don't want it used. This consistency would make the codebase
tighter.
| Reporter | ||
Updated•20 years ago
|
Blocks: rt-clean-up
Comment 3•20 years ago
|
||
I agree -- there's nothing wrong with having disabled Bugzilla accounts for
this, just like we have for nobody@mozilla.org or documentation@bugzilla.org.
OS: Linux → All
Hardware: PC → All
Updated•19 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•18 years ago
|
Assignee: myk → attach-and-request
Comment 4•17 years ago
|
||
Now that bug 455814 has been checked in, we could easily add mailing-lists to the CC list at no risk, i.e. we could require that all accounts added to it are valid Bugzilla accounts. Assuming we implement this restriction, what do we do on upgrade for older installations having non-Bugzilla accounts in the CC list? Remove them or automatically create an account for them?
Severity: major → normal
Comment 5•17 years ago
|
||
Automatically create a disabled account for them, I think.
Updated•16 years ago
|
Severity: normal → minor
You need to log in
before you can comment on or make changes to this bug.
Description
•