Red Hat Bugzilla – Bug 17241
Tin no longer runs metamail automatically with mime-encoded news postings
Last modified: 2008-05-01 11:37:58 EDT
In previous RedHat versions (up to 6.2), whenever I opened a newsgroup posting which was MIME-encoded, tin would always ask me if I wanted to view it with metamail. In pinstripe, tin no longer seems to detect this, and instead just posts the encoded message as ASCII and I had to manually pipe the message through /usr/bin/metamail. I downloaded the pinstripe tin SRPM and recompiled and forced installation, and now tin detects mime-encoded messages and asks about metamail like it always has. Perhaps metamail wasn't installed on the original compilation machine? The build process only enables metamail support if metamail is found by configure, or if configure is passed the --with-metamail option (which it isn't at present).
fixed in 1.4.4-3 and later (Rawhide)
*** Bug 19074 has been marked as a duplicate of this bug. ***
OK, this is _really_ fixed in 1.4.4-4 and later.
Which version will be included in RedHat 7.1? I just installed 7.1 Beta (Fisher) last night, and I've noticed that tin 1.4.4-3 is installed, and it still has this problem. A simple rpm --bebuild on my machine fixed the problem. However! I noticed when rebuilding 1.4.4-3 that configure has the -enable-metamail option passed to it, which I thought earlier would solve this. It appears that if metamail isn't installed that this still has no effect. I assume that 1.4.4-3 that comes with Fisher used the same SRPM that I downloaded from the SRPMS section off of the 7.1 Fisher directory on the ftp site.. it has the -enable-metamail flag set on configure, but "strings `which tin` |grep metamail" turned up nothing. Then I rebuilt the rpm and forced the installation, and the same command returned over half a dozen instances. So maybe tin requires more than the --enable-metamail flag after all. (I don't know if I should reopen this or not, probably not since it says it's fixed in -4)