Blocking spam from referral www.event-tracking.com

Spam referral traffic from www.event-tracking.com began showing up today.

What is spam referral traffic anyway and why is it bad? Trust us, you do not want this traffic.

http://www.analyticsedge.com/2014/12/removing-referral-spam-google-analytics/

Our .htaccess file which is right at the root of our web directory looks like this (as of this blog post date and time):

RewriteCond %{HTTP_REFERER} blackhatworth.com [NC,OR]
RewriteCond %{HTTP_REFERER} http://www.event-tracking.com [NC,OR]
RewriteCond %{HTTP_REFERER} tasks.2c-studio.com [NC,OR]
RewriteCond %{HTTP_REFERER} floating-share-buttons.com [NC,OR]
RewriteCond %{HTTP_REFERER} semaltmedia.com [NC,OR]
RewriteCond %{HTTP_REFERER} dailyrank.net [NC,OR]
RewriteCond %{HTTP_REFERER} floating-share-buttons.com [NC,OR]
RewriteCond %{HTTP_REFERER} 4webmasters.org [NC,OR]
RewriteCond %{HTTP_REFERER} bestwebsitesawards.com [NC,OR]
RewriteCond %{HTTP_REFERER} trafficmonetize.org [NC,OR]
RewriteCond %{HTTP_REFERER} trafficmonetizer.org [NC,OR]
RewriteCond %{HTTP_REFERER} webmonetizer.net [NC,OR]
RewriteCond %{HTTP_REFERER} webmonetizer.net [NC,OR]
RewriteCond %{HTTP_REFERER} 100dollars-seo.com [NC,OR]
RewriteCond %{HTTP_REFERER} hulfingtonpost.com [NC,OR]
RewriteCond %{HTTP_REFERER} buttons-for-website.com [NC,OR]
RewriteCond %{HTTP_REFERER} semalt.semalt.com [NC,OR]
RewriteCond %{HTTP_REFERER} darodar.com [NC,OR]
RewriteCond %{HTTP_REFERER} priceg.com [NC,OR]
RewriteCond %{HTTP_REFERER} ilovevitaly.co [NC,OR]
RewriteCond %{HTTP_REFERER} o-o-6-o-o.com [NC,OR]
RewriteCond %{HTTP_REFERER} humanorightswatch.org [NC,OR]
RewriteCond %{HTTP_REFERER} simple-share-buttons.com [NC,OR]
RewriteCond %{HTTP_REFERER} t.co [NC,OR]
RewriteCond %{HTTP_REFERER} 4webmasters.org [NC,OR]
RewriteCond %{HTTP_REFERER} best-seo-solution.com [NC,OR]
RewriteCond %{HTTP_REFERER} best-seo-offer.com [NC,OR]
RewriteCond %{HTTP_REFERER} theguardlan.com [NC,OR]
RewriteCond %{HTTP_REFERER} googlsucks.com [NC,OR]
RewriteCond %{HTTP_REFERER} make-money-online.7makemoneyonline.com [NC]
RewriteRule .* – [F]

Authenticate dovecot logins using WordPress user table checkpassword

After some extensive web searching on the subject, here is my configuration that authenticates dovecot logins using the auth_pass value in my WordPress v 4.3.1 user table. This allows me to use one single user login throughout my WordPress website. My dovecot setup is static only requiring password authentication. Your mileage may vary. Enjoy.

/etc/dovecot/conf.d/auth-sql.conf.ext
passdb {
driver = checkpassword
args = /usr/local/sbin/checkpassword

userdb {
driver = static
args = uid=vmail gid=vmail home=/var/www/home/%u
}

/usr/local/sbin/checkpassword
#!/usr/local/bin/bash
CHECKPASSWORD_REPLY_BINARY=”$1″
LOG=/var/log/dovecot
INPUT_FD=3
EXITCODE=1
read -d $’\0′ -r -u $INPUT_FD USER
read -d $’\0′ -r -u $INPUT_FD PASS
LOGINOK=`/usr/local/sbin/checkpassword.pl $USER $PASS`
if [ $LOGINOK == 0 ]; then
/usr/local/libexec/dovecot/checkpassword-reply
EXITCODE=0
fi
echo “`date “+%Y.%m.%d %H:%M:%S”` $*; Input: $USER LOGINOK: $LOGINOK” >>$LOG
exit $EXITCODE

/usr/local/sbin/checkpassword.pl
#!/usr/bin/perl -w

use DBI;
use Authen::Passphrase::PHPass;

my $userid=$ARGV[0];
my $password=$ARGV[1];

sub _app_mysql_init() {
$dbh = DBI->connect(“DBI:mysql:wordpress:localhost”, “root”, “xxxxx”, { RaiseError => 0, AutoCommit => 1 });
if (not $dbh) {
print “ERROR CONNECTING TO THE DATABASE SERVER, CONTACT YOUR SYSADMIN!”;
exit;
}
}

_app_mysql_init();

sub _query_pass() {

$se = $dbh->prepare(“SELECT user_pass FROM wp_users WHERE user_email = \”$userid\””);
$se->execute();
$numserows = $se->rows;
if ($numserows > 0) {
while (@serow = $se->fetchrow_array) {
$hash=$serow[0];
}
}
$ppr = Authen::Passphrase::PHPass->from_crypt($hash);
if($ppr->match($password)) {
print 0;
} else {
print 1;
}

}

_query_pass();

Allowing ‘Less Secure’ Apps Access to your Gmail Account

Allowing CORE AutumnTECH access into your Gmail account for purposed of email archival and encryption requires enabled ‘less secure’ access. This is accomplished by following the steps outlined here:

From: https://support.google.com/accounts/answer/6010255

Quick troubleshooting steps: