Validate Email Domain 1.0.1

[GameNet]

does.not-mattter-at.all@this-domain-does-not-exi.st

how do I do the test from your add-on?

 

[GameNet]

If you don't want to try this address try does.not-mattter-at.all@this-domain-does-not-exi.st

I thing there might be problem with my email server I will had to get back to you later

 

[Kirby]

how do I do the test from your add-on?

While the Add-on is disabled, go to your ACP > Tools > Test outbound email

Send the email and check error log afterwards.

If you get a similar error like the one you posted it is not releated to the Add-on (as that is disabled).

 

[GameNet]

If you get a similar error like the one you posted it is not releated to the Add-on (as that is disabled).

OK it's not related to the email address

 

[rdn]

Hi, is the PHP Intl extension needed for this add-on to operate as intended?

 

[bzcomputers]

Hi, is the PHP Intl extension needed for this add-on to operate as intended?

Yes, the intl extension is required to run the domain check which uses the function idn_to_ascii (which is provided by intl).

 

[Kirby]

Hi, is the PHP Intl extension needed for this add-on to operate as intended?

K

Post in thread 'Validate Email Domain'

Mar 5, 2023

This addon requires PHP 8.1 and PHP Intl?

Intl is most likely required, PHP 8.1 is not required.

Do you think it might be better to do the DNS check after the email input goes from in focus to out of focus rather than waiting to check after the register button is clicked?

This night be a bit more userfriendly, but unlike the current approach (which is only a really simple extension of existing functionality) it would require quite a bit of new code.
Not sure if I'd be willing to do that

• Kirby

• 

 

[rdn]

Oops, sorry, I already asked the same question.
Thanks for the response.

 

[Rayzggz]

Hi, I noticed that DNS validation also applies when existing users log in with their email address.

If their email domain was valid when they registered but later becomes invalid, email login fails with “The requested user could not be found,” even though the account still exists.

Would you consider making this behavior configurable? Perhaps the following options could help accommodate different needs:

• Validate everywhere, including login (current behavior)
• Validate during registration and email changes only
• Validate new registrations only

This could help prevent existing users from losing email login access while still allowing administrators to enforce stricter validation if preferred.