Warning: You are browsing the documentation for Symfony 2.6, which is no longer maintained.
Read the updated version of this page for Symfony 6.2 (the current stable version).
Validates that a value is a valid email address. The underlying value is cast to a string before being validated.
| Applies to | property or method |
| Options | |
| Class | |
| Validator | EmailValidator |
Basic Usage
- Annotations
- YAML
- XML
- PHP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
// src/Acme/BlogBundle/Entity/Author.php
namespace Acme\BlogBundle\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class Author
{
/**
* @Assert\Email(
* message = "The email '{{ value }}' is not a valid email.",
* checkMX = true
* )
*/
protected $email;
}Options
2.5
The strict option was introduced in Symfony 2.5.
strict
type: boolean default: false
When false, the email will be validated against a simple regular expression. If true, then the egulias/email-validator library is required to perform an RFC compliant validation.
message
type: string default: This value is not a valid email address.
This message is shown if the underlying data is not a valid email address.
checkMX
type: boolean default: false
If true, then the checkdnsrr PHP function will be used to check the validity of the MX record of the host of the given email.
checkHost
type: boolean default: false
If true, then the checkdnsrr PHP function will be used to check the validity of the MX or the A or the AAAA record of the host of the given email.
payload
type: mixed default: null
2.6
The payload option was introduced in Symfony 2.6.
This option can be used to attach arbitrary domain-specific data to a constraint. The configured payload is not used by the Validator component, but its processing is completely up to you.
For example, you may want to use several error levels to present failed constraints differently in the front-end depending on the severity of the error.
