Tested trunk checkout of today. when creating a DNS Zone, Email: [ ] e.g. postmaster.mydomain.com. - example is not an email - when leaving email empty it gets accepted - when trying to enter a valid email address (including '@') it gets rejected Error: Email format invalid.
Thats all correct except that a empty value is accepted, I added this to the bugtracker. As the example points out, the email has to entered in a special format, which is used by most DNS servers like BIND and MyDNS. Instead of: [email protected] you must enter: yourname.yourdomain.com.
Ah, ok clear.. how does dns handle email addresses like [email protected]? justin.albstmeijer.domain.com could be interpreted as [email protected] or [email protected] seems somewhat confusing for users.. Wouldn't it be better to default to postmaster.domain.com and give a warning within the email management tab that there needs to be a forward for [email protected] as long as it does not exist?
