Comcraptastic goes Cocks

Cocks Internet (Cox) blocks outgoing port 25. I just got an email from Comcast that they're blocking port 25 now too, but only for folks like me who actually use port 25 to go outside of Comcast's network (i.e., to any server other than Comcast's). Which I do because I route all my outgoing email through badtux.net to make sure it gets properly logged and archived. Comcraptastic! Now I gotta go figure out how to make Exim4 on Debian listen on something other than port 25 (I am *not* going to send email via Comcraptastic's SMTP server, I found out the hard way that Comcraptastic's SMTP server drops half the email that it gets into the bit bucket, apparently using some hyper-vigilant algorithm that detects many ordinary emails as "spam" or "viruses").

Oh well, at least now hopefully the other people on my neighborhood segment aren't going to overload our upstream with zombie porn spam anymore. Note that I run a Mac and have my WiFI on my Airport Extreme secured with the most secure encryption, so I know I wasn't the source of any spam (no viruses for Mac, remember?). But I certainly saw a spike in virus traffic last week that was probably zombifyin' machines all over Comcraptastic's network... made things here on the penguin's iceberg pretty goddamned craptacular until Compost got the morons cut off. Looks like their algorithm for "probably a spammer" can't tell the difference between a buncha spam going to lots of servers, and a few emails going to a single server. Morons. But what can you expect from folks who've outsourced everything and thus have only a few dozen people who know anything who keep the whole craptacular piece of shit network they run up and going somehow and thus haven't a second's amount of time to, actually, like, *think* about the craptacular code they wrote in the five seconds between solving one problem that threatens the whole network and solving another problem that threatens the whole network? It's all about how corporate management can squeeze their employees for more profit by replacing competent people who know their shit with idiot contractors who can't find their ass from a hole in the ground, and nothing about customer service, unless your definition of "service" is what a stallion does to a mare.

-- Badtux the ComCrapilated Penguin

Aftermath:
I followed the directions for configuring exim4 at:

http://edin.no-ip.com/content/exim4-courier-ssl-debian-etch-mini-howto

with the exception that I authenticate against SASL rather than against Courier since I don't run Courier, I run Dovecot. So I un-commented the SASL section of the configuration file rather than the Courier section of the configuration file. But that was done years ago (been prohibiting relaying w/o name and password on port 25 for years, have never allowed "bare" relays for obvious spammer control reasons), so all I had to do was configure my keys, set the SSL enable at the top, and change last line of /etc/default/exim4 to say

SMTPLISTENEROPTIONS='-oX 465:25 -oP /var/run/exim4/exim.pid'

and after restarting, voila. Now listening for SSL on port 465, and non-SSL on port 25 (for things destined for that mail server which also hosts my Badtux domains). Tested it, and it works with both Thunderbird and AppleMail (I run a Mac, remember?).