My blues cover playlist is here. It also includes the Robert Johnson songs I did a few years ago.  

 My Robert Johnson Challenge is here. I did all 29 Robert Johnson songs, one per week. 

 My Substack is here. It includes the above material with the articles around them, and some other additional music related articles.  

 The Reverbnation link for Alpha Dog Blues Band is here.  

We had high hopes for this oven. The $3100 price tag was hard to swallow, but if it worked and lasted it would be worth it. Unfortunately, the oven door crapped out after a couple of years and had to be manually pushed shut every time you used it. The estimate for a new door was about $1500! They couldn't replace just the spring or the hinge....stupid design. So we decided to wait.

A year went by and the entire oven crapped out and stopped working -- no lights or anything. We bought a countertop microwave to use in the meantime, knowing there was going to be a huge price tag. I called a company to service it a few weeks ago, and they were able to replace a couple of boards inside to allow it to work again, but they also said it might not last because the door is still not fixed--it CAN'T be fixed because GE no longer supplies that door. So we basically have a $4000 (after repairs) piece of junk. We also installed other GE appliances, but I'm now waiting for those to die too. If they do die, I'll bet the parts are not available anymore. The quality control is horrible and the service non-existent. I would never buy a GE appliance again, which is sad because we thought they were a good company. We purchased in Nov. 2017 and installed in April 2018, so the oven is only 6 years old, and the last two years it has been unusable. I would think for $3100 it would last a lifetime, or at least as long as we would be in this house.

Bottom line: avoid GE like the plague.

Update: This is the schedule I intend to follow: 

Update: A few things that I want to clear up about Robert Johnson's playing. 1) The recordings are the correct speed. There are a bunch of "slowed down" versions out there, where people insist that they sound better and that they are more accurate. This is utter hogwash. "Sounding better" is pure opinion. Debunked here. 2) Johnson used his own "special" tunings. Several people have come up with various tunings (including an Aadd9 tuning) because they think that the songs are too hard to play if you tune to the regular "standard", "Spanish", or "Vestapol" tunings that Robert (and all blues singers) use. Also utter hogwash. All you have to do is look at the picture of Robert with his long fingers to know that he can reach all those 7ths and other notes that apparently some folks can't play easily. If someone wants to use their own tuning, that's one thing, but don't assert that Robert used the tuning without proof. Interesting to note that some of the people pushing the speed hoax also pushed the mysterious "third picture" hoax and push the tuning hoax.

Update: cross-posted at Substack.

Update 8/18/22: Currently up to 7 songs. Full list is on Youtube

Most things seem to be working finally. Thanks to Tom Huerlimann for the great article on configuring ColdFusion 9 with Windows server 2016/IIS 10.

To further complicate matters, Don Law, who supervised the sessions, stated that Johnson used a borrowed guitar for the San Antonio sessions (1936) at the Gunter Hotel. Johnson arrived on Sunday to record, but was arrested that night and had to be bailed out of jail. Apparently, during the arrest the guitar was not available any more (broken, confiscated, or lost), and when recording was started on Monday, November 23, the studio obtained a guitar for Johnson to use. It could be anything. Stephen LeVere, who oversaw the mastering of the Complete Recordings, postulates that the San Antonio sessions sound like a flattop whereas the Dallas sessions sound like an archtop. Johnson probably used his own guitar for the Dallas sessions. It is known that Johnson liked the Kalamazoo archtop guitars, so this is plausible, and it does sound like an archtop to my ears as well. Johnny Shines stated that Johnson liked Kalamazoo and Stella guitars, and also mentioned that both he and Johnson had Kalamazoos with f-holes (archtop) and liked archtops, so the theory holds water (Johnny Shines interview).

Johnson had some of the best acoustic guitar sounds on record, for my money, in addition to being one of the greatest players of acoustic blues, but there are 3 distinct guitar sounds among the various recordings. The only thing this proves is that Johnson's sound came from his fingers, and the guitar he used is not important. This page lists his songs, recording dates, and master numbers, among other things and is a work in progress: Robert Johnson songs. Johnson recorded 59 takes of 29 songs, of which 42 takes still remain. Maybe someday others will be found, but it's likely many of the masters were destroyed during the war for the metal. Update: Among the 17 missing songs are 2nd takes of Terraplane Blues, Walkin Blues, Preachin' blues, and Hellhound on my Trail, and a third take of Milkcow's Calf Blues.

