Bsrgvty

Kerning for subscripts of sigma?

Accepted by European university, rejected by all American ones I applied to? Possible reasons?

Relationship between Gromov-Witten and Taubes' Gromov invariant

Worn-tile Scrabble

Geography at the pixel level

What is the light source in the black hole images?

Inverse Relationship Between Precision and Recall

Is it okay to consider publishing in my first year of PhD?

What is this sharp, curved notch on my knife for?

Is Cinnamon a desktop environment or a window manager? (Or both?)

How much of the clove should I use when using big garlic heads?

How to support a colleague who finds meetings extremely tiring?

Is bread bad for ducks?

Flight paths in orbit around Ceres?

Can you cast a spell on someone in the Ethereal Plane, if you are on the Material Plane and have the True Seeing spell active?

Cooking pasta in a water boiler

Is it correct to say the Neural Networks are an alternative way of performing Maximum Likelihood Estimation? if not, why?

APIPA and LAN Broadcast Domain

Deal with toxic manager when you can't quit

Can there be female White Walkers?

Why doesn't shell automatically fix "useless use of cat"?

What is the most efficient way to store a numeric range?

What information about me do stores get via my credit card?

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

Apex Email Validation [duplicate]

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

This question is an exact duplicate of:

• 
  Email Validation regex [on hold]
  
  1 answer
  
  

String email ='shilpa..test@gmail.com'

Boolean isValid =
Pattern.matches('([a-zA-Z0-9_-.]+)@(([a-z]1,3.[a-z]1,3.[a-z]1,3.)|(([a-zA-Z0-9-]+.)+))([a-zA-Z]1,|[0-9]1,3)',email);

I am trying to validate the email in apex, but before @ the above expression is allowing double dot (..), can anyone help me to modify this regex?

apex email regular-expressions email-validation

share|improve this question

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

marked as duplicate by Derek F, glls, Pranay Jaiswal, battery.cord, Himanshu yesterday

This question was marked as an exact duplicate of an existing question.

add a comment | 

0

This question is an exact duplicate of:

• 
  Email Validation regex [on hold]
  
  1 answer
  
  

String email ='shilpa..test@gmail.com'

Boolean isValid =
Pattern.matches('([a-zA-Z0-9_-.]+)@(([a-z]1,3.[a-z]1,3.[a-z]1,3.)|(([a-zA-Z0-9-]+.)+))([a-zA-Z]1,|[0-9]1,3)',email);

I am trying to validate the email in apex, but before @ the above expression is allowing double dot (..), can anyone help me to modify this regex?

apex email regular-expressions email-validation

share|improve this question

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

marked as duplicate by Derek F, glls, Pranay Jaiswal, battery.cord, Himanshu yesterday

This question was marked as an exact duplicate of an existing question.

add a comment | 

This question is an exact duplicate of:

• 
  Email Validation regex [on hold]
  
  1 answer
  
  

String email ='shilpa..test@gmail.com'

Boolean isValid =
Pattern.matches('([a-zA-Z0-9_-.]+)@(([a-z]1,3.[a-z]1,3.[a-z]1,3.)|(([a-zA-Z0-9-]+.)+))([a-zA-Z]1,|[0-9]1,3)',email);

I am trying to validate the email in apex, but before @ the above expression is allowing double dot (..), can anyone help me to modify this regex?

apex email regular-expressions email-validation

share|improve this question

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

share|improve this question

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

share|improve this question

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

edited 2 days ago

m Peixoto

728617

edited 2 days ago

m Peixoto

728617

asked 2 days ago

ShilpaShilpa

455517

asked 2 days ago

ShilpaShilpa

455517

1 Answer
1

active

oldest

votes

3

I recommend you take a look at Salesforce's documentation on allowed email address formats then search for pre-defined regex that validates against RFC 2822. It may be that Salesforce further constrains the specification so you may need to tweak the expression. (Try googling "rfc 2822 regex".)

In the short term, you could simply split the "local" part of your match (i.e. before the "@") to be something more like:

[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)*

share|improve this answer

edited 2 days ago

answered 2 days ago

Phil WPhil W

