Last modified: 2011-06-22 02:06:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14249 - BZ notification mails misbehave with long email addresses
BZ notification mails misbehave with long email addresses
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
All All
: Lowest trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
  Show dependency treegraph
Reported: 2008-05-24 15:22 UTC by Marco
Modified: 2011-06-22 02:06 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Marco 2008-05-24 15:22:11 UTC
Regarding bug 14243, I recieved the following mail yesterday:

>Simetrical <> changed:
>           What    |Removed                     |Added
>                 CC|                            |
>                   |                            |m
>            Summary|Security leak in edit part  |API allows editing with GET
>                   |                            |requests
>-- Configure bugmail: ------- You are receiving >this mail because: ------- You reported the bug. 

As Simetrical's email address is quite long, Bugzilla linewraps it, but in a wrong way; you cannot use this email address when you directly press on "Write a mail to this recipient".

(Yeah, I know this is a bit trivial, but it's a bug ;))
Comment 1 Brion Vibber 2008-05-27 23:21:28 UTC
Comment 2 p858snake 2011-06-22 02:06:45 UTC
WONTFIXing this, its a upstream issue that we will never likely patch ourselves and there isn't really any point to having it sit around in LATER forever.

Feel free to reopen when its fixed or if someone actually wants to work on it.

Note You need to log in before you can comment on or make changes to this bug.