One thing I will say about the guitar sound, I think the Gibson L1 shape and size is perfect for blues. Every guitar I've played in this configuration, including my own Martin CEO7 and my Kalamazoo KG14, sound amazing. The best sounding guitars I've heard have been old 1920's and 1930's Gibson L1 guitars. Whether or not he used something like this is open to speculation.

Update:The other question is, what sounds more like a Robert Johnson recording today, an 80 year old guitar with 80 year old wood (which was brand-spanking new when Robert Johnson recorded) or a brand new guitar built in a similar style to the old 30's guitars?

Update: Here is "Kind Hearted Woman Blues" from the San Antonio sessions: Kind Hearted Woman Blues. "Me and the Devil Blues", recorded in Dallas, uses the same tune, but you can here the difference in guitar tone. It has a more "ringing" tone, and the bass is more percussive sounding: Me and the Devil Blues. Below is my Kalamazoo KG31, which may or may not be the type used by Robert on the Dallas sessions (or was it a KG21?):. The KG 31 is bigger, with a 16" lower bout, whereas the KG21 has a 14 3/4" lower bout, similar to a Gibson L1.

Update 6/20/2019: Changed the information about Johnson's San Antonio sessions based on information in the new Johnson biography by Bruce Conforth and Gayle Dean Warlow. Johnson recorded all of the sessions with a borrowed studio guitar.

Update 11/21/2020: Finally obtained a Kalamazoo KG-21 archtop , which is likely the type of guitar that Johnson used on the Dallas recordings. He and Johnny Shines carried Kalamazoo archtops (either a KG-31 or KG-21) with them until around December 1937 when they were lost in a fire. After that, Johnson likely obtained his Kalamazoo KG-14 that is seen in the famous cigarette photo in Steele, Missouri.

Update 8/17/2021: Annye Anderson's book about her step-brother Robert is a must-read: Brother Robert. The cover is the most recently discovered picture of Robert with his Kalamazoo KG-14 guitar. In this more recent interview with Annye Anderson, interview, she describes obtaining Robert's guitar. Apparently Robert's sister Carrie sent her son Louis to Greenwood to obtain it, and it was transported to Anapolis and then Churchton, MD. It was subsequently lost.

Update: This was an old post, but it's still at the top so I've reinstated the code for this year as well. Take 40% any purchase on the site.

Update: After posting this, the delivery scheduled for today from the USPS shows as "delivered" on the tracking page, but it's not here. Who has it??? USPS is the worst of the lot.

With a good tube amp, you can set the amp for a good crunchy tone when pushed hard, then just back off the volume control on the guitar to play clean tones.  For blues players who don't have the amp overdriven as much as rock players, the overdriven sound is much more subtle. A good tube amp is like an extension of the guitar--it's like playing another instrument at the same time and trying to get the best music out of both. 

Every tube amp I've played has a "sweet spot" where it sounds best. Some amps have a great sound in several places. An old Marshall head was always best with everything on 10. For smaller venues when you can't reach the sweet spot, a pedal can boost the signal going into the amp to give it a slightly overdriven sound even though the volume is low. It's not quite the same as cranking the amp, though, but sometimes you don't have a choice.

Different output tubes (aka amplifier tubes, power amp tubes) have different tonal characteristics. The 6V6 tubes were used in Fender amps in the 60's and have a clean tone until pushed hard, then have a nice breakup. Depending on the amp and the circuit used, they can sound "mushy" when pushed too hard, like in an old Princeton, but I've recently heard a Swart Spacetone that sounds pretty darned good even when pushed to 10. One 6V6 puts out roughly 5 watts or so, and some amps have two in a push-pull circuit putting out about 10-14 watts. Fender Deluxe "blackface" had 2, and is one of the Holy Grail amps for guitar players.

A 6L6 is like a big brother to the 6V6, and puts out about double the output. Some amps that use the 6L6 are the old Fender Bassman, and newer EVH amps.  Loud American amps mostly had 6L6 tubes in the old days.

EL84 tubes have a more glassy sound (some say it sounds like an ice pick) but produces a more definite mid-range "crunch" when pushed hard. It puts out about 6-7 watts, but a push-pull pair can put out 14-20 watts or more, depending on the circuit. The Fender Blues Junior uses EL84 tubes.

