When you send emails to users of your site through using the PHP mail() function, they will sometimes turn up in the mailbox of customers of your site with the following from address:

From: Root <root@apache.ecommercecompany.com>

This makes absolutely no sense to your customers, and often they will think it is spam and delete it. Often, the decision will be made for them by their web mail host, such as hotmail.com or googlemail.com, and they will never even see the email. You don’t want this to happen.

Writing email templates that appear “trustworthy” and have a low chance of being mislabled as spam by the webmail companies, is quite a difficult task, and there’s quite a bit to know about it. However it is quite easy to change the default “From:” email address that PHP sends your emails on as, and that will definitely help.

Assuming you’re running a linux server using sendmail, all you have to do is this.

First create an email address that you would want the customers to see, through editing the /etc/aliases files and running the command newaliases. I created an email address called customer-emails@ecommercecompany.com.

Then change the following sendmail_path line in your php.ini file to something like this:

/etc/php.ini
...
sendmail_path = /usr/sbin/sendmail -t -i -F 'customer-emails' -f 'Customer Emails <customer-emails@ecommercecompany.com>'
...


Broken down, those extra options are:
-F 'customer-emails' # the from email address, which has to be valid
-f 'Customer Emails <customer-emails@ecommercecompany.com>' # the email From header, which should have the name matching the email address, and it should be the same email address as above


Then restart apache, and it should load the php.ini file changes. Test it by sending a couple of emails to your email address, and you should see emails sent out like this:

From: Customer Emails <customer-emails@ecommercecompany.com>

/usr/sbin/unix2win
#!/bin/bash
# Converts a unix text file to a windows text file.
# usage: unix2win <text file to convert>
# requirements: sed version 4.2 or later, check with sed --version
sed -i -e 's/$/\r/' $1


/usr/sbin/win2unix
#!/bin/bash
# Converts a windows text file to a unix text file.
# usage: win2unix <text file to convert>
cat $1 | tr -d '\015' | tee $1 >/dev/null


I use these scripts with the combination of find and xargs to convert lots of log files into windows format with the following command. However this type of command can be dangerous, so don’t use it if you don’t know what you’re doing:

find sync-logs/ -name '*.log' -type f | xargs -n1 unix2win


I thought someone may well find a use for it – I’ve used the class in several different web scraping applications, and I found it handy. From the readme:

This is a class I wrote back in 2008 to help me pull down and parse HTML pages I updated it on
14/01/10 to print the results in a nicer way to the commandline.

- David Craddock (contact@davidcraddock.net)

/// WHAT IT DOES

It uses CURL to pull down a page from a URL, and sorts it into a 'Page' object
which has different attributes for the different HTML properties of the page
structure. By default it will also print the page object's properties neatly
onto the commandline as part of its unit test.

/// FILES

* README.txt - this file
* page.php - The PHP Class
* LIB_http.php - a lightweight external library that I used. It is just a very light wrapper around CURL's HTTP functions.
* expected-result.txt - output of the unit tests on my development machine
* curl-cookie-jar.txt - this file will be created when you run the page.php's unit test

/// SETUP

You will need CURL installed, PHP's DOMXPATH functions available, and the PHP
command line interface. It was tested on PHP5 on OSX.

/// RUNNING

Use the php commandline executable to run the page.php unit tests. IE:
$ php page.php

You should see a bunch of information being printed out, you can use:
$ php page.php > result.txt

That will output the info to result.txt so you can read it at will.

Here’s an example of one of the unit tests, which fetches this frontpage and parses it:

**++++
*** Page Print of http://www.davidcraddock.net ***
**++++

** Transfer Status
+ URL Retrieved:

http://www.davidcraddock.net

