Reply address empty error | Community
Skip to main content
priyankah586599
Level 4
Apr 13, 2018 6:13 AM UTC
Solved

Reply address empty error

Hi,

The campaign did not send out any delivery  because of the following error

13/04/2018 05:17:13 Failed Unreachable xxxx806@gmail.com The file '/usr/local/neolane/nl6/datakit/nms/eng/schema/deliveryAlert.xml' does not exist on the server. Unable to load the document of identifier 'nms:deliveryAlert' and type 'xtk:schema'. Reply address is empty. Cannot deliver the message. The campaign is in the Retry pending status. Pls guide.

Regards,

Priyanka

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    priyankah586599Accepted solution
    Level 4
    May 15, 2018 6:52 AM UTC

    Hi Florent,

    Yes, We have a separate LUT in our project where Reply address was missing. We added it and the issue was resolved!

    Regards,

    Priyanka

    View reply

    4 replies

    priyankah586599AuthorAccepted solution
    Level 4
    May 15, 2018 6:52 AM UTC

    Hi Florent,

    Yes, We have a separate LUT in our project where Reply address was missing. We added it and the issue was resolved!

    Regards,

    Priyanka

    Translate
      florentlb
      florentlb
      Level 10
      May 15, 2018 6:48 AM UTC

      Hi Priyanka,

      Were you able to identify and solve your issue?

      Florent

      Translate
      florentlb
      florentlb
      Level 10
      Apr 19, 2018 3:39 PM UTC

      Hi Priyanka,

      Sorry for the delay in replying. Can you share more details about your delivery? Please make sure you have set all required fields for the delivery (such as the reply address mentioned in your error message).

      If you are sure that all you fields are correctly configured, I'd advise to contact our support team to have it investigated.

      Florent

      Translate
      priyankah586599Author
      Level 4
      Apr 13, 2018 8:29 AM UTC

      Reply pls!

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...