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. . .

Similar Messages

Inbound delivery notification in scm

hi all,
i have created in bound delivery in ecc 6.0 , maintain integration model for the same for data transfer between sap erp and scm. how to create inbound delivery notification based on the inbound delivery received from sap erp.
kindly guide me out for creation of inbound delivery.
Regards,
velu

Hi,
You need to map the delivery types and item categories first.
Regards,
MdZ

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.

Blackberry's automatic delivery notification encourages spam mail.

To anyone who is listening, please either disable the Blackberry's automatic delivery notification, or give us Blackberry users the option to change it to manual delivery notification requiring our approval before delivery notification is sent.
Spammers harvest the email addresses and the automatic delivery notification tells them that they sent spam to a good/valid address.
My wife and I both noticed that since we started using the Blackberry, the number of spam mail has progressively increased. Today, I discovered why. I noticed in the sent mail log, that the Blackberry is sending out delivery notification automatically each time an email is opened/read. A lot of times, I can't figure out if something is junk until I open up the email. That's when the Blackberry sends delivery notification. Sure, the spammers request delivery notification, that's how they can confirm whether their junk mail reached the intended party. And thus, they harvested a valid email address that they use for the next spam mail. The Blackberry makes it too easy for the spammer to validate a good delivery email address, and for mail that's being forwarded from a "disposable address" to my real address, now the spammers get to harvest my real email address when the Blackberry includes it in their delivery notification.
So please, please disable the automatic delivery notification. Let me decide who I will send delivery notification.
Thank you in advance!

ladyv114 wrote:
How do you disable the automatic delivery notification?
On BIS, I don't think there is a way; on BES your BES Admin can do this.
Please also read my post above.
If you've found a solution through a post; please mark it as a solution.
If someone's was particularly helpful, give them kudo's!.
Get busy living, or get busy dying.
http://blog.port3101.org/hdawg/

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.

Delivery Notification as per the Due date to supplier

Hi All,
My client requirment is before delivery of PO quantity vendor get reminder throuh mail delivery notification on due date of PO quantity (before 4 days reminder) so kindly let me know how to configur in SAP .
Regards
Santosh P

Hi Narendra,
Thxs for quik response,
I created Purchasing value key with Negative indicator like first reminder is -8.second is -4 and third is -2 and assigned the respetive material master and w r t material PO created. When i am doing ME9F exceuting its showing error No suitable purchasing documents found,while i am exceucting i select PO No,Purchase Org,application EF and message type MAHN but its shoing error ..kindly let me know how i can proceade.
Please note, My client requirment is once PO delivery date falls with the reminder period its should remind vendor through mail,
Regards
Santosh

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.

Error while activating Inbound Delivery Notification

Hi,
I have created and Inbound delivery in ERP, the material is batch managed and packed with HU. Once saved on ERP system, I find the Inbound Delivery Notification in SCM EWM system with HU, material and batch number appearing. Up to this point all good.
However, when I am trying to hit the button 'Activate' so that I can create Inbound delivery, system comes up with error message - 'Please specify an external number range' (message NR753) I have no idea where it's coming from.
For further information - I am using standard Doc Type INB with Doc Cat. PDI and it's assigned with an Internal Number Range.
What's missing?
I help will be rewarded.
Thanks,
Amit

Thanks Virendra,
You have pointed to the right direction. Basically, without checking for the posts here, which are really helpful, I went to system one more time only to find that I have made a configuration error. I am just sharing if anyone else in future faces same situation, he/she can be benefited out of it.
In EWM system - I had created number range with transaction SNRO for object /SCWM/SSCC putting 01 (from 1 - 1999999) as internal and 02 (from 2000000 - 2999999) as external number range.
In EWM system - I had assigned the number range in following place:
Extended Warehouse Management > Cross Process Settings > Handling Units > External Identification > SSCC Generation Acc. to EAN128 > Maintain SSCC Generation for Each Warehouse Number
In ERP system - I had created number range with SNRO for object LE_SSCC with same attributes as above. i.e. 01 as internal and 02 as external.
Now when I packed the inbound delivery in ERP system, I used packaging material for which the number range is internal (i.e. 01) and it created HU with SSCC number. Up to this all were good. But when the same HU transferred from ERP to EWM system, SAP treated the HU number coming from ERP system as external HU number (which is logical) but it was looking at number range 02 (since it was marked as external) but was failing to match as the allowed numbers doesn't fit along with the number transferred from ERP system. Hence it was giving error.
As a solution I declared 01 as external and 02 as internal and also inverted the number range assignment for SSCC generation in EWM system.
It created Inbound Delivery successfully.
Thanks all of you for helping on it.
Cheers,
Amit

