I have found the cause of the DKIM problems. When Mailman unfolds and refolds the DKIM-Signature header it replaces tabs with spaces. This makes the difference between a message that passes according to /usr/bin/dkimproxy-verify (part of the libmail-dkim-perl package) and one that fails. Is anyone here any good at Python who can have a look at this? Some special case code to use tabs for the DKIM-Signature header should solve these problems without causing any other problems. Note that a problem that was reported in the past was Mailman replacing spaces with tabs when folding the Subject header. Obviously we don't want to regenerate that problem so changing the behavior of all headers would be a bad thing. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
Hello Russell, On Sat, 2015-10-17 at 20:46 +1100, Russell Coker wrote:
I have found the cause of the DKIM problems. When Mailman unfolds and refolds the DKIM-Signature header it replaces tabs with spaces. This makes the difference between a message that passes according to /usr/bin/dkimproxy-verify (part of the libmail-dkim-perl package) and one that fails.
Is anyone here any good at Python who can have a look at this? Some special case code to use tabs for the DKIM-Signature header should solve these problems without causing any other problems.
Note that a problem that was reported in the past was Mailman replacing spaces with tabs when folding the Subject header. Obviously we don't want to regenerate that problem so changing the behavior of all headers would be a bad thing.
Sounds like the issue is to configure Mailman to leave spaces as spaces, and tabs as tabs, if possible. There may be a standard as to whether the headers should have spaces, or tabs, but I would expect that conformance by the mail readers would be more in the breach than being correct, especially in the light of Outhouse (outlook). Regards, Mark Trickett
On Sat, 17 Oct 2015 09:43:01 PM Mark Trickett wrote:
Note that a problem that was reported in the past was Mailman replacing spaces with tabs when folding the Subject header. Obviously we don't want to regenerate that problem so changing the behavior of all headers would be a bad thing.
Sounds like the issue is to configure Mailman to leave spaces as spaces, and tabs as tabs, if possible. There may be a standard as to whether the headers should have spaces, or tabs, but I would expect that conformance by the mail readers would be more in the breach than being correct, especially in the light of Outhouse (outlook).
The way Mailman works is that it parses the headers and then re-folds them to write the message. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802047 I've filed a bug report requesting special-case handling of the DKIM header in Mailman. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802048 I've filed a bug report about the way libmail-dkim-perl handles this (it should be able to treat space and tab the same). -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On 17 October 2015 at 07:24, Russell Coker <russell@coker.com.au> wrote:
The way Mailman works is that it parses the headers and then re-folds them to write the message.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802047
I've filed a bug report requesting special-case handling of the DKIM header in Mailman.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802048
I've filed a bug report about the way libmail-dkim-perl handles this (it should be able to treat space and tab the same).
It looks like Mailman 2.1.19 has many additions to help with DMARC. https://mail.python.org/pipermail/mailman-announce/2015-January/000198.html The current server looks like it is running 2.1.15. Does Debian have 2.1.19 in backports or similar? Sean
-- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
Thanks for the information. I think it's time to upgrade the server to Jessie. On October 17, 2015 11:31:40 PM GMT+11:00, Sean Crosby <richardnixonshead@gmail.com> wrote:
On 17 October 2015 at 07:24, Russell Coker <russell@coker.com.au> wrote:
The way Mailman works is that it parses the headers and then re-folds
them
to write the message.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802047
I've filed a bug report requesting special-case handling of the DKIM header in Mailman.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802048
I've filed a bug report about the way libmail-dkim-perl handles this (it should be able to treat space and tab the same).
It looks like Mailman 2.1.19 has many additions to help with DMARC.
https://mail.python.org/pipermail/mailman-announce/2015-January/000198.html
The current server looks like it is running 2.1.15. Does Debian have 2.1.19 in backports or similar?
Sean
-- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
------------------------------------------------------------------------
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
-- Sent from my Samsung Galaxy Note 3 with K-9 Mail.
participants (3)
-
Mark Trickett -
Russell Coker -
Sean Crosby