Re: [secretariat][gorc-ig] Fwd: Undeliverable: RDA Virtual Plenary 17 - Notification of Acceptance

03 Mar 2021

Hi Stefanie, all
I know Vivien. She was at NIH but moved to Deloitte the other year so should have a new contact email there. I’d only been using the gmail one though so can’t provide updated details.
Good to reach out and check best contact detail now
From: <***@***.***> on behalf of StefanieKethers via Global Open Research Commons IG <***@***.***>
Reply to: "***@***.***" <***@***.***>
Date: Wednesday, 3 March 2021 at 07:12
To: RDA Secretariat <***@***.***>, Global Open Research Commons IG <***@***.***>
Subject: [secretariat][gorc-ig] Fwd: Undeliverable: RDA Virtual Plenary 17 - Notification of Acceptance
Hi all,
Does anyone know Vivien Bonazzi? She has three RDA accounts, two of which are subscribed to groups, but unfortunately only her gmail address works.
It would be good if we could reconcile the three accounts, as she currently does not receive emails via the GORC IG and the WG&IG Chairs (I just got a bounce).
If nobody knows her, I'll contact her.
---------- Forwarded message ---------
From: Microsoft Outlook <***@***.***>
Date: Tue, Mar 2, 2021 at 4:38 AM
Subject: Undeliverable: RDA Virtual Plenary 17 - Notification of Acceptance
To: <***@***.***>
[Image removed by sender.]
Your message to ***@***.*** couldn't be delivered.
When Office 365 tried to send your message, the receiving email server outside Office 365 reported an error.
Office 365
Action Required
Policy violation or system error
How to Fix It
Check the "Reported Error" from the "Error Details" section shown below for more information about the problem. The error might tell you what went wrong and how to fix it. For example, if the error states that the message was blocked due to a potential virus or because the message was too large, try sending the message again without attachments.
If you're not able to fix the problem, it's likely that only the recipient's email admin can fix it. Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin about the problem. Give them the "Reported Error" from the "Error Details" section below.
Was this helpful? Send feedback to Microsoft.
More Info for Email Admins
Status code: 550 5.0.350
The error reported by the receiving server wasn't specific enough to determine the exact nature of the problem. These errors often indicate the message violates a security or policy setting configured on the recipient's email servers.
If the sender is unable to fix the problem by modifying their message, then it's likely a problem that only the recipient's email admin can fix. Try the following:
Check the error for information about the problem - The "Reported Error" returned by the external email server can be found in the "Error Details" section below. This error might tell you what went wrong and provide clues for how to fix it. For example, if the error states the message was rejected due a Sender Policy Framework (SPF) issue, then you'll have to work with your domain registrar to correctly configure your domain's SPF records.
Check the error for information about where the problem is happening - For example, look for a domain name like A domain name in the error might suggest who is responsible for the error. It could be the recipient's email server, or it could be a third-party service that your organization or the recipient's organization is using to process or filter email messages.
If you can't fix the problem, contact the responsible party's email admin - Give them the error code and error message from this non-delivery report (NDR) to help them troubleshoot the issue. For security or policy violation issues, it might be sufficient for them to just add your sending IP addresses or domain to their allowed senders list.
It's likely that only the recipient's email admin can fix the problem. Unfortunately, it's unlikely Office 365 Support will be able to help with these kinds of externally reported errors.
Original Message Details
Created Date:
01/03/2021 17:38:28
Sender Address:
Recipient Address:
RDA Virtual Plenary 17 - Notification of Acceptance
Error Details
Reported error:
550 5.0.350 Remote server returned an error -> 550 #5.1.0 Address rejected.
DSN generated by:
Remote server:
Message Hops
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none;
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;;
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2-rdafound-onmicrosoft-com;
Received: from LO2P123MB1789.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:d0::18)
by LO2P123MB3743.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:12d::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.28; Mon, 1 Mar
2021 17:38:28 +0000
Received: from LO2P123MB1789.GBRP123.PROD.OUTLOOK.COM
([fe80::7880:901a:3c64:2e71]) by LO2P123MB1789.GBRP123.PROD.OUTLOOK.COM
([fe80::7880:901a:3c64:2e71%6]) with mapi id 15.20.3890.028; Mon, 1 Mar 2021
17:38:28 +0000
From: Secretariat <***@***.***>
To: andrew.treloar <***@***.***>, "***@***.***"
<***@***.***>, "***@***.***" <***@***.***>,
"***@***.***" <***@***.***>, "***@***.***"
<***@***.***>, mark.leggott <***@***.***>,
"***@***.***" <***@***.***>
CC: "***@***.***" <***@***.***>
Subject: RDA Virtual Plenary 17 - Notification of Acceptance
Thread-Topic: RDA Virtual Plenary 17 - Notification of Acceptance
Thread-Index: AQHXDsGwpeUEhGsp4kaC2Yvti0hSCw==
Date: Mon, 1 Mar 2021 17:38:28 +0000
Message-ID: <***@***.***>
Accept-Language: en-GB, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.46.21021202
authentication-results:; dkim=none (message not signed)
header.d=none;; dmarc=none action=none;
x-originating-ip: [2603:7081:3e02:47ca:19c:6c2e:b86d:962]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b9df4165-0b92-42f3-afa3-08d8dcd8d30e
x-ms-traffictypediagnostic: LO2P123MB3743:
x-ld-processed: 27ba0302-8538-4f6c-8fa9-772b1589479d,ExtAddr
x-microsoft-antispam-prvs: <***@***.***>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: culFbD5QAFQhRg8Vy9doQCZ7rkbpJEM1Tv5Jgrl3zfyi36pwxdA7/rb4HCNbkBMj5ktWA+V941VLagVo6MCgikVgj6GwgviYAyx4Uz+y+keOwt/EWRRHX1Xjot3ZgyMQdCJ7/62h0qMLBCSKUoC6SLc+rMQLblpY9M8ptP7ra+iv1mIxOrv4OSGquCkDALRu+eH2GVjVduv7MlThH/rKE64wEpfHUu0mkY1A7gtymtihKFjlVOdLbZ0mkmyDjHERQOQvTiP6apMO6lnIY/g53Eh46cs09ts9nVfrpa7agLwYNjsFTv5KulD5+hkRaNsYYmu/KpumTKe071tGcw1w4FscyDIXClWXBzvIVD6LWA1WF1rwNcEpV0UAE8GoMyrynN9m+5ov9MRn3qYPliah+htXXlY1AwwO9cxqpN+ALFnpnZkO4lhLsXlJiRHuXvSFX4e+Yf7RypDpj+lJnQXtViw2+YwhLtXyXTjckh4QHf7Ty3ac0JDzGl1X13gRMq1/va3wflE7gLYkVmtbSxfua3BRi3yfFNEiietE+aAHiE6mcoggiEbflKKbdIXHnofZ8geHcSIqcCn1rkMNLPX6Xd4Mv8W6tFx7DwBeGCPhy1ML9K/+iSAL1uwjvPM8+lCfJrTzbV6jzqrFkc8Q09/sjCXyyZZpaV6KVgN1C7jmNwNu/eHSsjfPAjRSjGzs+JS/
x-forefront-antispam-report: CIP:;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:LO2P123MB1789.GBRP123.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(366004)(376002)(39830400003)(396003)(136003)(346002)(66476007)(5660300002)(66556008)(66946007)(91956017)(2616005)(76116006)(478600001)(66446008)(64756008)(4326008)(110136005)(316002)(296002)(8676002)(6512007)(36756003)(83380400001)(186003)(71200400001)(6506007)(6486002)(2906002)(166002)(8936002)(15650500001)(86362001)(33656002)(45980500001)(369624004);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata: =?utf-8?B?aEt4V0pQSGkxMzFveG53ZEd6clVsQ0tsSWFrTm9PVWFpUnBMak5CWndmNlI2?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LO2P123MB1789.GBRP123.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: b9df4165-0b92-42f3-afa3-08d8dcd8d30e
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2021 17:38:28.4417
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 27ba0302-8538-4f6c-8fa9-772b1589479d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: HhECTgaupjYseGf4nouSKMoXQoZdnoyZduc6+HAP11Jn3nDEwQb/VADqR8J76ldCA+cprsn2fhfqSaH4dlzyJZyC/ttxIw/Gt/sSXgnODRE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB3743
---------- Forwarded message ----------
From: Secretariat <***@***.***>
To: "andrew.treloar" <***@***.***>, "***@***.***" <***@***.***>, "***@***.***" <***@***.***>, "***@***.***" <***@***.***>, "***@***.***" <***@***.***>, "mark.leggott" <***@***.***>, "***@***.***" <***@***.***>
Cc: "***@***.***" <***@***.***>
Date: Mon, 1 Mar 2021 17:38:28 +0000
Subject: RDA Virtual Plenary 17 - Notification of Acceptance
Dear Chairs of the Global Open Research Commons IG,
Congratulations! Your RDA Virtual Plenary 17 (VP17) session application titled A typology of the components of Global Open Research Commons has been approved by the Technical Advisory Board (TAB). Please consider this your official notification of acceptance.
Although your submission is fine, TAB has asked the Secretariat to communicate to you their recommendations to incorporate more interaction in the agenda, which could increase engagement with your audience, as well as reduce the scope a bit as it appears quite ambitious. If you have any questions or concerns regarding these suggestions, or would like to discuss your submission with TAB, please contact your TAB liaison, Frankie Stevens (copied in this email).
At this time, the Secretariat is scheduling all approved sessions and the draft programme will be published on 12th March. Any requests for changes should be made by 19th March and the final detailed programme with your session time and link to your session page will be published by 23rd March 2021 on the RDA website.
For this meeting, the organising committee has selected a virtual conference platform to integrate all aspects of the meeting (scheduling, meeting delivery, networking, etc.).
Information will be provided to you in the upcoming weeks regarding the platform, specifically related to its functionality and available training and support.
Going forward, please begin planning for your session. As a reminder, there will be some individuals who attend your session who are unfamiliar with your group’s work. We encourage you to keep your session page updated with information about your group, your session and opportunities attendees will have to engage with you and others during the session.
Please contact us at ***@***.***, or your TAB liaison, Karin Breitman (in copy), if you have any questions about your session.
Registration for VP17 will soon be going live, please see here for details together with an outline of the registration fees.
We look forward to your participation at VP17, and on behalf of the RDA TAB and Secretariat, thank you for your ongoing engagement with the RDA.
All the best,
RDA Secretariat
Dr Stefanie Kethers
Senior Business Analyst, ARDC
Director of Operations, Research Data Alliance
M +61 405844197
[Image removed by sender.]
Monash University
ARDC Office
Building T, 100 Sir John Monash Drive
Caulfield East, VIC 3145, Australia
[Image removed by sender.]
[Image removed by sender.]
[Image removed by sender.]
ARDC acknowledges the Traditional Owners of the lands
that we live and work on across Australia and pays its respect
to Elders past and present.
Please consider the environment before printing this e-mail.