+ CURL Fetch Status:
Array
(
    [url] => http://www.davidcraddock.net
    [content_type] => text/html; charset=UTF-8
    [http_code] => 200
    [header_size] => 237
    [request_size] => 175
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 1.490972
    [namelookup_time] => 5.3E-5
    [connect_time] => 0.175803
    [pretransfer_time] => 0.175812
    [size_upload] => 0
    [size_download] => 30416
    [speed_download] => 20400
    [speed_upload] => 0
    [download_content_length] => 30416
    [upload_content_length] => 0
    [starttransfer_time] => 0.714943
    [redirect_time] => 0
)

** Header
+ Title: Random Eye Movement
+ Meta Desc:
Not Set
+ Meta Keywords:
Not Set
+ Meta Robots:
Not Set
** Flags
+ Has Frames?:
FALSE
+ Has body content been parsed?:
TRUE

** Non Html Tags
+ Tags scanned for:
Tag Type: script tags processed: 4
Tag Type: embed tags processed: 1
Tag Type: style tags processed: 0

+ Tag contents:
Array
(
    [ script ] => Array
        (
            [0] => Array
                (
                    [src] => http://www.davidcraddock.net/wp-content/themes/this-just-in/js/ThemeJS.js
                    [type] =>
                    [isinline] =>
                    [content] =>
                )

            [1] => Array
                (
                    [src] => http://www.davidcraddock.net/wp-content/plugins/lifestream/lifestream.js
                    [type] => text/javascript
                    [isinline] =>
                    [content] =>
                )

            [2] => Array
                (
                    [src] =>
                    [type] =>
                    [isinline] => 1
                    [content] =>
                 var odesk_widgets_width = 340;
                var odesk_widgets_height = 230;

                )

            [3] => Array
                (
                    [src] => http://www.odesk.com/widgets/v1/providers/large/~~8f250a5e32c8d3fa.js
                    [type] =>
                    [isinline] =>
                    [content] =>
                )

            [count] => 4
        )

    [ embed ] => Array
        (
            [0] => Array
                (
                    [src] => http://www.youtube-nocookie.com/v/Fpm0m6bVfrM&hl=en&fs=1&rel=0
                    [type] => application/x-shockwave-flash
                    [isinline] =>
                    [content] =>
                )

            [count] => 1
        )

    [ style ] => Array
        (
            [count] => 0
        )

)

**----
*** Page Print of http://www.davidcraddock.net Finished ***
**----

If you want to download a copy, the file is below. If you find it useful for you, a pingback would be appreciated.

As a break from my contract work, I took the W3Schools PHP Certification. I didn’t do any revision, which probably wasn’t wise. It was a bit more difficult than I thought, but I passed still.

Linux

Linux is easy because that’s what most people who use VIM run, and so it is very well tested.

~/.vimrc – Configuration file for command line vim.
~/.gvimrc – Configuration file for gui vim.

OSX

OSX is simple also, as it’s based on unix:

~/.vimrc – Configuration file for command line vim.
~/.gvimrc – Configuration file for gui vim.

Windows

Windows is not easy at all.. it doesn’t have a unix file structure, and doesn’t have support for the unix hidden file names, that start with a ‘.’, ie: ‘.vimrc’, ‘.bashrc’, and so on. Most open-source programs like VIM that require these hidden configuration files, and have been ported over to windows, seem to adopt this naming convention: ‘_vimrc’, ‘_bashrc’.. and so forth. So:

_vimrc – Configuration file for command line vim.
_gvimrc – Configuration file for gui vim.

Renaming configuration files from “.” to “_” wouldn’t make much difference on its own. You’d have to rename your files, but.. big deal. It’s not much of a problem.

Another, more tricky, problem you may encounter however, is that there’s no clear home directory on windows systems. Each major incarnation of windows seems to have a slightly different way of dealing with user’s files.. from 2000 to XP, a change, from XP to Vista, there is a change. I haven’t tried VIM on W7 yet, but it seems similar to Vista in structure, so this information may actually be consistent to W7.

