Log a tip to recover from bad cookie

For some reason, it left an unclean cookie and could load that anymore.
The only way out seems to be to delete the cookie. We should probably
delete the b0rken cookie file ourselves but we tell the user to do so.
More logging for the actual remaining text web site

Some times it is not clear to me why it returns no remaining SMS. So I
want to be able to see the loaded page.
Bail out if recipient is unknown

So far, the recipient was evaluated after the message was given. That is
not how o2sms behaved and I find it very unpleasant to have to search
and retype the message if the alias is wrong, i.e. mistyped. So what we
do now is to raise an error and print the available aliases.

Conflicts:
	cliresms
README: Refer to correct config file name, ~/.cliresms.conf

~/.cliresms/config is not read.
Made error printing more visible

I found myself not having seen error conditions, usually when the cookie
is not good anymore, i.e. due to IP changes. Now the error output is
more distinct and at least for me, works better.

An idea might be to have colourful output if a capable terminal was
detected.