Archive for May, 2007
Maybe I won the SPC challenge and got the bad one, but it’s D-Link so there’s a pretty good chance you could win too.
One of the D-Link “HD” BoPL adapters that I got for my wireless link to bridge the network between the guy’s house (where the cable connection is) and his garage (where the antenna and radio are mounted) called it quits a couple of weeks ago after 6 weeks of use. When I first got them and plugged them in they ran so hot that I immediately assumed that D-Link’s BoPL adapters are the force behind climate change.
The thing got so hot that it managed to reflow the solder around the pins of header J2 on the board opposite the one with the heat sink.
Even ignoring the fact that the thing ultimately failed, it sucked anyway. Typical latencies of 80ms were just acceptable given that it was just a bridge to a cable internet connection, but frequent occurrences over multiple consecutive hours of 3000+ ms latencies just blew. More than once I got pissed off enough waiting that I switched to using my dial-up connection. The problem was probably noise from something, but there was nothing different running off of his electrical panel when it happened. It could have been a neighbor that shares the same transformer, but given that the signal doesn’t seem to make it past where the neutral is bonded to ground I’d hope that they’ve got enough signal headroom to overcome outside noise.
So with one of the units non-functional (the BoPL side of the unit is non-responsive) I’ve now run some indoor cat5e across the guy’s yard (which is both cheaper at about $10 of cable as opposed to 2 of the $100 DHP-300s and a heck of a lot more responsive with <1ms latencies) until he digs a hole to add onto his house this summer (at which point I’ll bury some outdoor cat5e). I don’t even really have a use for them anymore (nor want to use them anywhere with their sucky 3000+ ms latencies) I’m not even sure if I’m going to bother dealing with getting D-Link to warranty them. Perhaps I can convince them to send me some network cards instead. If you work for D-Link give me a shout!
In any case, I guess I’ll go back to my assertion that pretty much the only reliable thing that D-Link sells is their DFE-538TX 10/100 PCI network cards.
May 30th, 2007
For those of you who missed it, we released Apache SpamAssassin 3.2.0 on May 2nd after a few RCs and a bit of pestering people to test it out. Most of the bugs people encountered in the final release were with their integration software not adhering to API requirements that haven’t changed in ages. There’s a few other bugs that will be fixed in a soon to be released (I hope) 3.2.1… nothing of major concern to most people that would prevent you from upgrading to 3.2.0 now though.
Justin Mason outlined a number of key features introduced in 3.2.0 in his posting here. Two other things I’d add off the top of my head are the support of Mail::SPF which is the current SPF reference implementation (it does away with a lot of legacy crude present in Mail::SPF::Query and generally works a lot better) and the new “whitelist_auth” option that allows a user to whitelist a sender that passes any of DKIM, DomainKeys or SPF. It’s basically whitelist_from_dkim, whitelist_from_dk and whitelist_spf all rolled into one. The benefit is that an end-user doesn’t have to know which (or keep track of changes in which) form of email auth a user/domain is using.
It looks like I was pretty close on calling the release time frame too. In this post, on September 1, 2006, I guessed at late winter or early spring. I went skiing the last week of April and we released during the first week of May. Can’t get much better than that! I just hope I didn’t delay the release on some subconscious level.
Oh, the newest release of SpamAssassin will catch more spam (than older versions) for you too. Go figure.
May 27th, 2007
…and it does. Below is the header from a mail generated by an “email this tracking page to somebody” web request via their website. WTF is “+0000 (EST)” in the Date field value. Really. Is it Canada Post that sucks, SAP, or both. Well I know for the most part Canada Post sucks and, well, SAP sucking on this point wouldn’t surprise me at all.
This really reinforces my feeling that their panic inspired product e-Post probably sucks and is likely prone to getting caught up in anti-spam systems.
In any case, being dumb costs you. For this stupidity SpamAssassin awards you with:
50_scores.cf:score INVALID_TZ_EST 2.601 2.065 2.265 2.696
50_scores.cf:score DATE_IN_PAST_03_06 2.299 1.394 1.306 0.044
4.9 for set 0 — which lucky for them is the only thing that hits in set 0.
3.459 for set 1 — it’s a good thing the body is formatted to avoid checksum database hits.
Set 2 and 3 scores are pretty safe as long as the user’s bayes database doesn’t take off in the wrong direction (I hit BAYES_50).
Oh yeah, they forge the mail from: too! Idiots.
Received: from OT1LF900.CPC (mailoutcpc.canadapost.ca [188.8.131.52])
by mx-04.dostech.net (8.13.8/8.13.8) with SMTP id l4FKMgXq005778
for <email@example.com>; Tue, 15 May 2007 16:22:43 -0400
Received: from (10.130.62.19) by OT1LF900.CPC via smtp
Tue, 15 May 2007 21:26:36 -0400
Received: from canadapost.ca ([10.100.21.29]) by cpcw1003.cpggpc.ad with Microsoft SMTPSVC(6.0.3790.211);
Tue, 15 May 2007 16:22:42 -0400
Date: Tue, 15 May 2007 16:22:41 +0000 (EST)
X-Priority: 3 (Normal)
X-Mailer: SAP Web Application Server 6.40
X-OriginalArrivalTime: 15 May 2007 20:22:42.0226 (UTC) FILETIME=[CA55D120:01C7972E]
May 15th, 2007