EL34 tubes are the EL84's bigger brother, and used in Marshall amps and clones. They have that great rock "crunch" when pushed hard, and glassy clean tones when the volume is backed off. Marshall amps were essentially clones of the Fender Bassman, only using EL34 tubes instead of 6L6 tubes, and utilizing closed back cabinets.

One tube you don't see very often is a 6973, used in some old Supro and Gretsch amps. I think this tube might have the best sound of all, but I don't own one of these amps. Yet. It sounds somewhat like a cross between the 6V6 and EL34, getting a pretty nice clean sound, but a moderate overdrive when cranked to 10, not as crunchy as an EL34, but not as mushy as a 6V6.

These days I have different tube amps for different venues. 

For small gigs I bring my VHT Special 6; hand-wired point-to-point like the old days, but made in China. It might be the most well-made mass-produced amp out there without going to a boutique amp builder. The VHT takes a 6V6, but it can be swapped out for a 6L6, EL34, or with an adapter, an EL84. I keep an EL34 in mine, and it sounds great. It's a simple amp with no reverb or effects of any kind. 

For slightly larger gigs I use a Bugera V22, which I picked up ridiculously cheap. It has a great natural sound, somewhere between and old Vox and a blackface Fender. It uses EL84 tubes, but sounds much less ice-picky than other EL84 amps I've played through, and more like an old-school amp.

Next is my Sligo Surfman, built by a local guy Steve Clark. It uses 6L6 tubes and puts out about 40 watts, but has a master volume for getting some breakup at lower volumes. 

For larger blues gigs I usually bring out my Sonny Jr. "Super Sonny", which is essentially a hand-wired clone of an old tweed Fender Bassman, but modified for harmonica. It sounds great with guitar too, especially with a pedal boosting the signal slightly in front of it.

I also usually carry with me a backup amp, which is a hand-build Bogen clone. Bogen built PA amplifiers in the 50s and 60s. This one has 2 6V6 tubes and sounds pretty great with guitar, even though it's not a guitar amp. 

I also have a small practice amp, which is a Magnasync Moviola amp, taken from an old 50's/60's film editing machine, utilizing a 6AQ5 output tube. The power of the amp is not enough for a gig with other musicians, but it sounds pretty nice for recording or as a bedroom practice amp.

 I also recently obtained a Bugera 6262, essentially a 100 watt clone of a British style (Marshall) amp that is low budget but sounds great. I will use this for rock gigs. 

The quest for the best guitar tone continues every day. Even though I have enough amps for a lifetime, I'm always looking for the ultimate guitar sound.

Update: Hard drive restored, back to normal.

USE [master]
GO

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

CREATE PROCEDURE [dbo].[sp_TruncateLogs] 
       @databaseName nvarchar(1024)
AS
BEGIN
 SET NOCOUNT ON;

 DECLARE @sql NVARCHAR(1000)
 DECLARE @logfilename NVARCHAR(1000)

 SELECT @logfilename = b.name
 FROM sys.sysdatabases a 
  INNER JOIN sys.sysaltfiles b
   ON a.dbid = b.dbid
 WHERE fileid = 2
  AND a.name = @databaseName

 IF @@rowcount = 1 BEGIN
 
  SET @sql = '
  USE ' + @databaseName + '
  BACKUP LOG ' + @databaseName + '
  with truncate_only
  dbcc shrinkfile (' + @logfilename + ', 1)'

  EXECUTE sp_executesql @sql
 END

END

Next, just add it to the loop in the original ColdFusion scheduled task script:

<cfstoredproc datasource="master" procedure="dbo.sp_TruncateLogs">
      <cfprocparam cfsqltype="cf_sql_varchar" value="#ListGetAt(variables.databases, variables.i)#" />
</cfstoredproc>

My work environment is a lot different from the typical development workflow that I am accustomed to, so I wanted to set up an Ant build script for my local use on my laptop, and a remote FTP development server. ColdFusion Builder has most of what is needed, with the exception of a couple of Java classes for the FTP functionality (commons-net-*.jar and jakarta-oro-*.jar). Download these and add to the ColdFusion Builder (or Eclipse) plugins /lib folder for Ant, located here typically: C:\Program Files\Adobe\Adobe ColdFusion Builder\plugins\org.apache.ant_1.7.1.v20090120-1145\lib

