From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | Steve Midgley <science(at)misuse(dot)org> |
Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org |
Subject: | Re: FW: Re: type for storing emails? |
Date: | 2019-11-12 16:44:52 |
Message-ID: | VisenaEmail.3b.a983a8bb456c831f.16e6080d141@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
På tirsdag 12. november 2019 kl. 16:50:35, skrev Steve Midgley <
science(at)misuse(dot)org <mailto:science(at)misuse(dot)org>>:
[...]
Not to be pedantic but in the data model, you could have a couple of
verification data fields (e.g. verification_code; email_verified), and actually
send an email and record if the user comes back with the correct verification
code. It's obviously not something that can be handled solely via specs or
database, but a data model can accommodate actual email verification (as I know
you know, but thought I should make clear for future readers of the archives).
My point is; There is no way to tecnichally verify that an email actually
«exists» (as in being active and will be routed to an actual recipient). Yes,
you can do all sorts of acrobatics, and may in many attempts succeed, but there
exists no method guaranteeing this. Many email-servers will for example happily
receive the email, respond "OK, got it", but throw the email in an "unknown
recipients"-bin, effectively ignoring any email sent to a non-existing address.
--
Andreas Joseph Krogh
From | Date | Subject | |
---|---|---|---|
Next Message | stan | 2019-11-12 17:09:12 | install problem with extensions |
Previous Message | Steve Midgley | 2019-11-12 15:50:35 | Re: FW: Re: type for storing emails? |