unbelieveable i am building and stressing serveral releases 3.1.10 is the last one not suffering from the problem "--" instead "-- mime-id" and i have clearly no idea why this started around June to affect more and more users
BUG - 3.1.13: 7d23183993e0ad81b8b0fc1920ba8e651043669e BUG - 3.1.12: 1801c11f9e18a80c5eb2ae272bcbeb6d5f634e74 BUG - 3.1.11: aa751fa4f998993a911dbf7f19fb06a4aceea843 CLEAN - 3.1.10: 2e819d439c5e731b082bf83420f8ad20d89c0182 with 3.1.10 it's impossible for me to produce enough concurrency to get any single mismatch ___________________________________ that below is expected because fixed with the following commit http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=8a042214ae1d120581740020f4e73c3cf8d3a6c0 Jul 21 15:04:55 IMAP 33: EXPECTED: 16292abceedfc6f37707cb1adf35e1e1a46d7d2b / FOUND: 2703f68a52cc815e2d2944b046fcc3c07c0bc47f (Ostrava Tuesday morning)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
