Simple annoying e-mail related problems

One thing that always causes hassle for us as an e-mail services provider is the use of double extension file names attached to e-mails. e.g. annualreport.doc.pdf – this looks harmless, however in file naming terms it’s wrong. A filename should be comprised of a meaningfull name and it’s extension. I don’t know if this is a user issue or an application issue, but I suspect a bit of both.

If you insist on using double file extensions because your application makes them that way, then change the application. Or even better rename the file before sending. You have to save it anyway, correct? Well then, save the file with the proper file extension, then e-mail that file to the intended recipient.

The main reason for this slightly ranty post is that our mail scanning software catches all double extension attachments and treats them as an attempt to send a virus. Now it doesn’t delete them, or do anything funky with them, it sends the original message with the attachment replaced with a warning text file letting us know what server and the location to the e-mail in the quarantine so we can release it for you. It does this as a lot of traditional viruses used to send themselves from an infected users pc to everyone in their address book as an attachment with a name of something like .doc.com or .doc.exe and it would infect the end users pc.

I’ve considered removing this restriction a few times. But the pedant in me doesn’t let me. Please just use common sense and use proper file extension naming, for the sake of everyone.

Crazy weather???

Holy hell! The weather the last 2 days has been mad, completely looney. Last night when I lef the pub at 11:30 (got out during the 30 minute drinking up window, incase any law enforcement types read this) and proceeded to head home. Sure next thing I know its a blizzard!! My bag of chips was getting snow in it :( – crazy. And again today there is snow, sleet, rain, crazy high winds. All in all, very unsettled. Reminds me a bit of The Day after tomorrow.

Promise Raid cards?

Yes the saga continues, only 4 years later. A few years ago we dabbled with promise cards. A) they were cost effective, B) they apparently had a good feature set and C) Our vendor at the time recommended them.  Long story short, they sucked. We used the TX2300 I think then. Over the past while we’ve been using another vendor that is local to us instead of just using Dell and HP so we can diversify. They were raving about the new Ex series of cards so we got an Ex8350 card off them and put it into a quad core server with plenty of ram etc.

Initial findings:

Redhat EL 4U4 supports the card. Yaay. However the kernel on the install cd didn’t. Promise had no driver for U4. We contact redhat, follow instructions, nothing. Redhat come back at 09:06 the following morning with a new driver disk that is untested, but hey it worked! Horray. Installed RHEL 4, upgraded to latest redhat kernel and all looked great.

The card performed quite well during initial testing. Compile times were up on other systems and uncompressing tar.gz files etc was very quick. I wasn’t sure if this was the quad core or the raid card/disk performance but I gave the raid card the benefit of the doubt.

Things started to get a bit hairy after 2 weeks or so. The server was our latest shared hosting box, which is a beast in comparison to some of the older machines with 4 cores on the cpu. It started showing high load averages even when it wasn’t particularly busy. A closer look and see a huge amount of IO wait. I think nothing off it but keep an eye on the server. Last friday it had a serious brain fart, a simple untar job of a 200mb file brought the load to over 200 and poor Niall had to look after it.

Another week has passed and it has another brain fart, this time input/output errors for almost all binaries on the file system. Now this brings back vivid memories of our first ever shared server from years ago with the card in it that I mention above. So Promise cards suck. Redhat support is second to none. Infact Redhat are bloody brilliant, never has a vendor been so usefull or quick to help me out on an issue before.