Untitled

DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.example.com 287A320BB2C
Date: Thu, 13 Jul 2017 12:24:10 -0400
From: auth-results@verifier.port25.com
To: oleksandr@example.com
Subject: Authentication Report
Message-Id: <1499963048-634214@verifier.port25.com>
Precedence: junk (auto_reply)
In-Reply-To: <1607288.e7jaYuyJD9@example.com>

This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com.  The service allows email senders to perform
a simple check of various sender authentication mechanisms.  It is provided
free of charge, in the hope that it is useful to the email community.  While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DKIM check:         fail
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname:  vulcan.example.com
Source IP:      1.2.3.4
mail-from:      oleksandr@example.com

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=oleksandr@example.com

DNS record(s):
    example.com. 3600 IN TXT "v=spf1 ip4:1.2.3.4 ip6:2001:a:b:c:d:e:f:0 mx -all"
    example.com. 3600 IN TXT "yandex-verification: 797fca4c7fe0b971"


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         fail (signature doesn't verify)
ID(s) verified:

Canonicalized Headers:
    from:Oleksandr'20'Natalenko'20'<oleksandr@example.com>'0D''0A'
    subject:bad'20'letter'0D''0A'
    date:Thu,'20'13'20'Jul'20'2017'20'18:24:06'20'+0200'0D''0A'
    message-id:<1607288.e7jaYuyJD9@example.com>'0D''0A'
    to:check-auth@verifier.port25.com'0D''0A'
    mime-version:1.0'0D''0A'
    content-type:text/plain;'20'charset="utf-8"'0D''0A'
    content-transfer-encoding:7Bit'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=example.com;'20's=dkim-20170712;'20't=1499963047;'20'h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding;'20'bh=Ss9bCWAg7WbklSeflA/G2W86zuVUtRcU0GiO0VrTDTw=;'20'b=

Canonicalized Body:
    letter'20'body'0D''0A'


DNS record(s):
    dkim-20170712._domainkey.example.com. 3356 IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGNgqaYVVs35YySpI4n151IFQQpj0Cr/HysLWC5bpr0a+JRHbI4ilE3/anq3H6K7hRcOGeOC7hOxCCHdVXQY+h7KKRs9qQqv+UsWlWSGqCaufSVdEil5P3I98x6vqJvlxUMFlSmdFU6Jlt0q6BEQ2YtFRYBFnmaYjqNpRKBO2XdwIDAQAB"

Public key used for verification: dkim-20170712._domainkey.example.com (1024 bits)

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.4.1 (2015-04-28)

Result:         ham (0.9 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 NO_DNS_FOR_FROM        DNS: Envelope sender has no MX or A DNS records
 0.8 DKIM_ADSP_ALL          No valid author signature, domain signs all mail
-0.0 T_RP_MATCHES_RCVD      Envelope sender domain matches handover relay
                            domain
 0.0 T_SPF_TEMPERROR        SPF: test of record failed (temperror)
 0.0 T_SPF_HELO_TEMPERROR   SPF: test of HELO record failed (temperror)
-0.0 BAYES_20               BODY: Bayes spam probability is 5 to 20%
                            [score: 0.0515]
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
 0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid


==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================

SPF and Sender-ID Results
=========================

"none"
      No policy records were published at the sender's DNS domain.

"neutral"
      The sender's ADMD has asserted that it cannot or does not
      want to assert whether or not the sending IP address is authorized
      to send mail using the sender's DNS domain.

"pass"
      The client is authorized by the sender's ADMD to inject or
      relay mail on behalf of the sender's DNS domain.

"policy"
     The client is authorized to inject or relay mail on behalf
      of the sender's DNS domain according to the authentication
      method's algorithm, but local policy dictates that the result is
      unacceptable.

"fail"
      This client is explicitly not authorized to inject or
      relay mail using the sender's DNS domain.

"softfail"
      The sender's ADMD believes the client was not authorized
      to inject or relay mail using the sender's DNS domain, but is
      unwilling to make a strong assertion to that effect.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability to
      retrieve a policy record from DNS.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being absent or
      a syntax error in a retrieved DNS TXT record.  A later attempt is
      unlikely to produce a final result.


DKIM and DomainKeys Results
===========================

"none"
      The message was not signed.

"pass"
      The message was signed, the signature or signatures were
      acceptable to the verifier, and the signature(s) passed
      verification tests.

"fail"
      The message was signed and the signature or signatures were
      acceptable to the verifier, but they failed the verification
      test(s).

"policy"
      The message was signed but the signature or signatures were
      not acceptable to the verifier.

"neutral"
      The message was signed but the signature or signatures
      contained syntax errors or were not otherwise able to be
      processed.  This result SHOULD also be used for other
      failures not covered elsewhere in this list.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability
      to retrieve a public key.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being
      absent. A later attempt is unlikely to produce a final result.


==========================================================
Original Email
==========================================================

Return-Path: <oleksandr@example.com>
Received: from vulcan.example.com (1.2.3.4) by verifier.port25.com id hcufag2bkd06 for <check-auth@verifier.port25.com>; Thu, 13 Jul 2017 12:24:08 -0400 (envelope-from <oleksandr@example.com>)
Authentication-Results: verifier.port25.com; spf=pass  smtp.mailfrom=oleksandr@example.com;
 dkim=fail reason="signature doesn't verify"
Received: from spock.localnet (unknown [IPv6:2001:a:b:c:d:e:f:0])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vulcan.example.com (Postfix) with ESMTPSA id 8839B20BB27
	for <check-auth@verifier.port25.com>; Thu, 13 Jul 2017 18:24:07 +0200 (CEST)
DMARC-Filter: OpenDMARC Filter v1.3.2 vulcan.example.com 8839B20BB27
Authentication-Results: vulcan.example.com; dmarc=fail (p=none dis=none) header.from=example.com
From: Oleksandr Natalenko <oleksandr@example.com>
To: check-auth@verifier.port25.com
Subject: bad letter
Date: Thu, 13 Jul 2017 18:24:06 +0200
Message-ID: <1607288.e7jaYuyJD9@example.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com;
	s=arc-20170712; t=1499963047;
	h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding;
	bh=Ss9bCWAg7WbklSeflA/G2W86zuVUtRcU0GiO0VrTDTw=;
	b=IwYx+IUVxn8o5PG4VCxBvSxeP7z0s5juznFM2Yw/lId2PqlAXXLHbD7cRYhjNbJchnIU3n
	ld/ltSrmwtr41shBbDkGI99nilimrH60f2D2GUPZxC2rsvvOUvekAU83kNaUIBLMLwIBwV
	9dISq1gK3msz2ln8Klq8Y/NkHEB1rRY=
ARC-Seal: i=1; s=arc-20170712; d=example.com; t=1499963047; a=rsa-sha256;
	cv=none;
	b=saKKzveUQe9fj3x4otNnw9Or3qJpcPGMAVXLIrJRKqZxjTAF50RFAWZS4BO3AnUgvQXLle8etujmbxjZHZW61ye17cW0GJ6etzDHRuOEOqlfMq+pqTUf6DIeqwOqPv9jk3JO7NhXH7lPuwzo2J9DntYifuXdhOsWh4r0nHqEgAw=
ARC-Authentication-Results: i=1; auth=pass smtp.auth=oleksandr@example.com
	smtp.mailfrom=oleksandr@example.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com;
	s=dkim-20170712; t=1499963047;
	h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding;
	bh=Ss9bCWAg7WbklSeflA/G2W86zuVUtRcU0GiO0VrTDTw=;
	b=Z6k+gBsjmgtUa9Sec4W8pF3n7tVnbaHSIrIFTxVfYS0WmxuczrEL82LebZWGGBvD/b7OPR
	5eqwOv3CtASyzhG30sSRpOBUo9nKfJN1/OUsOiiA2XwW0G12XNA1/RGhsUr+pT6sXu1TRY
	qMP1xHZe2H3OZAkrEi+T6HSxPhQPjSA=

letter body