Delivery Notification: Delivery has failed

I keep receiving a "Delivery Notification: Delivery has failed" message about a message that I apparently sent 4 years ago. How can I stop it?
Also please see notes at bottom of post!
thanks and regards
vats3
Delivery Notification: Delivery has failed
1 Attachment
This report relates to a message you sent with the following header fields:
Message-id: <[email protected]>
Date: Thu, 04 Nov 2010 11:58:43 -0700 (PDT)
From: {edited for privacy}
To: addressees deleted for this forum entry
Subject: Re: ACC Ladies Night Out
Your message cannot be delivered to the following recipients:
Recipient address: {edited for privacy}
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
Remote system: dns;mta6.am0.yahoodns.net (TCP|206.46.173.19|47987|63.250.192.46|25) (mta1640.mail.gq1.yahoo.com ESMTP ready)
Reporting-MTA: dns;vms173019.mailsrvcs.net (tcp_yahoo-daemon)
Arrival-date: Fri, 16 May 2014 10:29:51 -0500 (CDT)
Original-recipient: rfc822;{edited for privacy}
Final-recipient: rfc822;{edited for privacy}
Action: failed
Status: 5.0.0 (SMTP transmission failure has occurred)
Remote-MTA: dns;mta6.am0.yahoodns.net
(TCP|206.46.173.19|47987|63.250.192.46|25)
(mta1640.mail.gq1.yahoo.com ESMTP ready)
Diagnostic-code: smtp;554 5.7.9 Message not accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html
1. Hamburger Hamlet
2. Clydes
3. Rio Grande
The rest of the original messge was deleted by vats3 for this forum and also forum software gave me the following:
"Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied."
could it be that the removed html was causing the problem?
About Us | Store Locator | Support | Site Map | Send Feedback | Careers | Verizon Think

If you are using a mail client, make sure the failed message is not in your outbox. If it is in there, the mail client will keep trying to send the email until you remove it.

Similar Messages

Delivery Notification: Delivery has been delayed

