Re: GUILTY COMMIT FOUND -> Re: re-construct: 3.1.10 last clean version

Reindl Harald <[email protected]>
Newsgroups gmane.mail.imap.dbmail
Organization the lounge interactive design
Message-ID <[email protected]>
"69c0592867ad012bd1b78b873b65f7e53064971c" looks way better

* high concurrency
* loop of 3000 times "Panel: E-Mail-Debug - IMAP-POP3-Download" with
  POP3 and IMAP with no mismatch between both
* checksum of all testmessages for POP3 and IMAP correct
* see also attachment

not sure if the conlusion "putting gmime back in charge" is
entirely correct or the dbmail code just had some memory bug
but at least i see no current problems and can't find the context
of the 8c612adbe6468e2cb4d520789cd35156145c5f37 commit in my archive

only that below where i was too stupid to notice the regression
while other commits between 3.1.10 and 3.1.11 obviously are fine
__________________________________________________________________________________________

2014-02-26 version 3.1.11
2014-02-25 IMAP: add loop protection to cleanup callback
2014-02-24 Fixed wrong result check in change username function
2014-02-21 fix regression in utf7 mailbox matching
2014-02-18 IMAP: fix inverted logic during abort
2014-02-18 LMTP/TIMSIEVE: fix possible segfaults
2014-02-17 POP3: fix segfault; fixes bug #1043
2014-02-10 IMAP: EOF on stdin is not an error
2014-02-10 remove unused file

!! -- KILLER -- !! 2014-02-10 support wrapped boundaries during reconstruction !! -- KILLER -- !!

2014-02-07 boundary fix for sha512 passwords
2014-01-30 fix unit-tests after merge
2014-01-30 Merge branch 'dbmail_3_1_utf8_fix' of https://github.com/alyarskiy/dbmail
2014-01-30 Fixed long (>255) utf8 headers + unit-test
2014-01-28 Revert "IMAP: defer bailout in case of EOF"
2014-01-22 version 3.1.10
__________________________________________________________________________________________

Am 26.02.2014 22:48, schrieb Jorge Bastos:
> Anyone already using 3.1.11?
> Maybe this is the version that I'll use for my upgrade, but 'd like some
> feedback from anyone using it already

yes because there are only small well deserved bugfixes from 3.1.10 to 3.1.11
http://git.dbmail.eu/paul/dbmail/log/?h=dbmail_3_1

2014-01-28 Revert "IMAP: defer bailout in case of EOF" closes a big memory leak

