ArrivalEvent for InvalidMailId

Options
krithvit
krithvit
edited April 27, 2011 in Cloud Fax and Notifications #1

            Comments given by Easylink (Adams, William [wadams@easylink.com]):

 The Arrival Event would have been generated in the SOAP XML response for the invalid email address as soon as the sc.com mail server had accepted the email connection from Easylink and responded that the user ‘S’ does not exist for which to deliver the email. As Easylink delivers almost all email in under 30 seconds, the error response back from sc.com would have also happened very quickly - so the invalid email ArrivalEvent response would have been generated very soon after job submission.

Based on the above comments provided by Adam, William - If the email address is invalid with the valid domain name, the SOAP response will provide the exact status description to MDIS.

 But when we tested from SCB by posting 5 jobs to one single Invalid email address (abzzzz@sc.com) with valid domain, but we are able to receive the FAILURE status only for 4 jobs and the remaining one got updated with  SUCCESS status which is incorrect.

 Also whenever we tried to post some jobs to invalid email id via Outlook, we are able to get the bounce back failure response immediately. Similarly, we would like to understand how Easylink works? Please provide us the list of steps which will be performed from Easylink after the jobs been submitted from MDIS to Easylink. 

Expecting your earliest response for the above 2 queries

Comments

  • skamens
    skamens
    #2
    Options

    Without seeing the details of the job, I can't be sure, but my guess is that the system performed its standard deduplication on your deliveries.

    By default, we will only deliver to a single address once within a job, so we would have attempted only one of the 5 deliveries to the invalid address.  The other items would have been cancelled with a gamma status code of 5201, indicating a duplicate.

  • krithvit
    krithvit
    #3
    Options

    Please find the job id's for the request posted with invalid email id abzzzz@sc.com

    37927831|usme (FAILED)
    39813261|usme (FAILED)
    37927855|usme (SUCCESS)
    39804904|usme (FAILED)
    39805198|usme (FAILED)

    Four jobs got failed but one got Success status.As per your comemnts , even deduplication should make all the job id's failed.

    Please give Your comments on this.

  • krithvit
    krithvit
    #4
    Options

    Please find the job id's for the request posted with invalid email id abzzzz@sc.com

    37927831|usme (FAILED)
    39813261|usme (FAILED)
    37927855|usme (SUCCESS)
    39804904|usme (FAILED)
    39805198|usme (FAILED)

    Four jobs got failed but one got Success status.As per your comemnts , even deduplication should make all the job id's failed.

    Please give Your comments on this.

  • skamens
    skamens
    #5
    Options

    I see the Arrival Event indicating the failed delivery on all five of these jobs.

    However, from looking at the details, it looks like the arrival event for job 37927855 (which is showing SUCCESS above) was received about 2 hours after the ones for the other four jobs, so presumably when you checked the status, it didn't show up as having failed yet. 

    This kind of thing is relatively normal in the email world.  It's not unusual to get bounceback messages hours or even days after a message is sent. 

    To get the most accurate data, we recommend querying for status a day or so after the job is sent to make sure all events get picked up.

Categories