sumantasaha

Handle Email Bounce

0 votes

Hi,

We have the requirement to display the user whose email has bounced. We have used EMAIL_BOUNCE event, but that event is not having all the information it feels. Please propose a possible way to get the data during EMAIL_BOUNCE.

 

Thanks, 

Sumanta


Reply to: Handle Email Bounce

0 votes

Update on the post:

I have tried to handle the EMAIL_BOUNCE event in callback. However, the event is not triggered even incorrect email address mentioned.


Reply to: Handle Email Bounce

0 votes

Hi Sumanta,

 

When a recipient set auto-reply for the email or when OneSpan Sign failed to deliver the email to the mailbox in either of the two scenarios: (1)email domain is not valid (2)email username doesn't exist, an Out-Of-The-Office email will be sent to inform your package owner:3-5-1

At the same time, the EMAIL_BOUNCE callback event will be triggered, a POST request with below payload will be sent to your callback URL:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"EMAIL_BOUNCE","sessionUser":"f657e425-276f-4843-995a-33f31d523ef8","packageId":"I7B2Ptw2RCIva2zYH-VMYRspH1c=","message":"OOTO","documentId":null,"createdDate":"2020-03-05T16:39:04.620Z"}

 

From where, the name "EMAIL_BOUNCE" is the callback event type, the sessionUser "f657e425-276f-4843-995a-33f31d523ef8" is the signer ID of the recipient, and the package ID.

 

If your account owner hasn't received the OOTO email, you can share the package ID and the environment(sandbox vs production), so that I can help you check the email status.

 

Duo

 

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Handle Email Bounce

0 votes

The available values of "message" from the payload are "BOUNCE" and "OOTO", tells your application whether the event was triggered because the email is invalid or because of the OOTO reply.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Handle Email Bounce

0 votes

Is it possible via API to return the email address that bounced ?

Mark knollin


Reply to:

0 votes

Hi Mark,

 

Take this callback for example:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"EMAIL_BOUNCE","sessionUser":"f657e425-276f-4843-995a-33f31d523ef8","packageId":"I7B2Ptw2RCIva2zYH-VMYRspH1c=","message":"OOTO","documentId":null,"createdDate":"2020-03-05T16:39:04.620Z"}

The "sessionUser" here refers to the Signer ID. If you pulled the package JSON with "GET /api/packages/{packageId}", signer ID can be located at "roles" > "signers" > "id".

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Handle Email Bounce

0 votes

Yes I see the "id : xxxx" under signers and just above in the JSON at the same level, I see the detail about the signer, email, name , company ect...

Mark knollin


Reply to: Handle Email Bounce

0 votes

My Onespan callback notifications were working fine until recently. Now Onespan call back notifications are sending me a "GET" request instead of a "POST" request. This must be why all of a sudden my payload is empty. Any idea what has happened ?

Mark knollin


Reply to: Handle Email Bounce

0 votes

FYI, I found the problem. I had setup a URL redirect on the server and by doing this for some reason the POST was getting converted to a GET request. Maybe onespan cannot find my URL redirect and generates an error which turns the POST into a GET request.

I removed the call back URL and replaced it with the original URL I was using in the beginning and now I am getting the POST requests correctly.

Mark knollin


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off