Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 576584

Summary:

Problems with emo-records email address

Product:

Community

Reporter:

Michael Jaeger <mcj>

Component:

Mail

Assignee:

Eclipse Webmaster <webmaster>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

mariateresa.delgado, shawn.kilpatrick, wayne.beaton

Version:

unspecified

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
screenshot showing the e-mail address which apparently does not work for my two e-mails	none

Description Michael Jaeger

2021-10-12 16:32:08 EDT

Created attachment 287307 [details]
screenshot showing the e-mail address which apparently does not work for my two e-mails

Hello,

I trie to change my e-mail address because of a change of employer.

The web page tells me to write at emo-records@...

Please see the screenshot.

Writing to this e-mail does not work for me. Pls see the error message below.

I have tried with both my old company account (when it was still working) and my private e-mail. In both cases the same error.

To where shall I submit my request to emo-records?

Please note that my company e-mail address does not work anymore, but "mcj@mcj.de" works.

Kind regards, Michael

the error message is:

This message was created automatically by mail delivery software.
Error
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

 emo-records@eclipse.org
   host mail.eclipse.org [198.41.30.200]
   SMTP error from remote mail server after RCPT TO:<emo-records@eclipse.org>:
   554 5.7.1 <emo-records@eclipse.org>: Relay access denied
Reporting-MTA: dns; wp223.webpack.hosteurope.de

Action: failed
Final-Recipient: rfc822;emo-records@eclipse.org
Status: 5.0.0
Remote-MTA: dns; mail.eclipse.org
Diagnostic-Code: smtp; 554 5.7.1 <emo-records@eclipse.org>: Relay access denied
Return-path: <mcj@mcj.de>
Received: from dynamic-2a01-0c22-77a0-5e00-9c3d-8b3a-50c0-ee6b.c22.pool.telefonica.de ([2a01:c22:77a0:5e00:9c3d:8b3a:50c0:ee6b]); authenticated
	by wp223.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	id 1mVq6k-0000Ey-L0; Thu, 30 Sep 2021 09:03:54 +0200
From: "Michael C. Jaeger" <mcj@mcj.de>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_725CD23F-FA2E-41CC-A3EE-D1DA0788F636"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Subject: Fwd: Eclipse Committer Account Change
Message-Id: <DAEF28BA-AE14-417D-A8D7-5C81C4098968@mcj.de>
References: <284D1919-74AE-4586-BCB7-1E1C175A80B5@siemens.com>
To: emo-records@eclipse.org
Date: Thu, 30 Sep 2021 09:03:54 +0200
X-Mailer: Apple Mail (2.3445.104.21)

Comment 1 Maria Teresa Delgado

2021-10-13 11:22:06 EDT

Webmaster, could you please help?

Comment 2 Eclipse Webmaster

2021-10-13 11:37:49 EDT

We had a minor outage in mail routing at the end of September which has been resolved.

This message looks like it dates form this time, do you have a more recent example of it failing?

-M.

Comment 3 Michael Jaeger

2021-10-26 16:41:10 EDT

I am sorry, my recent e-mail to emo-records was to use mcj@mcj.de. Apparently you changed the address to other "found address". This is not OK, as it mention the wrong affiliation for this project.

Comment 4 Eclipse Webmaster

2021-10-27 10:17:03 EDT

(In reply to Michael Jaeger from comment #3)

Sorry I don't understand your last comment.  Are you still unable to contact emo-records ?

-M.

Comment 5 Wayne Beaton

2021-11-02 12:05:20 EDT

AFAICT, we have the correct email address and employer information for Michael, so  I think that we're done here. Please correct me if I'm wrong.

I'm capturing a timeline for the retrospective.

* Michael sent a note on September 30/2021 to inform the EMO Records team of the email change; that email bounced;
* Michael opened this issue on October 12/2021;
* Maria Teresa forwarded a note to EMO Records pointing to this issue on October 13/2021;
* Shawn reached out to Michael on October 18/2021;
* The issue was resolved on October 28/2021.

AFAICT, it took 16 days once we became aware of the issue to effect this change. This is too long. I'll initiate an internal audit.