Bursting and DeliveryManager - How to identify wrong email address

Question

Hi,
I have created a BI report (based on Data Template)
Report generates the XML and then in the afterReport trigger, I am calling Bursting Program to send emails to the customers.
Everything works fine.
Problem is:
If, there is any wrong email address, then we are NOT receiving any notification and undeliverable message.
This happens for Bursting Request (program).
I have also written a sample Java Code using "DeliveryManager" XDO class, to check whether it thorws the exception in case of wrong email ID or incorrect domain.
But it also completes successfully and without any error. (no email .... obviuosly)
import oracle.apps.xdo.delivery.*;
public class EmailTest
public static void main(String args[])
try{
DeliveryManager dm = new DeliveryManager();
DeliveryRequest req = dm.createRequest(DeliveryManager.TYPE_SMTP_EMAIL);
req.addProperty(DeliveryPropertyDefinitions.SMTP_SUBJECT, "test mail");
req.addProperty(DeliveryPropertyDefinitions.SMTP_HOST, "appsrelay.xxx.com");
req.addProperty(DeliveryPropertyDefinitions.SMTP_FROM, "[email protected]");
req.addProperty(DeliveryPropertyDefinitions.SMTP_TO_RECIPIENTS, "[email protected]"); //WRONG EMAIL ADDRESS HERE
req.addProperty(DeliveryPropertyDefinitions.SMTP_CONTENT_TYPE, "application/pdf");
req.addProperty(DeliveryPropertyDefinitions.SMTP_CONTENT_FILENAME,"test.pdf");
req.setDocument("/home/appldev2/WYSEINVPRINTN2_17402678_1.PDF");
req.submit();
req.close();
catch(Exception e)
System.out.println("Exception at: "+e);
Then, I tried writing a send mail program using JAVAX EMAIL APIS.
import java.util.*;
import java.io.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.activation.*;
public class EmailTest2
public static void main(String args[])
String to = "[email protected]"; //WRONG EMAIL ADDRESS HERE
String cc = "[email protected]";
String bcc = "[email protected]";
String from = "[email protected]";
// SUBSTITUTE YOUR ISP'S MAIL SERVER HERE!!!
String host = "appsrelay.xxx.com";
String Subject="";
Properties props = new Properties();
// Get a session
Session session = Session.getInstance(props);
try{
Transport bus = session.getTransport("smtp");
bus.connect();
Message msg = new MimeMessage(session);
Address fromAddress = new InternetAddress(from);
msg.setFrom(fromAddress);
Address[] toAddresses = InternetAddress.parse(to);
msg.setRecipients
(Message.RecipientType.TO,toAddresses);
Address[] ccAddresses = InternetAddress.parse(cc);
msg.setRecipients
(Message.RecipientType.CC,ccAddresses);
Address[] bccAddresses = InternetAddress.parse(bcc);
msg.setRecipients
(Message.RecipientType.BCC,bccAddresses);
Subject = "test emails";
msg.setSubject(Subject);
msg.setSentDate(new Date());
MimeBodyPart p1 = new MimeBodyPart();
p1.setText(" \n" + "Please find attached the SPQ approval letter \n\n" + "Regards, \n");
Multipart mp = new MimeMultipart();
mp.addBodyPart(p1);
msg.setContent(mp);
msg.saveChanges();
bus.sendMessage(msg, toAddresses);
bus.sendMessage(msg, ccAddresses);
bus.close();
catch(Exception e)
System.out.println("Exception at: "+e);
This, program throws Exception when there is any invalid character or wrong domain specified.
"class javax.mail.SendFailedException: 553 5.1.2 <[email protected]>... Invalid host name"
Please help me to get some clue about how we can track the invalid email address and also, undeliverable emails in Bursting or XDO DeliveryManager classes.
Thanks a Lot,
-- Ejaz
Edited by: ESyd on Aug 9, 2010 1:14 AM

Answer 1

Hi,
Actually delivery failure notification is nothing to do with bursting or Delivery API, For me it deliver the notification if delivery address is incorrect (not exists), though the bursting engine does not through any error for invalid email format.
If you really looking for the solution, as a workaround :
I would use the file delivery
Implement the Bursting Status Listener
within Before Document Delivery, implement the customize delivery solution by using javax.mail logic to email the report.
For most of us, It is too much and better to raise a SR, but you already implemented the other part, so just combine these two to get what you want.