{"action":"created","issue":{"url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/208","labels_url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/208/labels{/name}","comments_url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/208/comments","events_url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/208/events","html_url":"https://github.com/smtpd/qpsmtpd/issues/208","id":55698108,"number":208,"title":"dkim plugin: Sign for others","user":{"login":"salvis","id":373828,"avatar_url":"https://avatars.githubusercontent.com/u/373828?v=3","gravatar_id":"","url":"https://api.github.com/users/salvis","html_url":"https://github.com/salvis","followers_url":"https://api.github.com/users/salvis/followers","following_url":"https://api.github.com/users/salvis/following{/other_user}","gists_url":"https://api.github.com/users/salvis/gists{/gist_id}","starred_url":"https://api.github.com/users/salvis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/salvis/subscriptions","organizations_url":"https://api.github.com/users/salvis/orgs","repos_url":"https://api.github.com/users/salvis/repos","events_url":"https://api.github.com/users/salvis/events{/privacy}","received_events_url":"https://api.github.com/users/salvis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-28T00:44:39Z","updated_at":"2015-01-29T01:22:29Z","closed_at":"2015-01-28T01:48:37Z","body":"I'm still wrestling with dkim...\r\n\r\nThe doc says\r\n\r\n> **Sign for others**\r\n> \r\n> Following the directions above will configure QP to DKIM sign messages from authenticated senders of example.org. Suppose you host client.com and would like to DKIM sign their messages too? Do that as follows:\r\n> \r\n>  cd ~smtpd/config/dkim\r\n>  ln -s example.org client.com\r\n>\r\n> QP will follow the symlink target and sign client.com emails with the example.org DKIM key.\r\n\r\nI've done that, but I keep getting the signature for example.org (i.e. d=example.org), which means it fails alignment with user@client.com.\r\n\r\nHow can I get d=client.com if the sender is user@client.com?\r\n\r\nHans"},"comment":{"url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/comments/71951999","html_url":"https://github.com/smtpd/qpsmtpd/issues/208#issuecomment-71951999","issue_url":"https://api.github.com/repos/smtpd/qpsmtpd/issues/208","id":71951999,"user":{"login":"salvis","id":373828,"avatar_url":"https://avatars.githubusercontent.com/u/373828?v=3","gravatar_id":"","url":"https://api.github.com/users/salvis","html_url":"https://github.com/salvis","followers_url":"https://api.github.com/users/salvis/followers","following_url":"https://api.github.com/users/salvis/following{/other_user}","gists_url":"https://api.github.com/users/salvis/gists{/gist_id}","starred_url":"https://api.github.com/users/salvis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/salvis/subscriptions","organizations_url":"https://api.github.com/users/salvis/orgs","repos_url":"https://api.github.com/users/salvis/repos","events_url":"https://api.github.com/users/salvis/events{/privacy}","received_events_url":"https://api.github.com/users/salvis/received_events","type":"User","site_admin":false},"created_at":"2015-01-29T01:22:29Z","updated_at":"2015-01-29T01:22:29Z","body":"Now it works like a charm, thank you!\r\n\r\nIn my case, client.com is my domain, too, and it doesn't make much sense to have different keys, but I didn't realize that dkim was so smart to differentiate between following the symlink and having a real directory.\r\n\r\nThe documentation seemed to suggest that you could configure DMARC to get the unaligned DKIM to pass, but I don't think this is true. I've posted a pull request with a doc update.\r\n\r\nHans"}}