slowass.net gets a lot of hits on port 25, usually in waves. I never see them coming, and enough email gets through that I don't really notice that they've happened, but when I least expect it, all of my clients start to grumble that I'm not responding to their emails. I'm not getting their emails. Some botnet owner thinks slowass.net is a major ISP with thousands of users, and machines from a poll of hundreds of thousands -- at least. I've automated firewalling them in the past, but eventually so many were firewalled that the machine got stuck spending 95% of its CPU time in the kernel, enforcing the bans). As soon as one IP is firewalled, another connects and starts trying to brute force out user names. The net result is that email at slowass.net has been extremely unreliable through virtue of working well enough that I start to trust it, and I'm too vain to stop using it and just move everything to gmail. That and I really like emailing with mutt. If your client can't handle 10,000 messages in the inbox and sort snappily with little RAM, it sucks (more than mutt).
After this last round, exasperated, I told a client I was going to ask Google about their hosted email service and otherwise apply for the beta. On a Friday evening, I used Google to search for the service, found it, logged in to my account, and (verbosely -- big surprise) filled out the form. They wanted to know what I was using for email now. This struck me as an open-ended question, so I told them: Postfix with Perl in a
Later that same Friday, an approval form letter was sitting in my gmail box. There was a step of setting up an admin user for the domain (to add other users and whatnot). The login screen for @gmail.com users but has the login box on the opposite side, clearly labeled @slowass.net.
Logging in, there's an additional administration screen with the inbox the second link on the very top nav. The inbox area looks just like the traditional gmail.com user interface, but had additional little status boxes on the right side telling me in some sanitized language that the account wasn't active yet, and linked to the
I feel like I should be doing some pentesting or something for the priviledge, but I think I'm just going to try to forget about all of this and move on, happily operating just like I always have -- mutting out messages all day long, stockpiling gigs and gigs of sent and recieved mail, tagging messages, following my RSS feeds of tagged messages, building local indices of my mail messages, sorting and searching in mutt, and all of that -- only with port 25 *closed*, less spam, and hopefully (knocking on wood), no more dropped messages.