The ServerSide has redesigned their backend from EJB onto Tapestry and JDO. They argue that they chose JDO to avoid vendor lockin because it’s a standard. Ok reason, but I don’t see it as very likely to happen. By the time they decide to switch again I bet they will be switching to another standard alltogether. 😉 Read the details here.
The followup to the first post on the new query parser for Hibernate is up here.
It is technical compiler stuff. I guess I should have paid a bit more attention in my compiler classes. 😉
As I said I’ve been wrestling with Exim for the last couple of days. The mess started when I started as MX for a new domain with primarily forwarding to a couple of external addresses.
The problem occurred because the server the mails were forwarded to checked the domain in the sender address. My current Exim setup didn’t do this, and thus accepted a bunch of spam mail which it tried to forward to the external server. No surprise, it got rejected. But because the domains were false I got a hughe queue with bounce-messages that could not be delivered.
So I decided, what the heck I could turn sender verification on too. It’s not like I have enormous loads, so I could handle the overhead. Bad idea. 😉 It seems the sender verification just checks for A-records. Domains that have no A-record, but have MX records were getting rejected. Not very popular when one of my users got a mail bounced from a business associate. 😉 So stay away from the option if you’re running Exim.