The Vista 64 version of VIM I have, looks in another place for configuration files. For a global configuration file, it looks in “C:\Program Files”. Yes.. “C:\Program Files”. According to Vista 64’s version of VIM.. that’s the exact directory where I installed VIM. This is clearly not right. What’s happening is that the file system on windows is different to the unix-type file systems, and the VIM port is having problems adapting. The real VIM install directory is C:\Program Files\vim72. Because VIM is looking for a global configuration file in “C:\Program Files\_vimrc”, it’ll never find it.

Now you could override this with a batch file that sets the right environmental variables on startup, or you could change the environmental variables exported in windows, but I prefer to have a user-specified configuration file in my personal files directory, as it’s easier to backup and manage. If you wanted to specify the environmental variables yourself, which I’m guessing many will, the two environmental variables to override are:

$VIM = the VIM install directory, not always set properly, as I mentioned.
$HOME = the logged in user’s documents and settings directory, in windows speak this is also where the ‘user profile’ is stored, which is a collection of settings and configurations for the user. The exact directory will depend on which version of Windows you’re running, and if you override the HOME folder, you may have problems with other programs that rely on it being static.

On my Windows Vista 64 install:

$VIM = “C:\Program Files”
$HOME = “C:\Users\Dave”

You can see what files VIM includes by running the handy command

vim -V

at a command prompt; it will go through the different settings and output something similar to this:

Searching for "C:\Users\Dave/vimfiles\filetype.vim"
Searching for "C:\Program Files/vimfiles\filetype.vim"
Searching for "C:\Program Files\vim72\filetype.vim"
line 49: sourcing "C:\Program Files\vim72\filetype.vim"
finished sourcing C:\Program Files\vim72\filetype.vim
continuing in C:\Users\Dave\_vimrc
Searching for "C:\Program Files/vimfiles/after\filetype.vim"
Searching for "C:\Users\Dave/vimfiles/after\filetype.vim"
Searching for "ftplugin.vim" in "C:\Users\Dave/vimfiles,C:\Program Files/vimfiles,C:\Program Files\vim72,C:\Program Files/vimfiles/after,C:\Users\Dave/vimfiles/after"
Searching for "C:\Users\Dave/vimfiles\ftplugin.vim"
Searching for "C:\Program Files/vimfiles\ftplugin.vim"
Searching for "C:\Program Files\vim72\ftplugin.vim"
line 49: sourcing "C:\Program Files\vim72\ftplugin.vim"
finished sourcing C:\Program Files\vim72\ftplugin.vim
continuing in C:\Users\Dave\_vimrc
Searching for "C:\Program Files/vimfiles/after\ftplugin.vim"
Searching for "C:\Users\Dave/vimfiles/after\ftplugin.vim"
finished sourcing $HOME\_vimrc
Searching for "plugin/**/*.vim" in "C:\Users\Dave/vimfiles,C:\Program Files/vimfiles,C:\Program Files\vim72,C:\Program Files/vimfiles/after,C:\Users\Dave/vimfiles/after"
Searching for "C:\Users\Dave/vimfiles\plugin/**/*.vim"
Searching for "C:\Program Files/vimfiles\plugin/**/*.vim"
Searching for "C:\Program Files\vim72\plugin/**/*.vim"
sourcing "C:\Program Files\vim72\plugin\getscriptPlugin.vim"
finished sourcing C:\Program Files\vim72\plugin\getscriptPlugin.vim
sourcing "C:\Program Files\vim72\plugin\gzip.vim"
finished sourcing C:\Program Files\vim72\plugin\gzip.vim
sourcing "C:\Program Files\vim72\plugin\matchparen.vim"
finished sourcing C:\Program Files\vim72\plugin\matchparen.vim
sourcing "C:\Program Files\vim72\plugin\netrwPlugin.vim"
finished sourcing C:\Program Files\vim72\plugin\netrwPlugin.vim
sourcing "C:\Program Files\vim72\plugin\rrhelper.vim"
finished sourcing C:\Program Files\vim72\plugin\rrhelper.vim
sourcing "C:\Program Files\vim72\plugin\spellfile.vim"
finished sourcing C:\Program Files\vim72\plugin\spellfile.vim
sourcing "C:\Program Files\vim72\plugin\tarPlugin.vim"
finished sourcing C:\Program Files\vim72\plugin\tarPlugin.vim
sourcing "C:\Program Files\vim72\plugin\tohtml.vim"
finished sourcing C:\Program Files\vim72\plugin\tohtml.vim
sourcing "C:\Program Files\vim72\plugin\vimballPlugin.vim"
finished sourcing C:\Program Files\vim72\plugin\vimballPlugin.vim
sourcing "C:\Program Files\vim72\plugin\zipPlugin.vim"
finished sourcing C:\Program Files\vim72\plugin\zipPlugin.vim
Searching for "C:\Program Files/vimfiles/after\plugin/**/*.vim"
Searching for "C:\Users\Dave/vimfiles/after\plugin/**/*.vim"
Reading viminfo file "C:\Users\Dave\_viminfo" info
Press ENTER or type command to continue

