Most dmarc reports from Comcast cannot be read

[tierpod]

Most dmarc reports from Comcast cannot be read

[tierpod]

Hello @vbaarda ! Thank you for report. Could you please attach such xml.gz file with problem for investigation?

[vbaarda]

Hi @tierpod ,

Here's the entire email attachment, including boundary markers:

--_=_swift_v4_1679569616_ff5b7f4f0bf85de1e4715557e5d25910_=_
Content-Type: application/gzip;
 name=comcast.net!centerpointutah.org!1679443200!1679529600.xml.gz
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename=comcast.net!centerpointutah.org!1679443200!1679529600.xml.gz

H4sIAAAAAAAAA41U0Y7aMBB85r4C8U5COLgeks/Xp35B+xwZZxNcEtuynbT9++7aJkcqWlVC4B1P
dnYmK9j7z6FfT+C8MvptUxW7zRq0NI3S3dvm29cv29fN+p0/sRagOQt55U8rlukc2ay8FYg7sMaF
eoAgGhEEQitmXFdrMQCXZpDCh0JDYOWMEgUGoXreDMLJrWgGpT+LHlzwxeKRxCJ+llENn/bb6uXT
6Xioqt1xK0EHcNYoHcYgLgWKsPKDTI/iWFA7obuovGJn6BT6wB6Hw/N+h3YSEi9BN/HquD+90BXV
1KRcdJkl7mwza3olf9V2PPfKXyCLG7Sg+cMx8x3RRHNVA3esTIcIedtGhH4JsNzBd5AYi421/wB8
QqwMvKKp6UBAazhW+E0jP5gPY5XGpUmd+ZEi8GZ0EmpleXV4LTDkosLP/ogy800kSjNqFGRlOkQs
i8Ak+hETi60pBuWt8SrQ0mijAc3fIZlDzq3wHi9zCNFly1vcAjLZJo3ykQi+kmSAqQbDVq3CHU38
C4gGXN06Mzx+EfeEvAUT9MZCgmgJ0X/hQZyqwvnOT3k9F7Q4xB/iTIzhUjvwYx/yNHfe/m854vZT
gxxOLnI80OMGGMevz5jQrUgxzUrsFt0s+VdLC1kv0RwfyB02j8W/55lfEq7t0jjR0qrhPs5/K78B
O6dZ94oEAAA=

--_=_swift_v4_1679569616_ff5b7f4f0bf85de1e4715557e5d25910_=_--

Please note that the attachment and the base64 encoding are fine. I can decode it with uudeview, openssl, and python (email.message.Message.get_payload())

[tierpod]

Yes, I see that attachment looks fine. Unfortunately, upgrading to last stable versions of emersion libraries didn't fix this problem. I can try to investigate it a little deeper, if you send me the whole email file (you can download eml file from gmail and attach it to this topic or sent to my email).

[vbaarda]

Hi @tierpod ,

I will send it to your email address. Nothing super private there, just some email addresses, but would rather not post it here. Subject line will be the URL of this issue. Thanks!

[vbaarda]

@tierpod

I no longer have an environment for testing the fix. You can close this issue if you wish.

[tierpod]

Looks like problem is gone after one more emersion packages update