I haven't found a lot of useful information for the ColdFusion developer on setting up Ant build scripts, so hopefully this will help someone. Basically, a build script is XML that contains a project tag and one or more target tags under it. You can also set up a property file that contains details about your project. This makes it easier to set up a generic build script that can be reused. Simply change the properties in the property file.

I'm going to assume that the project will have all the files to be deployed at the root of the project. This is not always the case, and indeed not usually the case, but changing paths is easy enough in the script. I'll add a build folder to the root of the project, and add the build.properties and build.xml files to this directory.

My build.properties file looks like this:

#deploy to LOCAL server
deploy.dir.local=c:/inetpub/wwwroot/mysite

#deploy to DEV server
deploy.dev.ftp.host=myftpsite.com
deploy.dev.ftp.username=myusername
deploy.dev.ftp.password=mypassword
deploy.dev.ftp.basedir=/

#deploy to LIVE server
deploy.live.ftp.host=myliveftpsite.com
deploy.live.ftp.username=myusername
deploy.live.ftp.password=mypassword
deploy.live.ftp.basedir=/

It contains information on the local directory where I do local testing, the FTP site where the development server resides, and the live server where the final deployment will happen. My build.xml file looks like this:

<project name="My Project" basedir="../." default="deploy.local">
 <!-- Load properties -->
 <property file="build/build.properties"/>

 <target name="deploy.local" description="Deploy to local webserver">  
  <echo>Copying files to local webserver...</echo>
  <mkdir dir="${deploy.dir.local}"/>
  <copy todir="${deploy.dir.local}">
   <fileset dir=".">
    <include name="**/*" />
    <exclude name="build/*" />
   </fileset>
  </copy>  
 </target>
 
 <target name="deploy.dev" description="Release to remote dev webserver">  
  <echo>Copying files to dev FTP server ${deploy.dev.ftp.host}...</echo>
  <ftp server="${deploy.dev.ftp.host}"
   remotedir="${deploy.dev.ftp.basedir}"
   userid="${deploy.dev.ftp.username}"
   password="${deploy.dev.ftp.password}"
   depends="yes">
   <fileset dir=".">     
    <include name="**/*" />
    <exclude name="build/*" />      
   </fileset>
  </ftp>   
 </target>
 
 <target name="deploy.live" description="Release to remote webserver">  
  <echo>Copying files to live FTP server ${deploy.live.ftp.host}...</echo>
  <ftp server="${deploy.live.ftp.host}"
   remotedir="${deploy.live.ftp.basedir}"
   userid="${deploy.live.ftp.username}"
   password="${deploy.live.ftp.password}"
   depends="yes">
   <fileset dir=".">     
    <include name="**/*" />
    <exclude name="build/*" />      
   </fileset>
  </ftp>   
 </target> 
</project>

A couple of explanations: the fileset tag includes the directory outside of the build directory (project root in this case), and the exclude tag excludes the build directory from the build process. You don't want these in your deployment directories. The depends attribute in the FTP tag allow you to exclude unchanged files from the FTP process, otherwise the build will FTP the entire project each time.

With these files in place, you can right-click on the build.xml file in the project and click Run As > Ant Build.... This brings up the Run dialog (clicking the option without the elipsis runs the build using the last known configuration).

Here, you can simply check the deployment options you want to use. If you are doing only local testing, check only the deploy.local box. If you want only the dev server, check that box. You can also check any combination. Next time, you can click Run As > Ant Build without the elipsis and it will just run using the last configuration. For example, if doing only local testing, check that box, so every time you hit the Run button, only local files will be deployed. The process is fast. Only changed files are deployed.

Run button

When you run the build, the Console window will show the results of building

Buildfile: C:\Documents and Settings\tmuck\Adobe ColdFusion Builder workspace\myproject\build\build.xml
deploy.local:
     [echo] Copying files to local webserver...
[copy] Copying 1 file to c:\inetpub\wwwroot\myproject
BUILD SUCCESSFUL
Total time: 407 milliseconds

I hope that helps someone.

I was also thinking about a SQL Server upgrade. I'm running the Express version, which is perfect for most small-medium web sites. One thing it doesn't have is a way to do maintenance. I've been doing manual backups. Well, after looking at the price of a SQL Server license, I decided to look for a good automated backup. I found a backup script online at http://www.mssqltips.com/tip.asp?tip=1174 and modified it to meet my needs (made directory name a parameter)

