Bug 32136 - E-mail testing
Summary: E-mail testing
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-08 17:54 UTC by Christopher Brannon
Modified: 2022-11-09 15:29 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2022-11-08 17:54:42 UTC
Email Checker (email-checker.net) is a tool that does some e-mail validation.  Step 1 Koha already does, but I am curious if Koha could do steps 2 and 3?

How do we verify an email ?
First it checks for email address format.
Then make sure that domain name is valid. We also check whether it’s a disposable email address or not.
In the final step, It extracts the MX records from the domain records and connects to the email server (over SMTP and also simulates sending a message) to make sure the mailbox really exists for that user/address. Some mail servers do not cooperate in the process, in such cases, the result of this email verification tool may not be as accurate as expected.

The tool itself limits you to 5 checks per hour.  There is a premium plan, and also an API.

Only 5 lookups per hour, in free plan.

Upgrade to our premium plan or use the API.

This would be a great tool when creating a patron record.  With the way it is worded, I don't know if the API is free to use, but if not, I'm wondering if we could incorporate the same methods in Koha?
Comment 1 David Cook 2022-11-08 22:57:25 UTC
Checking that the domain name is valid and extracting the MX records is easy enough.

Connecting to the target mail server to try to check if the mailbox exists is more problematic. 

Depending on the usage you envision, this could be a good use case for a Koha plugin.