Am 21.07.2014 16:05, schrieb Paul J Stevens:
> Ok. I'm putting gmime back in charge of parsing for boundaries.
> 
> Currently testing the change.
> 
> On 21-07-14 15:42, Reindl Harald wrote:
> 
>> CLEAN - snapshot: a3f2972ed0f3f4d16fed27418c2013c6094533ab.tar.bz2 
>> _____________________________________________________
> 
>> BROKEN: 8c612adbe6468e2cb4d520789cd35156145c5f37 support wrapped
>> boundaries during reconstruction
> 
>> there must be happening something bad in memory
> 
>> that is the guilty commit and sadly i remember that it fixed a bug
>> rpeorted from myself in case of specific messages not proper
>> re-constructed at least on Apple Mail 
>> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=8c612adbe6468e2cb4d520789cd35156145c5f37
> 
>>  no idea why a commit from 2014-02-10 took that long to get visible
>> each day more
> 
>> Am 21.07.2014 15:08, schrieb Reindl Harald:
>>> 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

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
checksum-test.txt (text/plain, 5.5 KB)
Jul 21 16:46:42 IMAP 01: OK: 04073992ce1c1e75d9bd88e0388486dcc80df627 (Test 5)
Jul 21 16:46:42 IMAP 02: OK: a1fbc899f71b36c2fad84ff096c611dfa75b5d68 (RE: NEU)
Jul 21 16:46:42 IMAP 03: OK: 4cd84fdff079a6cdfb1c81c641e41a693fc6aaa4 (AW: category banner)
Jul 21 16:46:42 IMAP 04: OK: d2b09869c14b6321185effdafcd34c65ca4e940f (Re: Einladung 5. juli)
Jul 21 16:46:42 IMAP 05: OK: d1e3cfa77ece15ad6a44a79a3597dc4775cd514c (Re: Einladung 5. juli)
Jul 21 16:46:42 IMAP 06: OK: 12baedbadb4b0ed23dbe167325fbe90a6188eff2 (Panel: E-Mail-Debug - IMAP-POP3-Download)
Jul 21 16:46:42 IMAP 07: OK: 7f1c0f7c0de0f586439729b8139ba3501fd857df (Re: Danke-so schoen)
Jul 21 16:46:42 IMAP 08: OK: 60e5602ad6f817bd2d010f0d387788f79d26c64b (Re: [Full-disclosure] Apache suEXEC privilege elevation - information disclosure)
Jul 21 16:46:42 IMAP 09: OK: b3175f870fe801b273f69b9d57161529a618abe0 (WG: ENERGIEMASKOTTCHEN - Logobewertung im Rahmen des AlterVis Projektes)
Jul 21 16:46:42 IMAP 10: OK: 7384b2dbed2b5a492eb7f97d4604c78d81faef27 (TEST: multiple nested mimeparts)
Jul 21 16:46:42 IMAP 11: OK: 1a9d8ddd802fb33b01662a46bf673f2e417d6524 (User Quarantaene Account Information)
Jul 21 16:46:42 IMAP 12: OK: 4cc44eb6e4a220c453fc86791e778887b7555bde (utf7_header)
Jul 21 16:46:42 IMAP 13: OK: d8c9b88b779953e64bd0e13e0c56f3be6fd52b4a (test)
Jul 21 16:46:42 IMAP 14: OK: b5e97924ae0bafb2db279dc95c25a04922e3c305 (simple_with_from)
Jul 21 16:46:42 IMAP 15: OK: 3d478742c59382997a1013d98956f333eea7ad56 (simple_groups)
Jul 21 16:46:42 IMAP 16: OK: f474411ae10cd36c24158b10635e3e66d5bf415f (rfc822)
Jul 21 16:46:42 IMAP 17: OK: 4af68269447d156d0913cabe6a587018378be7b2 (raw_lmtp_data)
Jul 21 16:46:42 IMAP 18: OK: f0d1f8a67ddb181d08f44e5ac8ab1b535e49c45f (outlook_multipart)
Jul 21 16:46:42 IMAP 19: OK: 39c015c410ab20797649033dfa5a85782762e392 (multipart_signed)
Jul 21 16:46:42 IMAP 20: OK: a7182a8690080839d458d8ab392c181fa49d9999 (multipart_mixed)
Jul 21 16:46:42 IMAP 21: OK: 284a906f6a3649baaa986147f9a2ab293108ad01 (multipart_message_6)
Jul 21 16:46:42 IMAP 22: OK: c395119902fd115d463deca0e850beb23e214990 (multipart_message_5)
Jul 21 16:46:42 IMAP 23: OK: a7d151e32e24e72ab1a2fb8b3317d1f039707059 (multipart_message_4)
Jul 21 16:46:42 IMAP 24: OK: 2210e351665b9771a6eefab2cb0c8bf43a04fcea (multipart_message_3)
Jul 21 16:46:42 IMAP 25: OK: 0e2409bcf6921c5da801e1bf4ca4f57be9f07775 (multipart_message_2)
Jul 21 16:46:42 IMAP 26: OK: 84d11dc83e24300aa1f3146fa1118e315c0f6cc7 (multipart_message_1)
Jul 21 16:46:42 IMAP 27: OK: 7e6b52635da61dbf7a0204df73b6daf1af1b79bc (multipart_alternative)
Jul 21 16:46:42 IMAP 28: OK: 60dd43bb886f6c47d89b5dc3ab3f7f764b68eb2e (message_rfc822)
Jul 21 16:46:42 IMAP 29: OK: 59aa5e165c538a7cedad0f207329a65c5daf5cd0 (broken_message_2)
Jul 21 16:46:42 IMAP 30: OK: 61c1c2627a4e5fb9b4e7731b06d53e82e4ed2bfd (broken_message_1)
Jul 21 16:46:42 IMAP 31: OK: 49c28482302d4c8407b7a793e6af3d7e70f3d71d (Re: Mdulo Extintores)
Jul 21 16:46:42 IMAP 32: OK: 6750f16e78601afb5b7ea4d98b1e4899a8463e15 (Re: [gentoo-dev] New developer:  Miroslav ulc (fordfrog))
Jul 21 16:46:42 IMAP 33: OK: 16292abceedfc6f37707cb1adf35e1e1a46d7d2b (Ostrava Tuesday morning)