I'm not getting only "Delivery Notification: Delivery has failed" but no "Delivery Notification: Delivery has been delayed"
please help me on this.
Chinthake
# /opt/sun/comms/messaging64/sbin/imsimta qm
qm.maint> sum
Queued Queued
Channel Messages = Active + Delayed Size (Mb)
process 0 0 0 0.0
process_dsn 0 0 0 0.0
reprocess 0 0 0 0.0
tcp_intranet 0 0 0 0.0
tcp_local 60147 60147 0 322.8
tcp_notify 6267 6267 0 39.0
tcp_yahoo 790 790 0 10.5
Totals 67204 67204 0 372.3
qm.maint> top tcp_notify
Building a list of message files to scan from the queue directory tree...
The list will contain only messages from channels matching "tcp_notify"
Scanning 6268 message files...
Scanned 6268 message files in 12.9481 seconds (484.09 messages/second)
Top 20 Subject: header lines which occur 2 or more times
Count Subject
====== ======================================================================
6178 Delivery Notification: Delivery has failed
qm.maint>
# /opt/sun/comms/messaging64/sbin/imsimta version
Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 64bit)
libimta.so 6.3-5.02 (built 17:38:05, Oct 12 2007; 64bit)
SunOS whale1 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V240
18-Apr-2008 10:51:44.86 tcp_local tcp_local E 1 [email protected] rfc822;[email protected] [email protected]
18-Apr-2008 10:56:02.29 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 12:39:56.56 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 14:36:56.22 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 16:46:57.58 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 21:18:53.01 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 01:22:37.67 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 05:26:21.68 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 13:45:08.09 tcp_local Q 1 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 22:08:13.46 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 06:11:57.68 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 14:46:20.35 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 23:29:46.72 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 07:37:34.24 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 11:39:57.29 tcp_local Q 2 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 13:26:22.90 tcp_local Q 3 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 21:44:28.30 tcp_local Q 3 [email protected] rfc822;[email protected] [email protected] TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
# cat imta.cnf
! IMTA configuration file
! part I : rewrite rules
! Domain Rewrite Rules.
! Uncomment this line to use domain rewrite rules
! from the configuration file instead of the domain database.
! Please refer to the iMS documentation for details.
!<IMTA_TABLE:domains.rules
! Rules to select local users
$* $A$E$F$U%[email protected]
whale1.slt.lk $U%[email protected]
siore.com $U%[email protected]
yahoo.com [email protected]
! ims-ms
.ims-ms-daemon $U%$H.ims-ms-daemon@ims-ms-daemon
! lmtp
!.lmtp $U%$H@lmtpcs-daemon
! lmtpn
!.lmtpn $U%$H@lmtpcn-daemon
! native
.native-daemon $U%$H.native-daemon@native-daemon
! pipe
.pipe-daemon $U%$H.pipe-daemon@pipe-daemon
<IMTA_TABLE:internet-dsn.rules
! tcp_local
! Rules for top level internet domains
<IMTA_TABLE:internet.rules
! tcp_intranet
! Do mapping lookup for internal IP addresses
[] $E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemon
.siore.com $U%$H.siore.com@tcp_intranet-daemon
* $U%$&0.siore.com
! reprocess
reprocess $U%reprocess.whale1.slt.lk@reprocess-daemon
reprocess.whale1.slt.lk $U%reprocess.whale1.slt.lk@reprocess-daemon
! process
process $U%process.whale1.slt.lk@process-daemon
process.whale1.slt.lk $U%process.whale1.slt.lk@process-daemon
! defragment
defragment $U%defragment.whale1.slt.lk@defragment-daemon
defragment.whale1.slt.lk $U%defragment.whale1.slt.lk@defragment-daemon
! conversion
conversion $U%conversion.whale1.slt.lk@conversion-daemon
conversion.whale1.slt.lk $U%conversion.whale1.slt.lk@conversion-daemon
! bitbucket
bitbucket $U%bitbucket.whale1.slt.lk@bitbucket-daemon
bitbucket.whale1.slt.lk $U%bitbucket.whale1.slt.lk@bitbucket-daemon
! deleted
deleted-daemon $U%$H@deleted-daemon
.deleted-daemon $U%$H@deleted-daemon
! inactive
inactive-daemon $U%$H@inactive-daemon
.inactive-daemon $U%$H@inactive-daemon
! hold
hold-daemon $U%$H@hold-daemon
.hold-daemon $U%$H@hold-daemon
! part II : channel blocks
!defaults notices 1 2 4 7 copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com
!defaults notices 1 2 4 nowarnpost nosendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com logging notificationchannel process_dsn dispositionchannel process_dsn
defaults notices 1 2 4 copywarnpost nosendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com logging notificationchannel process_dsn dispositionchannel process_dsn
! delivery channel to local /var/mail store
l subdirs 20 viaaliasrequired maxjobs 7
whale1.slt.lk
! ims-ms
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 2 pool IMS_POOL fileinto $U+$S@$D
ims-ms-daemon
! native
native defragment subdirs 20 maxjobs 1
native-daemon
! pipe
pipe single defragment subdirs 20
pipe-daemon
! tcp_local
!tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck disconnectbadcommandlimit 5 mailfromdnsverify
tcp-daemon
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4
tcp_intranet-daemon
! tcp_submit
tcp_submit submit smtp mx single_sys mustsaslserver maytlsserver missingrecipientpolicy 4
tcp_submit-daemon
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4
tcp_auth-daemon
! tcp_tas
tcp_tas smtp mx single_sys allowswitchchannel mustsaslserver maytlsserver deliveryflags 2
tcp_tas-daemon
! tcp_lmtpss (LMTP server - store)
!tcp_lmtpss lmtp flagtransfer
!tcp_lmtpss-daemon
! tcp_lmtpcs (LMTP client - store)
!tcp_lmtpcs defragment lmtp port 225 nomx single_sys subdirs 20 maxjobs 7 pool SMTP_POOL dequeue_removeroute
!lmtpcs-daemon
! tcp_notify
!tcp_notify smtp mx single_sys remotehost inner subdirs 20 maxjobs 10 pool NOTIFY_POOL backoff "pt4h" "pt8h" notices 1 loopcheck
tcp_notify smtp mx single_sys remotehost inner subdirs 20 maxjobs 10 pool NOTIFY_POOL notices 1 backoff "pt4h" "pt8h" nosendpost loopcheck
tcp_notify-daemon
!tcp_yahoo
tcp_yahoo smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 30 threaddepth 32 pool SMTP_POOL maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 recipientlimit 125
!tcp_yahoo-daemon
yahoo.com
! reprocess
reprocess
reprocess-daemon
! process
process
process-daemon
! defragment
defragment
defragment-daemon
! conversion
conversion
conversion-daemon
! bitbucket
bitbucket
bitbucket-daemon
! deleted
deleted
deleted-daemon
! inactive
inactive
inactive-daemon
! hold
hold
hold-daemon
!process_dsn
process_dsn
process_dsn-daemon

jay_plesset wrote:
The notification messages are generated by the "return" job, that's normally scheduled to run nightly. If you're not receiving/sending these, you will need to check that that return job is in fact getting run.Adding to Jay's comment, I set up the same configuration you are using and the notifications of Delayed email were working fine:
26-Apr-2008 00:30:00.82 tcp_local process_dsn E 1 rfc822;[email protected] [email protected] tcp-daemon.server.aus.sun.com ''
Date: Sat, 26 Apr 2008 00:30:00 +1000 (EST)
From: [email protected]
Subject: Delivery Notification: Delivery has been delayedI am using the following CONVERSIONS mapping table entry:
CONVERSIONS
IN-CHAN=process_dsn;OUT-CHAN=tcp_*;CONVERT Yes,Channel=tcp_notifyRegards,
Shane.

Delivery Notification: Delivery has timed out and failed

