Closed Bug 1359469 Opened 8 years ago Closed 8 years ago

Hard Block McAfee Anti-Spam Thunderbird Extension v2.0 for Thunderbird >= 52.0

Categories

(Toolkit :: Blocklist Policy Requests, enhancement)

52 Branch
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: wsmwk, Unassigned)

References

Details

(Whiteboard: [extension])

+++ This bug was initially created as a clone of Bug #1354912 +++ Please change the block requested in bug 1354912 from soft block to hard block. Thanks Extension name: McAfee Anti-Spam Thunderbird Extension Extension UUID: {msktbird@mcafee.com} Extension versions to block: <= 2.0 Applications, versions, and platforms affected: Thunderbird * Block severity: soft Reasons: addon causes topcrash bug 1281610 for Thunderbird 52.0 See bug 1281610 comment 17 and 18 for latest data. As of a last week McAfee have a potential solution that we have tested (as noted in bug 1281610). But I haven't heard from them for several days and they have notoriously long lead times to get fixes out, so I'm not willing to wait any longer for their plans nor their solution to ship.
I should add, IMO McAfee must be doing some trickery here, because I would have hoped the soft block to be more effective than it has been. Also, I've had some crashing users tell me they did not get a soft block notice. So this is an additional reason I'm asking for hard block.
Possible for this to be in production today? Is blocking our next release. Thanks
Flags: needinfo?(jorge)
This is currently blocked on some issues with the Kinto tool: https://github.com/mozilla-services/amo-blocklist-ui/issues/129
Flags: needinfo?(jorge)
The block update has been staged now. Andreas, please review. I'll send you the details over email.
Flags: needinfo?(awagner)
The block is now live.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(awagner)
Resolution: --- → FIXED
(In reply to Andreas Wagner [:TheOne] [use NI] from comment #5) > The block is now live. Thanks Andreas. For anyone concerned about why this block was put in place please see bug 1354912 comment 6
See Also: → 1354912
You need to log in before you can comment on or make changes to this bug.