portal.mshanken.com Open in urlscan Pro
199.167.227.42  Public Scan

Form analysis
1 forms found in the DOM

Name: abuseForm — POST abusereport.cfm

<form id="abuseForm" name="abuseForm" class="topLabel page1" autocomplete="off" enctype="multipart/form-data" method="post" action="abusereport.cfm" onsubmit="return doSubmitEvents();">
  <ul>
    <li id="fo8li7" class="two-column     ">
      <label class="desc" id="title7" for="jobID"> Critical Impact Job ID / Message ID <span id="req_7" class="req">*</span>
      </label>
      <div>
        <input id="jobID" name="jobID" type="text" class="field text large" value="b1a5768703df8bc13947229f28c3afba" maxlength="255" size="30" tabindex="1" required="">
      </div>
    </li>
    <li id="fo8li11" class="     ">
      <label class="desc" id="title11" for="firstname"> First Name </label>
      <span>
        <input id="firstname" name="firstname" type="text" class="field text fn" size="30" tabindex="2">
      </span>
      <label class="desc" id="title11" for="lastname"> Last Name </label>
      <span>
        <input id="lastname" name="lastname" type="text" class="field text ln" size="30" tabindex="3">
      </span>
    </li>
    <li id="fo8li4" class="two-column     ">
      <label class="desc" id="title4" for="emailaddress"> Email </label>
      <div>
        <input id="emailaddress" name="emailaddress" type="email" spellcheck="false" size="30" class="field text medium" maxlength="255" tabindex="4">
      </div>
    </li>
    <li id="fo8li5" class="two-column     ">
      <label class="desc" id="title5" for="comments"> Comments, Questions, Reason For Report </label>
      <div>
        <textarea id="comments" name="comments" class="field textarea medium" spellcheck="true" rows="10" cols="50" tabindex="5"></textarea>
      </div>
    </li>
    <li class="buttons ">
      <div>
        <input type="hidden" name="jid" id="jid" value="b1a5768703df8bc13947229f28c3afba">
        <input type="hidden" name="unsubscribe" id="unsubscribe" value="">
        <input type="hidden" name="eid" id="eid" value="bfd5f68038aeb58ce3e76a0e50d35c2b">
        <input type="hidden" name="spam" id="spam" value="">
        <input type="hidden" name="nodupe" id="nodupe" value="">
        <input type="hidden" name="s" id="s" value="6">
        <input id="saveForm" name="saveForm" class="btTxt submit" type="submit" value="Submit">
      </div>
    </li>
  </ul>
</form>

Text Content

CRITICAL IMPACT ABUSE DESK

After sending email on behalf of our clients to millions of users a day, we're
bound to get abuse reports every now and then. We take abuse reports seriously,
and we go to great lengths to prevent abuse within our system.


HOW CRITICAL IMPACT PREVENTS AND COMBATS ABUSE

 1. We have a team of human reviewers approving new Critical Impact accounts and
    detecting abuse. Our staff uses a broad range of criteria to evaluate
    accounts, ranging from the obvious WHOIS and IP information, to some
    not–so–obvious behavioral patterns.
 2. We require all users to agree to our Terms of Use before they can set up a
    Critical Impact account, and again before they can import any existing
    customer lists into their accounts.
 3. For customers who are starting from scratch with Critical Impact and don't
    have a list of customers to import, we offer customizable signup forms to
    place on their website. The signup forms only use the double opt–in method.
    This method keeps bad signups out and stores opt–in proof for every
    subscriber (like IP Address and date/time stamps).
 4. Customers must submit their physical mailing address and a permission
    reminder ("you are receiving this email because you signed up at...") for
    every list they set up in Critical Impact. We insert that information is
    inserted into their campaigns.
 5. We automatically insert a one–click unsubscribe link in every campaign sent
    from our system.
 6. All lists managed in Critical Impact are automatically cleaned of soft
    bounces (on the fifth campaign attempt) and hard/undeliverable bounces are
    cleaned instantly.


HOW WE EDUCATE CUSTOMERS

 1. We keep our users updated with the latest email-marketing best practices,
    tips, etiquette, and do's and don'ts via our Critical Impact Blog and
    customer newsletters
 2. Throughout Critical Impact's user interface (when sending campaigns, setting
    up lists, and designing templates), we provide customers with constant,
    helpful links and background information that help them understand etiquette
    and spam laws.


HOW WE DEAL WITH ISSUES

 1. We embed every email campaign sent from our servers with a Job ID so that
    recipients can easily report abuse to Critical Impact. When we receive
    complaints through our abuse form, we investigate immediately. If the
    campaign or user account appears suspicious in any way, we'll suspend the
    account during the investigation.
 2. We're registered with major ISPs and anti-spam authorities to receive
    automated feedback loop alerts when any of our users' recipients report
    abuse. When we're able to parse those alerts, we remove the recipient from
    our user's list. If the reports exceed a certain threshold, we send a
    warning to our user. If the warnings exceed a reasonable threshold, we
    suspend the user's account and investigate. Most ESPs and ISPs will tell you
    a reasonable threshold for abuse complaints is 0.1 percent (1 out of a
    thousand people reported your campaign as junk). Because of the sheer volume
    of emails sent from our IPs, and because most of our IPs are shared across
    multiple users, our threshold is actually much more strict.


REPORT EMAIL ABUSE

Use the form to report a job id you found in the email header) to Critical
Impact's abuse desk.

If you want a response from us, or if you want us to remove you from the
Critical Impact user's list, please include your email address or contact
information along with your report. Including your email address is optional,
but it's extremely useful in helping us investigate the sender for abuse.

 * Critical Impact Job ID / Message ID *
   
 * First Name Last Name
 * Email
   
 * Comments, Questions, Reason For Report
   
 * 

Copyright  Critical Impact Software, Inc. 1725 Eye Street NW, Suite 300
Washington DC 20006