I keep getting several emails a day from [email protected]. If you read the body of the email you can see an email that looks like it was sent by me but I didn't send it. Does anyone know what is happening? Thanks! Here is the body of the text.
his report relates to a message you sent with the following header fields:
Message-id: <CHILKAT-MID-f2c8ecc8-c296-f5b0-c180-400d4263475b@USER00>
Date: Mon, 28 Feb 2011 11:14:03 -0800
From: [email protected]
To: [email protected]
Subject:
=?iso-8859-1?Q?=D2=F3=F0=FB=F1=EE_=F1=EA=E8=E4=EA=EE=E9_=EE=F2_20_=E4=EE50%?=
Your message is being returned; it has been enqueued and undeliverable for
4 days to the following recipients:
Recipient address: [email protected]
Reason: unable to deliver this message after 4 days
Recipient address: [email protected]
Reason: unable to deliver this message after 4 days
Recipient address: [email protected]
Reason: unable to deliver this message after 4 days
Delivery attempt history for your mail:
Fri, 04 Mar 2011 18:19:16 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Fri, 04 Mar 2011 10:18:41 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Fri, 04 Mar 2011 02:18:26 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Thu, 03 Mar 2011 18:18:12 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Thu, 03 Mar 2011 10:18:11 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Thu, 03 Mar 2011 02:18:07 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Wed, 02 Mar 2011 18:17:56 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Wed, 02 Mar 2011 10:17:34 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Wed, 02 Mar 2011 02:17:33 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Tue, 01 Mar 2011 18:17:32 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Tue, 01 Mar 2011 10:17:19 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Tue, 01 Mar 2011 02:16:40 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 22:15:25 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 18:14:19 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 14:12:32 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 13:44:39 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 12:14:37 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Mon, 28 Feb 2011 11:14:22 -0800 (PST)
Temporary error returned by SMTP partner.
smtp;476 connections from your host are denied
Reporting-MTA: dns;asmtp011.mac.com (tcp-daemon)
Arrival-date: Mon, 28 Feb 2011 11:14:13 -0800 (PST)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;[email protected]
Action: failed
Status: 4.4.7 (unable to deliver this message after 4 days)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;[email protected]
Action: failed
Status: 4.4.7 (unable to deliver this message after 4 days)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;[email protected]
Action: failed
Status: 4.4.7 (unable to deliver this message after 4 days)
From: [email protected]
Date: February 28, 2011 1:14:03 PM CST
To: [email protected]
Subject: Òóðû ñî ñêèäêîé îò 20 äî 50%
Reply-To: [email protected]
ÝÊÑÏÅÄÈß - ýòî âñåãäà ëó÷øèå òóðû ïî ñàìîé îïòèìàëüíîé öåíå!
Îáðàùàÿñü ê íàì âû íà 100% óâåðåíû â êà÷åñòâå è ëó÷øèõ öåíàõ ïðåäëàãàåìûõ íàìè Òóðîâ
Çàêàçûâàéòå ïðÿìî ñåé÷àñ: http://www.expedea.ru/
Èëè çâîíèòå ïî òåë: 8(499)150-80-57 è 8(499)150-90-85
Íà ñàéòå Ýêñïåäèÿ âû íàéä¸òå òîëüêî ðåàëüíûå òóðû, ìû íå èñïîëüçóåì ñòàíäàðòíûå ïîèñêîâèêè òàê êàê èíôîðìàöèÿ â íèõ ÷àñòî íå àêòóàëüíà.
Íà íàøåì ñàéòå Ýêñïåäèÿ ïðåäñòàâëåíû ëó÷øèå ÒÎ ñ ïîèñêîâèêàìè - ïîäîáðàâ ñåáå òóð ñàìîñòîÿòåëüíî âû âñåãäà ìîæåòå ðàññ÷èòûâàòü íà 5% ñêèäêó îò öåí ÒÎ.
Çäåñü âû òàê æå ñìîæåòå íàéòè ëó÷øèå ×èïÒðèï òóðû (ÒÓÐÛ Ñ 50% ñêèäêîé) ïðîâåðåííûõ íà àêòóàëüíîñòü ñî çíàêîì êà÷åñòâà ÝÊÑÏÅÄÈß.
ÅÑËÈ ÂÛ ÇÀÒÐÓÄÍßÅÒÅÑÜ Ìû ïîäáåð¸ì Âàì ëó÷øèé òóð ïî ëó÷øåé öåíå â ëþáóþ ñòðàíó,ëþáîé âèä òóðîâ, òàê-êàê ÝÊÑÏÅÄÈß ýòî âñåãäà ëó÷øèå öåíû íà òóðèñòè÷åñêîì ðûíêå!
Òóðñêèäêè ðàññ÷èòûâàþòñÿ èíäèâèäóàëüíî â îôèñå ïðîäàæ è çàâèñÿò îò ñòîèìîñòè âûáðàííîãî Âàìè òóðà, òóðîïåðàòîðà, âðåìåíè âûëåòà.
Çàêàçûâàéòå ïðÿìî ñåé÷àñ: http://www.expedea.ru/
Èëè çâîíèòå ïî òåë: 8(499)150-80-57 è 8(499)150-90-85
Åñëè âàì íå èíòåðåñíà äàííàÿ èíôîðìàöèÿ, òî ïåðåøëèòå ýòî ïèñüìî íà: [email protected]

