This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, I have an entity with an email address. Its property is set to validate that this is so. When I enter an email address of "abc+def@example.com", Lightspeed throws a ValidationException. As you may already know, "abc+def@example.com" is a valid address and often used as an alias in gmail and other postfix mail systems (like OS X Mail). See https://mail.google.com/support/bin/answer.py?answer=12096. You may want to look at http://haacked.com/archive/2007/08/21/i-knew-how-to-validate-an-email-address-until-i.aspx for a discussion as to what is allowed and not allowed as email addresses. This is happening in production and is critical for me to fix. Any chance it can be fixed in Lightspeed? Thanks,
|
|
|
|
|
We're not planning to support the full range of addresses permitted by the RFC, because if someone types one of the more obscure variations, it's far more likely to be a typo than to be a correct but unusual address. You can always create your own validation if you need to support 'technically legal but nobody uses them' addresses (e.g. a Format validation that passes any string with a single @ in it). However, we recognise that the '+' convention is widely used and we shouldn't be rejecting it. So this will be fixed in the next nightly build of LightSpeed. If there are any other conventions that are common enough that you need to support them but which we are currently rejecting then do let us know. |
|
|
|
|
Thanks mate. The regex provided on the haacked site does a pretty good job and we haven't found any issues with it. It covers most of the commonly used conventions. Werner |
|
|
|
