| |||||||||||||||||||||||||||||||
|
Hash: SHA1 Hi @ll, i have a postfix 2.4.0 server as relay for a few exchange servers on dyn ips auth via sasl. now i integrated dkim-milter-0.6.3 with smtpd_milters = inet:localhost:8891 non_smtpd_milters = inet:localhost:8891 milter_default_action = tempfail milter_protocol = 2 /usr/bin/dkim-filter -u postfix -l -c relaxed -p inet:8891@localhost -d example.de -k /etc/domainkeys/mail.private -s mail this works nice as long as use a thunderbird with sasl password but if some server ( one of them is in $mynetworks ) relays mail via sasl i get a message like dkim-filter[8919]: (unknown-jobid) external host unknown attempted to send as ... which seems to be a work as designed message (no bug etc) i posted to the dkim-milter list and sombody said it may be fixed with parameters -m mta [,...] A comma-separated list of MTA names (a la the sendmail(8) Dae- monPortOptions Name parameter) whose mail should be signed by this filter. There is no default. - -M macro[=value][,...] Defines a set of MTA-provided macros which should be checked to see if the sender has been determined to be a local user and therefore whether or not the message should be signed. If a value is specified, the value of the macro must match the value specified (matching is case-insensitive), otherwise the macro must be defined but may contain any value. The set is empty by default. - -I eilist Identifies a file of "external" hosts which may send mail through the server as one of the signing domains without creden- tials as such. Basically suppresses the "external host (host- name) tried to send mail as (domain)" log messages. Entries in the eilist file should be of the same form as those of the -a option above. The list is empty by default. my tip goes to -M macro , when i look to http://postfix.sectoor.de/MILTER_README.html#macros there might be a match to sasl auth, but i am unclear how to use -M in this context. i found http://www.ijs.si/software/amavisd/amavisd-new-docs.html#dkim which should fix the problem in another way ( but i have to study this first ) anybody outside who has an equal setup and knows how to fix the problem in a elegant way? - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGHrzyfGH2AvR16oERApYIAJwIxXjyVh7EHnVFpNM9Wdz0jXmnXACdEOXK h5Lmw1+qjQiZo+GoDKwIrVw= =92Wx -----END PGP SIGNATURE-----
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com