That's spam. They are spoofing your email addy as a return address and as the sender. No way to stop it because once the email gets on a mailing list, it is sold all over the world.
I too have the same issue with my .mac email addy. I want to stop receiving only .mac addressed emails from being delivered as they are now 99% spam and nothing useful comes in that mailbox anymore.
Anyone have an idea on how to stop ONLY .mac emails?? but not affect me.com or icloud.com since they are all tied together?
Mike

Delivery Failure/Delivery Notification: Delivery has failed issues

Anyone getting hundreds of emails that seem to have been sent from your mac.com account but you haven't them or know any of the receipents? Delivery failure messages are coming from [email protected] and [email protected]
I was on the phone with Apple Express Lane and the support tech tried really hard to help me but couldn't. He is asking me to figure out who sent the email and tell them to stop. I'm no techogeek and don't even know where to start.
Does anyone know how to stop these fraudulent emails from cloggin up my email on all my devices?
I get from 50-100 a day and it is really annoying to delete them everyday.
Here is a sample of the header I get:
This report relates to a message you sent with the following header fields:
Message-id: <[email protected]>
Date: Mon, 18 Jun 2012 06:00:00 +0200
From: Wvvke lcmhw <[email protected]> <----i removed my email address
To: [email protected], [email protected] <--- i removed the long list recipients emails none of which I know
Subject: fobiqe <------many different subjects this is just an example of one
The long header reads:
Return-path <>
Received: from st11b01mm-asmtp205.mac.com ([17.172.48.68]) by ms02534.mac.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.24.0) 64bit (built Jan 3 2012)) with ESMTP id <[email protected]> for [email protected]; Mon, 19 Jun 2012 12:14:48 +0000 (GMT)
Original-recipient: rfc822; [email protected]
Too lazy to hand jam the whole header...Any help, suggestions etc to stop this annoyance?

When people receive emails which appear to come from their own address but they haven't sent they naturally tend to be concerned: however it's most unlikely that anyone has hacked their account, they've just been targeted by one of two common spammers' techniques: both arise because it's all too easy to forge the 'from' address on messages to be something other than the real one.
There are two things that can happen. One is that the sender has forged the 'from' address to be the same as the 'to' address (so other people will see it coming from themselves, not you), presumably in the hope of confusing spam filters. It's harmless, if extremely annoying. Delete it (never ever answer spam or try to unsubscribe from it), and you don't need to be worried about it.
The other problem - which appears to be what is affecting you - is that a spammer is forging your address as the 'from' address on a whole batch of messages. The first thing you hear about this is when you start getting bounce messages because the spam has been sent to non-existent addresses and is being bounced to you. There's no point at all in responding to it. It's infuriating but normally stops after a bit as they move on to another forged address.
There isn't really anything you can do about it: closing the account isn't really worth the hassle unless you are totally swamped, because you will have to tell everyone your new address. Apple can't really do any more than they already are about spam.

How can I do? keep received "Fwd: Delivery Notification: Delivery has failed" I didnt send this mail.

I received this mail more then 300 per-day please help!!
his report relates to a message you sent with the following header fields
Message-id: <[email protected]>
Date: Thu, 19 Sep 2013 20:17:19 -0500
From:
To:
Subject:
=?UTF-8?B?0L/QuNGB0YzQvNC+INC+0YIg0J3QsNGC0LDQu9GM0Lgg0JrRgNCw0LLRhtC+?=
=?UTF-8?B?0LLQvtC5?=
Your message cannot be delivered to the following recipients:
Recipient address:
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;550 spam message discarded. Please visit http://help.mail.ru/notspam-support/id?c=AZdNgCI5VwDmYlnFlVmFRa7O5sgRbqo7CgAAAOx TAACbOVgO or report details to [email protected]. Error code: 804D970100573922C55962E645855995C8E6CEAE3BAA6E11. ID: 0000000A0000
Remote system: dns;mxs.mail.ru (TCP|17.158.161.4|37589|94.100.176.20|25) (Mail.Ru ESMTP)
Original-envelope-id: [email protected]
Reporting-MTA: dns;nk11p00mm-asmtp005.mac.com (tcp-daemon)
Arrival-date: Fri, 20 Sep 2013 01:17:28 +0000 (GMT)
Original-recipient: rfc822;
Final-recipient: rfc822;
Action: failed
Status: 5.0.0 (SMTP transmission failure has occurred)
Remote-MTA: dns;mxs.mail.ru (TCP|17.158.161.4|37589|94.100.176.20|25)
(Mail.Ru ESMTP)
Diagnostic-code: smtp;550 spam message discarded. Please visit
http://help.mail.ru/notspam-support/id?c=AZdNgCI5VwDmYlnFlVmFRa7O5sgRbqo7CgAAAOx TAACbOVgO or
report details to [email protected]. Error code:
804D970100573922C55962E645855995C8E6CEAE3BAA6E11. ID: 0000000A0000
寄件人:
標題: письмо от Натальи Кравцовой
日期: September 19, 2013 6:17:19 PM PDT
Доброго Вам дня! сразу представлюсь Наталья Кравцова, сейчас появилась возможность работать на дому, это совсем не сложно и увлекательно и к тому же прибыльно! Зарегистрируйтесь http://artslivrylevel.com/sgceu.html?stavbib [кнопка находиться внизу сайта] это одна минутка времени и бесплатно, далее можно приступать к работе и зарабатывать мин. 197 - 553 долл. в день! Поверте мне, стоит один раз попробовать, чтоб понять, что эта работа уже стала для многих постоянной! Совсем несложно и к тому-же у нас служба поддержки клиентов работает 24 часа в сутки, Вам всегда помогут
профессионалы! С Уважением и пожеланиями прислушаться к моим словам! Наталья Кравцова P.S Вот честно говорю ,просто попробуйте, я Вам гарантирую, что работа Вам пригодиться эта на долгое время и выручит в трудную минуту.
<Email Edited by Host>