Notice how it does pull in all the syntax highlighting macros and other extension files correctly, which are specified in the .vim files above.. but it doesn’t pull in the global configuration files that I’ve copied also to C:\Program Files\vim72\_gvimrc and C:\Program Files\vim72\_vimrc. However, it does pickup the files I copied to C:\Users\Dave.. both the C:\Users\Dave\_vimrc and C:\Users\Dave\_gvimrc are picked up, although VIM will normally read ‘_gvimrc’ when the gui version of VIM is run (called gvim).

To see exactly what those environmental variables are being set to, when you’re inside the editor, issue these two commands, and their values will be show in the editor:

:echo $HOME
:echo $VIM

It seems to make sense for me – and perhaps you, if you’re working with VIM on windows – to place my _vimrc and _gvimrc files configuration files in $HOME in Vista. They are then picked up without having to worry about explicitly defining any environmental variables, creating a batch file, or any other hassle.

You can do this easily by the following two commands:

:ed $HOME\_vimrc
:sp $HOME\_gvimrc

That will open the two new configuration files, side by side, and you can paste in your existing configuration that you’ve used in Linux, and windows will pick them up the next time you start VIM.

It is a huge community, and I highly recommend the site to those who wish to work from home. You will become part of the global IT workforce, so you may have to lower your rates, but if you’re good at what you do, then you can easily earn a modest living from anywhere. Someone I know is working via oDesk while traveling around Asia, for example.

Risky? Just a bit. A few years later he lost his life during a similar attempt. But no-one can doubt the guts required, and the level of skill he achieved, in this type of climbing.

Here is a simple method for using regex in the powerful text editor VIM that will work well for common use.

Method

We are going to take the “search and delete a word” problem for an example. We want to delete all instances of the singular noun “needle” in a text file. Let’s assume there are no instances of the pluralisation “needles” in our document.

1. Debug on.. turn some VIM options on
   :set hlsearch
:set wrapscan
– this will make all regex expressions possible to debug by visually showing what they match in your document (first line) and make all searches wrap around instead of just search forward from your current position, which is the default. (second line)
2. Develop and Test.. your regex attempts by using a simple search. Here we see three attempts at solving the problem: :/needl
:/needle
:/\<needle\> – our third try is correct, and highlights all words that spell “needle”. The \< and \> markers allow you to specify the beginning and the end of a word. Play with different regexs using the simple search and watching what is highlighted, until you discover one that works for you.

