Disregard Certain Delivery failed MEssages

I have messaging server 5.2 (Patch 2)
I have setup a channel filter that forwards (keep;redirect;) all mail to an external email archive server (It bcc's it), and thats working fine.
I am aware that if the email_archive server goes offline, that the emails may be returned to sender with a "Delivery Notification: Delivery has failed" message.
Is their a way to discard those? Keep in mind that I only want to disregard the ones that have failed going to the email_archive server.
Thanks

mrMerclyn wrote:
I have messaging server 5.2 (Patch 2)
I have setup a channel filter that forwards (keep;redirect;) all mail to an external email archive server (It bcc's it), and thats working fine.
I am aware that if the email_archive server goes offline, that the emails may be returned to sender with a "Delivery Notification: Delivery has failed" message.
Is their a way to discard those? With MS6.3 you could use the "capture" sieve keyword instead of redirect.
The "capture" keyword changes the envelope sender to be the postmaster address and therefore any bounces go back to the postmaster rather then the 'original' sender e.g.
capture :message "[email protected]";
Keep in mind that I only want to disregard the ones that have failed going to the email_archive server.I tried a few combinations of filters/mapping rules to achieve this with iMS5.2 but without any success. So at this juncture I suggest you go with either Jay's suggestion if you don't want to upgrade to MS6.3 or the capture sieve option if you do upgrade.
Regards,
Shane.

Similar Messages

Yosemite mac mail drowning in mail delivery failed messages I didn't send!

babs bellNov 14, 2014 7:03 PM
Since upgrading to Yosemite, I am getting hundreds (tens of thousands this week!) emails that read:
From: Mail Delivery System
Subject: Mail delivery failed: returning message to sender
But I didn't send any of the emails! I've spent this entire week deleting them, working on phone with my server who claims to have fixed it (NOT!), and 5 hours on phone support with Apple today. Still happening. There must be a setting that is screwed up in Yosemite, eh? Who can help me? Using Mac Mail on Mac Book Pro. I'm drowning here! GLUG. Thanks!
Edit

Did all of that with Apple and they nor my server thought this was the problem, nor did they get it resolved. I'm wondering if there's a rule in Mail preferences that I accidentally deleted that could be the cause. There were two rules and neither made any sense to me but as soon as I deleted the first one, I realized I probably shouldn't have. And there's been a huge problem since...not sure that's why but I must find the resolution. I did have genieo somehow installed so Apple got it uninstalled and did tons of things to my system to clean this and that. BUT the problem remains. If you use mac mail and Yosemite, can you check the two rules that automatically were in the mail preferences window to tell me what rule I deleted? Thank you so very much!

"Mail Delivery Failed:returning message to sender" recipients not familiar

I am getting a "Mail Delivery Failed" message. The address' that failed are to recipients I am not familiar with and have not tried to email. Has my email been hijacked?

I'm getting the same problem ... only it happens to anyone who sends a message TO me. This only happens on my .mac address --- not other email addresses that I use. It's as if the .mac smtp code is ADDING a bcc to any message sent to me! All the comments to date have been less than encouraging - surely SOMETHING can be done about this! No?

TS5185 imessage delivery fails ands needs to be resent as text to person that no longer has an iphone

I recently upgraded to the 5s. My brother used to have an iphone but switched to another phone. When i try to text him, my phone tries to send an imessage and i get a delivery failed message and have to resend as a text. i have removed his contact info a couple of times and reseyt imessage several times but still keep having this issue. Any ideas?

That's because your brother failed to turn off iMessage before switching to a different phone. He will need to fix that. The only thing that you can do to avoid the problem is turn off iMessage.

When I send a text message it says delivery failed. When I resend it sends the message twice. Why am I having problems?

When I send a text message it says delivery failed. When I resend it sends the message twice. Why am I having trouble?

Oh goodness! We want your text going through the first time, dria56. Does this happen when you're messaging someone in particular or is it every message you send? Is it a plain text or a message with more than 160 characters/graphics/pictures?
JenniferH_VZW
Follow us on Twitter www.twitter.com/vzwsupport

TS3988 I have an icloud account and I view my mail with Mail V5.2. I recieve my email but the senders get messages saying the delivery failed. Can anyone explain this or help me.

I have an icloud account and I view my mail with Mail V5.2. I recieve my email but the senders get messages saying the delivery failed. Can anyone explain this or help me.

Thank you for replying. Yes I deleted the old email address..

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

I keep getting a filter fail message when i try to print

i cannot print, i have a new mac and i need help, can someone help me out?

Hi @pkjbadala ,
I see that you are getting a filter failed message, when you try to print. I will certainly do my best to help you.
Repair the Disk Permissions on the Mac:
Close all applications.
On the Apple menu bar, click Go, click Applications and then click Utilities.
Double-click Disk Utility.
Highlight your hard drive/partition on the left.
Click Verify and then Repair Disk Permissions.
Restart the computer..
Reset the Printing System:
Note: This will remove all printers in the print and Fax/Scan, any printer removed can be re-added later by clicking the plus (+) symbol.
Click the Apple icon and then click System Preferences.
Click Printers & Scanners.
Right-click (or Ctrl +click) in the left white side panel, then click Reset printing system.
Click OK to confirm the reset.
Type the correct Name and Password.
Click OK to reset the printing system.
Then click the + sign to add the driver, highlight the printer. (you might have to click the drop down to select the printer's name) Then click on the Add button.
Try and print a document.
How is the printer connected? (USB/Ethernet/Wireless)
If you need further assistance, just let me know.
Have a great day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

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 fails: "The server response was: 4.7.0 Temporary server error. Please try again later. PRX3"

Trying to setup an Exchange 2013 server, with the DC and Exchange on same machine. WHen I try to deliver for either of the 2 mailboxes I have setup, I get this error.
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX3
It doesn't seem to be a resource issue (I'm running an XL instance on Azure), and all other connectivity works fine (and fast). I just can't receive email there.
Looking in the event logs, I saw one issue related to the Front End HTTP proxy, but I wouldn't assume that's relevant here. (And connectivity via Outlook & OWA seem to be fine, with the exception
of some redirect issues on the latter).
I did end up installing Exchange on a secondary drive for space considerations, so the location is different... not sure if that would factor in either.
Any ideas? I don't even really know where to start debugging this. I'm trying to set this up to work on some event sync/forwarding code.

Ok, I think I solved my problem but figured I would update here for others who may be running into the same issue.
In my \Exchange\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive\*.LOG, I found more detailed information on the issue.
"Message or connection acked with status Retry and response
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 10.10.10.1:2525"
I thought creating an endpoint for 25 would be sufficient, but once I created another endpoint for 2525 then my tests started working.

Redirecting failed messages to other consumers of distributed queue

Hi,
We have a simple cluster with two servers A and B, each hosting one MDB whose task is to consume message from a distributed queue and forward them to an EIS via a JCA resource adapter. Server B acts as a failover server. If the resource adapter is unable to deliver the message, the MDB will throw a runtime exception and the message will therefore be redelivered. In order to achieve high-availability, we have configured the distributed queue to send the redelivered message to an error destination (dead-letter-queue DLQ). The DLQ again has another instance of the MDB as a consumer with a different resource adapter.
Using DLQs is working fine as a high-availability mechanism when the MDB is unable to deliver the message to the EIS, but is this a common or valid approach?
An alternative to using DLQs would be to configure weblogic to send redelivered message to other consumers on the distributed queue. The problem we have is that the failed message always gets redelivered to the same MDB (i.e. the MDB which consumes messages but throws an exception because the resource adapter fails). Is it somehow possible to configure the MDB or even change the MDB code to notify weblogic to send the failed message to another consumer of the distributed queue? Would the MDB be able to disconnect the JMS connection when throwing the exception and if so, would the disconnection cause the application server to deliver the message to another consumer?
Many thanks

Thanks Tom,
Setting the distributed-destination-connection property to EveryMember seems to be exactly what we need to allow other distributed queue member to consume the message which has been put back on the queue after a rollback. In order to ensure that it won't be the same MDB consuming the failed message again, we would have to temporarily suspend the MDB. From what I read, one approach is to sleep the MDB after throwing the runtime exception (but is this possible, i.e. is it not going to interrupt the onMessage before going to sleep?). I also read that there is a new property from WLS 9.0 onwards to automatically stop the MDB for a certain time after an exception has ocurred, how can I configure this? Are we also going to have to set the MDB pool size to 1 in order to ensure that the message gets consumed by an MDB on a different server?
We have also tried to use a non-collocated approach instead using a collocated approach with distributed queues but we end up with the same problem that a message does not get redelivered to MDBs on other servers after a runtime exception has been thrown.
Thanks a lot

Resend a failed message

We have an IDOC to File Scenario. We are FTPing the file on the Receiver end.
When the receiver System is Down after certain number of attempts my job fails with the red flag.
Once the file System is up, how to resend the Faile Message(As it is not possible for us to trigger the IDOC again!!!).
Thanks.

Jenni,
You can resend the messages by selecting the message and clicking Resend button in RWB. You can also refer Naveen's blog :/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
-raj.

SMS delivery failed all of a sudden

I have money in my skype account but my smses from my pc to mobile are not being delivered,these last 2 days and its frustrating me, help!!!!

Exactly the same here. All my sms messages from Skype to cell phone are getting DELIVERY FAILED! I have NO idea why????

I am receiving an installation failed message

I just purchased adobe creative cloud, and when I try to install certain apps they came up with an "installation failed" message.
When I click the learn more, it prompts me to another window. If I click, windows photo viewer can not open the file type. I'm sure there is a simple solution, please help.

Nobody can tell you anything without proper system information and installation logs. And well, if the files even attempt to open in Photo Viewer, you have other problems than your CC install to boot...
Working with your Operating System’s Tools | Mylenium's Error Code Database
Troubleshoot with install logs | CS5, CS5.5, CS6, CC
Mylenium

Delivery expired (message too old)

Hello,
I am getting a few errors each day related to the following type of message. I have done some web searches, and a few pointed to Windows 2008 DNS as a possible problem. However, our Ironports point to our external DNS which is BIND.   Here is the relevant data from message tracking.
SMTP delivery connection (DCID 163673330) opened from IronPort interface 10.193.13.181 to IP address 10.192.3.45 on port 25.
19 Jul 2011 17:20:01 (GMT -04:00)
(DCID 163673329) Message 492404228 to [email protected] bounced by destination server. Reason: 5.4.7 - Delivery expired (message too old) ('000', ['[Errno 61] Connection refused']) [(\'X-SBRS\', \'None\'), (\'X-HAT\', \'Group: RELAYLIST, Policy: $RELAYED\'), (\'X-VITAFiles\', \'Attached: image001.jpg, image002.jpg\'), (\'subject\', \'RE: orientation\'), (\'from\', \'"Evans, PATRICIA EVANS (DBHDS)" <[email protected]>\'), (\'to\', \'"Breeding, Myra" <[email protected]>\')]
Anyone else see this? Any ideas on how to fix it?
Thanks ahead of time!
Elias

Greetings Elias,
With the data you provided its a bit difficult to say if this is related to a DNS issue or not. A couple of things you may want to do here to further diagnose this.
If delivery attempts fail, this means the destination's mail server did not accept a given message after 72 hours or 100 iterations of consecutive tries (example).   This issue can be seen either incoming (delivery to your internal groupware server) or outgoing (towards another domain via the Internet).   While this does not necessarily signal a problem with your local IronPort ESA, you can work around this by extending the retransmission period or number of attempts, and therefore increasing the chances for successful delivery.   These values are controlled by the IronPort's Bounce Profiles.
Note: If you wish to make the retransmission timeout more lax, increasing the value may increase your chance for successful delivery.   The overall duration (i.e., "maximum number of seconds") defines times in terms of seconds. The default value is 259,200 seconds, or three days. We'd recommend increasing this threshold to 345,600 seconds (four days) or 432,000 (five days) if necessary.
To edit the "Default" bounce profile via the GUI:
1) Go to Network > Bounce Profiles > select your Profile Name
2) set "Maximum Number of Retries" to change the number of times we attempt delivery
3) set "Maximum Time in Queue" to specify the total length of time to store the message for retransmission
4) set "Maximum Time to Wait per Message" to give the maximum interval between retries
Alternatively, we can use the CLI 'bounceconfig' command to set the same values.
You may also want to enable the domain debug logs to this host. This way you can see the full smtp conversation between your appliance and the remote host. This may provide some more detail on the previous failures before it gets to this state.
Additionally you may want to also consult the mail logs for the previous failures.
Below is some more information on setting up the domain debug logs.
The domain debug log is a system log designed to record all SMTP traffic between a specific domain and an   Email Security Appliance (ESA) for a finite number of sessions. This log type can assist in troubleshooting issues that relate to a specific recipient domain or host. Each session is recorded until the number of session defined has been reached, at which time the log will stop collecting data. You can stop domain debug before all sessions have been recorded by deleting or editing the log subscription.
Configuration
Logs can be configured and created through the IronPort CLI   using the logconfig command or via the GUI.
To configure logs via the GUI, see the Advanced User Guide: Log Subscriptions .
Below is an example of creating a Domain Debug Log subscription using the CLI:.
example.run> logconfig
Currently configured logs:
1. "antispam" Type: "Anti-Spam Logs" Retrieval: FTP Poll
2. "antivirus" Type: "Anti-Virus Logs" Retrieval: FTP Poll
3. "asarchive" Type: "Anti-Spam Archive" Retrieval: FTP Poll
4. "avarchive" Type: "Anti-Virus Archive" Retrieval: FTP Poll
5. "bounces" Type: "Bounce Logs" Retrieval: FTP Poll
6. "cli_logs" Type: "CLI Audit Logs" Retrieval: FTP Poll
7. "error_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
8. "euq_logs" Type: "IronPort Spam Quarantine Logs" Retrieval: FTP Poll
9. "euqgui_logs" Type: "IronPort Spam Quarantine GUI Logs" Retrieval: FTP Poll
10. "ftpd_logs" Type: "FTP Server Logs" Retrieval: FTP Poll
11. "gui_logs" Type: "HTTP Logs" Retrieval: FTP Poll
12. "mail_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
13. "reportd_logs" Type: "Reporting Logs" Retrieval: FTP Poll
14. "reportqueryd_logs" Type: "Reporting Query Logs" Retrieval: FTP Poll
15. "scanning" Type: "Scanning Logs" Retrieval: FTP Poll
16. "sntpd_logs" Type: "NTP logs" Retrieval: FTP Poll
17. "status" Type: "Status Logs" Retrieval: FTP Poll
18. "system_logs" Type: "System Logs" Retrieval: FTP Poll
19. "updater_logs" Type: "Updater Logs" Retrieval: FTP Poll
Choose the operation you want to perform:
- NEW - Create a new log.
- EDIT - Modify a log subscription.
- DELETE - Remove a log subscription.
- SETUP - General settings.
- LOGHEADERS - Configure headers to log.
- HOSTKEYCONFIG - Configure SSH host keys.
[]> new
Choose the log file type for this subscription:
1. IronPort Text Mail Logs
2. qmail Format Mail Logs
3. Delivery Logs
4. Bounce Logs
5. Status Logs
6. Domain Debug Logs
7. Injection Debug Logs
8. System Logs
9. CLI Audit Logs
10. FTP Server Logs
11. HTTP Logs
12. NTP logs
13. LDAP Debug Logs
14. Anti-Virus Logs
15. Anti-Virus Archive
16. Scanning Logs
17. IronPort Spam Quarantine Logs
18. IronPort Spam Quarantine GUI Logs
19. Reporting Logs
20. Reporting Query Logs
21. Updater Logs
[1]> 6
Please enter the name for the log:
[]> debug_example
Enter the name of the domain for which you want to record debug information.
[]> example.com
Please enter the number of SMTP sessions you want to record for this domain.
[1]> 8
Choose the method to retrieve the logs.
1. FTP Poll
2. FTP Push
3. SCP Push
4. Syslog Push
[1]>
Filename to use for log files:
[example.com.text]>
Please enter the maximum file size:
[10485760]>
Please enter the maximum number of files:
[10]>
Currently configured logs:
1. "antispam" Type: "Anti-Spam Logs" Retrieval: FTP Poll
2. "antivirus" Type: "Anti-Virus Logs" Retrieval: FTP Poll
3. "asarchive" Type: "Anti-Spam Archive" Retrieval: FTP Poll
4. "avarchive" Type: "Anti-Virus Archive" Retrieval: FTP Poll
5. "bounces" Type: "Bounce Logs" Retrieval: FTP Poll
6. "cli_logs" Type: "CLI Audit Logs" Retrieval: FTP Poll
7. "debug_example" Type: "Domain Debug Logs" Retrieval: FTP Poll
8. "error_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
9. "euq_logs" Type: "IronPort Spam Quarantine Logs" Retrieval: FTP Poll
10. "euqgui_logs" Type: "IronPort Spam Quarantine GUI Logs" Retrieval: FTP Poll
11. "ftpd_logs" Type: "FTP Server Logs" Retrieval: FTP Poll
12. "gui_logs" Type: "HTTP Logs" Retrieval: FTP Poll
13. "mail_logs" Type: "IronPort Text Mail Logs" Retrieval: FTP Poll
14. "reportd_logs" Type: "Reporting Logs" Retrieval: FTP Poll
15. "reportqueryd_logs" Type: "Reporting Query Logs" Retrieval: FTP Poll
16. "scanning" Type: "Scanning Logs" Retrieval: FTP Poll
17. "sntpd_logs" Type: "NTP logs" Retrieval: FTP Poll
18. "status" Type: "Status Logs" Retrieval: FTP Poll
19. "system_logs" Type: "System Logs" Retrieval: FTP Poll
20. "updater_logs" Type: "Updater Logs" Retrieval: FTP Poll
Choose the operation you want to perform:
- NEW - Create a new log.
- EDIT - Modify a log subscription.
- DELETE - Remove a log subscription.
- SETUP - General settings.
- LOGHEADERS - Configure headers to log.
- HOSTKEYCONFIG - Configure SSH host keys.
[]>
example.run> commit
Domain Debug Log
Below is an example of a Domain Debug Log looks like when the IronPort appliance delivers a message to the recipient domain: "example.com".
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '220 ESmtp mail.example.com ESMTP service ready'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'EHLO ironport.com'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-mail.example.com'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-8BITMIME'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250-SIZE 31981568'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 PIPELINING'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'MAIL FROM:<[email protected]>'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 sender <[email protected]> ok'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'RCPT TO:<[email protected]>'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 recipient <[email protected]> ok'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'DATA'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '354 go ahead'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'Received: from unknown (HELO)(10.250.7.164)rn by ironport.com with SMTP; 22 Mar 2005 16:52:08 -0800rn'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: 'Message-ID: <[email protected]>rnFrom: "User" <[email protected]>rnTo:<[email protected]>rn Subject:TestrnDate:Tue,22Mar200516:57:28-0800rnMIME-Version:1.0rn
Content-Type:multipart/alternative;rntboundary="----=_NextPart_000_000A_01C52F00.3AA3B580"rnX-Priority: 3rnX-MSMail-Priority: Normalrn X-Mailer: Microsoft Outlook Express 6.00.2900.2180rnX-MimeOLE: Produced ByMicrosoft MimeOLEV6.00.2900.2180rnrnThis is a multi-part messageinMIMEformat.rnrn------=_NextPart_000_000A_01C52F00.3AA3B580rnContent-Type:text/plain;rntcharset= "iso-8859-1"rnContent-Transfer-Encoding: quoted-printablernrnThis isthebodyofthemail.rnThisisadisclaimer.rnrn------=_NextPart_000_000A_01C52F00.3AA3B580rnContent-Type:text/html;rntcharset=   "iso-8859-1"rnContent-Transfer-Encoding:quoted-printablernrnrnrnrnrnrnrnrnThis is the body of thernmail.
This is a disclaimer.rn rnrn------=_NextPart_000_000A_01C52F00.3AA3B580--rn'
Tue Mar 22 16:52:07 2005 Info: 411 Sent: '.rn'
Tue Mar 22 16:52:07 2005 Info: 411 Rcvd: '250 ok dirdel'
Tue Mar 22 16:52:12 2005 Info: 411 Sent: 'QUIT'
Tue Mar 22 16:52:12 2005 Info: 411 Rcvd: '221 mail.example.com'
Christopher C Smith
CSE
Cisco IronPort Customer Support

Disregard Certain Delivery failed MEssages

Similar Messages

Maybe you are looking for