Usually this means that a spammer has compromised the mail account or PC of one of your contacts, and is forging your address as the return address in the headers of his messages. The bounce messages from mail servers that reject the spam come back to you. You should check your own mail accounts to make sure there's been no unauthorized activity. You can create a Mail rule to delete the bounce messages automatically.

Getting "Delivery Notification: Delivery has failed" messages

When I haven't sent the email. I'm guessing someone is spamming my email address but how can I stop them? Or can I?
Getting more and more junk mail at my mac.com. Has my email address been comprimised?
Thanks,
Panama

Could this be the person spamming my email? Should I contact aol?
Possibly. But equally likely - if not more likely - is that someone you know with a PC has a virus which is using entries from their address as return addresses for spam.
Won't hurt to try contacting aol. Good luck with that.
charlie

Sending email error "Delivery Notification: Delivery has failed" Why all of a sudden???

I have been communicating just fine with a collegue of mine for a few weeks. no issues. Within the last week when I attempt to send him an email I recive the following error message:
Your message cannot be delivered to the following recipients:
Recipient address: {edited for privacy}
Reason: SMTP transmission failure has occurred
Diagnostic code: smtp;554 Message not allowed - [320]
Remote system: dns;e.mx.mail.yahoo.com (TCP|206.46.173.17|45952|67.195.168.230|25) (mta1034.mail.ac4.yahoo.com ESMTP YSmtp service ready)
He again sent me an email last night and I received his but when I replied this morning I got the above error message again.
Can anyone help as to why this would happen all of a sudden like this? I am not receiving any other errors at all for any of my other email communications.
Thank you
Solved!
Go to Solution.

I Google'd the error message and found this interesting thread:
http://forums.mozillazine.org/viewtopic.php?f=39&t=1452845
The error mentioned is caused by the sending computer clock being off.. I see you are getting the error from a Yahoo server, which matches the discussion in the thread. The thread is in relation to using thunderbird as the email client, but I suspect that does not matter. So maybe check the date/time set in your computer and see if it is off?
Other than that, I have no idea...sorry.
Justin
Verizon FiOS TV, Internet, and phone
QIP6416-P1, IMG 1.7.1, Build 09.97
Keller, TX 76248

How to stop failed delivery notifications generated by auto responder

Hi,
I set up an auto responder on my iCloud account and its generating hundreds of failed delivery notifications. How can I stop these? All the discussions I've found on this so far are relating to spammed accounts.
Problem is I have limited data whilst I am away and all these emails are going to use up my quota!
If you can help, I'd be very grateful..
thanks
This report relates to a message you sent with the following header fields:
Message-id: <[email protected]>
Date: Fri, 28 Dec 2012 05:09:57 +0000
From: Mita De <[email protected]>
To: [email protected]
Subject: Re: Delivery Notification: Delivery has failed
Your message cannot be delivered to the following recipients:
Recipient address: [email protected]
Original address: [email protected]
Reason: Over quota
Original-envelope-id: [email protected]
Reporting-MTA: dns;nk11p04mm-amail04501a.mac.com (ims-ms-daemon)
Arrival-date: Fri, 28 Dec 2012 05:10:18 +0000 (GMT)
Original-recipient: rfc822;[email protected]
Final-recipient: rfc822;[email protected]
Action: failed
Status: 4.2.2 (Over quota)
From: Mita De <[email protected]>
Subject: Re: Delivery Notification: Delivery has failed
Date: 28 December 2012 05:09:57 GMT
To: [email protected]
I am currently away in Asia until 19th Jan but will be checking emails as often as possible.
Unless your email is related to Coop, then please contact XXX until 21st Jan when I will be back in the office.
Merry Christmas and Happy New Year!

Narasimha.Murthy.d wrote:
I am using JSF version 1.3There exist no "JSF 1.3". When talking about "JSF" without mentioning the implementation name, we assume it as JSF specification. The JSF specification is only been available as 1.0, 1.1, 1.2 and 2.0. As said before, we´re more interested in the JSF implementation name. Is it Apache MyFaces? Is it Sun RI or Sun Mojarra? And then please tell the version from that.

Delivery notification

Hi,
in the "imsimta qm top" output:
Count Subject
====== =======
9 Delivery Status Notification (Failure)
7 Delivery Notification: Delivery has failed
What is the difference between the two subjects ?
Regards

You're looking at the subject line of messages. I suggest that you look at the actual message itself.
I suspect that the reason delivery failed is different. . .

Turning off "Delivery Notification" messages