3. Run… your regex:%s/\<needle\>//g – once you’ve figured out a regex, run the regex on your document. This example will execute a search for the word “needle” and delete every one. If you wanted to substitute needle for another word, you would put the word in between the // marks. As we can see, there is nothing between the marks in this example, so it will replace instances of “needle” with nothing. This means it will serve to delete every instance of the word “needle”.
4. Check things are OK… with your document :/\<needle\>
:/needle
:/needl – has the regex done what you want? Use the search function to see if regex has done what you wanted it to do. The above examples show different searches through the document to see if different variations remain. Any matches of these searches will highlight any problems. You can use the lower-case N(next search result) and lower-case P(previous search result) commands to navigate through any found search results. You must remember to manually look through the document and see what the regex has changed, make sure there aren’t any unwanted surprises!
5. Recover… from any mistakes u – just press the U key (with no capslock or shift). This will undo the very last last change made to the document.
6. Redo… any work that you need to <ctrl>-r – use the redo fuction; press the CONTROL and R keys together (with no capslock or shift). This will redo the last change made to the document.
7. Finish up and Write… to file :w – write your work on the document to file. Even after you have written out to file, you can probably still use the undo function to get back to where you were, but it’s best practice to not rely on this, and only write once you’re done.
8. Debug off.. turn some options off
   :set nohlsearch
:set nowrapscan
– turn off the regular expression highlighting (line 1). turn off the wraparound searching (line 2). You can leave either or both options on if you want, they’re often useful. Up to you.

Use a combination of these wonderful commands to test and improve your regex development skills in VIM.

Examples

Here I use the shorthand “#…” to denote comments on what I’m doing… if you want to copy and paste the example as written, then you will have to remove those comments.

1. Remove ancient uppercase <BLINK> tags from a document.

:set wrapscan # debug on
:set hlsearch # debug on
:/<BLINK> # try 1.. bingo! first time.. selected all tags I want
:%s/<BLINK>//g # lets execute my regex remove
:/BLINK # check 1.. testing things are OK in my file by searching through..
:/blinked # check 2.. yep thats ok..
:/<BLINK\> # check 3.. yep looks ok... the problem tags are gone
# ...manual scroll through the document.. looks good!
:w # write out to file
:set nohlsearch # debug off
:set nowrapscan # debug off

2. Oh no! We missed some lower and mixedcase <bLiNK> tags that some sneaky person slipped in. Let’s take them out.

:set wrapscan # debug on
:set hlsearch # debug on
:/<blink> # try 1.. hm.. worked for many, but didnt match BlInK or blINK mixedcase
:/<blink>/i # try 2.. much better.. seems to have worked!
:%s/<blink>//i # lets execute my regex remove
:/BLINK # check 1.. testing things are OK in my file by searching through..
:/blinked # check 2.. yep thats ok..
:/<blink> # check 3.. yep thats fine.
:/<blink>/i # check 4.. looks good... problem solved
# ...manual scroll through the document.. looks much better!
:w # write out to file
:set nohlsearch # debug off
:set nowrapscan # debug off

3. Replacing uppercase or mixedcase <BR> tags with the more modern <br>.

:set wrapscan # debug on
:set hlsearch # debug on
:/<BR> # try 1.. hmm.. just uppercase.. not gonna work..
:/<br> # try 2.. hmm.. just lowercase..
:/<BR>/i # try 3.. ahh.. that'll be it then
:%s/<BR>/<br>/gi # lets execute my regex substitution
:/BR # check 1.. testing things are OK in my file by searching through..
:/br # check 2.. yep thats ok..
/bR # check 3 ..yup..
:/<BR>/i # check 4.. yep looks ok... the problem tags seem to be gone
# ...manual scroll through the document.. looks good!
:w # write out to file
:set nohlsearch # debug off
:set nowrapscan # debug off

For More..

Regexs are the gift that just keeps on giving. Here are some good resources on regexs in general, and regexs in VIM.

• A great modern way to learn regexs.. try them online! interactive flash awesomeness.
• A neat graphical VI/VIM cheat-sheet.
• An advanced VIM/regex tutorial..
• More VIM/regex ninja skills.
• Stackoverflow is a good place to find practical ways to solve regex problems with VIM.
• Probably the most definitive regex site on the ‘net

Volunteers on the OLPC project have developed a low-cost heart rate monitor that can be plugged into the XO laptop, making steps towards an affordable monitoring system for hospitals in developing countries.

For more information on the development, see the: OLPC Goldenstate project. People in the US can currently buy the sensor here; unfortunately there is no international shipping yet in place.