Bug 1388782

Summary: bugzilla rejected automatically generated bug report claiming spam
Product: [Fedora] Fedora Reporter: George R. Goffe <grgoffe>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: abrt-devel-list, bazanluis20, huiwang, iprikryl, itamar, jberan, mhabrnal, michal.toman, mmilata, qgong
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:48:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
saved bug report from bug report wizard on fedora 25 system. bugzilla claimes that this report contains spam. none

Description George R. Goffe 2016-10-26 07:57:34 UTC
Created attachment 1214200 [details]
saved bug report from bug report wizard on fedora 25 system. bugzilla claimes that this report contains spam.

Description of problem:
start of firefox caused segfault in KWin. during the wizzard processing I got a message that the report contains spam. see enclosed bug report.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Emmanuel Seyman 2016-10-26 08:06:58 UTC
This looks specific to bugzilla.redhat.com .

Comment 2 Jeff Fearn 🐞 2016-10-27 03:32:13 UTC
Hi George, due to the ongoing spamming of Bugzilla instances we recently introduced a spam detection module, it occasionally gets false positives on trace backs and memory dumps, we are asking people to submit that kind of data as attachments.

I'm moving this bug to the abrt package because I think the best thing here would be for the wizard to have a clear statement about attaching these reports as attachments.

In some cases the cure is worse than the disease, but we are still getting a lot of spam comments blocked by the spam module so I think it's a win ATM.

Comment 3 George R. Goffe 2016-10-27 13:20:47 UTC
Jeff,

Thank you for all your help with this.

I was thinking that it might be nice for the wizard to prompt for adding as an attachment but this would defeat the purpose of the screening I think. As it is, just knowing what's going on could defeat the screening... the screening would force serious spammers to add their crap as attachments. 

Anyway, thanks for your help.

George...

Comment 4 Fedora End Of Life 2017-11-16 18:44:51 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:48:11 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.