marioneil

email - testing boundary conditions

Wednesday, December 6, 2017 at 07:50am
0 votes
Hi We are testing boundary conditions for email length and are getting the following error when creating a package. can you tell us why theis email is being rejected? : Response code: 400 : Silanis Error Response: {"messageKey":"error.validation.invalidEmail","message":"Email address is invalid: 'mohammed.belyamani.mohammed.belyamani.mohammed.belyamani.mohamme@abcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankscotibanksscsoti.com'","code":400}
Approved Answer
harishaidary

Reply to: email - testing boundary conditions

Thursday, December 7, 2017 at 05:05am
0 votes
You can find our release notes here: https://docs.esignlive.com/content/f_release_notes/esignlive_release_notes.htm
Haris Haidary OneSpan Technical Consultant
harishaidary

Reply to: email - testing boundary conditions

Wednesday, December 6, 2017 at 10:00am
0 votes
Hi Mario, Here's the validation we do on email addresses: 1. The complete email has to be greater than 6 characters 2. The user part (before the @) has to be 64 characters or less 3. The domain part (after the @) has to be 64 characters or less
Haris Haidary OneSpan Technical Consultant
marioneil

Reply to: email - testing boundary conditions

Thursday, December 7, 2017 at 04:50am
0 votes
Hi Was the email validation changed recently? We used to be able to follow the rules below 1. Maximum of 64 characters in the "local part" (before the "@") 2. maximum of 255 characters in the domain part (after the "@") 3. total length of 320 characters. Is there a notification process for feature releases?
harishaidary

Reply to: email - testing boundary conditions

Thursday, December 7, 2017 at 04:59am
0 votes
Hi Mario, I'm not sure of what the validation was before but that's how it is right now. We'll do our best to keep these information up to date and available in our documentation. Just out of curiosity, do you have a use case where you foresee clients having emails as long as mohammed.belyamani.mohammed.belyamani.mohammed.belyamani.mohamme@abcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankabcdefbankscotibanksscsoti.com?
Haris Haidary OneSpan Technical Consultant
marioneil

Reply to: email - testing boundary conditions

Thursday, December 7, 2017 at 05:02am
0 votes
This is a test case implemented by consumers of my service. I just pass on the input get to eSignLive The unit test started failing, Im not sure what the use case is for this case. Does eSignLive publish release notes? Can I be added to the email list?
jponcerlx

Reply to: email - testing boundary conditions

Monday, February 12, 2018 at 09:51am
0 votes
Hi Haris, We've come across a number of email validation errors outside of the 3 you listed. Most recently, we were testing with this email: 
[email protected]
From what I gather, it must be the capital 's' at the end of the string. The error message is the same as the one listed at the top of this thread. Are there other checks in place?
harishaidary

Reply to: email - testing boundary conditions

Tuesday, February 13, 2018 at 07:15am
0 votes
Hi, The application essentially uses the Apache email validator class to validate email addresses (https://commons.apache.org/proper/commons-validator/apidocs/org/apache/commons/validator/routines/EmailValidator.html). Hence, if you want to know the exact rule, you'll have to look into that class.
Haris Haidary OneSpan Technical Consultant

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

LoginSign Up