Totalise again

[karen2205]

Boring saga
The headers of the email I was sent yesterday:

From: "Totalise" <custserve@totalise.co.uk>
22:40 < Karen> To: "Totalise" <custserve@totalise.co.uk>
22:40 < Karen> Subject: Your account status.

Yes, really. That's all there was to them.

Today's bombshell:

Dear Customer

We wrote to you recently to explain that it will not be possible to collect your e-mail whilst connected to the Internet using another service provider, unless you have signed up for Totalise JustMail.

We are still collecting e-mails which are being sent to your Totalise address and you may have unread mail in your mailbox. In order to access these e-mails you will either need to connect to the Internet through Totalise, or signup for the JustMail service.

Totalise JustMail

>> Access using an e-mail programme or through our Webmail service
>> Access your e-mail wherever you're connected
>> Virus scanning on all your incoming e-mail
>> 20MB webspace


Totalise JustMail costs only £2.50 a month.

Please go to http://www.totalise.co.uk/justmail for more details and to sign up.

If you no longer need your Totalise e-mail address you will need to remove the settings from your e-mail programme. It is currently trying to access your Totalise account and this message will appear in your in-box each time it does so until you either sign up for JustMail or delete the Totalise account from your e-mail programme.

Thanks and best regards

Totalise
Customer Services



With headers:

Date: Thu Dec  9 22:39:24 2004
From: support@totalise.co.uk
To: support@totalise.co.uk
Subject: Unread e-mail

So my incentive for moving away from totalise has just got even bigger. It can't be done over night - too much useful stuff goes in there so I'll have to connect via totalise dialup every once in a while till I manage to sort this.


About the only good thing that's come of this is that when I have my copy of Unix for Dummies beside me, I can make urchin do things! Possibly not very sensible things - like

cat "#keble.log"

(#keble sorted me out with

less "#keble.log"

which allowed me to search for what I needed).

Comments

[crschmidt.livejournal.com]

The headers are probably so slim because they're not actually sending the email: they're just dumping the email direct into the database for it or something like that, I'd bet.

[karen2205]

Yeah - are they supposed to do that though? Surely there's an RFC somewhere that says emails should come with headers even if you're just dumping them in databases?

[crschmidt.livejournal.com]

In this case, it's not really mail. It just happened to be in your inbox and look like mail to you, but since it was never sent, received, or delivered, there's no additional headers that would come from anywhere. The headers that are attached to most mail messages are a remnant of the transfer process: since this mail never went anywhere, it didn't have a way to pick those up.

[simm42.livejournal.com]

you can always do cat file | grep pattern

or just grep patern file(s)


Oldest phrase in unix: "Theres more than one way to do it"

[crschmidt.livejournal.com]

Which applies even more to Perl than it does to Unix in general.

[simm42.livejournal.com]

Very much so - but sine karen is only just starting on unix I wasn't going to scare her with the idea of using perl instead of grep awk and sed for everything :) (generally my prefered way I will admit)

[karen2205]

Hmm - isn't perl overkill when you're doing searches this simple?

[karen2205]

*nods* just bear with me - I only read about the pipe command on the way to
work this morning!

grep never seems to do quite what I want it to do - this is, I think, 'cos
it's very powerful and I need to read the man page all the way through,
rather than declaring it too long/complicated!

Is it possible to grep the man pages?