Re: FW: Validation failure signature crypto failed

2017-01-24 Thread A. Schulze via Unbound-users
Am 24.01.2017 um 22:11 schrieb Jac Backus: > But for mail.crypsys.nl dnsviz.net shows only an A record, but no TXT record: http://dnsviz.net/d/mail.crypsys.nl/dnssec/ - click "update now" - click "Advanced options (forced ancestor analysis, recursive, explicit delegation, etc.)" - select

Re: FW: Validation failure signature crypto failed

2017-01-24 Thread A. Schulze via Unbound-users
Am 24.01.2017 um 16:56 schrieb W.C.A. Wijngaards via Unbound-users: > It means that the contents of the TXT record have been altered, and the > text in it does not match the RRSIG digital signature. If this was a > spurious technical failure, it could be due to upper/lowercase somehow >

Re: FW: Validation failure signature crypto failed

2017-01-24 Thread W.C.A. Wijngaards via Unbound-users
Hi Jac, I don't really know about postfix or email, but 'signature crypto failed' means that the data did not match the signature. Thus SERVFAIL is the correct rcode. It means that the contents of the TXT record have been altered, and the text in it does not match the RRSIG digital signature.

FW: Validation failure signature crypto failed

2017-01-24 Thread Jac Backus via Unbound-users
Hello, I have a FreeBSD server with Unbound .1.5.7 as a resolver. I use Postfix for mail and postfix-policyd-spf-perl to check spf. My problem is, that mail from a certain domain is refused. When I test, I see this: # perl /usr/local/libexec/postfix-policyd-spf-perl