Am 02.09.2013 23:59, schrieb "Daniel Schütze" <[email protected]>": > I have then recompiled/installed dbmail 3.1.4 and noticed no change > (roundcube still failed to open a message it > could open in dbmail 3.1.3). By failed to open I mean no message text or > attachments was shown. > > I then deinstalled dbmail 3.1.4 and went down to dbmail 3.1.3 and again > roundcube could open the message. > > Also note that this test case message entered my dbmail system for the first > time when it was running dbmail 3.1.4 > with gmime-26-2.6.16
very interesting so we know two important things * for whatever reason re-construction has still a problem * split and store of messages was and is still fine the second point is finally the most important one because it means as far as i remember since dbmail-2.x in 2009 there was no single case where a messsge was destroyed at store/receive - while it is not funny that there are re-construct troubles this is very important because it can be fixed without lose data or even with downgrades i only would like to understand why this happens with 3.1 because from the software architecture 3.1 is so much better, has mostly no memleaks and no trheads runnign with 100% CPU as 3.0x shows over and over again resulted i löet it run with 3000 Mhz on the vSphere cluster because dbmail-impad still works and after restart it takes only a short timeframe until it spins up frankly i would like to have predicatable real-load tests which are showing such behavior before release and i seem to be still too stupid :-( i fear pray and whine does not make things better for now :-(
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
