You are currently receiving this
informational message with the original email attached.
We need your help in notifying the team or sender
responsible for this mail flow to ensure future email is
delivered properly.
The host that sent this message is not compliant with
Oracle's email security policy (DMARC). Please notify
the person(s) responsible for this message and share the
content below so they can take actions to resolve their
issue.
If you have no idea who is responsible, then please
address the #ww-oracle-dmarc slack channel for
assistance.
Deadlines
• We plan to move to quarantine non-compliant messages
early 2023 (date to be determined). After this date, if
the issues are not fixed, messages will be held in a
folder on our email gateway and will not be delivered to
you.
• We will then move to reject early 2023 (date to be
determined). After this date, messages will be rejected.
For more technical resources and information, see:
https://confluence.oci.oraclecorp.com/display/EMAIL/DMARC+for+Oracle+IT+and+Email+Delivery+Frequently+Asked+Questions
https://confluence.oraclecorp.com/confluence/display/OITGLOBAL/DMARC+Global+FAQ
Thank you in advance for your attention to this matter.
+1
for separate call or change of time on April 5.
regards,
Guru
Maybe we could schedule a
separate call to go over the servlet TCK, or
even just change the time for the April 5
meeting. Here is a poll for different times:
Really good idea! Thanks for this
cheers
Olivier
I would be happy to
participate, especially to talk about
the servlet TCK refactoring PR but 11am
EST is definitely complicated for my
AEST timezone. :(
--
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
--