Is it possible to totally suppress messages regarding delivery status from Postmaster? I run a pair of JESMS 6.2 servers which are SMTP relays primarily and the accounts used to send mail are not "people" but services. I'd like the "Delivery Notification: Message has been delayed/failed/etc" to not be generated. I think there's a setting in imta.cnf for this but am wary of the syntax. Can anyone advise what the line should look like?
"defaults notices 1 2 4 7 logging copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost blah.com blah.com"
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
SunOS 5.10 Generic_118833-33 sun4v sparc SUNW,Sun-Fire-T1000

MikeTimbers wrote:
Is it possible to totally suppress messages regarding delivery status from Postmaster?What you propose in contrary to the general nature of email delivery (we strive to not silently 'lose' email which is what this translates too) so there isn't a simple one command to achieve it.
You could prevent notification/disposition emails by using the notificationchannel/dispositionchannel keyword:
http://msg.wikidoc.info/index.php/Dispositionchannel%2C_notificationchannel_Channel_Options
This allows you to change the source channel of these emails. Then by adding a 'discard;' sieve sourcefilter to this new process channel, the emails should be dropped.
"defaults notices 1 2 4 7 logging copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost blah.com blah.com"The copywarnpost and copysendpost are the keywords used to control the behaviour of sending a copy of the bounce/notification message to the postmaster. It doesn't control whether the original bounce/notification message is created. If you don't care about these postmaster copies you can disable them by replacing copysendpost with nosendpost and copywarnpost with nowarnpost.
http://msg.wikidoc.info/index.php/Sendpost%2C_nosendpost%2C_copysendpost%2C_errsendpost_Channel_Options
http://msg.wikidoc.info/index.php/Warnpost%2C_nowarnpost%2C_copywarnpost%2C_errwarnpost_Channel_Options
Regards,
Shane.

Delivery Notification & Failed Message Routing At the same time

Hi All,
Here's our scenario.
BizTalk Orchestration --> One Way Send Port --> SAP
Now, we've enabled 'Delivery Notification' on the Logical Send Port, so if the message fails due to some connectivity issue, it's caught in Orchestration and persisted in another custom database from where it'll be automatically retried. Problem is although
the Orchestration instance is terminated after catching the exception, Send Port instance remains suspended, we don't want that, to solve this we 'Enabled Failed Message routing' on the Send Port and had another Send Port to subscribe to those failed messages
and terminate them.
But after that, failures are not really handled as expected, sometimes the message is not routed back to orchestration (delivery failure notification), sometimes the Failed Message routing port is not getting the message, it's intermittent and unexpected.
Would you guys be able to help us here with.
1. Do you see us doing something wrong?
2. Any other solution to this problem rather than using 'Failed Message routing', may be programmatically terminating the Send Port instance? any examples of that?
Thanks alot
Syed

Hi Sayed,
In my view the issue is with your design of using Delivery Notification and Failed message routing together.
Case 1 : The thing is that when you enable failed message routing on the send port it will not suspend the message and the message will be delivered successfully and since message will be delivered successfully your Delivery Notification exception will not
get invoked.
Case 2 : Since the delivery notification works on the ACK NACK concept, sometimes it could happen that before failed message routing send port subscribes the message the NACK message may have been send to the Orchestration hence the message is routed back
to the Orchestration.
Hence you are getting the unexpected behavior. You could always create powershell or MSbuild scripts to remove the send port suspensions. Below links gives you the code to remove suspended and terminated instances :
http://code.msdn.microsoft.com/windowsdesktop/Script-to-delete-biztalk-1cd312ac
http://stackoverflow.com/questions/11795105/get-all-suspended-instances-for-specific-application-in-biztalk
Please indicate "Mark as Answer" or "Mark as Helpful" if this post has answered the question
Regards,
Rahul Madaan
biztalkvillage.blogspot.com

Delivery has failed message to iCloud account

I regularly email a friend with an iCloud account and receive back a "Delivery has failed to these recipients or groups" message. She is actually getting the emails, but iCloud/MobileMe is trying to forward the emails to a nonexistant account and that causes it to bounce back to me (and presumably everyone else who sends her email). This is a user who has had Mac mail since the beginning of time, first a "DotMac" account, then a "MobileMe" account and now "iCloud". Evidentally this was caused by the transition to iCloud from her former account. Being nontechnical she tried to fix mail problems by creating a new iCloud account, which of course did not fix anything and created this problem where her real email address attempts to forward mail to a nonexistant email address, both theoretically sourced on iCloud. The Genius Bar guy told her it would automatically fix itself in June, which is both ridiculous and difficult to believe that it will self-repair.
Yes she's called and talked to Apple about it. It seems to me that there is a reference on the mail server that is causing emails to her real account to be forwarded to the not-real account. This reference can't be deleted? My friend has given up on getting it fixed. Any chance someone at Apple is willing to do something about it?