Jul 21 16:46:53 POP3 01: OK: 04073992ce1c1e75d9bd88e0388486dcc80df627 (Test 5)
Jul 21 16:46:54 POP3 02: OK: a1fbc899f71b36c2fad84ff096c611dfa75b5d68 (RE: NEU)
Jul 21 16:46:54 POP3 03: OK: 4cd84fdff079a6cdfb1c81c641e41a693fc6aaa4 (AW: category banner)
Jul 21 16:46:55 POP3 04: OK: d2b09869c14b6321185effdafcd34c65ca4e940f (Re: Einladung 5. juli)
Jul 21 16:46:57 POP3 05: OK: d1e3cfa77ece15ad6a44a79a3597dc4775cd514c (Re: Einladung 5. juli)
Jul 21 16:46:59 POP3 06: OK: 12baedbadb4b0ed23dbe167325fbe90a6188eff2 (Panel: E-Mail-Debug - IMAP-POP3-Download)
Jul 21 16:46:59 POP3 07: OK: 7f1c0f7c0de0f586439729b8139ba3501fd857df (Re: Danke-so schoen)
Jul 21 16:46:59 POP3 08: OK: 60e5602ad6f817bd2d010f0d387788f79d26c64b (Re: [Full-disclosure] Apache suEXEC privilege elevation - information disclosure)
Jul 21 16:47:27 POP3 09: OK: b3175f870fe801b273f69b9d57161529a618abe0 (WG: ENERGIEMASKOTTCHEN - Logobewertung im Rahmen des AlterVis Projektes)
Jul 21 16:47:33 POP3 10: OK: 7384b2dbed2b5a492eb7f97d4604c78d81faef27 (TEST: multiple nested mimeparts)
Jul 21 16:47:33 POP3 11: OK: 1a9d8ddd802fb33b01662a46bf673f2e417d6524 (User Quarantaene Account Information)
Jul 21 16:47:35 POP3 16: OK: f474411ae10cd36c24158b10635e3e66d5bf415f (rfc822)
Jul 21 16:47:35 POP3 18: OK: f0d1f8a67ddb181d08f44e5ac8ab1b535e49c45f (outlook_multipart)
Jul 21 16:47:36 POP3 19: OK: 39c015c410ab20797649033dfa5a85782762e392 (multipart_signed)
Jul 21 16:47:36 POP3 20: OK: a7182a8690080839d458d8ab392c181fa49d9999 (multipart_mixed)
Jul 21 16:47:36 POP3 21: OK: 284a906f6a3649baaa986147f9a2ab293108ad01 (multipart_message_6)
Jul 21 16:47:37 POP3 22: OK: c395119902fd115d463deca0e850beb23e214990 (multipart_message_5)
Jul 21 16:47:37 POP3 23: OK: a7d151e32e24e72ab1a2fb8b3317d1f039707059 (multipart_message_4)
Jul 21 16:47:38 POP3 24: OK: 2210e351665b9771a6eefab2cb0c8bf43a04fcea (multipart_message_3)
Jul 21 16:47:38 POP3 25: OK: 0e2409bcf6921c5da801e1bf4ca4f57be9f07775 (multipart_message_2)
Jul 21 16:47:39 POP3 27: OK: 7e6b52635da61dbf7a0204df73b6daf1af1b79bc (multipart_alternative)
Jul 21 16:47:39 POP3 28: OK: 60dd43bb886f6c47d89b5dc3ab3f7f764b68eb2e (message_rfc822)
Jul 21 16:47:40 POP3 30: OK: 61c1c2627a4e5fb9b4e7731b06d53e82e4ed2bfd (broken_message_1)
Jul 21 16:47:40 POP3 32: OK: 6750f16e78601afb5b7ea4d98b1e4899a8463e15 (Re: [gentoo-dev] New developer:  Miroslav ulc (fordfrog))
Jul 21 16:47:41 POP3 33: OK: 16292abceedfc6f37707cb1adf35e1e1a46d7d2b (Ostrava Tuesday morning)
signature.asc (application/pgp-signature, 246 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPNLUgACgkQhmBjz394AnnMDgCaA/sRKRabZFg4s30HyjgTuT+V
FWgAn2ob+DzZHlIAUuBsCSbhvrvvy8nA
=jpYo
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.