Re: dbmail breaks PGP/MIME mails
Thomas Raschbacher <[email protected]> Thu, 19 Apr 2018 09:00:59 +0200
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
Hmm duno about that one, but i don't use SpamAssassin at the moment.. That aside - and without checking now - are there any test-emails with expected results, that would test that part of dbmail automatically? On 2018-04-18 17:48, Reindl Harald wrote: > Am 18.04.2018 um 07:32 schrieb Thomas Raschbacher: >> hmm .. >> >> I have no such problems with dbmail 3.2.3 (and gmime 2.6.20 > > looking at all the urgent fixes after 3.0 as well as 3.1 where a ton > of people pretended all is fine made me shy in case of dbmail updates > especially when development seems to be dead > > %changelog > * Wed Dec 7 2016 Reindl Harald <[email protected]> > - add dbmail-prepend-headers-during-delivery.patch > > is at least this one part of 3.2 or did it too never made it to a > stable tarball? and yes - add own headers at the bottom is a major > issue when it comes to software like SpamAssin which needs to find the > trust-path > >> On 2018-04-16 14:34, Reindl Harald wrote: >>> moving from imap-sent folder to a local-folder don't break it see >>> diff from the this way "saved" orginal sent and the broken one >>> >>> this is the source-tarball and one of the last important patches >>> how dbmail is built here >>> https://access.thelounge.net/harry/dbmail-sources.zip >>> >>> dbmail.spec from the rpmbuild also attached >>> >>> >>> Am 16.04.2018 um 14:29 schrieb Reindl Harald: >>>> sorry for the mail-flood - but i will try to move it now to a >>>> local folder - i think the breakage to the sent message happens >>>> instantly but thunderbird before moveing it shows some caching >>>> where it is fine and not put through dbmail re-construct >>>> >>>> good question if this also happens when move it straight to a >>>> local folder >>>> >>>> Am 16.04.2018 um 14:24 schrieb Reindl Harald: >>>>> this message was broken too while the sent message was green >>>>> until i moved it with drag&drop from sent to the dbmail >>>>> folder with the intention to make a diff >>>>> >>>>> now for both copies enigmail says "wrong signature" >>>>> >>>>> Am 16.04.2018 um 14:09 schrieb Reindl Harald: >>>>>> Am 16.04.2018 um 13:48 schrieb Thomas Raschbacher: >>>>>>> do you have that problem vor every signed email, or just >>>>>>> occasionally? cuz i haven't noticed problems on my part >>>>>>> yet >>>>>> >>>>>> hard to say, but on enough that i stopped using Enigmail >>>>>> long ago when neraly every list message i wrote came back >>>>>> with broken signature in case i used GPG/Mime meaning >>>>>> "signature.asc" attached instead inline signing >>>>>> >>>>>> for me at that time it wasn't clear that it's my own >>>>>> mailserver running dbmail-1.3 and not the list servers >>>>>> which are breaking something but the diff you can see is >>>>>> the outbound mail of someone which used dbamil himself and >>>>>> switched to dovecot directly copied from his dovecot-imap >>>>>> compared to my broken received one >>>>>> >>>>>>> On 2018-04-01 13:14, Reindl Harald wrote: >>>>>>>> ping - see also attached as diff >>>>>>>> >>>>>>>> if someone is able to fix that for dbmail-3.1 i offer >>>>>>>> to pay the work >>>>>>>> >>>>>>>> 2874f497fb429ed139e94342ca1c84325b20b3f1 is the git >>>>>>>> with latest fixes for 3.1 before move to github - not >>>>>>>> sure if they ever made it to a offical release and we >>>>>>>> applied the patch from paul (also attached) >>>>>>>> >>>>>>>> frankly i would sell my soul when dbmail get active >>>>>>>> maintainment again because the silence of the last few >>>>>>>> years holds me back to consider upgrade to 3.2 given >>>>>>>> that upgrades to 3.0 and 3.1 in both cases needed a lot >>>>>>>> of urgency patches after user complaints with several >>>>>>>> clients mostly re-construct errors _______________ >>>>>>>> >>>>>>>> * Mi Dez 07 2016 Reindl Harald <[email protected]> >>>>>>>> - add dbmail-prepend-headers-during-delivery.patch >>>>>>>> >>>>>>>> * Mi Jan 20 2016 Reindl Harald <[email protected]> >>>>>>>> - update to 2874f497fb429ed139e94342ca1c84325b20b3f1 >>>>>>>> bugfix snapshot - prevent assertion in p_string_erase >>>>>>>> >>>>>>>> * So Jul 27 2014 Reindl Harald <[email protected]> >>>>>>>> - update to 3.1.17 release >>>>>>>> >>>>>>>> Am 30.03.2018 um 16:23 schrieb Reindl Harald: >>>>>>>>> dbmail-3.1.17-4.fc26.20171030.rh.2874f497fb429ed139e94342ca1c84325b20b3f1.x86_64 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>> >>>>>>>>> >>>>> >>>>>>>>> >>>> >>>>>>>>> > see screenshot - the linebreak in line 50 seems to change between \r\n >>>>>>>>> and only \n which completly breaks the signature - >>>>>>>>> inline signed mails don't break because they don't >>>>>>>>> have a "signature.asc" attachment >>>>>>>>> >>>>>>>>> the plaintext version shows the same amount of >>>>>>>>> linebreaks, but i have also seen dbmail-3.1 caces >>>>>>>>> where some new lines are added or missing >>>>>>>>> >>>>>>>>> pretty sure at reconstruct where i pointed out some >>>>>>>>> year ago to Paul that sometimes linebreaks change and >>>>>>>>> that could break signed mails while the response was >>>>>>>>> they don't matter > > > _______________________________________________ > DBmail mailing list > [email protected] > http://lists.nfg.nl/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] http://lists.nfg.nl/mailman/listinfo/dbmail
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE62Mx48XBif2bZfwnzmuFS0rK9ToFAlrYPqwACgkQzmuFS0rK 9TrnBQ/+P0OPX4XkLk64Y95sRj2k/YHbCyxMg+cYVlOyEk2p1hzIT3YZTe4IV7DS 82wGLO9xKcbpc2YsBjtT/hYaae5OWTp0Py3+9d48z96B7BQq+SsHim1Xy9jbMRqj pPTE64jrVCV6tdTvLlwM71LE+uOZCp3Y8KzgQAR+Kp43nfJ0GaxU5fRuIaXglumK NQ8Lv6ckHnsEDDYAyTBQ0dhyErgqWWeRvGJrXqtT6HpN57u5eYH2CFY65V2l4zpH 5WWfd5M/bRX/BMk5RfwrFL9FqKv5MAppYCIgjdtOWb3NqRaxEb+LsCDfncIrLWL/ 4FcuX0egrI6F36mKGUFeDugT3y+WiLv7UumXO/vvG0KWFJLLOITKSgsqrCWEzu3b 5r5WAtvY6F0iKpCEJKiCyXpitv898K/lhwuF97SHJSQcaqMaH/Pb5eXTUoz7WDdp TJDZhbqs6fdtxRUKOgLO+I8lLWFFUz6tzzUD49VelcH3aXw1ylyHQGIdOIHvjF7N OsY1htj/dAgZvld8r8qNOcbIAWG1FgtzIu5nFZy0J454TvTaij7x5gK3zH9s2D1K SoqbvKMlQ+wSK0++Tet8U9KcH/93GJB0VxHEwRgZqLQBVQQpZIq18Vaxyvww6nP0 q1N76R/7C3vSLFjjIxy0g8ga7OFxALVaqDCypnD3My9FjGvYlqE= =RpTu -----END PGP SIGNATURE-----