On 11/13/22 7:43 AM, Kristian Klausen wrote:
On 31.10.2022 15.11, Geert Hendrickx wrote:
Hi,
Thanks for investigating and reporting the issue!
Me and foutrelis[1]has been doing some debugging and after upgrading
mailman3 from 3.3.5-6 -> 3.3.7-1, we are unable to reproduce the issue.
Lookin
On Sun, Nov 13, 2022 at 15:07:20 +0100, Geert Hendrickx wrote:
> On Sun, Nov 13, 2022 at 13:43:03 +0100, Kristian Klausen wrote:
> > P.S. Adding a emoji 😎 to verify that this is indeed fixed at your end.
>
>
> Hi
>
> Your message was base64-encoded (I think by GnuPG), so passes OK anyway.
>
> T
On Sun, Nov 13, 2022 at 13:43:03 +0100, Kristian Klausen wrote:
> P.S. Adding a emoji 😎 to verify that this is indeed fixed at your end.
Hi
Your message was base64-encoded (I think by GnuPG), so passes OK anyway.
Trying again with this shorter message. Tħåñk ÿóú спасибо.
Geert
On 31.10.2022 15.11, Geert Hendrickx wrote:
In the chain sender => list.archlinux.org => list members, I suspect it's
Mailman (on the Arch list server) that does not support 8BITMIME; since
OpenDKIM on that server succesfully verified the DKIM signature, the mail
arrived there as 8bit, but is bei
In the chain sender => list.archlinux.org => list members, I suspect it's
Mailman (on the Arch list server) that does not support 8BITMIME; since
OpenDKIM on that server succesfully verified the DKIM signature, the mail
arrived there as 8bit, but is being distributed to list members as 7-bit.
Coul
On 10/30/22 19:04, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:57 (+0100), Jaron Kent-Dobias wrote:
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
Excellent debugging - congrats for finding the
On Sunday, 30 October 2022 at 23:57 (+0100), Jaron Kent-Dobias wrote:
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
One last email: what the lists are specifically doing is rewriting 8bit
encoded emails in a
On Sunday, 30 October 2022 at 23:56 (+0100), Jaron Kent-Dobias wrote:
Consider this email as a test for what the Arch Liunx lists do: α, β,
γ, …
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
Now to deal wi
On Sunday, 30 October 2022 at 18:52 (-0400), David Rosenstrauch wrote:
On 10/30/22 6:48 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing
the problem?
After a quick google, this a
On 10/30/22 6:48 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing the
problem?
After a quick google, this appears to be a known and old problem:
https://stbuehler.de/blog/articl
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing the
problem?
After a quick google, this appears to be a known and old problem:
https://stbuehler.de/blog/article/2011/05/19/dkim_fails_at_content-transfer-encod
On Sunday, 30 October 2022 at 18:30 (-0400), David Rosenstrauch wrote:
I guess it's working now, so all's well that ends well? But still
really weird.
Maybe not - your latest email also failed DKIM for me. Regarding Genes'
email, python-dkim's 'dkimverify' utility also registers a fail.
One
For what it's worth, I get the same from time to time.
I've blamed my setup and/or OpenDKIM up until this point.
And I will try to evaluate the recommendations from Gene as well as
correlate my error messages with the headers given here.
//Anton
On 10/30/22 23:37, David Rosenstrauch wrote:
On 10/30/22 6:27 PM, Genes Lists wrote:
Hi David / Jaron
One thought - typically dmarc gets dkim validation from a separate
milter dmarc.
And many folks still run opendkim which is unmaintained.
Versions prior to 2.11.0.Beta2 (which arch kindly offers) are definitely
broken. I don't even t
On 10/30/22 6:13 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 17:58 (-0400), David Rosenstrauch wrote:
Anyone know why these fail messages might be happening?
FWIW, my OpenDKIM with default settings flagged your earlier email with
a DKIM fail, but passed this one. The failure
Hi David / Jaron
One thought - typically dmarc gets dkim validation from a separate
milter dmarc.
And many folks still run opendkim which is unmaintained.
Versions prior to 2.11.0.Beta2 (which arch kindly offers) are definitely
broken. I don't even trust that one.
Jaron do you run opendk
On Sunday, 30 October 2022 at 17:58 (-0400), David Rosenstrauch wrote:
After posting a message to this list earlier today, I immediately
received nearly a dozen DKIM fail messages, all being sent by the
"OpenDMARC Filter" at various domains, and all saying that the DKIM
fail
After posting a message to this list earlier today, I immediately
received nearly a dozen DKIM fail messages, all being sent by the
"OpenDMARC Filter" at various domains, and all saying that the DKIM fail
reason was "signature verification failed".
I raised this issu
18 matches
Mail list logo
