Re: [ebxmlms-develop] Non-delivery notification

[Patrick Y. <kc...@ce...>]

Non-delivery notificationAgreed. This is a nice feature. I have marked =
it down. To generalize the problem, do you think we need to restructure =
the channels for the MSH server to report status to MSH clients (e.g. =
failure notifications, sending success notifications, error messages, =
etc.)? Any ideas?

Regards, -Patrick
  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Tuesday, March 02, 2004 10:18 AM
  Subject: [ebxmlms-develop] Non-delivery notification


  Now that we have a production system up and running, there are =
opportunities for improvement. :-)=20

  One of these is notification of delivery failures. At the moment, =
Hermes tries N times to deliver a message, and sends a failure message =
to the back end on the Nth failure. What we'd really like to know, =
though, is when each failure occurs, so when the first failure happens, =
we can investigate why it is failing and hopefully fix it in time for a =
retry to work.

  I don't think this can be done at the moment, but it would be nice to =
make it an option to send a message to the back end saying "failure M of =
N" each time a delivery attempt failure occurs.

  PJDM=20
  --=20
  Peter Mayne=20
  Technology Consultant=20
  Spherion Technology Solutions=20
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
  T: 61 2 62689727  F: 61 2 62689777=20