?

Log in

No account? Create an account

Previous Entry | Next Entry

.... the aftermath

Oh, it continues.

This morning I get in to discover that hooray! My site is actually up and functioning as advertised. I shoot straight in to do my crucial updating and start merrily FTP-ing up my modified pages. Second directory I notice an unfamiliar file, one that's way too big ... its extension is .eml, which rings a vague bell. My blood runs just a little bit cold. I hover briefly over the disconnect button, briefly over the unfamiliar file, and then just finish my update (just five files) disconnect in short order and feed ".eml file extension" into google.

Oh buggering bollocks.

I do a quick run over the systems I buy from XXXXDELETEDXXXX and I'm not especially surprised when I discover that their mailserver isn't working, I'm not getting the automatic receipt email back from their service email, and that there's a fifteen-ring wait on their helpline. They've presumably had a full weekend of attempting to get NIMDA (or something similar) out of their IIS servers while getting all their hosted websites back online immediately.

However, I'm not impressed that it still isn't sorted out, particularly as they were always so ready to boast about how solid they were against virus attack. I'd quote, but it looks like that page has been pulled from the website :)

And, despite my firewall, my anti-virus software, whatever they're doing to curb proliferation, and the fact that the footprint on my site looks like the one left by an unsuccessful server infection (according to my google-informed guesswork) there is no way I am logging on to FTP to my site again until those unfamiliar files are gone.

And now I have to figure out what to tell my manager. Nothing, till I've heard from someone who knows something at XXXXDELETEDXXXX, I suppose. So far I've only spoken to a service mouth. She said, "Yes, we've had problems. They're sorted now. But we're still dealing with the aftermath."

Joy.