How to subscribe to support bulletins

[Marcin_Lubojanski]

Anyone knows how can I subscribe to support bulletins? I had it configured some time ago but I didn't receive any new support bulleting last 2 years. 
I have tried to find it on netapp webpage but no success 🙂 
A colleague of mine is receiving them but he have no idea if he ever subscribed to that...

Example email:

From: NetApp Customer Communique <NetAppCustomerCommunique@netapp.com>
Sent: streda 29. marca 2023 5:06
To: NetApp Customer Communique <NetAppCustomerCommunique@netapp.com>
Subject: NetApp Support Bulletin - SU530: [Impact Critical] NTLM authentication fails due to enforcement of Netlogon RPC sealing (Microsoft CVE-2022-38023)

[Ontapforrum]

I received one this morning too 🙂 but never bothered to find out where it is subscribed.

Could you try login to your support profile, and then go to either email subscriptions or My profile section, preferences ? 

Also, check these:
https://security.netapp.com/advisory/
https://security.netapp.com/bulletins/
https://www.netapp.com/utility/subscribe/

Are you able to open a non-technical case ? Someone should be able to guide you.

[elementx]

If they can't figure out why and where they're getting it from, then it's a NetApp bug and the email itself could be the first bug to create.

Such emails should have "industry-standard" information in the footer - what they are, where to adjust one's preferences, where to unsubscribe (could be the same link as for editing preferences) and where to send feedback.

[Marcin_Lubojanski]

There was no information about that in the email that my colleague forwarded to me. I agree, for every email that came as part of any subscription - there should be a footer with info how to change the subscription. Not sure if that's not against GPDR if it's not there...

[elementx]

It's probably against GDPR, but in any case, it's bad user experience.

You could contact Support, attach the email, and ask them to figure out for you which team should fix this issue (as it's not a "product" issue, it's probably a NetApp IT or Support issue so request routing maybe slightly unusual).