CREATE PROCEDURE [dbo].[sp_BackupDatabase]
@databaseName nvarchar(1024),
@type CHAR(1) = 'F',
@directory nvarchar(1024) = 'C:\SQLBackup'
AS
BEGIN
SET NOCOUNT ON;

DECLARE @sql NVARCHAR(1000)
DECLARE @currentDate NVARCHAR(20)

SELECT @currentDate = REPLACE(CONVERT(VARCHAR, GETDATE(),111),'/',') +
REPLACE(CONVERT(VARCHAR, GETDATE(),108),':',')

IF @type = 'F'
SET @sql = 'BACKUP DATABASE ' +
@databaseName +
' TO DISK = ' +
@directory + '\' +
@databaseName + '\' +
@databaseName + '_Full_' +
@currentDate + '.BAK'

IF @type = 'D'
SET @sql = 'BACKUP DATABASE ' +
@databaseName +
' TO DISK = ' +
@directory + '\' +
@databaseName + '\' +
@databaseName + '_Diff_' +
@currentDate + '.BAK' WITH DIFFERENTIAL'

IF @type = 'L'
SET @sql = 'BACKUP LOG ' +
@databaseName +
' TO DISK = ' +
@directory + '\' +
@databaseName + '\' +
@databaseName + '_Log_' +
@currentDate + '.TRN'

EXECUTE sp_executesql @sql
END

Next, I created my own stored procedure for deleting old database backups. Basically, in a "real" SQL Server, the backup task will delete backups back to a date you specify. We'll pass in the database name, type of backup, timeframe (in weeks), and the directory name.

CREATE PROCEDURE [dbo].[sp_RemoveOldBackups]
@databaseName sysname,
@backupType CHAR(1) = 'F',
@howlong integer = 4,
@directory nvarchar(1024) = 'C:\SQLBackup'
AS
BEGIN
SET NOCOUNT ON;
DECLARE @type nchar(3)
SET @type = 'BAK'
if @backupType = 'L' BEGIN SET @type = 'TRN' END
DECLARE @backupPath nvarchar(2048)
SET @backupPath = @directory + '\' + @databaseName
declare @DeleteDate nvarchar(50)
declare @DeleteDateTime datetime
set @DeleteDateTime = DateAdd(ww, -1 * @howlong, GetDate())
set @DeleteDate = (Select Replace(Convert(nvarchar, @DeleteDateTime, 111), '/', '-') + 'T' + Convert(nvarchar, @DeleteDateTime, 108))

EXECUTE master.dbo.xp_delete_file 0, @backupPath, @type, @DeleteDate,1

END

Now, rather than use Windows scheduled tasks for this, I wanted a simple ColdFusion scheduled task. The stored procedures should be stored in the master database, so you'll need a datasource that will allow execute permissions on these two stored procedures. Finally, save the following into a ColdFusion file and store it in one of your web sites. Set the scheduled task to execute once a week.

<cftry>
<!--- List of databases to backup --->
<cfset variables.databases = "mydatabase,Northwind,myOtherDatabase" />
<!--- Path to the backup folder --->
<cfset variables.backupPath = "Z:\SQLBackup" />
<!--- How many weeks to keep backups --->
<cfset variables.howLong = "4" />

<!--- Loop through the databases --->
<cfloop from="1" to="#ListLen(variables.databases)#" index="variables.i">
  <cftry>
    <!--- First, backup the database --->
    <cfstoredproc datasource="master" procedure="sp_BackupDatabase">
      <cfprocparam cfsqltype="cf_sql_varchar" value="#ListGetAt(variables.databases, variables.i)#" />
      <cfprocparam cfsqltype="cf_sql_char" value="F" />
      <cfprocparam cfsqltype="cf_sql_varchar" value="#variables.backupPath#" />
    </cfstoredproc>
    <!--- Next, delete the old databases --->
    <cfstoredproc datasource="master" procedure="sp_RemoveOldBackups">
      <cfprocparam cfsqltype="cf_sql_varchar" value="#ListGetAt(variables.databases, variables.i)#" />
      <cfprocparam cfsqltype="cf_sql_char" value="F" />
      <cfprocparam cfsqltype="cf_sql_integer" value="4" />
      <cfprocparam cfsqltype="cf_sql_varchar" value="#variables.backupPath#" />
    </cfstoredproc>
    <cfcatch>
      <cflog application="yes" text="Database backup failed #now()# for #ListGetAt(variables.databases, i)#" />
    </cfcatch>
  </cftry>
</cfloop>
<cfcatch>
   <cflog application="yes" text="Database backup failed #now()# outside loop" />
</cfcatch>
</cftry>

Obviously, this is the bare bones of a backup system. You can modify the scripts to perform differential backups to meet your needs, log file backups, and add some error handling to the stored procedures, but this is a good start.

For ColdFusion coding I have been using Eclipse at work for the past couple years, only because that is the standard that we have at the office and require it's Subversion support, but it's sadly lacking in many key areas. It doesn't have a design view, which is a pretty basic feature for a web development environment. Also, the most frustrating part is that the code hinting, code completion, and context-sensitive help is pretty poor, and often inaccurate. I don't know how many times I've hit a key and had some bizarre code completion happen that has no relation to what I'm typing. A good coding environment is two steps ahead of you and knows what you want to type next. Apple's Xcode IDE is brilliant in this regard, as is Microsoft's coding environments. Dreamweaver is finally starting to get there, after all these years. Not quite there yet, but it's much better than alternatives for ColdFusion programmers, in my view. For PHP coding, it's pretty great, too.

All of my available extensions seem to work without issue in Dreamweaver CS5. If anyone has any issues, please let me know.

Bigger news is that through these blues jams I've joined a couple of local bands -- The Alpha Dog Blues Band and the Southside Georgetown Bluesbreakers. Alpha Dog plays regularly at the Cowboy Cafe, JVs, and 219 Restaurant. The Bluesbreakers have played one gig at the DC Blues Society fish fry this past month.

Through the jams I've met a lot of great people and fine musicians. Some cool local DC bands to check out if you can are Idle Americans, Big Boy Little Band, Swampkeepers, Hot Rods and Old Gas, and the Andy Poxon Band.

Alpha Dog Blues Band is playing the following dates:

http://www.bloombit.com/Articles/2008/05/ASCII-Encoded-Binary-String-Automated-SQL-Injection.aspx

I put something like this in my application.cfm file to re-rout the attackers temporarily:

<cfif FindNoCase('user>0',cgi.query_string) OR findNoCase('declare',cgi.query_string)
OR findNoCase('EXEC(@',cgi.query_string)>
    <cflocation url="http://www.ftc.gov">
</cfif>

On the other hand, some things look like they were tacked on as an afterthought, and the overall interface is not as user-friendly as a basic Windows program should be that has been around for as many years as it has. The title bar is gone and the path to the current file has been stuck into a little spot that is reserved for page tabs. It sounds like a minor thing, but it's one of the most important parts of coding in a multi-tab editor. As soon as you open more than a few pages, the file path is cut off, and with a few more open, it disappears. Major step backwards here:

The other obvious usability problem here is the black text on dark grey in the tabs. On a laptop it's impossible to see, as is the white text on the dark grey. Also, the individual pages have a close button (X) which is a great bonus, but it would have been nice to have a close button on the frequently used panels (like Find/Replace) so you don't have to right click to pick a menu item to close a panel. Also, the entire border of the program is gone, making it blend into other open programs on your desktop. I understand this is the new "owl" interface, but owls should be left in the woods to live in trees. We really don't need the artsy fartsy stuff in a code editor.

But all in all, I would recommend the program. I use Eclipse all day long at my place of employment, and it is simply not as intuitive or easy to use as DW. Code view in DW has come a long way since the days of Ultradev. Download it and try it out, and by all means make suggestions in the forums on things that can be made better.

http://cgi6.ebay.com/aw-cgi/eBayISAPI.dll?RedirectEnter&partner=ShowItem&loc=http%3A%2F%2Fus.ebayobjects.com%2F2c%3B9739597%3B9123118%3Bz%3Fhttp%3A%2F%2Fcontactbay-ws-bayisapi.xm.com%2F

It's amazing that with all the phishing attempts out there, eBay is actually falling down on the job by allowing their own site to redirect unsuspecting users to the phishing web site.