Featured Badge Removed. Can't understand why - please help

[Dewde]

Recurring Emails for Gmail was among the first extensions to be included in the CWS as an MV3 and also among the first to get a Featured badge. It had the featured badge for years.

Recently, the badge has been removed and no reason given. I simply can't understand what the problem could be, because we haven't published any update since Nov 2024 and the badge has only been removed in July 2025, some 8 months later.

We have not changed anything in the listing or code and the badge got removed anyway. We applied again, but got rejected. Please, at least point in the right direction.

[Oliver Dunk]

Hi Dewde,

Generally, we don't share specific reasons when an item doesn't qualify for the featured badge. We also review items periodically so it is possible for the rating to change without releases.

One thing I notice looking at your listing is that your extension requests host permissions for all URLs. Is this needed? I can imagine why that may be flagged as it seems unnecessary for the functionality.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4e21dc86-da82-474a-a726-03b37823681cn%40chromium.org.

[Oliver Dunk]

Hmm, that is a bit tricky.

Why do you need to recreate the email yourself? Is there not a way to clone the original email or copy content over without needing to access it?

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

On Thu, Aug 28, 2025 at 2:55 PM Dewde <dee...@gmail.com> wrote:

Hi Oliver, I'd love to remove "host_permissions": ["*://*/*"], but I fail to see how. When the user creates a scheduled email from Gmail, the extension tries to accurately reproduce the email in our system for later sending. This includes all its attachments and this is where the problem lies. Gmail has many domains for attachments, docs or signatures and there's no public list. Restricting to some domains that we're aware of opens the door to many bugs and failures creating the emails. I'd love to implement a better solution, if there is any.

[Dewde]

Hi Oliver, I'd love to remove "host_permissions": ["*://*/*"], but I fail to see how. When the user creates a scheduled email from Gmail, the extension tries to accurately reproduce the email in our system for later sending. This includes all its attachments and this is where the problem lies. Gmail has many domains for attachments, docs or signatures and there's no public list. Restricting to some domains that we're aware of opens the door to many bugs and failures creating the emails. I'd love to implement a better solution, if there is any.

On Thursday, August 28, 2025 at 4:27:41 PM UTC+3 Oliver Dunk wrote: