Incorrect registrant on the Apache Hadoop mailing list is causing a lot of
delivery failure return mails
--------------------------------------------------------------------------------------------------------
Key: HADOOP-8062
URL: https://issues.apache.org/jira/browse/HADOOP-8062
Project: Hadoop Common
Issue Type: Task
Reporter: Harsh J
Priority: Trivial
Unsure who has moderation/admin access to mailing list subscriptions for Apache
Hadoop but the following address somehow got registered but is not useful for
the mailer:
bq. "NOTES:Stanislav_Seltser/SSP/SUNGARD%SSP-Bedford"@sas.sungardrs.com
Failure mail that comes for every mail the mailer sends:
{code}
Your message
Subject: Re: Hadoop Terasort Error- "File _partition.lst does not exist"
was not delivered to:
"NOTES:Stanislav_Seltser/SSP/SUNGARD%SSP-Bedford"@sas.sungardrs.com
because:
The message could not be delivered because the recipient's destination email
system is unknown or invalid. Please check the address and try again, or
contact your system administrator to verify connectivity to the email system of
the recipient. [MAPI Reason Code: 0, MAPI Diagnostic Code 48]
Final-Recipient:
rfc822;"NOTES:Stanislav_Seltser/SSP/SUNGARD%SSP-Bedford"@sas.sungardrs.com
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Notes;The message could not be delivered because the
recipient's destination email system is unknown or invalid. Please check the
address and try again, or contact your system administrator to verify
connectivity to the email system of
---------- Forwarded message ----------
From: <harsh cloudera.com>
To: <common-u...@hadoop.apache.org>
Cc:
Date: Wed, 25 Jan 2012 01:10:21 -0500
Subject: Re: Hadoop Terasort Error- "File _partition.lst does not exist"
Apparently, you are running terasort with a local job runner as
explained by the presence of "org.apache.hadoop.fs.RawLocalFileSystem"
and "LocalJobRunner" in your provided log message.
{code}
If this is the wrong place to report this, please do help moving it to right
section -- INFRA?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