No on both replies.... I confirmed the same behavior with a different user that was able to send to all 1100 users before also...so it doesn't seem to be user specific.
I did try it again w the original user- this time the send log showed 0 unresolved recipients- and seemed to look normal- yet the sender received the same undelivered message and the emails were not sent\received.
159Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2195,172.16.240.11:11277,172.16.240.11:2525,*,,Transfering 1073 resolved and 0 unresolved recipient(s)
2014-01-07T20:51:33.159Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2196,172.16.240.11:11277,172.16.240.11:2525,>,BDAT 6868789,
2014-01-07T20:51:33.159Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2197,172.16.240.11:11277,172.16.240.11:2525,*,,Sending blob ADRC-2.1.0.0
2014-01-07T20:51:37.441Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2198,172.16.240.11:11277,172.16.240.11:2525,<,"250 2.6.0 CHUNK received OK, 6868789 octets",
2014-01-07T20:51:37.519Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2199,172.16.240.11:11277,172.16.240.11:2525,*,,"Transfering 2 mailitemlevel and 4292 recipient level properties for recipient(s) [email protected], [email protected],...etc..rest
of recipients.....
014-01-07T20:51:37.519Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2200,172.16.240.11:11277,172.16.240.11:2525,>,BDAT 90147,
2014-01-07T20:51:37.519Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2201,172.16.240.11:11277,172.16.240.11:2525,*,,Sending blob EPROP-1.2.0.0
2014-01-07T20:51:37.597Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2202,172.16.240.11:11277,172.16.240.11:2525,<,"250 2.6.0 CHUNK received OK, 90147 octets",
2014-01-07T20:51:37.597Z,Mailbox Proxy Send Connector,08D0CEFC897B36E7,2203,172.16.240.11:11277,172.16.240.11:2525,>,BDAT 72380 LAST,

IMCEAMAILTO issue causing "Delivery has failed ...".

What started as a single user experiencing an issue sending emails to some addresses has started to become multiple users.
In Outlook 2007, when a user does a reply to some emails the E-mail Type: changes from the normal SMTP to MAILTO and then when the user sends the email it is rejected because either Outlook or our Exchange server is adding @domain.local to the end of
the
recipient’s email address.
This also happens with emails where the senders address is shown as a clickable option [mailto:[email protected]].
Email address has been changed to
[email protected] for confidentiality reasons.
Delivery has failed to these recipients or distribution lists:
'[email protected]'
A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: mailserver.ourdomain.local
[email protected]
#550 5.4.4 ROUTING.NoNextHop; unable to route ##
Original message headers:
Received: from mailserver.ourdomain.local ([fe80::d597:2413:93ab:cf17]) by mailserver.ourdomain.local ([fe80::d597:2413:93ab:cf17%13])
with mapi; Thu, 14 Oct 2010 13:58:28 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Internal User <[email protected]>
To: "'[email protected]'"
<[email protected]>
Date: Thu, 14 Oct 2010 13:58:27 +0100
Subject: email
Thread-Topic: email
Thread-Index: Actrn34QI8tEGRBCR/qQGIH5MxGgyA==
Message-ID: <[email protected].local>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <[email protected].local>
MIME-Version: 1.0

Okay here's the skinny. I don't see an immediate patch coming out for this. Also I'm concerned that Microsoft sees this currently as a single call, not that a bunch of folks are impacted.
While there is a bug they are tracking on this Offug49462, short term there will only be info detailed in the security update that there's a side effect of this update. No eta of when exactly that wording will be posted in the bulletin, but that certainly
will be sooner than a patch fixing this.
The trigger appears to be when you click on mailto links.
You have two choices as I see it:
1. uninstall the patch, and wait until I post back that there is an ultimate fix. I don't see this coming out in a week or two honestly, so be aware that per my read on the situtation, this won't be resolved quickly with another patch.
2. leave the security patch on, and as a workaround to ensure that you don't accidentally click on a mailto link and thus flip your email addresses and get NDRs to do the following:
In Outlook:
Click Tools > Options
Click the Mail Format tab
Click Editor Options
Click Proofing
Click AutoCorrect Options
Click the AutoFormat Tab
Uncheck "Internet and network paths with hyperlinks"
Click OK, OK and OK
Neither one is good, but it's all I have right now until something is coded up long term.
So here's where you can do me a favor. Call 1-800-Microsoft and explain to them you have an issue with a security update 2344993, say that you too are impacted by Offup49462 bug and tell them how many in your firm/office/school have been impacted.
Like I said right now they only have one call on this issue, and I'd like to ensure they see more numbers of impacted people.
Thanks.
Susan-at-msmvps.com

Redirect Rule - Delivery has failed to these recipients or groups

First of all my apology if this is wrong Forum. Please guide me to correct forum.
Scenario is that we need to send emails to AD Group using C# code or script.
First we tried C# code and it don't work, as per our finds, log in / password is required. Also, it was taking to much time because of protocol and we need to send 10 to 15 emails at same time.
We tried script and this time we created a mail box say, temp. We send emails to temp and added rules on bases of subjects of emails.
Now, issue is if we setup forward rule, temp is able to forward email to AD group. If we setup redirect rule, email is not send to AD Group and temp received failure delivery.
Delivery has failed to these recipients or groups:
AD Group Name
Your message can't be delivered because delivery to this address is restricted.
For more information about this issue see DSN code 5.7.1 in Exchange Online.
We even made temp owner of AD group.
Any help?
http://farhanfaiz.wordpress.com

