First: thank you all for the answers.
It's clear that's very bumpy road, someone doesn't care about few checks
a day and it's ok some other take it as a bad practice, some other block
the IP so there's no way to have an overall view. A lot of provider
blocks the VRFY command so that's not an option too.
Our customer is actually testing captainverify.com service (even if we
suggested not to trust these kind of services).
May it (or something similar) be a right/trustable way?
Let me quickly reply to the answers I got:
Yes, we are in EU and yes, I confirm that the "legal" situation is
clear; in detail:
Data owner: Big electrical company (nominate both our customer and us as
"External Data Processor")
We must follow their instruction present in the agreement: verify the
correctness of the data AND NOT contact the end user.
Contacting a mail provider in order to verify the correctness of the
data is in the purpose of the agreement and of the data treatment so
it's not a violation.
Contacting the end-user is a violation of both the agreement and privacy.
===
I never said we want to check in any "hidden/anonymous" way, I don't
know why someone figured it out
===
It should be a manual process, during the day contracts come to the
office and an employee manually insert data, she should click a specific
button in order to check, no batch process.
===
For 4XX return code I planned to show the error the operator may
re-check later (or not) based on the right choice after reading the message
===
I know that misspelled recipient may sometimes be present but it's a
small percentage of a small percentage, it approximate 0.
In 5 months there was 4 cases; all of them was non existent mailbox, if
a system like this was present it prevented quite every error.
===
Yes, the collection by the paper is required from the Energy company
that's not a choice; they switched back to the "old style" but using
API's in order to de-duplicate (or aggregate) already present customers,
this is why they ask also the e-mail as mandatory with all the user data
needed in the contract.
===
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
