Mailing List Archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I dropped using GMime for finding the mime boundary in aug 2013
because of some suspicions wrt gmime's thread-safety. This has been
causing some problems since. Calling 3.1.10 clean is kind of
dangerous. 3.1.10 did not support multiline boundaries, and 3.1.10
suffered from segfaults and other problems (esp for SSL connections).

I'm perfectly happy to restore the gmime scanner in this case, and see
if that helps.

stay tuned

On 21-07-14 15:08, Reindl Harald wrote:
> 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)
>
>
>
> _______________________________________________ DBmail mailing
> list DBmail@dbmail.org
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>

- --
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
www.nfg.nl/info@nfg.nl/+31.85.877.99.97
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlPNGK8ACgkQ8iITvBH4zTGCKgCfRYO6W8By68VZoIuVKep57HaE
S+4AnAoOFHZX64YSAe+51b6Gu/Lxk+vs
=37TF
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

i did not call 3.1.10 clean in general but it don't contain
the specific race bug, se my followup mail

that commit introcuces the problem
http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=8c612adbe6468e2cb4d520789cd35156145c5f37

see attached diff files
not happening with a3f2972ed0f3f4d16fed27418c2013c6094533ab

Am 21.07.2014 15:42, schrieb Paul J Stevens:
> I dropped using GMime for finding the mime boundary in aug 2013
> because of some suspicions wrt gmime's thread-safety. This has been
> causing some problems since. Calling 3.1.10 clean is kind of
> dangerous. 3.1.10 did not support multiline boundaries, and 3.1.10
> suffered from segfaults and other problems (esp for SSL connections).
>
> I'm perfectly happy to restore the gmime scanner in this case, and see
> if that helps.
>
> stay tuned
>
> On 21-07-14 15:08, Reindl Harald wrote:
>> 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)