Hi malikfarhan
I understand that delivery has failed to those recipients or groups when you setup the redirect rule.
Based on my research, you could have a try as follows
Open the EAC, navigate to Recipients > Groups.
In the list of groups, click the distribution group that you want to view or change, and then click Edit
icon .You can go to properties for DG, -> Select Delivery management ->Senders inside and
outside of my organization , Click on Save.
You can further limit who can send messages to the group by allowing only specific senders to send messages to this group. Click
Add + and then select one or more recipients.
For more details, you could click this link: https://technet.microsoft.com/en-us/library/bb124513.aspx?f=255&MSPPError=-2147217396
I am glad to be of help to you .
Regards,
David

Delivery has failed to these recipients or groups

Delivery has failed to these recipients or groups:
[email protected] ([email protected]) The server has tried to deliver this message, without
success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.
Diagnostic information for administrators:
Generating server: HYPER-SUNMAIL.xyz.org Receiving server: abc-bd.com (213.199.154.87)
[email protected] 7/29/2014 9:41:44 AM - Remote Server at abc-bd.com (213.199.154.87) returned '550 4.4.7 QUEUE.Expired; message expired' 7/29/2014
9:36:07 AM - Remote Server at abc-bd.com (213.199.154.87) returned '451 4.4.0 Error encountered while communicating with primary target IP address: "421 4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed. Either
there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 213.199.154.87:25'
Original message headers:
Received: from HYPER-SUNMAIL.xyz.org (192.168.0.21) by HYPER-SUNMAIL.xyz.org
(192.168.0.21) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sun, 27 Jul
2014 15:41:37 +0600
Received: from HYPER-SUNMAIL.xyz.org ([::1]) by HYPER-SUNMAIL.xyz.org
([::1]) with mapi id 15.00.0847.030; Sun, 27 Jul 2014 15:41:37 +0600
From: Administrator <[email protected]>
To: "[email protected]" <[email protected]>
Subject: check the mail
Thread-Topic: check the mail
Thread-Index: AQHPqX711QV7LAHG7kGziKuia+iJGw==
Date: Sun, 27 Jul 2014 09:41:37 +0000
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.0.5]
x-brightmail-tracker: H4sIAAAAAAAAC+NgFnrCqsTGxXJgBYOobtDJK8EGN9c8OMZssaF9LZMDYwBDFGtmXlJ+RQJrxvPu92wFu1Uqth58wdrAuF+5i5GLQ0hgE6PEy9fTmSGcPkaJS/2fmLoYOTmYBUwlrnxtZIGwFSUu3GsAsjk42AR0JFb/cwIJiwg4S6y6fJ0ZJCwsIC7xf3ImRFhGYueBtWwQtp7EmtfNjCA2i4CqxNNzP5hBbF4BV4npp++wgtiMAmIS30+tgdoqLnHryXwwW0JAQGLJnvPMELaSRO/td1Bxf4lPq16yQMwRlDg58wkLRNxMYu+DJUwg50gI6EosuMMFEQ6UWHulmxkibCpx9X0wRNhWYs+MiVDVzhLzbtTDhB/17GaEsLUltr/axwph60hsurYKapG8xP9796Fse4kt3VNYIcbIS+y6pw8TXrd9ClSJr8SVCZOhbi+UeL98BdMERpVZSIE8CymQZyEFwywkLy5gZFnFKOYRGeAapBsc6ufr6OmjV5yWUq6XX5S+iRGYAtZIs3PtYGz75HSIUZKDSUmU1zztcLAQX1J+SmVGYnFGfFFpTmrxIUYJDh4lEV6lLKAcb3FBYm5xZjpMSoaDQ0mC96EZUEqwKDU9tSItM6cktQgifYpRUkqcV/j3oWAhAZC+jNI8uNwlRlEpYd4jIUCNPAWpRbmZJRDxW4zCHA+ZhFjy8vNSpYBOZAACDcZXjOIcjErCvCbZIPWZeSVwJ7wCuo4J6DpGoDqg60oSEVJSDYwuBturL112XRTwsyOp5m3Rj2vlzP37dk3+cOeaWi/Dsv1uK/pW8C/ek5/C2/dqdmCbdudmO0055YlGnNN8q7/uEEg4lnO523Opbhtr3saKwKhNNqLPVJf+eTr5cvuk3RdeKoSu39UfXZpVqX9s7zvZa7xu/MJ17Cff3uZyWHxJwvrEqmkiKwyUWIozEg21mIuKEwFXjS8rdwMAAA==
Content-Type: multipart/alternative;
boundary="_000_ddb6a985d4d0418b91ad37942ea4dcecHYPERSUNMAILxyzorg_"
MIME-Version: 1.0
Md. Ramin Hossain

Hi,
From your description, I recommend you check the SMTP protocol logging on Send Connectors to find out why this message can't be delivered. SMTP log is very useful on diagnose mail delivery problem.
Here is the default location:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpSend
For more information, here is a thread for your reference:
Configure Protocol Logging
http://technet.microsoft.com/en-us/library/bb124531(v=exchg.150).aspx
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Delivery Notification: Delivery has failed

Similar Messages

Maybe you are looking for