42962 - sanitycheck should catch invalid mail templates

Status: RESOLVED WONTFIX

(Bugzilla :: Administration, task, P3)

Description

[Sebastian Späth]

Filing that bug for [e-mail] who is trying to create a bugzilla account.

You will be able to create an account but on the page where it says, your
password has been mailed to you, there will be the line added:
"No recipient addresses found in header". No e-mail will ever arrive.
The same error occurs when mailing your password to yourself (password forgotten
option)

This is critical as no new bugzilla accounts can be created!

Comment 1

[Tara Hernandez]

Is this for Mozilla.org or a local installatino of Bugzilla?

Comment 2

[Sebastian Späth]

*The* mozilla installation (bugzilla.mozilla.org), just try to mail yourself 
your password...
you have to turn cookies off, but what do I say: You should know best :-)

Comment 3

[Dawn Endico]

the passwordmail param's first line was a blank. I removed that. Maybe 
new accounts will work now.

Comment 4

[Sebastian Späth]

Great! The error message is gone, I get my password via a-mail at once.
So I assume creating new accounts should be working now.

I take the freedom as bug reporter to mark this one FIXED

Comment 5

[Matthew Tuck [:CodeMachine]]

This seems fixed, but I won't verify this until there is a sanity check to find
it in future.

Comment 6

[Dave Miller [:justdave]]

In search of accurate queries....  (sorry for the spam)

Comment 7

[Gervase Markham [:gerv]]

[e-mail] - so what's happening about this sanity check, then? :-)

Gerv

Comment 8

[Matthew Tuck [:CodeMachine]]

Nothing as far as I know.  I'm just waiting.

Comment 9

[Dave Miller [:justdave]]

this won't get fixed if the bug is closed....

Comment 10

[Matthew Tuck [:CodeMachine]]

Moving to new Bugzilla product ...

Comment 11

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 12

[Joel Peshkin]

These unloved bugs have been sitting untouched since June 2002 or longer.  If
nobody does anything else to them, they certainly won't make 2.18
Retargetting to 2.20.  If you really plan to push them right now, you might pull
them back in.

Comment 13

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.

Comment 14

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 15

[Frédéric Buclin]

Mail templates no longer exist as parameters. They have been moved to real templates.