Yves Dorfsman writes:
 > On 2015-09-10 05:43, Edward Ned Harvey (lopser) wrote:
 > > I cannot believe my eyes, and I'm not finding anybody complaining about 
 > > this
 > > on the internet, so can somebody please confirm you see the same behavior?
 > > 
 > > When you send email from yahoo, and the recipient doesn't exist (email
 > > bounces) then yahoo deletes the bounce message. So the sender is unaware of
 > > the problem, and continues sending email into oblivion.
 > 
 > It looks like your server is accepting the mail instead of stopping
 > it with a 550, which would be the right thing to do.

Mail to nonexistent recipients is better handled by rejection during the
SMTP session with a 5xx reply code to RCPT than by accepting it and then
generating a bounce message.  In particular this tends to better prevent
loops (such as when the bounce goes back to a badly-implemented
autoresponder) and bounces to forged sender addresses.  At the very
least it won't be *your* MTA generating the bounce message if a problem
like that arises.  If a legitimate sender sent the mail, *their* MTA
should be the one to generate a bounce message.

 > Then, what you call the "bounce email", which from what I can tell is
 > just a regular email, has a few anomalies such as the Return-Path not
 > being a valid email address, so it could be that yahoo spam filters
 > are refusing delivery.

The envelope sender for delivery status notifications is required to be
the null sender <>.  The Return-Path: header will typically show the
envelope sender, although many MTAs will insert a Return-Path: header
showing <MAILER-DAEMON>" (perhaps also with a domain) if the null
envelope sender was used.

What I actually see happening when I send a test message to the
nonexistent recipient <metabol...@nedharvey.com> is:

1.  The mail is being handled by outlook.com.  This means it may be
    difficult to change the observed behavior.

2.  As expected the envelope sender was null <> and so "Return-Path:
    <MAILER-DAEMON>" appears.

3.  outlook.com is sending back a verbose, highly customized,
    plain-text+HTML bounce message which may also have something to do
    with Yahoo filtering it.

[ Apparently including the entire outlook.com bounce exceeded the
  message size limit for this list, so I truncated it. ]

Return-Path: <MAILER-DAEMON>
Received: from na01-bn1-obe.outbound.protection.outlook.com 
(mail-bn1on0111.outbound.protection.outlook.com [157.56.110.111])
        by hexadecimal.uoregon.edu (8.14.4/8.14.4/Debian-8) with ESMTP id 
t8AH13Tc015884
        (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT)
        for <ste...@hexadecimal.uoregon.edu>; Thu, 10 Sep 2015 10:01:05 -0700
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="f968c49f-d67f-44a5-a4c2-d1a94a13e962"
X-MS-Exchange-Message-Is-Ndr:
Content-Language: en-US
Message-ID: 
<1f8f9961-89fc-402b-bb63-6d9b92fd9...@blupr04mb372.namprd04.prod.outlook.com>
In-Reply-To: <0b9ad4ea-962b-4ef4-81c5-cc35ba3e9...@by2ffo11fd015.protection.gbl>
References: <0b9ad4ea-962b-4ef4-81c5-cc35ba3e9...@by2ffo11fd015.protection.gbl>
Auto-Submitted: auto-replied
X-Microsoft-Exchange-Diagnostics:
        
1;BLUPR04MB372;25:AfxQxMgFznCJAp76xR38EiPhvEhc0TNu1CPQIxza5iQ1TJNJhwx2xZF6gVr0z+yPJx3bI7DU2HEZBWqfqN3rd9icfjMEtozdvEAMLMrVs2pmNm2VOa3H2+40YrBhlHeww/qBqsuEhAEDVLU+uS4nIw/ZI56vjOggUDpVZNJzSoaj/fT6a57JCKOQdAS9lm8tKYyIJhb81r9NXwrTW4pm3DE3Sbm3lzdPxcr7K4rcJWeC14/gxmaM4pCTQB2KZNXU;4:HKJMnMudd9A4s/iGhp+jl1is2aWfavCpFx2CsIkYG23WRG1kOplzQ68cS3ovEGT1ilAnd2h+5/7NH22BBJGq7a8zMMfgZpbbvzECAuX0QaFLVg7PoaKKQtWwslAGjNcGQrHvrPFQ80ar7+7o6Q2RvLHRMiSMOLxPtGyEp0FcRkpEgkqr3EV7CHoBk41C9IL7mwIIkgXXvff8aj/4oLcF02TcaVctNfJhqBLXnTbOEHQZe0I9nDP2Bxs4cU0UyVRWwN2EHg1OOfiIw0SbU3JxDgCf28KlfJ021dopt51JcaIOBNeqa65MyLNnjW+iqBho
X-Microsoft-Antispam-PRVS:
        
