Perhaps other monks have wider experience/knowledge of ready-made software.

As for me, I don't know the code currently you're using... but I probably wouldn't tackle the issue using third party software, anyway. Rather, IMO, the process several of us are advocating -- integrated email verification -- is one I would tackle from scratch, whether as additional code for your extant package or as a module.

Many of the details here can be modified to suit your preferences and requirements, but here's a possible workflow:

  1. The user submits your registration form
  2. your cgi (the form's action)
    • assigns the request a unique ID
    • stores that and the user's email (and other data?)
    • sends an email with the ID to the address supplied.
    The email (and, preferably, the registration page as well) explains that the user must reply (within a short time limit -- definition of "short time" left to you) to an email account you control to confirm the account request.
  3. A second script (or, for a really low intensity operation, a human) monitors incoming mail on the specified account, intercepting those with whatever subject line you assign to your initial outgoing mail.
  4. The second script compares the ID (plus address, name, etc, as your please) in the incoming email with the data stored by the cgi.
  5. If they match, the second script blesses (creates, calls a creator script, whatever) a new account.
          } else {
  6. ...if there is no match, second script takes no action...
          } but {
    periodically, second script reviews aging account request info (as stored in step 2) and kills those which have timed out.

Updated formatting for clarity

In reply to Re^5: Mail::Verify or Mail::CheckUser for Email Verification? by ww
in thread Mail::Verify or Mail::CheckUser for Email Verification? by newbie00

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.