Forum Discussion

EVSpinner's avatar
EVSpinner
Level 5
10 years ago

Discovery accelerator results

Hi everyone, I have a question about Discovery Accelerator I'm new to DA (I've got as far as installing it in the lab, configuring, starting to read the Admin guide and setting up a new case, but ...
  • Kenneth_Adams's avatar
    10 years ago

    Hmm.... I know I responded to this post a few minutes ago, but it's not showing up.

     

    EVSpinner, the search criteria screen shot looks to have the criteria properly configured.  The issue I see as the cause is likely the SMTP addresses used by the 3 custodians you've specified.

    By default, DA will use only the SMTP address(es) of the chosen custodians in the search criteria.  As such, the SMTP addresses of your 3 custodians will be listed in the criteria passed to the search engine along with the subject or content and date range criterial

    Now, DA does a literal pattern match on any criteria passed to the search engine.  As such, an SMTP address for another author that contains the SMTP address of one of the 3 custodians would cause a match to occur.  For example.  Let's say that custodian Craig (C:Craig) has an SMTP address of 'Craig.Smith@mydomain.local'.  Let's also say that there is another author with an SMTP address of 'James.Craig.Smith@mydomain.local'.  Any emails sent by James Craig Smith would be included in the items captured by the search because his SMTP address contains the SMTP address of custodian Craig.  The search criteria would match on the 'Craig.Smith@mydomain.local' portion of James's SMTP address, thus causing it to be included in the search hits.

    Take a close look at the SMTP address of the author of the unexpected hit (or authors of those hits).  I believe you'll see this is the cause for their inclusion in the captured items.  If this is the cause of those hits and you must be able to exclude them, you'll need to run a new search in a new case or research folder with the SMTP address(es) of the unexpected author(s) excluded (i.e., -James.Craig.Smith@mydomain.local) on a separate line (each).

    If you find this does not explain your unexpected hits, please open a support case so we can provide a tool to use to capture the indexed metadata of those unexpected hits and to configure captures of the search criteria in a new search using the same criteria as the search in which those items were captured.