support of non standard headers ?

Asked by Gael C.

Hello,

Some MTA (like Gmail) use non standard headers for their DKIM signature.

Currently, the DKIM-Signature is hardcoded in the codebase – Is there a plan to open the possibilities ?

For example, the DKIM object could be passed a list of non-standard headers.

If the code were on github, I would probably have forked it and proposed a pull request, but I'm unfamiliar with launchpad.

Regards,
Gael

Question information

Language:
English Edit question
Status:
Answered
For:
dkimpy Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Scott Kitterman (kitterman) said :
#2

As a small project with essentially one very part time developer, it's not feasible to chase everything.

This is a DKIM library, so I think it makes sense for it to support DKIM as standarized (RFC or soon to be RFC) and I think it supports all the standardized extensions.

If you have a suggestion for a change to make it more flexible (including documentation), I'm open to it, but it's not something I'm going to write.

To get the code, go here:

https://code.launchpad.net/dkimpy

I think it's reasonably self-explanatory. It's not on GitHub for multiple reasons that Microsoft is very unlikely to change.

Can you help with this problem?

Provide an answer of your own, or ask Gael C. for more information if necessary.

To post a message you must log in.