<blupr04mb3723c3482c86ac7042b95c2b8...@blupr04mb372.namprd04.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(108003899814671);
X-Exchange-Antispam-Report-CFA-Test:
        
BCL:0;PCL:0;RULEID:(601004)(8121501046)(5005006)(3002001);SRVR:BLUPR04MB372;BCL:0;PCL:0;RULEID:;SRVR:BLUPR04MB372;
X-Forefront-PRVS: 06952FC175
X-Forefront-Antispam-Report:
        
SFV:NSPM;SFS:(10019020)(189002)(377454003)(479174004)(3905003)(199003)(319900001)(450100001)(50986999)(54356999)(84326002)(19580405001)(76176999)(76576001)(11286001)(42382002)(97736004)(74316001)(46102003)(18206015028)(5007970100001)(4001540100001)(19580395003)(1496007)(33646002)(62966003)(2351001)(78352002)(229853001)(19617315012)(77156002)(101416001)(102106001)(2950100001)(5001960100002)(107886002)(189998001)(83832001)(105586002)(89962001)(106356001)(87976001)(64706001)(575784001)(5001920100001)(5001830100001)(5001860100001)(15975445007)(31696002)(86152002)(2171001)(1476001)(68736005)(512954002)(92566002)(110136002)(7099028)(82146005)(5001840100002);DIR:OUT;SFP:1102;SCL:1;SRVR:BLUPR04MB372;H:;FPR:;SPF:None;PTR:InfoNoRecords;MX:0;A:0;LANG:en;
Received-SPF: None (protection.outlook.com:  does not designate permitted
 sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=<>; 
X-Microsoft-Exchange-Diagnostics:
        
=?us-ascii?Q?1;BLUPR04MB372;23:GVzK0hsDeJsirkctujIpL0z82h0/tFEm8Ss3lKSsIA?=
 =?us-ascii?Q?33Nobk6zKlgep38C4NNt6mi05F73FuCJLT+TlO2cp/nrlnFSMPIOW9VWnw0d?=
 =?us-ascii?Q?JsAgRK+2Hxpt7/fz/5dF6MFt2x9i02OVTH2R/F8sZcYrZhvk+XnU5+bgkrVb?=
 =?us-ascii?Q?vv8toRP4Qr8RJWEX3XBlzMs5JIOBQxjLL5IuNyg5/o5Bd5fqx3g0jJpx5mGu?=
 =?us-ascii?Q?APiPlXCwKyBJZC0Fpa5Pq1w2G4tlYb8/XHyCVj/212rwTcw1/nJHD5dopO4F?=
 =?us-ascii?Q?X27R2tT/z3G2QQl9beL7479CY8BgFYawCUVn+XFtKn8CepEN+7g7+EmBx2HV?=
 =?us-ascii?Q?iB8/4SH5/NLP+T4G2nJOy9UQDQWB8xirBaRaYFKeUg68y+F6ApNF6UARs6ek?=
 =?us-ascii?Q?zAek796PfWVnMZ/P6cjDtBh5Y8bdzNcyJU3CossEMQMiWHsutsXwXdTv+Ycb?=
 =?us-ascii?Q?h5uEDZ7ttGI7OjlHNOqniqSUOMt5WXFwxjsHyoIJYXp/HCsFvyD9zT8LeHvf?=
 =?us-ascii?Q?BM31AJ2kZf/bUkW9PPh9x9HSQSYV/kPPV3+JfyZ29zr9VKlhAKjgOIm07UWu?=
 =?us-ascii?Q?V8N5XE1WtUNz47hOBVtSgZ8W0r2XLLap0T53awkCzi6iHjo5a1fsXh5Bh4Ue?=
 =?us-ascii?Q?ZYFB3s34GXO2EtD84QAaquV5uamyRXD4SnbgSZ+DBjEfInAoa72aWta9pIio?=
 =?us-ascii?Q?e84rM8HrQ4ECkQY2VjLU2AWrrWO42QzHSZFTfqL3CpNLF6/XBpj2v7g/oy7s?=
 =?us-ascii?Q?RTPtLVnfLV8128P8ciGB02Fr2sm4jwiJLhzH6BmNSeXT7vdgwcmrrAvz9rtj?=
 =?us-ascii?Q?RDpWPxR+yOUfJQTM6NbZCAQ7g2ES7BdgxU5EMF59k3bAo4NVWvspAJvfgWaC?=
 =?us-ascii?Q?+ErnkmhnkJf74rFZ5uAM/Vmhsq8Tf21j98FnJbCSBiBFmb6pn4c7/uJj8MHP?=
 =?us-ascii?Q?jaBBKh/x/DAyN5BGfZpJ5kgVRADM7cM47sLPvHtxaCLp4kUaWCxQubbkQ2EP?=
 =?us-ascii?Q?s70IGt8oXWFY02dYDsNJlcTjA6BxRSfHA5ru3cRVnl5ffpT7O4CvW1AoP4xv?=
 =?us-ascii?Q?D5MHo4nmWiKw7Lu5Cjvzi7t/RcFD7Z7mDdPdUY3DZNPU5cyYh1iXZyLvaFD/?=
 =?us-ascii?Q?FaMYIzL255DfK3Qopskkw/Jb9CCzViiJZzUMvMS84dr+oagVyACESgDwBVNO?=
 =?us-ascii?Q?jAlrza9NzkaWeoOxMpuv07n3wy3e5C8+Nms5wc7zkH2E6dRT10+oQoJwWcav?=
 =?us-ascii?Q?io8LbNYfZf2QCHqOGYtqz+HQnP35BTAsVtFjR1hyWBUVESxDOXYhfJLTqZJU?=
 =?us-ascii?Q?DWsYaY7TR8a3v3U8NJal6ZHDhXBUF3qk7anF8FewlTf3RxRFSXGW/x+qX396?=
 =?us-ascii?Q?yWTlrclezntiNsUKixqlG/ZXpNDvXvkIFlpOEwnaWj+SH1QvUA1BroJdTlsl?=
 =?us-ascii?Q?B9auNJ+zvf1pRSH8Fc/qVTmqF/yBbTULg3PeAi5nBd++mOBPKKtps9kP+lzw?=
 =?us-ascii?Q?IxCw+L879FFmUVCpvHVsDUHNHRG73nunk=3D?=
X-Microsoft-Exchange-Diagnostics:
        
1;BLUPR04MB372;5:9AadevMmcjk+ng5fJ+CqihF2esjd+6RZFz+YSTLIZIcdmnYNaFB6YIhScqmDE4Iyqa4Y0DzbhCbLYO/eCTCA+5QT8UMGKFfkwrWfeadq46PdiuucHmsctWjEgepIHv0ZuC65HMjsemB+aFN75fTUcA==;24:i9bou1GpOMtvSzgaSMf0vpkrYtbijozCgUuFmXl03z/UsAoU2iq7oAZlxEj2FdetGaEtiAh1EjNxqKKisnNK5/5KBLpRFWw5hNFHOBhBGKA=;20:YEjIAyK+ito+c+1o9KJWsVhWI+Mm9znswHG/rsxxBT7fx5UzCiU/Hphsh7yoxMd7SDlQ5rufRihaImzrpRqN/w==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: nedharvey.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Sep 2015 17:00:37.7290
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR04MB372
From: <postmas...@nedharvey.com>
To: <ste...@hexadecimal.uoregon.edu>
Subject: Undeliverable: test
Date: Thu, 10 Sep 2015 17:00:37 +0000

--f968c49f-d67f-44a5-a4c2-d1a94a13e962
Content-Type: multipart/alternative; differences=Content-Type;
        boundary="f5d366a9-fa9f-4e61-a886-e36b093fb653"

--f5d366a9-fa9f-4e61-a886-e36b093fb653
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?versio=
n=3Db8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to metabol...@nedharvey.com couldn't be delivered.

metabolism wasn't found at nedharvey.com

stevev  Office 365      metabolism
Action Required                 Recipient


Unknown TO address


How to Fix It
The address may be misspelled or may not exist. Try the following:

  *   Retype the email address then resend the message.
  *   Clear the recipient nickname cache in Outlook or Outlook Web App by f=
ollowing the steps in this article: NDR Response Code 5.1.10 in Exchange On=
line and Office 365<http://go.microsoft.com/fwlink/?LinkId=3D389363>.
  *   Contact the recipient (by phone or instant messaging, for example) to=
 check that the address is correct.
  *   The recipient may have set up mail forwarding to an incorrect address=
. Ask them to check that any forwarding they've set up is working correctly=
.


If the problem continues, forward this message to your email admin.


Was this helpful? Send feedback<http://go.microsoft.com/fwlink/?LinkId=3D52=
5921>.
________________________________


More Info for Email Admins
This error occurs because the sender sent a message to someone whose mailbo=
x is hosted by Office 365 but the email address is incorrect or doesn't exi=
st. The error is reported by the recipient's email system, but most often i=
t must be fixed by the person who sent it.

A common example of when this can happen is when the recipient changes thei=
r email address but the sender picks the person from their recipient nickna=
me list in Outlook or Outlook Web App. The nickname cache doesn't yet know =
about the new e-mail address -- it has stored the out-of-date email address=
 information -- so when the message is sent the wrong address is used, even=
 though the sender chose the right recipient.

Another example is if the recipient is an Office 365 user but a license is =
not assigned to the user. In the Office 365 Admin Center check that the use=
r has a valid license assigned to it.

Sometimes it needs to be fixed by the recipient or the recipient's email ad=
min, for example, when the recipient has created a mail forwarding rule to =
an incorrect address, or if there's a problem with their email address dire=
ctory. If the sender is using the correct recipient address, and it's still=
 not working, send a test message from another user mailbox to see if it's =
an issue unique to this sender. If you reproduce the problem sending from a=
nother user account, ask the recipient or the recipient's email admin to co=
nfirm that the recipient address exists, is correct, and is working. Sugges=
t they check for misbehaving forwarding rules or possible email address dir=
ectory issues (such as directory synchronization issues).

For more information, see NDR Response Code 5.1.10 in Exchange Online and O=
ffice 365<http://go.microsoft.com/fwlink/?LinkId=3D532972>.


Original Message Details
Created Date:   9/10/2015 4:59:45 PM
Sender Address: ste...@hexadecimal.uoregon.edu
Recipient Address:      metabol...@nedharvey.com
Subject:        test


Error Details
Reported error: RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP=
 address lookup
DSN generated by:       BLUPR04MB372.namprd04.prod.outlook.com


Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       9/10/2015
4:59:45 PM      hexadecimal.uoregon.edu BY2FFO11FD015.mail.protection.outlo=
ok.com       Microsoft SMTP Server   *
2       9/10/2015
5:00:36 PM      BY2FFO11FD015.protection.gbl    DM2PR04CA058.outlook.office=
365.com      Microsoft SMTP Server (TLS)     51 sec
3       9/10/2015
5:00:36 PM      DM2PR04CA058.namprd04.prod.outlook.com  BLUPR04MB372.namprd=
04.prod.outlook.com  Microsoft SMTP Server (TLS)     *

Original Message Headers

Received: from DM2PR04CA058.namprd04.prod.outlook.com (10.141.154.176) by
 BLUPR04MB372.namprd04.prod.outlook.com (10.141.25.148) with Microsoft SMTP
 Server (TLS) id 15.1.262.15; Thu, 10 Sep 2015 17:00:36 +0000
Received: from BY2FFO11FD015.protection.gbl (2a01:111:f400:7c0c::158) by
 DM2PR04CA058.outlook.office365.com (2a01:111:e400:243c::48) with Microsoft
 SMTP Server (TLS) id 15.1.262.15 via Frontend Transport; Thu, 10 Sep 2015
 17:00:36 +0000
Authentication-Results: spf=3Dnone (sender IP is 128.223.142.97)
 smtp.mailfrom=3Dhexadecimal.uoregon.edu; nedharvey.com; dkim=3Dnone (messa=
ge not
 signed) header.d=3Dnone;nedharvey.com; dmarc=3Dnone action=3Dnone
 header.from=3Dhexadecimal.uoregon.edu;
Received-SPF: None (protection.outlook.com: hexadecimal.uoregon.edu does no=
t
 designate permitted sender hosts)
Received: from hexadecimal.uoregon.edu (128.223.142.97) by
 BY2FFO11FD015.mail.protection.outlook.com (10.1.14.131) with Microsoft SMT=
P
 Server id 15.1.262.18 via Frontend Transport; Thu, 10 Sep 2015 16:59:45 +0=
000
From: <ste...@hexadecimal.uoregon.edu>
To: <metabol...@nedharvey.com>
Subject: test
Message-ID: <0b9ad4ea-962b-4ef4-81c5-cc35ba3e9568@BY2FFO11FD015.protection.=
gbl>
Return-Path: ste...@hexadecimal.uoregon.edu
Date: Thu, 10 Sep 2015 16:59:45 +0000
X-EOPAttributedMessage: 0
X-Microsoft-Exchange-Diagnostics: 1;BY2FFO11FD015;1:Q1EV7DwvRi5h/cvQ/PBfGKU=
fWlHN/RSsaQaqXIwO4nDo2Ed5Qf4h6YsU+TXPnkW68vpE2oG3N2seBAcuxjajdfMAL3n/7O5bu8=
it5j+23Bo9XECqpttIvN2F/w9+uthML8GFmFM91ycNxUXZUdFFC6AF8CqvTc1Su04R+iGHA8MIf=
XluJnnUfYo5iHvf4V6GpewzadWZBC/B4Gdw8kTgIRNGgXY6hwvYBuVxe4XYEN1BJz5KyOfn3kw/=
/SIyHJvK96ADL8d1u1B/Mom190+LGDcxnmz2BRguBsAf6/NJYcRNlEc74dNdd1kvHg+/0Ba0RmX=
RzqxloAAvjkTozs07sp+Yve6c07EQqCJ9xSuMQvIVg9Neaf30ibuY4Ukr6O/g5AIwj76gwpbm2W=
DKSgzYlQ=3D=3D
X-Forefront-Antispam-Report: CIP:128.223.142.97;CTRY:US;IPV:NLI;EFV:NLI;
MIME-Version: 1.0
Content-Type: text/plain
X-Microsoft-Exchange-Diagnostics:
        1;BLUPR04MB372;2:iCg8w2BirflmFW9s6y8rKWcinT/h8sj0sKyEJUtsmiQi8oVXgG=
by/4WAZ8vWq6TUmCcs3RAJhZzxJG7TZQuMMb4k8xhmtZvckdVMN8VXkSIVCZB60/9kU6P7K6lAH=
5asrOsX18g0YsR8PWpQieOwsPtqiuYw/PbfiKlN3l9G6pI=3D;3:mvrGt9FgjAYqFyl/n40Yzu5=
vWgZE1z3aEiEgSMHukl4pgeigXMPdcL0qQy0er4WewGltd8khgFz0/UTHKQn51UAYrOwJGwfYUi=
Bnx2WpGKuCIJEx4xxBr5auFDrPqvKxvR070aXEieaIKAjgbRfrosvAZMT8eu2x5KQg/ClH7C8Yq=
i7dLDzC/35Qe/N4pQTAd01BaM28e36eaXyv5RpE5KxhKgDx4gFLmJvqywZ9pqkDGSxLo8HLRr0l=
Izm8HxwizZNA+eGVJ3VpbrJ3KFOVeg=3D=3D;25:Rn8Q1U2dByyToPuXZIM/coETtbNPzKOK6Gv=
oPwQffpUko7eaR8PZ3jxiAY5LyhzyHX/bBF8gscHhyzDnaOxkypcnw6NwtTdwLTaHXqRsT8jF2m=
XlP8ezELgQ/XlPYu9FIUVG9OlpTdSD/sCRCYe+8w=3D=3D
X-Microsoft-Antispam:
        UriScan:;BCL:0;PCL:0;RULEID:(71701003)(71702001);SRVR:BLUPR04MB372;


_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to