Bug #43870 mysqlbug does not actually report bugs anywhere
Submitted: 26 Mar 2009 0:26 Modified: 1 Apr 2009 18:18
Reporter: Dan Jacobson Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:4.1, 5.0, 5.1, 6.0 OS:Any
Assigned to: CPU Architecture:Any

[26 Mar 2009 0:26] Dan Jacobson
There is a weird word at the end of this sentence on the mysqlbug man page:

...report by email. perform.

By the way, sending in bugs via mysqlbug does not work.
They apparently go into a black hole.

How to repeat:
man mysqlbug
[26 Mar 2009 14:43] Sveta Smirnova
Thank you for the report.

Verified as described.

Typo is at http://dev.mysql.com/doc/refman/5.1/en/mysqlbug.html
[1 Apr 2009 16:01] Paul DuBois
I've removed the extraneous word from the manual.

Recategorizing as Server: General and unassigning myself so that the "black hole" aspect of the bug description can be dealt with.
[2 Apr 2009 16:36] Timothy Smith
Updating title to reflect the current reason for this bug to be open.
[18 May 2010 22:08] Hartmut Holzgraefe
Three possible reasons for mail not working:

1) local mail setup not configured to send to the public world

2a) the target list mysql@lists.mysql.com is spam protected, so even if the message gets out it may require confirmation. 

2b) by default the outgoing From: address is "username@hostname" which is probably not a valid address, so the confirmation request from 2a) is never seen, and so the report is never unlocked