From: Tollef F. H. <tf...@er...> - 2010-03-11 08:38:01
|
]] Zack Rusin | On Wednesday 10 March 2010 14:59:42 Zack Rusin wrote: | > Maybe /usr/bin/mail is broken, I'll double check it. | | Yea, that's it. Someone installed a new mail daemon on the | server. We're using "-a" to specify the Content-Type header in mails, | but the heirloom mailx that has been installed uses the "-a" option to | specify attachments and since filename "Content-Type: text/plain;" is | not a valid filename it exits with an error. I'll try to fix it right | now. Ah, that would be it. (And mail(1) is hardly a mail daemon :-) | BTW, replacing a mail client on the server with something that's not | compatible is not very social. Rather than assuming malice, you may assume that I was trying to fix something when I made that change. The old mailx mangled UTF-8 content. The easiest way around this is to use /usr/bin/bsd-mailx rather than just mail. I believe it just does the right thing wrt content-type now, so just dropping -a should fix it. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are |