[imp] IMP hangs on verifying larger s/mime message, Reported Bug and others

[Michael M Slusarz]

Quoting Harakiri <harakiri_23 at yahoo.com>:

>
> --- On Sun, 12/7/08, Jan Schneider <jan at horde.org> wrote:
>
>> From: Jan Schneider <jan at horde.org>
>> Subject: Re: [imp] IMP hangs on verifying larger s/mime message,
>> Reported Bug and others
>> To: imp at lists.horde.org
>> Date: Sunday, December 7, 2008, 12:04 PM
>> Zitat von Harakiri <harakiri_23 at yahoo.com>:
>>
>> > Please have a look at these for the next major
>> release:
>> >
>> > [#7754] smime.php extractSignedContents hangs on
>> larger mails (openssl process never returns)
>> > http://bugs.horde.org/ticket/7754
>> >
>> > [#7756] checkRequestToken in Horde.php -> all
>> tokens are only valid for 0min
>> > http://bugs.horde.org/ticket/7756
>> >
>> > [#7757] replying to S/MIME encrypted messages -> No
>> message Text
>> > http://bugs.horde.org/ticket/7757
>>
>> We are choosing the bugs that we are going to fix
>> ourselves, thanks. Unless you want to pay someone to fix
>> those for you?
>>
>> Jan.
>
>
> You really need a lesson in being to swanky, all i said was "please
> have a look at it" and btw - i fixed YOUR bugs with my patch
> suggestions as you can see

We appreciate your patches, but I believe Jan was simply commenting on  
the unnecessary e-mail follow-up to this list.  If a suspected problem  
is discovered, a bug reports is sufficient.  The developers actively  
read the incoming bug reports and will prioritize as necessary.   
However, there is no need to send a follow-up e-mail to the list, and  
then demand "Please have a look at these for the next major release".   
This is probably not a good practice for *any* open-source project,  
not just Horde, where the developers are not paid to make releases.

FWIW, Request #7754 was looked at and implemented (although it was far  
from a critical issue/bug - it was a performance issue that I  
personally have never had an issue with in the past, even with large  
messages), I haven't looked at #7756 personally (the other devs know  
more about that code than me), and #7757 is bogus (it will never be  
fixed in IMP 4, but is already fixed in IMP 5 code).

michael

--
___________________________________
Michael Slusarz [slusarz at horde.org]