Create Warehouse Request for Inbound Delivery Notification

Dear Experts,
I have created Inbound Delivery in ECC and Inbound Delivery Notification has been created in SAP EWM.
Kindly suggest me how and where can I create Warehouse Request for Inbound Delivery Notification.
I donot see any transaction or link to create Warehouse Request for the Inbound Delivery.
I am new to EWM. Please suggest.
Regards,
Shetty

Hi,
After the Inbound delivery has been distributed to the EWM environment the Inbound delivery notification (IDN) is created. So far so good but after the IDN has been created you will have to activate it manually if it didn't automatically. In order to activate it please go to transaction /n/SCWM/IDN - Maintain Inbound Delivery Notification and execute it for all of the IDNs that are not activated. Then you activate it and it creates the ID.
After the ID has been created, if the system (Post Processing Framework) didn't create the tasks relevant for receipt than you have to go into the ID and choose Inbound Delivery - Follow-On Functions - Warehouse Tasks and create and save the warehouse tasks relevant for receipt.
All the best,
Claudiu Maxim

Delivery notification for two way ports

HI
I am using a two way BasicHttp Adapter for sending requests and receiving response from a Web service. I want to handle Delivery Notification errors but since it works only for one way ports how can i implement the same for my scenario Please advice.
Regards
Suresh

Hi Suresh,
Snippet below from the
link should answer your specific question.
Handling Delivery Failure Exception (using a request-response port)
There is a great post
by Naveen Karamchetti about this; this is the key steps…
In order to catch an exception within your scope block in BizTalk while using a request-response port, you might have to do the following:
Set the retry-count to 0 on your physical request-response port which you use to bind.
Enable the flag Delivery Notification to ‘Transmitted’ on your logical request-response port within the orchestration.
Catch the “Microsoft.XLANGs.BaseTypes.DeliveryFailureException” exception and handle it as you’re please.
The Delivery Notification flag on the Send Port indicates that the orchestration must be NOTIFIED back, in case the message has not been received by the destination. Delivery Notification works only when
the Retry Count set to 0. When a message cannot be delivered, a Delivery Failure Exception is raised and the exception needs to be handled by the Orchestration.
Rachit
Please mark as answer or vote as helpful if my reply does

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.

Sending email and get delivery notification

Hi,
I want to send an email from HTMLDB and I see that the HTMLB mail package also use the utl_smtp package to implement this function. So I write a store procedure to send email with the help of utl_smtp and it works. Additional to every send I want a delivery confirmation to the sender adress, because it is very important to see, which mails weren't delivered. I've searched for an parameter to set and found these syntaxes in the "PL/SQL Packages and Types Reference".
UTL_SMTP.MAIL (
c IN OUT NOCOPY connection,
sender IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL);
UTL_SMTP.RCPT (
c IN OUT NOCOPY connection,
recipient IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL)
RETURN reply;
UTL_SMTP.RCPT (
c IN OUT NOCOPY connection,
recipient IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL);
The following statement stay in the Reference for the description of "parameters":
parameters The additional parameters to RCPT command as defined in Section 6 of [RFC1869]. It should follow the format of "XXX=XXX (XXX=XXX ....)".
I read a little bit about SMTP in RFC1869 and I write change the statements:
utl_smtp.mail(mail_conn,sender);
utl_smtp.rcpt(mail_conn,recipient);
to:
utl_smtp.mail(mail_conn,sender, 'NOTIFY="SUCCESS,FAILURE"');
utl_smtp.rcpt(mail_conn,recipient, 'NOTIFY="SUCCESS,FAILURE"');
I get now the following syntax error: "ORA-29279: SMTP permanent error: 501 Syntax Error"
I tried also the statement without success:
utl_smtp.mail(mail_conn,sender, 'NOTIFY=SUCCESS,FAILURE');
utl_smtp.rcpt(mail_conn,recipient, 'NOTIFY=SUCCESS,FAILURE');
What can I do to get this delivery confirmation. E.g. in Outlook is possible to set this as option for emails before you send it. Any ideeas?
Thanks!
Serban Vettori

