Validate Email Domain 1.0.1

[V3NTUS]

It only caused many of the following in my admin cp:

• Error: Class 'Egulias\EmailValidator\EmailValidator' not found
• in src/addons/Kirby/ValidateEmailDomain/XF/Validator/Email.php:16

Making users unable to completely signup or make any site payments in the meantime.

Running XF 2.1.7 and php 7.4 with the required module (idn_to_ascii() from intl) enabled.

 

[Ivancas]

@Kirby can you check my question at https://xenforo.com/community/threads/validate-email-domain.212767/post-1660007 ?

 

[Kirby]

Kirby updated Validate Email Domain with a new update entry:

1.0.1 - Maintenance Release

Bugs Fixed​

• Fixed typo passing param $errorKey to parent method

New Features​

• None

Other Changes​

• Aded requirement XenForo 2.2.0+ to addon.json

Read the rest of this update entry...

 

[Kirby]

When calling the parent class's isValid method, there appears to be a spelling error in the errorkey parameter, preventing it from returning correctly.

Thanks, fixed in 1.0.1.

It only caused many of the following in my admin cp:
[...]
Running XF 2.1.7

XenForo 2.1 does not ship the required classes; upgrade to XenForo 2.2.13 or don't use the Add-on.

I mean if it's possible for you to add an option/task to check all current users and their email addresses rather than only checking new registered users.

That would be a resource intensive process and therefore quite some work to implement properly - probably more work than I want to invest here

Why would you want to do this anyway?

 

[Ivancas]

Why would you want to do this anyway?

Because instead of waiting for emails to bounce and affect the email score they can be removed or mark as inactive.

 

[Unique Username]

Because instead of waiting for emails to bounce and affect the email score they can be removed or mark as inactive.

I would have to agree with @Kirby that would be resource intensive. My suggestion would probably be checking the email upon sending, and if an email is invalid it cancels the send to that particular recipient and marks them as email invalid.

Now this won't prevent all your emails from bouncing, there could be another hundred ways emails can bounce. Some could be, email doesn't exist, mailbox full etc. My suggestion would be make sure to properly maintain your list, if a user hasn't been around for a year, it's probably best to disable their marketing mail. You could also see bounces informing you that your IP is blocked etc

 

[Kirby]

@Ivancas
I think you vastly overestimate the usefulness of (repeatedly) checking existing email addresses for valid DNS:
Usually the vast majority of users has email adresses from big / established ISPs or email service providers like GMail, Yahoo, Hotmail, GMX, T-Online, etc.

Those domains almost never go bad, so repeatedly checking them is rather pointless.

That being said, it's not impossible to implement smth, but you still didn't answer what you would want to do in case of a failure:

• Change primary usergroup
• Add secondary usergroup
• Set user status (to what?)
• Ban user
• Set a custom user field
• Smth. entirely different

?

 

[Ivancas]

Those domains almost never go bad

If a user creates an account using a wrong email, the account will be inactive awaiting for email confirmation. It could be quite useful to have a task (on admin.php?tools/rebuild) where we can scan all inactive users (or active as well) and move those with invalid email addresses to a secondary group so we can choose to mass delete them if needed. This task can be manually run as much as needed (but not a cron job, which would be unecessary).

 

[Unique Username]

If a user creates an account using a wrong email, the account will be inactive awaiting for email confirmation. It could be quite useful to have a task (on admin.php?tools/rebuild) where we can scan all inactive users (or active as well) and move those with invalid email addresses to a secondary group so we can choose to mass delete them if needed. This task can be manually run as much as needed (but not a cron job, which would be unecessary).

Couldn’t you just search for all the accounts that are awaiting email confirmation and update them to email invalid?

 

[Ivancas]

and update them to email invalid?

no, because they could be valid emails. What I'm try to say is in "awaiting email confirmation" you have valid and non valid email accounts.

 

[Unique Username]

no, because they could be valid emails. What I'm try to say is in "awaiting email confirmation" you have valid and non valid email accounts.

I get what you're saying, but if it's awaiting confirmation for more than 24 hours, chances are the confirmation email has bounced. They would get a notice telling them to change their email, and if it was a valid email, they could just add the email back.

Edit: I don't want to take away from the discussion around the app, but feel free to DM me if you want to discuss more about email and such.

 

[Ivancas]

Edit: I don't want to take away from the discussion around the app

The suggestion I made is for the app and I just answered @Kirby questions

They would get a notice telling them to change their email, and if it was a valid email, they could just add the email back.

You are relying on the user to log in and change his email but you are forgetting about bots (that create accounts with fake emails for example) or users that just left the account forgotten and never log in to confirm his email. Those users remain in the database and are useless.

 

[Unique Username]

The suggestion I made is for the app and I just answered @Kirby questions


You are relying on the user to log in and change his email but you are forgetting about bots (that create accounts with fake emails for example) or users that just left the account forgotten and never log in to confirm his email. Those users remain in the database and are useless.

Then, search for accounts awaiting confirmation emails and that have not logged in for x amount of time and delete them.

 

[Ivancas]

Then, search for accounts awaiting confirmation emails and that have not logged in for x amount of time and delete them.

Then the whole purpose of this addon is useless..