Member Avatar for Cragdo
Cragdo 2 Light Poster

Hi folks,

I apologize if this is a strange question for this forum beforehand.

I recently set up a contact form for a client and a user has entered their email address incorrectly into the form and now my client can't get in touch with the enquirer and may lose out in a job as a result.

I am now going to put a confirm email field into the form to at least lessen the possibility of this happening again(hoping people don't just copy and paste).

My question is this. Is there an easy way my client can find out the enquirers correct email address from the wrong email address, considering it must be a close match to the correct address, and from the area the enquirer lives that was given in the form?

Thank you

  • 1 Contributor
  • 0 Replies
  • 101 Views

Dani AI

Generated

For : concise, practical steps to try now and a few reliable prevention measures.

Immediate recovery steps — check whether the form submission was stored anywhere (database, admin email archive, or site logs). Inspect the client mailbox for bounce/DSN messages and the web server/mail server logs: those often include the SMTP response (eg. "550 user unknown" vs "host not found") which tells whether the mailbox or the whole domain is wrong. If the submission included any other contact info (phone, postal town, company), use that first — calling or a short postal note is far more reliable than guessing an email. Public directory and social profiles keyed to the name + town sometimes locate a correct address, but treat that information carefully.

What to try before guessing an address — small domain typos are common (transposed letters, missing dot, common domain misspellings). Only attempt to contact a guessed address if the message contains nothing sensitive; do not send private client details to an address that might belong to someone else. If the mailserver returned a bounce citing a similar-looking mailbox on the same domain, that is a stronger clue than pure guesswork.

Prevention and UX fixes — always persist raw submissions server-side so admin access does not rely solely on delivery. Add real-time validation and an explicit "confirm email" field, perform a server-side MX/domain existence check, and require a quick verification click (double opt-in) before using the address for mission-critical contact. Small UX touches help: inline suggestions for common domains, clear microcopy about how the email will be used, and a required secondary contact method (phone or SMS) when follow-up is important.

Caution — follow local privacy rules (do not scrape or publish private data) and avoid emailing sensitive client information to unverified addresses. If no other contact can be found, treat the lead as unrecoverable and tighten the form/workflow to prevent repeat losses.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.