Skip to main content

An interesting SPAM story.

Got this great email today:?

Greetings,

It is indeed my pleasure to write you this letter, which I believe will be a surprise to you as we have never met before, and
I am deeply sorry if I have in any manner disturbed your privacy. Please forgive this unusualmanner of contacting you, but this particular letter is of exceptional and very private nature. There is absolutely going to be a great doubt and distrust in your heart in respect of this email, coupled with the fact that, so many individuals have taken possession of the Internet to facilitate their nefarious deeds, thereby making it extremely difficult for genuine and legitimate business class persons to get attention and recognition. There is no way for me to know whether I will be properly understood, but it is my duty to write and reach out to you.

My name is Mrs.Vivian Salem, wife of late Salem Nasim in Iraq, some years ago, I lost my husband Nasim and three children Husam, 15 years old,Wasim, 12 years old and Merna, 6years old, this Happened when a Combatant Military Tank shelled our car as my family attempted to flee heavy fighting in Baghdad, View the Website below for detail

Story of how I lost my family .

Before my husband and my Children was killed, he Deposited the sum of $31.6 million ( Thirty one million six hundred thousand Dollars ) with a Security & Finance company in Asia. I had contacted a Diplomat who was attached to the United Nation Peace keeping forces in Asia and has assured me of assisting me to move the Boxes through Diplomatic Cargo,ONLY if I had a PARTNER to receive it on my behalf .

All I need from you is to receive the Fund as my husband business Associates and Invest the fund into any Lucrative Investment in your country.I will remunerate you with 30 % at the end,but most of all is that I solicit your trust in this
transaction and will not want you to betray me at the end Please in your reply to this my private email

(vivisalem@blumail.org), include your Mobile number ,Home telephone number and your residential or company address for easy Communication.

Thank you,
Mrs.Vivian Salem

An interesting twist on the old African millionaire ploy. In the words of MR T, I pity the fool!?

Comments

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second