Description of problem: Apparently this file did not get shipped with F8 version of php-pear-Mail-Mime, which then upsets horde: [Fri Dec 07 15:09:45 2007] [error] [client <IP_Address>] PHP Warning: MIME_Structure::require_once(Mail/mimeDecode.php) [<a href='function.MIME-Structure-require-once'>function.MIME-Structure-require-once</a>]: failed to open stream: No such file or directory in /usr/share/horde/lib/Horde/MIME/Structure.php on line 308, referer: https://www.domain.com/imp/message.php?index=29248 Version-Release number of selected component (if applicable): 1.5.2-2.fc8 How reproducible: Always. Steps to Reproduce: 1. Attempt to open MIME e-mail in IMP/Horde. Actual results: Mail doesn't show, error message in log file. Expected results: Worked fine before. Additional info: CentOS 5.1 does have that file, in an older version of the package. Not sure what happened in the meantime.
I had the same problem and investigated bit more. It seems like that since version 1.5 of pear-mail-mime mimeDecode is removed from the package. (upstream) mimeDecode has now it's own pear-package, namely Mail_mimeDecode. (http://pear.php.net/package/Mail_mimeDecode) So maybe this new package can be added to Fedora.
Ping... Could we have that package in F8, as per comment #1?
Created attachment 296977 [details] Spec file
*** Bug 435643 has been marked as a duplicate of this bug. ***
Created a new package request for Mail_mimeDecode: https://bugzilla.redhat.com/show_bug.cgi?id=436737 Reviewers welcome!
php-pear-Mail-mimeDecode has been pushed to all the F8 mirrors. I have also updated php-pear-Mail-Mime to require this new package, but that update is still pending. Enjoy!
php-pear-Mail-Mime-1.5.2-3.fc8 has been submitted as an update for Fedora 8
horde-3.1.7-2.fc8 has been submitted as an update for Fedora 8
horde-3.1.7-2.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
php-pear-Mail-Mime-1.5.2-3.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.