Victor, thank you for your help. It prompted me first to look again at
opendkim.conf and the various files of hosts, which were not entirely
correct. Still one problem left after the corrections which, with your
prompt re: macros, I tracked down to milter_mail_macros = i b in
main.cf, which I
On Wed, Dec 20, 2023 at 03:21:03PM +, Linkcheck via Postfix-users wrote:
>
> > How does your milter decide which messages to sign? Does it perhaps
> > look for:
> >
> > milter_macro_daemon_name=ORIGINATING
>
> I originally had this in place but could find no reason for it online nor
>
Thanks, I've now enabled that.
I'm ptrty sure the reason, though, is the single Received line, which
does (can) not give the domain's signing key from DNS.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
To find out why a milter signs or does not sign, it would be helpful to
see the milter’s configuration. With OpenDKIM, the setting ‘LogWhy yes’
is useful for debugging such issues.
___
Postfix-users mailing list -- postfix-users@postfix.org
To
Thank you for your response, Viktor.
> How does your milter decide which messages to sign? Does it perhaps
look for:
> milter_macro_daemon_name=ORIGINATING
I originally had this in place but could find no reason for it online
nor any sufficient reason to use it, so I removed it, with no
On Tue, Dec 19, 2023 at 04:07:11PM +, Linkcheck via Postfix-users wrote:
> Sort of. I now have a problem where (it seems) ALL authenticated mail is not
> being dkim signed
How does your milter decide which messages to sign? Does it perhaps
look for:
