So I try to send e-mail...

Date: 2000-05-16 19:20:00

So I try to send e-mail to someone using Juno (better to not ask too many questions here) and it bounces with a cryptic message that points here. I eventually figure out that the reason it bounced was because it refused to accept mail relayed from a SMTP server on a dialup line, plus known open SMTP relays. I was impressed that they actually bothered to note that it did restrict those who run their own SMTP servers on dialup connections and suggested a fix: route my outgoing mail through my isp's SMTP relays. That wouldn't be too hard, I'm sure, but it begs a question: is this necessary? In an ideal world, it wouldn't, because spam (specifically spam sent through insecure relays, what they're trying to curb there) wouldn't exist. In this reality, however, is it effective to throw the wheat out with the chaff, discarding all messages from unsecured or unverified relays? I would be tempted to say not, that it wouldn't be difficult for a competent admin to go through forged spam, figure out who sent it, and inform the isp, who would then kick the user off or be subpoenaed if the spam happened to be received in a state where forged spam is illegal. This would be more trouble, sure, and apparently Juno doesn't want to bother with that. I'm just very resistant to change anything on my workstation that I don't believe should be changed, where an intelligent solution exists that doesn't involve our running around like chickens with our heads cut off.

Went to a job interview today. Didn't expect too much coming into it, but when I saw a RedHat box on a shelf and a CVS book on the desk of the guy with whom I interviewed, I started to think differently. When he mentioned Inflow and pulled out a diagram with "rsync" and "php" and "zope" and "sql" and "cvs" scribbled all over it, I began to think this might be a good place. We'll see how Thursday's interview goes, but I've got a good feeling about this.