Chances are pretty good that:

1. If you receive a personal email from someone with a Gmail account who used the BCC feature of Gmail to send a bulk email to a LOT of people at once…
2. If the email contains 10 or more pages of uncivil ranting using words like: ungentle, indictments, infidelity, lawlessness, lies, apostasy, inquisitional, repent, rebuke, adulterous, defamatory, inflammatory, slanderous, libelous, torture, abuse, girlie-man, man-up, effeminate, wimpy, navel-gazing, kick-tail, mindlessly, impetuous, marital cheater, guilty, recalcitrant error, fallible, misled, sin-prone, and many more words like it (too many to count)…

…You might be receiving an email that violates the Google Gmail Terms of Use policy – (Click the link to read Section 3 of the policy and judge for yourself)!

If you want to report this misuse of Gmail to Google, you can and you should by following the Next 3 Steps.

Step 1

Go to this page titled: I would like to report a Gmail user who has sent messages that violate the Gmail Program Policies and/or Terms of Use. At the top of this screen Google states their appreciation of your report:

We appreciate reports concerning users who violate Gmail’s Program Policies and/or Terms of Use. Please fill out this form to report an incident to the Gmail Team. We’ll use the information you provide to conduct an investigation, and if we need more details, we’ll contact you.

Step 2

Fill out the form fields:

• Add an email address we can use to contact you: Enter a valid email address for yourself: I have a number of valid addresses to use and entered one of them.
  
• Your Gmail username (if you have one): my personal Gmail address is rbirkey@gmail.com, so I would enter “rbirkey”
• Full Gmail username of the person involved in the incident: In my case I would enter the 6 characters (SXBXEX) before “@gmail.com” of the person I am reporting
• Email headers of the questionable message: This is a bit harder. Most email software is not set to display the full headers of email by default. You have to go into your email software and find the menu item where it says essentially “display full headers,” or “display long headers.” In the case of Apple Mail, the menu command is found at: “View > Message > Long Headers” If you are using Gmail, the “Show Original” command is found in a drop down menu in the right top corner of the email message window. See yellow highlight in image below or follow the help that Gmail offers on this page at: “To see headers in Gmail, click ‘More options,’ and then click ‘Show original.’ For instructions on how to view headers in other webmail providers, please visit: http://www.spamcop.com/help_with_headers/.”

When you select this option on the email you are reporting, a separate browser window or tab will most likely open displaying the raw code of the email. Copy everything from the top down to where the body content begins. Your long headers should look something like this:

Delivered-To: username@domain.com
Received: by 10.68.56.234 with SMTP id d10cs152150pbq;
Sun, 19 Jun 2011 02:38:37 -0700 (PDT)
Received: by 10.101.167.36 with SMTP id u36mr2805790ano.125.1308476316788;
Sun, 19 Jun 2011 02:38:36 -0700 (PDT)
Return-Path:
Received: from we.epuv.net (79-101-157-161.dynrfbkamic.ighsp.telekovbm.rs [79.101.157.161])
by mx.google.com with ESMTP id j18si8341745ann.35.2011.06.19.02.38.34;
Sun, 19 Jun 2011 02:38:35 -0700 (PDT)
Received-SPF: neutral (google.com: 79.101.157.161 is neither permitted nor denied by best guess record for domain of dshedghk@qosrwedfb.net) client-ip=79.101.157.161;
Authentication-Results: mx.google.com; spf=neutral (google.com: 79.101.157.161 is neither permitted nor denied by best guess record for domain of dshkredf@qosrvbn.net) smtp.mail=dshkredf@qosrvb.net
Received: from [121.172.146.183] ([151.136.197.128] helo=localhost.localdomain)
by smtp1.wjdzwdeerg.com (envelope-from )
(ecelerity 3.0.22.936492 r(31834)) with ESMTP
id 03eE-630-9492e887Y3; Sun, 19 Jun 2011 11:34:41 +0100
To: username@domain.com
Message-Id: <201106190938.PYG462@fjgc.net>
Date: Sun, 19 Jun 2011 11:33:12 +0100
Sender: dshk@qosr.net
From: “Gucci Louis.Vuitton”
Mime-Version: 1.0
Subject: Replica-SHOP : Luxury Watches, Bags, Shoes gcm
Content-Type: text/plain;
charset=”us-ascii”
Content-Transfer-Encoding: 8bit

The reason for this step is that this information reveals to Gmail exactly where the email came from, and what path it took to arrive in your email inbox. The reason this is important is that email spammers and mis-users like to try to “spoof” or hide where their emails are coming from. The “long headers” make that a much harder thing to do. They are used to verify that the email did in fact come from the source you think it came from.

• Enter the Original subject line of the questionable message: In my example case the Email subject line is: “Replica-SHOP : Luxury Watches, Bags, Shoes gcm”
• Enter the Content of the questionable message *(Please paste the entire body of the message in the provided space above.):  In my example case it would be: “Super Replicas – Luxury Watches, Bags, Jewelry, Phones, Shoes – Unbelievable Pricing! Watch shows your status! Girls love cool watch! wio”
• Additional information: Provide any additional information about your experience that is pertinent: In my case I might say… “I believe sxbxex@gmail.com is violating your Terms of Use Policy and making a bad name for the Google and Gmail brand names. The sender refuses to remove people from his BCC List and sends offensive and untruthful information in an uncivil tone and manner including slander, libel and abusiveness.”
• Check “Yes” or “No” to “Did the message appear to be from someone impersonating Google?”: In my personal case the sender was using their real Gmail address and not trying to spoof or hide it, so I checked “No.”

Step 3

Review your answers and information for completeness and accuracy and then press “Submit”

That’s it! However, I suggest you repeat this process for every email you receive that is of this nature.