Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DKIM auth_only #44

Open
Safari77 opened this issue Nov 8, 2015 · 3 comments
Open

DKIM auth_only #44

Safari77 opened this issue Nov 8, 2015 · 3 comments

Comments

@Safari77
Copy link

Safari77 commented Nov 8, 2015

with "auth_only = yes", rmilter does not add dkim in these cases:

  1. user connects to postfix submission port and authenticates using certificate
  2. local user executes /usr/sbin/sendmail.postfix (e.g., using mutt)

For 1) , can a feature in rmilter be implemented that checks {cert_subject}, since postfix does not write
{auth_authen} into milter? I have allowed only postfix to access rmilter at 127.0.0.1:6666 .

  1. ... this sucks, milter protocol sucks

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@vstakhov
Copy link
Owner

Cert subject might be setup by a remote connection as well if it is trusted (e.g. by means of DANE or PKI). Hence, this value cannot be used. Moreover, the auth_ssf macro that specifies some mystery 'encryption bits' by sendmail, is not presented in Postfix. Therefore, I see no ways how to solve your problem without deep patching of MTA. The only thing I do is to setup special map of ip networks for which all mail should be signed regardless authentication.

@basbebe
Copy link

basbebe commented Dec 25, 2015

I had the same problem – took me some time to figure out that I could try auth_only = no;
Logging would be appreciated

@vstakhov
Copy link
Owner

There is now option called sign_networks which is intended to contain IP or networks for which rmilter should perform DKIM signing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants