Minor bug. It may happen only if a class exists, but it is not a MailResolver. Field validation logic checks this use-case, but the issue may happen on user instances after the upgrades of other plugins, which do not retain the binary compatibility