Hi Netcat,

We are currently working on updating the trusted roots based on the current
Mozilla NSS root list and we should be able to send an update to the
community in a few weeks.

Thanks,
Erhan

On Tue, Feb 10, 2026 at 5:37 AM Netcat Zhai <[email protected]> wrote:

> Hi, Erhan
>
> I hope this email finds you well.
>
> As we move into 2026, I am writing to inquire if there is a planned
> schedule or a tentative timeline for the Gmail S/MIME Root List updates
> this year.
>
> Having a clearer understanding of the upcoming update windows would be
> extremely helpful for our technical planning and for ensuring our clients’
> certificate automation processes remain fully compliant with Gmail’s
> standards.
>
> Thank you for your time and I look forward to hearing from you.
>
> Best regards,
>
> Netcat
>
> 在2024年4月11日星期四 UTC+8 02:04:09<Rob Stradling> 写道:
>
>> Thanks Erhan!  That's excellent news!
>>
>> > At that time, the list of trusted certificates disclosed to
>> https://support.google.com/a/answer/7448393?hl=en will be updated
>>
>> Whilst you're preparing this update, please also review/update the CA
>> Owner names on that page.  (I'm particularly keen to see "Comodo" updated
>> to "Sectigo" :-) ).
>>
>> ------------------------------
>> *From:* Erhan Nergiz <[email protected]>
>> *Sent:* 10 April 2024 18:19
>> *To:* CCADB Public <[email protected]>
>> *Cc:* Andy Warner <[email protected]>; Ryan Dickson <[email protected]>;
>> CCADB Public <[email protected]>; Rob Stradling <[email protected]>;
>> Nicolas Lidzborski␄ <[email protected]>
>>
>> *Subject:* Re: Google's S/Mime trusted list Inclusion
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know
>> the content is safe.
>>
>> Hi,
>>
>> An update of Gmail’s S/MIME trusted roots is currently underway, and we
>> expect the updated trust list to land in approximately 4 weeks. At that
>> time, the list of trusted certificates disclosed to
>> https://support.google.com/a/answer/7448393?hl=en will be updated and we
>> will follow up with this community.
>> For the time being, while we continue to consider resourcing and
>> operationalizing a dedicated root program like we see with Chrome’s, we
>> will plan regular updates to this list following the set of S/MIME roots
>> trusted by NSS.
>>
>> Thanks,
>> Erhan, on behalf of the Gmail Security team
>> On Tuesday, April 9, 2024 at 10:27:36 AM UTC-7 Andy Warner wrote:
>>
>> The Gmail team is currently working on an update. We've passed along
>> suggestions about improving comms back to submitters and providing public
>> info about their update cadence.
>>
>> On Tue, Apr 9, 2024 at 10:01 AM 'Rob Stradling' via CCADB Public <
>> [email protected]> wrote:
>>
>> Hi Ryan.  That page <https://support.google.com/a/answer/7448393> is
>> still dated February 2020, and despite filling in that form
>> <https://docs.google.com/forms/d/e/1FAIpQLScoF0R5fbyp83ln2PJ-4i5EVReDcZN9IGJVmGuNQDG6HAel7w/viewform>
>>  in
>> June 2023 we have not been contacted by the Gmail Team.
>>
>> Are you able to share any updates or even ETAs from your side?  Is the
>> Gmail Team still planning to "action CA inclusion requests"?
>>
>> Thanks in advance for any help you can provide.
>>
>> ------------------------------
>> *From:* 'Ryan Dickson' via CCADB Public <[email protected]>
>> *Sent:* 22 June 2023 20:28
>> *To:* Francisco Marques <[email protected]>
>> *Cc:* CCADB Public <[email protected]>
>> *Subject:* Re: Google's S/Mime trusted list Inclusion
>>
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you recognize the sender and know
>> the content is safe.
>>
>> Hi all,
>>
>>
>> *Following-up:* The Gmail Team is planning an update to this page
>> <https://support.google.com/a/answer/7448393?hl=en> to help better
>> answer the community's questions and help action CA inclusion requests.
>>
>>
>> In the interim, they created this form
>> <https://docs.google.com/forms/d/e/1FAIpQLScoF0R5fbyp83ln2PJ-4i5EVReDcZN9IGJVmGuNQDG6HAel7w/viewform>
>>  to
>> allow interested parties to connect with members of the Gmail Team.
>>
>>
>> We've also directly shared the list of POCs who expressed interest in
>> S/MIME for Gmail 1) on this thread and 2) at the recent CA/Browser Forum
>> Face-to-Face. I encourage all interested parties to respond to the form,
>> regardless of whether they've previously expressed interest.
>>
>>
>> Thank you for your patience!
>>
>>
>> - Ryan
>>
>>
>>
>> On Wed, Jun 21, 2023 at 11:27 AM Francisco Marques <
>> [email protected]> wrote:
>>
>>
>> Hi Ryan,
>> DigitalSign thanks you for the efforts on helping us on this subject.
>> We will wait for additional information.
>> Best regards,
>> Francisco Marques.
>> Em sexta-feira, 16 de junho de 2023 às 14:20:41 UTC+1, Ryan Dickson
>> escreveu:
>>
>> Hi all,
>>
>> We're still working with our colleagues within Google to identify an
>> appropriate POC to help with these requests.
>>
>> We appreciate your continued patience and will follow up as soon as
>> possible.
>>
>> - Ryan
>>
>>
>> On Mon, Jun 5, 2023 at 4:30 AM dr. Szőke Sándor <[email protected]>
>> wrote:
>>
>> Hi,
>>
>>
>>
>> we would need the same contact information too.
>>
>>
>>
>> Microsec is already included on the trusted CA list for S/MIME with one
>> Root certificate, but we set up a new ECC based hierarchy in 2017, and we
>> would like to finish the transition to this hierarchy.
>>
>>
>>
>> We tried to contact Google in March but we had no success.
>>
>>
>>
>> Sándor
>>
>>
>>
>>
>>
>> *From:* 'Antti Backman' via CCADB Public <[email protected]>
>> *Sent:* Monday, June 5, 2023 9:38 AM
>> *To:* CCADB Public <[email protected]>
>> *Cc:* Ryan Dickson <[email protected]>; CCADB Public <[email protected]>;
>> Francisco Marques <[email protected]>
>> *Subject:* Re: Google's S/Mime trusted list Inclusion
>>
>>
>>
>> Hi,
>>
>>
>>
>> We're experiencing similar challengies, so would it be possible to have
>> the same help for us also, thanks
>>
>>
>>
>> Antti Backman, on behalf of Telia Company.
>>
>>
>>
>> perjantai 2. kesäkuuta 2023 klo 20.47.26 UTC+3 Ryan Dickson kirjoitti:
>>
>> Hi Francisco,
>>
>>
>>
>> We've engaged with our colleagues who manage the set of CA certificates
>> trusted by Gmail for S/MIME on your behalf.
>>
>>
>>
>> Someone should reach out to you shortly.
>>
>>
>>
>> Thanks,
>>
>> Ryan
>>
>>
>>
>> On Fri, Jun 2, 2023 at 1:32 PM Francisco Marques <[email protected]>
>> wrote:
>>
>> Hello All,
>>
>> My name is Francisco Marques and I'm speaking on behalf of DigitalSign.
>>
>> DigitalSign is a European eIDAS QTSP, which currently already has 2 root
>> CAs included in Mozilla trusted list.
>>
>> The reason I'm opening this chat is due to the fact that DigitalSign s
>> trying to apply for the inclusion of its issuing CAs into the trusted store
>> for Gmail S/MIME (the end user certificates are S/MIME certificates used
>> for digital signature and email signature).
>>
>> Additional info: https://support.google.com/a/answer/7448393
>>
>> Unfortunately, we are unable to proceed due to contact absence and lack
>> of reply on the general contacts.
>>
>> Since there's no specific channel for this subject, we will be grateful
>> for any help/information anyone can give/share with us.
>>
>> Thank you very much!
>>
>> Best regards,
>>
>> Francisco Marques, speaking on behalf of DigitalSign.
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CCADB Public" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/ccadb.org/d/msgid/public/ee34eaf3-1184-496b-9583-ad059f4554dfn%40ccadb.org
>> <https://groups.google.com/a/ccadb.org/d/msgid/public/ee34eaf3-1184-496b-9583-ad059f4554dfn%40ccadb.org?utm_medium=email&utm_source=footer>
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CCADB Public" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/ccadb.org/d/msgid/public/4706a25b-c55f-403c-ac48-d5ef191cdea5n%40ccadb.org
>> <https://groups.google.com/a/ccadb.org/d/msgid/public/4706a25b-c55f-403c-ac48-d5ef191cdea5n%40ccadb.org?utm_medium=email&utm_source=footer>
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CCADB Public" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/ccadb.org/d/msgid/public/CADEW5O9D8sY-JrPobsjbYRSyGo2CRUaZgvQY3Ky8gBe1_iPAMA%40mail.gmail.com
>> <https://groups.google.com/a/ccadb.org/d/msgid/public/CADEW5O9D8sY-JrPobsjbYRSyGo2CRUaZgvQY3Ky8gBe1_iPAMA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CCADB Public" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>>
>> To view this discussion on the web visit
>> https://groups.google.com/a/ccadb.org/d/msgid/public/MW4PR17MB472942BCF46742C68736BD95AA072%40MW4PR17MB4729.namprd17.prod.outlook.com
>> <https://groups.google.com/a/ccadb.org/d/msgid/public/MW4PR17MB472942BCF46742C68736BD95AA072%40MW4PR17MB4729.namprd17.prod.outlook.com?utm_medium=email&utm_source=footer>
>> .
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/CAGAqBvmGgcYZPR%2BeZhbZeDBYyD_yT7Wg46wBqWm8aHc%2B40WpVw%40mail.gmail.com.

Reply via email to