806311

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Note that this local part is far more restrictive than Salesforce allows. It rather depends on just what you want to achieve.
  
  – Phil W
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The above solution work for not allowing dot which are together like shilpa..abc@gamil.com but doesn't work for seperate dot in email like shilpa.abc.test@gmail.com.
  
  – Shilpa
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @Shilpa You need a very complicated regex if you want to properly validate email addresses. They're far more complicated than you think.
  
  – sfdcfox
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't want very complex & proper email validation. from above regex (given n problem) after @ every thing works fine, but before @ i am facing some problems. Before @ email should allow abc.djhd.hfjdj and test--test--test--test-test.test.test_test__test but should not allow double dot continuously like test..test
  
  – Shilpa
  2 days ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Shilpa, I changed the regex for the local part to allow a.b.c.d etc. by simply indicating that the ".x" part can be repeated 0 or more times.
  
  – Phil W
  2 days ago
  

  
  
  
  

 | 
show 1 more comment

3

I recommend you take a look at Salesforce's documentation on allowed email address formats then search for pre-defined regex that validates against RFC 2822. It may be that Salesforce further constrains the specification so you may need to tweak the expression. (Try googling "rfc 2822 regex".)

In the short term, you could simply split the "local" part of your match (i.e. before the "@") to be something more like:

[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)*

share|improve this answer

edited 2 days ago

answered 2 days ago

Phil WPhil W

806311

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Note that this local part is far more restrictive than Salesforce allows. It rather depends on just what you want to achieve.
  
  – Phil W
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The above solution work for not allowing dot which are together like shilpa..abc@gamil.com but doesn't work for seperate dot in email like shilpa.abc.test@gmail.com.
  
  – Shilpa
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @Shilpa You need a very complicated regex if you want to properly validate email addresses. They're far more complicated than you think.
  
  – sfdcfox
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't want very complex & proper email validation. from above regex (given n problem) after @ every thing works fine, but before @ i am facing some problems. Before @ email should allow abc.djhd.hfjdj and test--test--test--test-test.test.test_test__test but should not allow double dot continuously like test..test
  
  – Shilpa
  2 days ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Shilpa, I changed the regex for the local part to allow a.b.c.d etc. by simply indicating that the ".x" part can be repeated 0 or more times.
  
  – Phil W
  2 days ago
  

  
  
  
  

 | 
show 1 more comment

3

I recommend you take a look at Salesforce's documentation on allowed email address formats then search for pre-defined regex that validates against RFC 2822. It may be that Salesforce further constrains the specification so you may need to tweak the expression. (Try googling "rfc 2822 regex".)

In the short term, you could simply split the "local" part of your match (i.e. before the "@") to be something more like:

[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)*

share|improve this answer

edited 2 days ago

answered 2 days ago

Phil WPhil W

806311

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Note that this local part is far more restrictive than Salesforce allows. It rather depends on just what you want to achieve.
  
  – Phil W
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The above solution work for not allowing dot which are together like shilpa..abc@gamil.com but doesn't work for seperate dot in email like shilpa.abc.test@gmail.com.
  
  – Shilpa
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @Shilpa You need a very complicated regex if you want to properly validate email addresses. They're far more complicated than you think.
  
  – sfdcfox
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't want very complex & proper email validation. from above regex (given n problem) after @ every thing works fine, but before @ i am facing some problems. Before @ email should allow abc.djhd.hfjdj and test--test--test--test-test.test.test_test__test but should not allow double dot continuously like test..test
  
  – Shilpa
  2 days ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Shilpa, I changed the regex for the local part to allow a.b.c.d etc. by simply indicating that the ".x" part can be repeated 0 or more times.
  
  – Phil W
  2 days ago
  

  
  
  
  

 | 
show 1 more comment

I recommend you take a look at Salesforce's documentation on allowed email address formats then search for pre-defined regex that validates against RFC 2822. It may be that Salesforce further constrains the specification so you may need to tweak the expression. (Try googling "rfc 2822 regex".)

In the short term, you could simply split the "local" part of your match (i.e. before the "@") to be something more like:

[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)*

share|improve this answer

edited 2 days ago

answered 2 days ago

Phil WPhil W

806311

[-a-zA-Z0-9]+(.[-a-zA-Z0-9]+)*

share|improve this answer

edited 2 days ago

answered 2 days ago

Phil WPhil W

806311

answered 2 days ago

Phil WPhil W

806311

answered 2 days ago

Phil WPhil W

806311