Hi,
I read at first parts of RFC 1869 (stands in your documentation) but it doesn't help me too much because it wasn't a concrete example there. The best adress is the RFC1891 "SMTP Delivery Status Notifications", that contains a lot of examples like:
MAIL FROM:<[email protected]> RET=HDRS ENVID=QQ314159
<<< 250 ok
RCPT TO:<[email protected]> NOTIFY=FAILURE \ORCPT=rfc822;[email protected]
<<< 550 error - no such recipient
RCPT TO:<[email protected]> NOTIFY=SUCCESS,FAILURE \ORCPT=rfc822;[email protected]
<<< 250 recipient ok
DATA<<< 354 send message, end with '.'
(message goes here)
.<<< 250 message received
QUIT<<< 221 bye
Your documentation is realy good but in this case wasn't really helpful. If you implement a function it were nice to document any input parameter. The user have to read several other documents to get ONE parameter! I personally don't like this. Perhaps there are other users which are really exalted to see such cross references.
Here is the right syntax for this problem:
utl_smtp.rcpt(conn, recipient, 'NOTIFY=SUCCESS,FAILURE')
You get in this way delivery notifications on succeded and failed messages. If you just want to get a delivery success notification just assign the input variable "parameters" with this value: 'NOTIFY=SUCCESS'. There is also a third possible value you can choose: "DELAY". This mean "notify me, if there is an email sending delay".
Best regards,
Serban Vettori

Delivery notification for messages i did not send

I have been receiving delivery notification from the [email protected] about email messages that I never sent from my mac.com account. They are either delayed or failed.
I understand that a spoof/spam is sending these messages with my email address as the from.
I am receiving 8-12 messages a day now and it has been going on for three weeks now.
I did read some similar questions but there seemed to be no answers on how to stop it other than install a junk mail application to filter all the messages we receive from the post master. This doesn't stop the the messages from being sent.
I don't want to have to change my email address which many people and systems have.
Is there a solution?
thank you
Julie

There isn't really anything you can do about it. As you have observed, your address is being forged on messages sent by someone else, so it's not a case of messages being sent from your account. I'm afraid there is nothing whatever you can do to stop this, which is infuriating but is unfortunately the case. However it usually stops after a bit as they move on to another victim.

Delivery Notification customization

Hi All,
I am using IMS 5.2, and i want to customize the Delivery Notification, any one have an idea how to do this. Because the notification message is not simple and it looks :
Ce rapport concerne un message que vous avez envoy� avec les champs d'en-t�te
suivants :
Return-path: <[email protected]>
Received: from ims-ms-daemon.mailsrv.mf.gov.dz by mailsrv.mf.gov.dz
(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
id <[email protected]>
(original mail from [email protected]); Tue,
3 Jan 2006 14:03:18 +0100 (CET)
Received: from conversion-daemon.mailsrv.mf.gov.dz by mailsrv.mf.gov.dz
(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
id <[email protected]>
(original mail from [email protected]) for [email protected]; Tue,
03 Jan 2006 14:03:05 +0100 (CET)
Received: from HADDOUDA ([10.10.0.27])
by mailsrv.mf.gov.dz (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
2004)) with SMTP id <[email protected]> for
[email protected]; Tue, 03 Jan 2006 14:02:22 +0100 (CET)
Date: Tue, 03 Jan 2006 14:02:56 +0100
From: "toufik haddouda (dgrfe)" <[email protected]>
Subject: ya taiba
To: [email protected]
Message-id: <002701c61066$29b82380$1b000a0a@HADDOUDA>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2739.300
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
Content-type: multipart/mixed; boundary="Boundary_(ID_dW/1rjZRkfzU0CQAeKvIsA)"
X-Priority: 3
X-MSMail-priority: Normal
Votre message ne peut pas �tre livr� aux destinataires suivants :
Recipient address: houda.hakem@ims-ms-daemon
Original address: [email protected]
Reason: Message too large
Regards.
Mourad.

The first part:
Ce rapport concerne un message que vous avez envoy� avec les champs d'en-t�te suivants :
may be customizable. The balance is the headers of the original message, and may not be changed.
Look in the MTA, itself, specifically
/usr/iplanet/server5/msg-(name of your server)/imta/config
and see if you can locate the files with such messages.

Mail delivery notification

How do I setup a message in Mail so that I receive a delivery notification?

open terminal
defaults write com.apple.mail UserHeaders '{"Disposition-Notification-To" = "[email protected]"; }'

Delivery notification

Similar Messages

Maybe you are looking for