Mailing List Archive

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 <h.reindl@thelounge.net>
- add dbmail-prepend-headers-during-delivery.patch

* Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net>
- update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix snapshot
- prevent assertion in p_string_erase

* So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net>
- 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

do you have that problem vor every signed email, or just occasionally?
cuz i haven't noticed problems on my part yet

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 <h.reindl@thelounge.net>
> - add dbmail-prepend-headers-during-delivery.patch
>
> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net>
> - update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix snapshot
> - prevent assertion in p_string_erase
>
> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net>
> - 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
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail

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 <h.reindl@thelounge.net> - add
>> dbmail-prepend-headers-during-delivery.patch
>>
>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net> - update
>> to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix snapshot -
>> prevent assertion in p_string_erase
>>
>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net> - 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 DBmail@dbmail.org
>> http://lists.nfg.nl/mailman/listinfo/dbmail

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 <h.reindl@thelounge.net> - add
>>> dbmail-prepend-headers-during-delivery.patch
>>>
>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net> -
>>> update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix
>>> snapshot - prevent assertion in p_string_erase
>>>
>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net> -
>>> 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 DBmail@dbmail.org
>>> http://lists.nfg.nl/mailman/listinfo/dbmail

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 <h.reindl@thelounge.net> - add
>>>> dbmail-prepend-headers-during-delivery.patch
>>>>
>>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net> -
>>>> update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix
>>>> snapshot - prevent assertion in p_string_erase
>>>>
>>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net> -
>>>> 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

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 <h.reindl@thelounge.net> - add
>>>>> dbmail-prepend-headers-during-delivery.patch
>>>>>
>>>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net> -
>>>>> update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix
>>>>> snapshot - prevent assertion in p_string_erase
>>>>>
>>>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net> -
>>>>> 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

hmm ..

