Cannot clone http.req/http.res properties
Temporary fixes #97
Make Imap node always read once on start
Closes Issue #96

Imap node now logs (in console) if it finds duplicate email on read or not.
It doesn't send on duplicates. It also now DOES fire once on startup AND re-deploy to populate anything downstream... at least that is the excuse for the change.

Signed-off-by: Dave C-J <dave@conway-jones.co.uk>
Always clone messages to ensure no cross-pollution
Part of #85

A function that returns the same message to multiple outputs, where each output is wired to at most one node was not having its messages cloned due to the change I made in #85 to be slightly more efficient. By returning the same message to each output, cross pollution was possible.
Merge branch 'master' of github.com:node-red/node-red
Fix milliseconds in delay
Merge remote-tracking branch 'upstream/master'
Merge pull request #101 from hardillb/master

Fix typo in the delay node
Switch node null/not null tests don't always work

    a === null / a !=== null

is different to

    typeof a == "undefined" / typeof a != "undefined"
Non-Cloning of req/res properties caused them to be lost

The previous fix to not clone the req/res objects introduced a bug where the req/res objects were lost from all but the first clone made out of a particular node.