2009-07-24 update: it works again
I wanted to report an issue with zsh, but I can't.
The problem is that they've got harsh blocking rules which prevent emails from any @gmail.com account. I went through a lot of trouble to research other email accounts and to sign up for one only to learn that @gmx.com email addresses are also blocked. An old @myrealbox.com account is also blocked.
5.7.1 Blocked by SpamAssassin
Seriously people, figure it out and make it work.
Apparently this was known a long time ago:
How do I report a bug? I can't.
Oh well, I'll dump it here and let fate decide.
Scott Morizot's firewall generator is a great tool, but I found an issue with it. There was a series of commands which weren't working because they were being summoned from a variable. It's easy enough to do a search-and-replace to use the raw commandlines instead, but I did some troubleshooting..
: Solved, see zsh command in a variable.
This works in bash, dash, ash and sash, but not in zsh:
a="echo foo bar" $a
in zsh, this works:
a="echo" b="foo bar" $a $b
in bash, dash, ash and sash, this works, but not in zsh:
a=ls b="-a -l" $a $b
I tried variations, such as:
a=ls b=" -a -l" $a$b
But I still can't get it working.
I'm a zsh user, to the point that I'd rather uninstall bash entirely. But it's incompatibilities like this which tick me off. I think this issue snuck through because the script had
#!/bin/sh which must have been linked to zsh. As I understand it, if zsh gets summoned through a
/bin/bash symlink it'll figure it out and go into compatibility mode.
At any rate, I don't care to troubleshoot any more. This was an interesting problem, but I don't use this firewall script anymore, and I'm not doing so much shell scripting right now. Later when I get around to it I'll have to follow up, since I do want to have commandlines with parameters stores inside a variable.
Or maybe I'll just do ruby scripting at the commandline instead of zsh. =/
2009-07-24 update ∞
Well I, at least, was able to sign back up to the zsh mailing list.
What's funny is that I went through the signup process and I didn't even remember that it had failed just days before. Me and my crazy memory and intuition.
Someone else is having an issue though, so perhaps there has been some unusual spamming activity and the mailing list went into lockdown to protect itself. Who knows, but it does seem that things are being looked at now.