Add an optional debug field in the request, which, if true, will output debug info in the output.
Problem
A lot of people wonder why an email verification fails. Add debugging info via the API will save debugging time.
Solution
{
"to_email": "test@gmail.com",
+ "debug": true
}
Which, if set, will also add a new debug field in the response, which gives additional info about how Reacher performed the verification. Things like:
[ ] how much time the whole verification took?
[ ] how many SMTP connections did it make? 1, or 2 (to avoid greylisting), or 0 (using API or headless browser)
[ ] the full SMTP handshake logs
Example:
{
"is_reachable": "unknown",
// -- snip --
"debug": {
"time_elapsed": 10539, // in ms
"smtp": {
"method": "smtp", // or "api" or "headless"
// fields below will depend on "method" above
"smtp_connections": 2,
"logs": [
">> STARTTLS<CRLF>",
"<< 220 TLS go ahead<CRLF>"
// -- snip --
]
}
}
Notes
For new contributors: This is a good issue to get to know the codebase. It's also possible to do this feature piecewise: a first good step might be to simply add the time_elapsed field
Feature Request
Add an optional
debug
field in the request, which, if true, will output debug info in the output.Problem
A lot of people wonder why an email verification fails. Add debugging info via the API will save debugging time.
Solution
Which, if set, will also add a new
debug
field in the response, which gives additional info about how Reacher performed the verification. Things like:Example:
Notes
For new contributors: This is a good issue to get to know the codebase. It's also possible to do this feature piecewise: a first good step might be to simply add the
time_elapsed
field