I have no such problems with dbmail 3.2.3 (and gmime 2.6.20


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 <h.reindl@thelounge.net> - add
>>>>>> dbmail-prepend-headers-during-delivery.patch
>>>>>>
>>>>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net> -
>>>>>> update to 2874f497fb429ed139e94342ca1c84325b20b3f1 bugfix
>>>>>> snapshot - prevent assertion in p_string_erase
>>>>>>
>>>>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net> -
>>>>>> 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
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail

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 <h.reindl@thelounge.net>
- 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 <h.reindl@thelounge.net>
>>>>>>> - add dbmail-prepend-headers-during-delivery.patch
>>>>>>>
>>>>>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net>
>>>>>>> - update to 2874f497fb429ed139e94342ca1c84325b20b3f1
>>>>>>> bugfix snapshot - prevent assertion in p_string_erase
>>>>>>>
>>>>>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net>
>>>>>>> - 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

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 <h.reindl@thelounge.net>
> - 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 <h.reindl@thelounge.net>
>>>>>>>> - add dbmail-prepend-headers-during-delivery.patch
>>>>>>>>
>>>>>>>> * Mi Jan 20 2016 Reindl Harald <h.reindl@thelounge.net>
>>>>>>>> - update to 2874f497fb429ed139e94342ca1c84325b20b3f1
>>>>>>>> bugfix snapshot - prevent assertion in p_string_erase
>>>>>>>>
>>>>>>>> * So Jul 27 2014 Reindl Harald <h.reindl@thelounge.net>
>>>>>>>> - 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
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail

I'm not sure this is related, and I probably should investigate further
before posting this here, but in my setup, dbmail seems to break DKIM
signatures.

I've seen that mails from booking.com and facebook.com have broken DKIM
signatures according to google's gmail, when forwarded by my mailserver.
This happens both for mail I forward to a gmail mail address, and email
that POPped by gmail. (Where forwarded mail doesn't get delivered because
of DMARC policies)

As I stated, I haven't really investigated, but this could be caused by
dbmail doing any kind of 'normalization' on mail message headers.

Does anyone here know if there an easy way to log raw incoming email
messages for a specific user or from a specific domain? I use a fairly
standard postfix/dbmail setup. Ideally I get to 'record' a DKIM-correct
message, that can be fed into dbmail-lmtp for testing.

I fired up my facebook account, and added a few email addresses to send
mails to my accounts. I found that mails sent to my gmail account directly
differ from the mails I receive with my dbmail server in one important way:
The 'Content-Type; header has a different format.

Sent (and received with gmail):
Content-Type: multipart/alternative;
boundary="b1_67a90b8ff6c9e9d71d8464cdb1c370fc"

As received with a mail client through dbmail:
Content-Type: multipart/alternative;
boundary=b1_a639100bff13cf3e25a329d562f419ee

The difference: It's originally sent as single-line header, but dbmail
touches it and reformats it. Removing the quotes and making it a multi-line
header.

For DKIM I know this is a problem. Facebook (and most other senders) sends
DKIM signatures with the h parameter set to
'Date:To:Subject:From:MIME-Version:Content-Type'. This means that the
signature is calculated on the body and these headers. Therefore any
modifications to these headers are an alteration of the message and cause
DKIM to fail.

I can imagine this could possibly break PGP/MIME, if it checks the
integrity in a similar way.


On Fri, Apr 20, 2018 at 6:14 PM Casper Langemeijer <casper@langemeijer.eu>
wrote:

> I'm not sure this is related, and I probably should investigate further
> before posting this here, but in my setup, dbmail seems to break DKIM
> signatures.
>
> I've seen that mails from booking.com and facebook.com have broken DKIM
> signatures according to google's gmail, when forwarded by my mailserver.
> This happens both for mail I forward to a gmail mail address, and email
> that POPped by gmail. (Where forwarded mail doesn't get delivered because
> of DMARC policies)
>
> As I stated, I haven't really investigated, but this could be caused by
> dbmail doing any kind of 'normalization' on mail message headers.
>
> Does anyone here know if there an easy way to log raw incoming email
> messages for a specific user or from a specific domain? I use a fairly
> standard postfix/dbmail setup. Ideally I get to 'record' a DKIM-correct
> message, that can be fed into dbmail-lmtp for testing.
>

the header mangeling is gmime
https://bugzilla.gnome.org/show_bug.cgi?id=776825
ftp://ftp.gnome.org/pub/GNOME/sources/gmime/3.0/

DKIM verifyication/scoring normally happens before dbmail-lmtpd and
forwardings should also not touch the spilt/reconstruct code

as far as i can see the GPG breakage happens around the "signature.asc"
with different types of new-lines and headers are typicall not part of
the gpg-signature

aynways, any difference between the inbound message and what you get
back from dbmail is harmful except the headers aded by lmtpd itself on
top (which was also wrong, Return-Path before the patch i requested
where on bottom while every hop touching a mail is supposed to add his
headers on top and don't touch any present headers)

Am 21.04.2018 um 11:01 schrieb Casper Langemeijer:
> I fired up my facebook account, and added a few email addresses to send
> mails to my accounts. I found that mails sent to my gmail account
> directly differ from the mails I receive with my dbmail server in one
> important way: The 'Content-Type; header has a different format.
>
> Sent (and received with gmail):
> Content-Type: multipart/alternative;
> boundary="b1_67a90b8ff6c9e9d71d8464cdb1c370fc"
>
> As received with a mail client through dbmail:
> Content-Type: multipart/alternative;
> boundary=b1_a639100bff13cf3e25a329d562f419ee
>
> The difference: It's originally sent as single-line header, but dbmail
> touches it and reformats it. Removing the quotes and making it a
> multi-line header.
>
> For DKIM I know this is a problem. Facebook (and most other senders)
> sends DKIM signatures with the h parameter set to
> 'Date:To:Subject:From:MIME-Version:Content-Type'. This means that the
> signature is calculated on the body and these headers. Therefore any
> modifications to these headers are an alteration of the message and
> cause DKIM to fail.
>
> I can imagine this could possibly break PGP/MIME, if it checks the
> integrity in a similar way.
>
>
> On Fri, Apr 20, 2018 at 6:14 PM Casper Langemeijer
> <casper@langemeijer.eu <mailto:casper@langemeijer.eu>> wrote:
>
> I'm not sure this is related, and I probably should investigate
> further before posting this here, but in my setup, dbmail seems to
> break DKIM signatures.
>
> I've seen that mails from booking.com <http://booking.com> and
> facebook.com <http://facebook.com> have broken DKIM signatures
> according to google's gmail, when forwarded by my mailserver. This
> happens both for mail I forward to a gmail mail address, and email
> that POPped by gmail. (Where forwarded mail doesn't get delivered
> because of DMARC policies)
>
> As I stated, I haven't really investigated, but this could be caused
> by dbmail doing any kind of 'normalization' on mail message headers.
>
> Does anyone here know if there an easy way to log raw incoming email
> messages for a specific user or from a specific domain? I use a
> fairly standard postfix/dbmail setup. Ideally I get to 'record' a
> DKIM-correct message, that can be fed into dbmail-lmtp for testing
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail

well, and here we are back at the bad or non existing maintainance state
of dbmail: configure: error: Unable to locate gmime development files

[builduser@testserver:~]$ rpm -qa | grep gmime
gmime-devel-3.0.5-1.fc27.20180421.rh.x86_64
gmime-3.0.5-1.fc27.20180421.rh.x86_64

Am 21.04.2018 um 12:35 schrieb Reindl Harald:
> the header mangeling is gmime
> https://bugzilla.gnome.org/show_bug.cgi?id=776825
> ftp://ftp.gnome.org/pub/GNOME/sources/gmime/3.0/
>
> DKIM verifyication/scoring normally happens before dbmail-lmtpd and
> forwardings should also not touch the spilt/reconstruct code
>
> as far as i can see the GPG breakage happens around the "signature.asc"
> with different types of new-lines and headers are typicall not part of
> the gpg-signature
>
> aynways, any difference between the inbound message and what you get
> back from dbmail is harmful except the headers aded by lmtpd itself on
> top (which was also wrong, Return-Path before the patch i requested
> where on bottom while every hop touching a mail is supposed to add his
> headers on top and don't touch any present headers)
>
> Am 21.04.2018 um 11:01 schrieb Casper Langemeijer:
>> I fired up my facebook account, and added a few email addresses to send
>> mails to my accounts. I found that mails sent to my gmail account
>> directly differ from the mails I receive with my dbmail server in one
>> important way: The 'Content-Type; header has a different format.
>>
>> Sent (and received with gmail):
>> Content-Type: multipart/alternative;
>> boundary="b1_67a90b8ff6c9e9d71d8464cdb1c370fc"
>>
>> As received with a mail client through dbmail:
>> Content-Type: multipart/alternative;
>> boundary=b1_a639100bff13cf3e25a329d562f419ee
>>
>> The difference: It's originally sent as single-line header, but dbmail
>> touches it and reformats it. Removing the quotes and making it a
>> multi-line header.
>>
>> For DKIM I know this is a problem. Facebook (and most other senders)
>> sends DKIM signatures with the h parameter set to
>> 'Date:To:Subject:From:MIME-Version:Content-Type'. This means that the
>> signature is calculated on the body and these headers. Therefore any
>> modifications to these headers are an alteration of the message and
>> cause DKIM to fail.
>>
>> I can imagine this could possibly break PGP/MIME, if it checks the
>> integrity in a similar way.
>>
>>
>> On Fri, Apr 20, 2018 at 6:14 PM Casper Langemeijer
>> <casper@langemeijer.eu <mailto:casper@langemeijer.eu>> wrote:
>>
>> I'm not sure this is related, and I probably should investigate
>> further before posting this here, but in my setup, dbmail seems to
>> break DKIM signatures.
>>
>> I've seen that mails from booking.com <http://booking.com> and
>> facebook.com <http://facebook.com> have broken DKIM signatures
>> according to google's gmail, when forwarded by my mailserver. This
>> happens both for mail I forward to a gmail mail address, and email
>> that POPped by gmail. (Where forwarded mail doesn't get delivered
>> because of DMARC policies)
>>
>> As I stated, I haven't really investigated, but this could be caused
>> by dbmail doing any kind of 'normalization' on mail message headers.
>>
>> Does anyone here know if there an easy way to log raw incoming email
>> messages for a specific user or from a specific domain? I use a
>> fairly standard postfix/dbmail setup. Ideally I get to 'record' a
>> DKIM-correct message, that can be fed into dbmail-lmtp for testing
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail

I've started working on porting dbmail to gmime3. My work is public, but not finished.
https://github.com/langemeijer/dbmail/tree/upgrade-to-gmime3 (https://link.getmailspring.com/link/1524473037.local-204e8f4e-7406-v1.2.1-7e7447b6@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Flangemeijer%2Fdbmail%2Ftree%2Fupgrade-to-gmime3&recipient=ZGJtYWlsQGRibWFpbC5vcmc%3D)

I am not a C developer by profession, and I lack experience. Most of the work I do on dbmail will be trivial coding though. There are some changes that require a little more work on dbmail source code, but I think it's not to big for me to handle.

I would very much appreciate it if someone could review my work when it's done. Meeting face-to-face would have my preference over working online.
On Apr 21 2018, at 12:44 pm, Reindl Harald <h.reindl@thelounge.net> wrote:
>
> well, and here we are back at the bad or non existing maintainance state
> of dbmail: configure: error: Unable to locate gmime development files
>
> [builduser@testserver:~]$ rpm -qa | grep gmime
> gmime-devel-3.0.5-1.fc27.20180421.rh.x86_64
> gmime-3.0.5-1.fc27.20180421.rh.x86_64
>
> Am 21.04.2018 um 12:35 schrieb Reindl Harald:
> > the header mangeling is gmime
> > https://bugzilla.gnome.org/show_bug.cgi?id=776825
> > ftp://ftp.gnome.org/pub/GNOME/sources/gmime/3.0/
> >
> > DKIM verifyication/scoring normally happens before dbmail-lmtpd and
> > forwardings should also not touch the spilt/reconstruct code
> >
> > as far as i can see the GPG breakage happens around the "signature.asc"
> > with different types of new-lines and headers are typicall not part of
> > the gpg-signature
> >
> > aynways, any difference between the inbound message and what you get
> > back from dbmail is harmful except the headers aded by lmtpd itself on
> > top (which was also wrong, Return-Path before the patch i requested
> > where on bottom while every hop touching a mail is supposed to add his
> > headers on top and don't touch any present headers)
> >
> > Am 21.04.2018 um 11:01 schrieb Casper Langemeijer:
> > > I fired up my facebook account, and added a few email addresses to send
> > > mails to my accounts. I found that mails sent to my gmail account
> > > directly differ from the mails I receive with my dbmail server in one
> > > important way: The 'Content-Type; header has a different format.
> > >
> > > Sent (and received with gmail):
> > > Content-Type: multipart/alternative;
> > > boundary="b1_67a90b8ff6c9e9d71d8464cdb1c370fc"
> > >
> > > As received with a mail client through dbmail:
> > > Content-Type: multipart/alternative;
> > > boundary=b1_a639100bff13cf3e25a329d562f419ee
> > >
> > > The difference: It's originally sent as single-line header, but dbmail
> > > touches it and reformats it. Removing the quotes and making it a
> > > multi-line header.
> > >
> > > For DKIM I know this is a problem. Facebook (and most other senders)
> > > sends DKIM signatures with the h parameter set to
> > > 'Date:To:Subject:From:MIME-Version:Content-Type'. This means that the
> > > signature is calculated on the body and these headers. Therefore any
> > > modifications to these headers are an alteration of the message and
> > > cause DKIM to fail.
> > >
> > > I can imagine this could possibly break PGP/MIME, if it checks the
> > > integrity in a similar way.
> > >
> > >
> > > On Fri, Apr 20, 2018 at 6:14 PM Casper Langemeijer
> > > <casper@langemeijer.eu <mailto:casper@langemeijer.eu>> wrote:
> > >
> > > I'm not sure this is related, and I probably should investigate
> > > further before posting this here, but in my setup, dbmail seems to
> > > break DKIM signatures.
> > >
> > > I've seen that mails from booking.com <http://booking.com> and
> > > facebook.com <http://facebook.com> have broken DKIM signatures
> > > according to google's gmail, when forwarded by my mailserver. This
> > > happens both for mail I forward to a gmail mail address, and email
> > > that POPped by gmail. (Where forwarded mail doesn't get delivered
> > > because of DMARC policies)
> > >
> > > As I stated, I haven't really investigated, but this could be caused
> > > by dbmail doing any kind of 'normalization' on mail message headers.
> > >
> > > Does anyone here know if there an easy way to log raw incoming email
> > > messages for a specific user or from a specific domain? I use a
> > > fairly standard postfix/dbmail setup. Ideally I get to 'record' a
> > > DKIM-correct message, that can be fed into dbmail-lmtp for testing
> >
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://lists.nfg.nl/mailman/listinfo/dbmail
>

Hmm i don't mind doing some review.. i have a bit of experience with
gtk/glib stuff and porting from one major version to another (though
mostly related to gtk1 -> gtk2)

face to face could be interesting, but depends on where everyone is
located. (I am in Austria)

On 2018-04-23 11:05, Casper Langemeijer wrote:

> I've started working on porting dbmail to gmime3. My work is public, but not finished.
>
> https://github.com/langemeijer/dbmail/tree/upgrade-to-gmime3 [1]
> I am not a C developer by profession, and I lack experience. Most of the work I do on dbmail will be trivial coding though. There are some changes that require a little more work on dbmail source code, but I think it's not to big for me to handle.
> I would very much appreciate it if someone could review my work when it's done. Meeting face-to-face would have my preference over working online.
> On Apr 21 2018, at 12:44 pm, Reindl Harald <h.reindl@thelounge.net> wrote:
>
> well, and here we are back at the bad or non existing maintainance state
> of dbmail: configure: error: Unable to locate gmime development files
> [builduser@testserver:~]$ rpm -qa | grep gmime
> gmime-devel-3.0.5-1.fc27.20180421.rh.x86_64
> gmime-3.0.5-1.fc27.20180421.rh.x86_64
> Am 21.04.2018 um 12:35 schrieb Reindl Harald:
> the header mangeling is gmime
> https://bugzilla.gnome.org/show_bug.cgi?id=776825
> ftp://ftp.gnome.org/pub/GNOME/sources/gmime/3.0/
> DKIM verifyication/scoring normally happens before dbmail-lmtpd and
> forwardings should also not touch the spilt/reconstruct code
> as far as i can see the GPG breakage happens around the "signature.asc"
> with different types of new-lines and headers are typicall not part of
> the gpg-signature
> aynways, any difference between the inbound message and what you get
> back from dbmail is harmful except the headers aded by lmtpd itself on
> top (which was also wrong, Return-Path before the patch i requested
> where on bottom while every hop touching a mail is supposed to add his
> headers on top and don't touch any present headers)
> Am 21.04.2018 um 11:01 schrieb Casper Langemeijer:
> I fired up my facebook account, and added a few email addresses to send
> mails to my accounts. I found that mails sent to my gmail account
> directly differ from the mails I receive with my dbmail server in one
> important way: The 'Content-Type; header has a different format.
> Sent (and received with gmail):
> Content-Type: multipart/alternative;
> boundary="b1_67a90b8ff6c9e9d71d8464cdb1c370fc"
> As received with a mail client through dbmail:
> Content-Type: multipart/alternative;
> boundary=b1_a639100bff13cf3e25a329d562f419ee
> The difference: It's originally sent as single-line header, but dbmail
> touches it and reformats it. Removing the quotes and making it a
> multi-line header.
> For DKIM I know this is a problem. Facebook (and most other senders)
> sends DKIM signatures with the h parameter set to
> 'Date:To:Subject:From:MIME-Version:Content-Type'. This means that the
> signature is calculated on the body and these headers. Therefore any
> modifications to these headers are an alteration of the message and
> cause DKIM to fail.
> I can imagine this could possibly break PGP/MIME, if it checks the
> integrity in a similar way.
>
> On Fri, Apr 20, 2018 at 6:14 PM Casper Langemeijer
> <casper@langemeijer.eu <mailto:casper@langemeijer.eu>> wrote:
> I'm not sure this is related, and I probably should investigate
> further before posting this here, but in my setup, dbmail seems to
> break DKIM signatures.
> I've seen that mails from booking.com <http://booking.com> and
> facebook.com <http://facebook.com> have broken DKIM signatures
> according to google's gmail, when forwarded by my mailserver. This
> happens both for mail I forward to a gmail mail address, and email
> that POPped by gmail. (Where forwarded mail doesn't get delivered
> because of DMARC policies)
> As I stated, I haven't really investigated, but this could be caused
> by dbmail doing any kind of 'normalization' on mail message headers.
> Does anyone here know if there an easy way to log raw incoming email
> messages for a specific user or from a specific domain? I use a
> fairly standard postfix/dbmail setup. Ideally I get to 'record' a
> DKIM-correct message, that can be fed into dbmail-lmtp for testing

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://lists.nfg.nl/mailman/listinfo/dbmail



Links:
------
[1]
https://link.getmailspring.com/link/1524473037.local-204e8f4e-7406-v1.2.1-7e7447b6@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Flangemeijer%2Fdbmail%2Ftree%2Fupgrade-to-gmime3&amp;recipient=ZGJtYWlsQGRibWFpbC5vcmc%3D