554: 5.2.0 MXIN603 DMARC validation failed.

kostenzer · 13 apr 2020

Hallo,

Stuur ik een mail naar HHH@home.nl gaat dat zonder problemen.
Stuur ik een mail naar xxx@ziggo.nl krijg ik Failure notice en 554: 5.2.0 MXIN603 DMARC validation failed.

home.nl is de voorloper van ziggo.nl

De complete teksten staan hier onder. E-mailadressen zijn vervangen door XXX , YYY wn HHH. Deze zijn in werkelijkheid alle drie totaal verschillend.

Code:

Sorry, we were unable to deliver your message to the following address.

<XXX@ziggo.nl>:
554: 5.2.0 MXIN603 DMARC validation failed. 

--- Below this line is a copy of the message.

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1586766893; bh=THP4iyOOZhwMFSLl7C/IgsmDVETDYXOioorxhL2lbLw=; h=To:From:Subject:Date:References:From:Subject; b=QKDYab1MesdKdMrlbbUEsOM+wT/QzvxwHmUgEz//JgRa9Usx7ApUmx+RwV8DSqUUm3HdXSaW+FoOGxurLoeYBclPtW7b4lsxZWwdRjrIue2Y5df/5x/JNP54K7yeJwvESH5k7CZVOZp1B8LvP/FIVGkpDdR3/rAIbhF2RzOiEx4SwCCaKkiMMj5GIa+OymtEd/aQPDwBbF7FCjBOufJnDg9Nz0tzAqnzfKQTf4WJcZTgRduPDfTxKL5T/8wr+/ImKIjLoMB51RH549CI8j+1EhsxaYigK9K1bubbPRebb7qn8wTZQjrL+EdziuailR5O8nQW4I+5f1VpsJChlmmXcw==
X-YMail-OSG: LoerEcEVM1lzmDeI3blm8KPeeCsbdRyP5bnMHyLQVtY9DKKcySaRpgBa6_c84DE
 efbj4VdxXHpL9xfXktrKU3ISq8ryuamHQXoEkAaH2fJrP62deJXEv16RiRfUIbDyR9kMTaXJDh1a
 YKE7ZmThtm6ZsZxms2NoU0GMA_.WRjPa66wQ8Crj6hMmsntqEx244_neu9WGO3atBev_wzhoXSan
 WJsBqH_O4kwPvUXEn1V9zACAP9KHbn8PvSzAx.OxowUe0VHupEAnD9VGfoT2IKtzYZVVo31DeVAX
 xtNA4t1NGgUeeDeM1by8yVE_kFHxkr4ucE80btZ5s80V7Z.Q_VFHRwzoTst2mxj2HQrFinjJ7xal
 2Fzj1CAMWrYD_U2Futrn4xqxL2wL5EQ8bi2tcnS1YRWiMdhaQ2I0.cTlotqeboYrDE_c9FnplvEG
 dDmDJRrNX3bteYOaZHoITxN205duQjN_QCLzO5p2wuzr35uQCN5Ckm5PTGyoSjuaLiHhlQG6FkIV
 W4fCWU_XdWAHG8rYDHz8HXr7lzBrs04qVHD63_P4RHZeCJVPAACjmo5Ut94nVpCNkaH3KxOTRJzF
 T61sUYU1.LNm1i_ldCOknfTezd8Adbpec.9..uL3uh.du3CaZGbVE9_Dw82J0ji4rXx64QQhWWaO
 Z_pdfjIsT.O1OACaRvKHVbFy5jr_Yde5O_sqIIdFA9Mn3g2gdvu4Z6uWciUCEIica_gFnWBWhukg
 tMEm27hJ6AYEklepQjVL8NWIcYVWgWgcGPbFRkGj5cCAAQm9BU1CyAW7Rkyp9ZWbEvjJ.CttzM43
 lFAIH1cVDGhMaVM44MO20Rm48vn5fiJgd3jDLiraf.Bcr0XzGlDACpc4YfE3ABD6Y.LoIkQspl91
 VECr3h5XgqqGDwXYM8cK3W1Q5aDbODJXu2v9oWIZoH.3ND.uqoVPR81E1KXw8YbpsAR6ws6qSvf3
 9uQ26nSfaHb3cT5jQOueJibuWMqapxVeQIMrZl.z3XRW8S2T0XWoeqVaJkQICZ.bF3xKHJ3sdig2
 i4LNYCBLg5K44LDOW9gCCI2nPpKCxQZkarbRs7GMnUuOVCx9d9Q35AoOpE30hk48E5GuYgGvvQAy
 2XNLDPkRbNfu0pbRBZ4LPk057STQvZcUANBn0R.Xm_Zsso.wyn7vw9C8K1A.COIPdKTIoHwUROG6
 etsZ.SHBqacXa9Psk8zqgfZx56_Fxv3YSHVma7vb4VNCMQRgXcZgDnF6fF_bxfk0TyRH3SDxSOHc
 nDaPBiNvU21SafGlvG6KgwyvYWmNeRIZV1KNC_v8.xyQW9uQhtFz_apzbLQM9QWo1_2hOnQuTciV
 E6W0CSJs1.f7f7OWkfy6219UJCiRvQvE398EUEUl9GHQRgfJ9jZ2c1_UIaqJjYfrLSR.xBMuUtOj
 oUpt9L_IuUO0A5Oy898Jp
Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.bf2.yahoo.com with HTTP; Mon, 13 Apr 2020 08:34:53 +0000
Received: by smtp406.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 0d7a313929f088fce94d851570e93262;
          Mon, 13 Apr 2020 08:34:48 +0000 (UTC)
To:  <XXX@ziggo.nl>
From: <YYY@aol.com>
Subject: Effe testen
Message-ID: <a4f02ba1-1833-8ba2-4c79-79ec1a9e8ebc@aol.com>
Date: Mon, 13 Apr 2020 10:34:45 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------B34F0667FDB5F9F257D94254"
Content-Language: nl
References: <a4f02ba1-1833-8ba2-4c79-79ec1a9e8ebc.ref@aol.com>
X-Mailer: WebService/1.1.15620 hermes Apache-HttpAsyncClient/4.1.4 (Java/11.0.6)
Content-Length: 740

This is a multi-part message in MIME format.
--------------B34F0667FDB5F9F257D94254
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


-- 
Free people use free and independent Thunderbird 
<\"https://www.thunderbird.net/nl//\"> mail

--------------B34F0667FDB5F9F257D94254
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <div class="moz-signature">-- <br>
      Free people use free and independent <a
        href="\&quot;https://www.thunderbird.net/nl//\&quot;">Thunderbird</a>
      mail</div>
  </body>
</html>

--------------B34F0667FDB5F9F257D94254--

Ik las ergens dat een mail versturen naar auth-results@verifier.port25.com er voor zorgt dat je gegevens krijgt.

Code:

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
"iprev" check:      pass
DKIM check:         pass
SpamAssassin check: ham

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

HELO hostname:  sonic304-9.consmr.mail.bf2.yahoo.com
Source IP:      74.6.128.32
mail-from:      YYY@aol.com

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

DNS record(s):
    aim.com. 60 IN TXT "v=spf1 include:aol.com ?all"
    aim.com. 60 IN TXT "spf2.0/pra include:aol.com ?all"
    aol.com. 60 IN TXT "spf2.0/pra ip4:204.29.186.0/23 include:spf.constantcontact.com include:aspmx.sailthru.com include:mail.zendesk.com ~all"
    aol.com. 60 IN TXT "v=spf1 ip4:204.29.186.0/23 include:spf.constantcontact.com include:aspmx.sailthru.com include:mail.zendesk.com include:_ipspf.yahoo.com ~all"
    aol.com. 60 IN TXT "'4a751cdeec084ee2bc9e2cb2e94ba8af'"
    aol.com. 60 IN TXT "knowbe4-site-verification=bc3830115833f4f956e30f506f1da8c8"
    aol.com. 60 IN TXT "facebook-domain-verification=ervjrx9gun9l4uhc6o4d05p65r2824"
    aol.com. 60 IN TXT "google-site-verification=NqM_NKWhteDHiJCOfhlQqKT4nxexIeFRie5MmWA1RBk"
    spf.constantcontact.com. 60 IN TXT "spf2.0/pra ip4:208.75.120.0/22 ~all"
    spf.constantcontact.com. 60 IN TXT "v=spf1 ip4:208.75.120.0/22 ~all"
    aspmx.sailthru.com. 60 IN TXT "v=spf1 ip4:64.34.47.128/27 ip4:64.34.57.192/26 ip4:65.39.215.0/24 ip4:192.64.236.0/24 ip4:192.64.237.0/24 ip4:173.228.155.0/24 ip4:192.64.238.0/24 ip4:204.153.120.0/23 ip4:162.208.119.181 ip4:147.75.65.174 ip4:147.75.65.173 ip4:147.75.98.190 ip4:139.178.64.159 ip4:139.178.64.195 -all"
    mail.zendesk.com. 60 IN TXT "v=spf1 ip4:192.161.144.0/20 ip4:185.12.80.0/22 ip4:96.46.150.192/27 ip4:174.137.46.0/24 ip4:188.172.128.0/20 ip4:216.198.0.0/18 ~all"
    _ipspf.yahoo.com. 60 IN TXT "v=spf1 include:_spf1.yahoo.com include:_spf2.yahoo.com include:_spf3.yahoo.com ~all"
    _spf1.yahoo.com. 60 IN TXT "v=spf1 ip4:27.123.206.0/24 ip4:46.228.39.0/24 ip4:66.163.184.0/21 ip4:66.196.81.0/24 ip4:67.195.22.0/24 ip4:67.195.60.0/24 ip4:67.195.87.0/24 ip4:68.142.230.0/24 ip4:72.30.234.152/29 ip4:72.30.238.0/23 ip4:74.6.128.0/21 ip4:77.238.176.0/22 ip4:87.248.110.0/24 ip4:98.136.164.0/24 ip4:98.136.185.0/24 ip4:98.136.217.0/24 ip4:98.136.218.0/24 ip4:98.137.12.0/24 ip4:98.137.64.0/21 ~all"


----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result:         pass (matches sonic304-9.consmr.mail.bf2.yahoo.com)
ID(s) verified: policy.iprev=74.6.128.32

DNS record(s):
    32.128.6.74.in-addr.arpa. 60 IN PTR sonic304-9.consmr.mail.bf2.yahoo.com.
    sonic304-9.consmr.mail.bf2.yahoo.com. 60 IN A 74.6.128.32


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: YYY@aol.com)
ID(s) verified: header.d=aol.com

Canonicalized Headers:
    to:check-auth@verifier.port25.com'0D''0A'
    from:<YYY@aol.com>'0D''0A'
    date:Sun,'20'12'20'Apr'20'2020'20'18:20:22'20'+0200'0D''0A'
    references:<9a8f016a-c97b-a0dc-c451-30e8901607fc.ref@aol.com>'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=aol.com;'20's=a2048;'20't=1586708426;'20'bh=SKE1AbHy4O172sYSgD5f2I63MTnSjXEAncHLlVp3+1A=;'20'h=To:From:Date:References:From:Subject;'20'b=

Canonicalized Body:
    This'20'is'20'a'20'multi-part'20'message'20'in'20'MIME'20'format.'0D''0A'
    --------------8E4B5BDBF56FC3640CEE5A5D'0D''0A'
    Content-Type:'20'text/plain;'20'charset=utf-8;'20'format=flowed'0D''0A'
    Content-Transfer-Encoding:'20'7bit'0D''0A'
    '0D''0A'
    '0D''0A'
    --'0D''0A'
    Free'20'people'20'use'20'free'20'and'20'independent'20'Thunderbird'0D''0A'
    <\"https://www.thunderbird.net/nl//\">'20'mail'0D''0A'
    '0D''0A'
    --------------8E4B5BDBF56FC3640CEE5A5D'0D''0A'
    Content-Type:'20'text/html;'20'charset=utf-8'0D''0A'
    Content-Transfer-Encoding:'20'7bit'0D''0A'
    '0D''0A'
    <html>'0D''0A'
    '20'<head>'0D''0A'
    '0D''0A'
    '20'<meta'20'http-equiv="content-type"'20'content="text/html;'20'charset=UTF-8">'0D''0A'
    '20'</head>'0D''0A'
    '20'<body>'0D''0A'
    '20'<br>'0D''0A'
    '20'<div'20'class="moz-signature">--'20'<br>'0D''0A'
    '20'Free'20'people'20'use'20'free'20'and'20'independent'20'<a'0D''0A'
    '20'href="\&quot;https://www.thunderbird.net/nl//\&quot;">Thunderbird</a>'0D''0A'
    '20'mail</div>'0D''0A'
    '20'</body>'0D''0A'
    </html>'0D''0A'
    '0D''0A'
    --------------8E4B5BDBF56FC3640CEE5A5D--'0D''0A'
    

DNS record(s):
    a2048._domainkey.aol.com. 60 IN CNAME a2048._domainkey.aol.com.
    a2048._domainkey.aol.com. 60 IN TXT "k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAugjjoWOWXaAXZh5iWdX9a27P6q0EZnjQQdFCplsFnxL85ppilMPGKZc1OA/aQK6bUFTuf4MJKr8JF3mp+O/Eo022W98Yc2JKPFY6PYxb81GWwpXNaQnug6bPVrLaQVJmxC7izdK6F0VmM6oLIiTNGMUVCwVndmDauFb3jFrf2Dgvgy/d9pjGKYEHKkSeYebWcxrGfOEkBAPcHfr0PUqe/hmp7Id6gO6EvMQ1kzyZHVmuJ3TZmpkQA5xY9CyD9f10lZ9MiFv89wM/u/m7ocAmmsk49aPi4DBwXSO8VSpbI5/oulw2SI41CYFgTdDByTvSr4hRjcyc4B3feYdhZ9egdQIDAQAB;"

Public key used for verification: a2048._domainkey.aol.com (2048 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.0 (2014-02-07)

Result:         ham (3.0 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
                            [score: 0.4358]
 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                            (YYY[at]aol.com)
-0.0 RCVD_IN_MSPIKE_H2      RBL: Average reputation (+2)
                            [74.6.128.32 listed in wl.mailspike.net]
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at https://www.dnswl.org/, no
                            trust
                            [74.6.128.32 listed in list.dnswl.org]
 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
-0.0 SPF_PASS               SPF: sender matches SPF record
 0.0 SPF_HELO_NONE          SPF: HELO does not publish an SPF Record
 0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                            domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
 0.2 FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom
                             freemail headers are different
 1.8 MISSING_SUBJECT        Missing Subject: header



==============================================================
Explanation of the possible results (based on RFCs 7601, 7208)
==============================================================


DKIM Results
============

none:  The message was not signed.

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

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

policy:  The message was signed, but some aspect of the signature or
    signatures was not acceptable to the ADMD.

neutral:  The message was signed, but the signature or signatures
    contained syntax errors or were not otherwise able to be
    processed.  This result is also 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.


SPF Results
===========

none:  Either (a) no syntactically valid DNS domain name was extracted from
    the SMTP session that could be used as the one to be authorized, or
    (b) no SPF records were retrieved from the DNS.

neutral:  The ADMD has explicitly stated that it is not asserting whether
    the IP address is authorized.

pass:  An explicit statement that the client is authorized to inject mail
    with the given identity.

fail:  An explicit statement that the client is not authorized to use the
    domain in the given identity.

softfail:  A weak statement by the publishing ADMD that the host is probably
    not authorized.  It has not published a stronger, more definitive policy
    that results in a "fail".

temperror:  The SPF verifier encountered a transient (generally DNS) error
    while performing the check.  A later retry may succeed without further
    DNS operator action.

permerror: The domain's published records could not be correctly interpreted.
    This signals an error condition that definitely requires DNS operator
    intervention to be resolved.


"iprev" Results
===============

pass:  The DNS evaluation succeeded, i.e., the "reverse" and
    "forward" lookup results were returned and were in agreement.

fail:  The DNS evaluation failed.  In particular, the "reverse" and
    "forward" lookups each produced results, but they were not in
    agreement, or the "forward" query completed but produced no
    result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an
    RCODE of 0 (NOERROR) in a reply containing no answers, was
    returned.

temperror:  The DNS evaluation could not be completed due to some
    error that is likely transient in nature, such as a temporary DNS
    error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or
    other error condition resulted.  A later attempt may produce a
    final result.

permerror:  The DNS evaluation could not be completed because no PTR
    data are published for the connecting IP address, e.g., a DNS
    RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR)
    in a reply containing no answers, was returned.  This prevented
    completion of the evaluation.  A later attempt is unlikely to
    produce a final result.




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

Return-Path: <YYY@aol.com>
Received: from sonic304-9.consmr.mail.bf2.yahoo.com (74.6.128.32) by verifier.port25.com id hicvsm2e8s46 for <check-auth@verifier.port25.com>; Sun, 12 Apr 2020 16:20:27 +0000 (envelope-from <YYY@aol.com>)
Authentication-Results: verifier.port25.com; spf=pass  smtp.mailfrom=YYY@aol.com;
 iprev=pass (matches sonic304-9.consmr.mail.bf2.yahoo.com)  policy.iprev=74.6.128.32;
 dkim=pass (matches From: YYY@aol.com)  header.d=aol.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1586708426; bh=SKE1AbHy4O172sYSgD5f2I63MTnSjXEAncHLlVp3+1A=; h=To:From:Date:References:From:Subject; b=FDU+kHuMIrMG4siLvAs9Id9J+OhHPPmXKdQ0pq2KOEOyYe/n9LsfAf1h6L4PSX+pfjjDyzoiz+rcWeB256iG2tx4mY5T9w6euU7ZOK+HhbKtuyMowA1U6JRwO0UKzUbhBRmg9H/DTRFV2JVFpQnGmfkK9NZWR3iHLfSnaA+HwwR54Oc1dEu6cb8VZotyfVf1v29OeEZY0+9aThceA/YGAiG34Rfd3GHnec6yjmtuamAwNk/tbYY42s6RMtC8WG9HTUJ23IiLA+8PBrj3LL1AwmRY2a5WcWKhtpR4LgbbDipDzn8/ncgtYpEM3wrxUQZYdE5OdrYv3J9E6JuEH+DYxw==
X-YMail-OSG: HOV4AMkVM1lhXrASWG0h0jWhphpn2QgvYB_aKrSQoPe2LhIAIi2ny.9UoXrKsVR
 7m5gOKTDergqXb_4lbgsAETnZDHKAjwl2YWZJ8EDlKDulYLhsSmSNVDP7rGK5NrvHtq1y2Sblc6c
 yX7JvC08PrNI_EfU4zSA2twU02N50QDZ6bsMrXvuots4ZuSfIjZt0GTmbyECm849s0MqoqToYCl0
 v.XJoOlJs5IRtAgPyGUNLsUAhmp7nj2IaadEldRvduPuQI8XwD8jkR0PJDmUQXQjNLzgL6Z1Nzpj
 KB9wKg1C.faOK26FZo6Mh_20HBmDfeh3tphXAHsXmiX9lqsuTZ3MyU3vhz5Lvk.A4d7J_Kg_glA2
 EHdA2BtRKi9zyBOO160ptVYaKBTVCSyMoayRBPF3pGLStSamTYU9z2f6pWuP9aUykg3B1di6LBF1
 .LwNRZJUCbYuHpEA1sOHICvq6Hr0hTk2acUuaNMCDPa.3p3_C3e0H9a2gEvuYuKQuxyg_HPfpQUz
 eDjf3qcigHxWjHDdnDrnUDeC6ft_8HlqxL3ie4jsTFgH7aDqoxsxFzGIg7FjTjWvji.NSA5RKxif
 hfBJn5kB5MMdWRbWohJiTwFfGFISwL4VOVFKGCl8uCrRjBWr8w3gT6Lzs6z3GnPjBbUUjAMPLN5R
 2Gh4fUv3csW2NNCvsdfhbjY75XeM_5AW2bdeCoigBimB3J3uAVhM.l2P5HXnA5FN5JZsXUii8so_
 h41IoTD1kZ9_Nf05_SAiUZE2mBI4ajfBSqg0mt.h7S31k0suvKSGpGy4ElFHJmrHqXqOFIOifBhw
 GJF7LjP3X5eTqvbotPb4buIx1I0PZRHFz7fv3z1qIElh_hTl_RwS_jkaWUYN_4SGiREG0YIlP47y
 wpHNrr30an.bzYJi3u_Enrh0IROUBewu6Mcuk6PUlTo9eXXrENKaY3b29nWkR4U077v5gq2tu6gD
 cm67RCv_grAWp76_uKIqQJ4UMCgDPKiznA48HFoPksJPlT3TouGPTDgUIkZkp6Jq0Ugoe0.mNyG3
 jYiibbmcN9fHRq1jR.Ncc9Lm9TiL36KwsrkzAH.sZeorLJSH06LqCL5xV8PXjV4tddgempBD.nLk
 oULiljHrYmiRIVzhnKHRNU2Ir.Ny9rbsUG6LuDdBY_HMHCOWU_27VrN3yI_qAW_otQ7ZmTU.COvn
 UNuvsO_b.838RRCamu2covW9eZNbUwQBEv97jqSn7uq3TPHl9Z9kV89is0q1cxC.i1DKZrGfmMa7
 7lUYwlaDabP3x3AnwsS0HpFTm8IFojO.dC2TBy90j0cUqShOwXhLbUyrJQrSTAe4q7Lejt0AYiES
 1S30YbdMNCYX7ZHfRNTyVsp.WDMf8.NbosdfyDaBi6kNPohu1p2A-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Sun, 12 Apr 2020 16:20:26 +0000
Received: by smtp419.mail.ir2.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a71f2ab0d5abff1c7dfc561b9a7db5aa;
          Sun, 12 Apr 2020 16:20:24 +0000 (UTC)
To: check-auth@verifier.port25.com
From: <YYY@aol.com>
Message-ID: <9a8f016a-c97b-a0dc-c451-30e8901607fc@aol.com>
Date: Sun, 12 Apr 2020 18:20:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------8E4B5BDBF56FC3640CEE5A5D"
Content-Language: nl
References: <9a8f016a-c97b-a0dc-c451-30e8901607fc.ref@aol.com>
X-Mailer: WebService/1.1.15620 hermes Apache-HttpAsyncClient/4.1.4 (Java/11.0.6)
Content-Length: 740

This is a multi-part message in MIME format.
--------------8E4B5BDBF56FC3640CEE5A5D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


-- 
Free people use free and independent Thunderbird 
<\"https://www.thunderbird.net/nl//\"> mail

--------------8E4B5BDBF56FC3640CEE5A5D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <br>
    <div class="moz-signature">-- <br>
      Free people use free and independent <a
        href="\&quot;https://www.thunderbird.net/nl//\&quot;">Thunderbird</a>
      mail</div>
  </body>
</html>

--------------8E4B5BDBF56FC3640CEE5A5D--

Mij zegt dit alles niet veel, om niet te zeggen, bar weinig.

Van Ziggo naar Ziggo, ik zit ook bij Ziggo, lukt wel. Alleen het is na tig jaren de tweede mail die ik via Ziggo verstuurde. Ik zal dat e-mail adres ook verder niet gebruiken.

Zou mooi zijn als iemand er een vinger achter kan krijgen.

mvg

Rob

OctaFish · 13 apr 2020

Je zegt dat je naar verschillende email adressen verstuurt; weet je zeker dat het xxx@ziggo.nl een werkend adres is? Krijg je bijvoorbeeld wel eens een mail van dat adres, en kun je dan wel een reply doen?

kostenzer · 13 apr 2020

Yep.
Ik antwoordde namelijk op de mail van xxx.ziggo.nl en toen kwam Failure notice.

RogerS · 13 apr 2020

En via welke mailserver verstuur je die e-mail? Die DMARC error doet vermoeden dat je niet de Ziggo mailserver hiervoor gebruikt.

kostenzer · 13 apr 2020

Thunderbird?
Dat is namelijk in de stukjes met code ook te vinden.

OctaFish · 13 apr 2020

Een agent is niet hetzelfde als een mailserver.

kostenzer · 13 apr 2020

Dan zou ik het niet weten.
Ik kan gissen.
AOL.com?
Yahoo.com?
Ziggo, als provider?

Scrapheap · 13 apr 2020

Je kunt toch in de accountinstellingen van Thunderbird kijken welke smtp-server daar is ingesteld voor het account waarmee je die mail verstuurt..?

kostenzer · 13 apr 2020

Dan is het smtp.aol.com
Maar naar YYY@ziggo.nl lukt het niet en naar XXX@home.nl (=ziggo) lukt het niet.

dorado · 13 apr 2020

Kijk eens naar mail/serverinstellingen

Van Ziggo naar Ziggo, ik zit ook bij Ziggo, lukt wel

In het rapport staat dat de mail afkomstig is van @aol.com en niet van @ziggo.com

Code:

<XXX@ziggo.nl>:
To:  <XXX@ziggo.nl>
From: <YYY[b]@aol.com[/b]>
References: <a4f02ba1-1833-8ba2-4c79-79ec1a9e8ebc.ref@[b]aol.com[/b]>

Code:

Source IP:      74.6.128.32
mail-from:      YYY]b]@aol.com[/b]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=YYY[b]aol.com[/b]

DNS record(s):
    aim.com. 60 IN TXT "v=spf1 include	:[b]aol.com[/b] ?all"
    aim.com. 60 IN TXT "spf2.0/pra include:[b]aol.com[/b] ?all"
    [b]aol.com[/b]. 60 IN TXT "spf2.0/pra ip4:204.29.186.0/23 include:spf.constantcontact.com include:aspmx.sailthru.com include:mail.zendesk.com ~all"
    [B]aol.com[/B]. 60 IN TXT "v=spf1 ip4:204.29.186.0/23 include:spf.constantcontact.com include:aspmx.sailthru.com include:mail.zendesk.com include:_ipspf.yahoo.com ~all"
    [B]aol.com[/B]. 60 IN TXT "'4a751cdeec084ee2bc9e2cb2e94ba8af'"
    [B]aol.com[/B]. 60 IN TXT "knowbe4-site-verification=bc3830115833f4f956e30f506f1da8c8"
    [B]aol.com[/B]. 60 IN TXT "facebook-domain-verification=ervjrx9gun9l4uhc6o4d05p65r2824"
    [B]aol.com[/B]. 60 IN TXT "google-site-verification=NqM_NKWhteDHiJCOfhlQqKT4nxexIeFRie5MmWA1RBk"
   ----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: YYY[b]aol.com[/b])
ID(s) verified: header.d=[b]aol.com[/b]

Canonicalized Headers:
    to:check-auth@verifier.port25.com'0D''0A'
    from:<YYY[b]aol.com[/b]>'0D''0A'
    date:Sun,'20'12'20'Apr'20'2020'20'18:20:22'20'+0200'0D''0A'
    references:<9a8f016a-c97b-a0dc-c451-30e8901607fc.ref@[b]aol.com[/b]>'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=[B]aol.com[/B];'20's=a2048;'20't=1586708426;'20'bh=SKE1AbHy4O172sYSgD5f2I63MTnSjXEAncHLlVp3+1A=;'20'h=To:From:Date:References:From:Subject;'20'b=

Canonicalized Body:
    
DNS record(s):
    a2048._domainkey.[B]aol.com.[/B] 60 IN CNAME a2048._domainkey.aol.com.
    a2048._domainkey.[B]aol.com[/B]. 60 IN TXT "k=rsa;
Public key used for verification: a2048._domainkey.[B]aol.com[/B] (2048 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.

Return-Path: <YYY[b]aol.com[/b]>
Received: from sonic304-9.consmr.mail.bf2.yahoo.com (74.6.128.32) by verifier.port25.com id hicvsm2e8s46 for <check-auth@verifier.port25.com>; Sun, 12 Apr 2020 16:20:27 +0000 (envelope-from <YYY@aol.com>)
Authentication-Results: verifier.port25.com; spf=pass  smtp.mailfrom=YYY@[b]aol.com[/b];
From: <YYY[b]aol.com[/b]>
Message-ID: <9a8f016a-c97b-a0dc-c451-30e8901607fc@[b]aol.com[/b]>

kostenzer · 13 apr 2020

Heb gekeken......
Maar ik gebruik aol mail.
Wat moet ik dan bij ziggo? Dat begrijp ik niet.

OctaFish · 13 apr 2020

kostenzer zei:
Van Ziggo naar Ziggo, ik zit ook bij Ziggo, lukt wel.

Dan heb je toch een smtp.ziggo.nl o.i.d. om van te versturen?

RogerS · 13 apr 2020

DMARC is een beveiliging tegen het versturen van spam. Deze controleert of een server email mag versturen namens een bepaald domein.

En nu komt het. Je probeert dus via een AOL mailserver een mail met als afzender @ziggo.nl te versturen. Dat vind die Ziggo mailserver dus niet (meer) goed en stuurt een foutmelding terug.
Kan dus kloppen dat het wel een tijd zo gewerkt heeft, maar door verbeterde instellingen bij de provider werkt het dus opeens niet meer.

Oplossing is dus om bij je Ziggo account ook de ziggo smtp server in te stellen, en dan zou het weer moeten werken.

kostenzer · 14 apr 2020

Ik denk dat er verwarring opgetreden is.
Ik verzend van @aol.com
Een keer naar @ziggo.nl, dat mislukt.
Een keer naar @home.nl, dat lukt.
Een keer van a@ziggo.nl naar b.ziggo.nl lukte ook.

Maar ik denk dat het probleem opgelost is. Ik kreeg dit screenshot van hem:

Dus zijn mailbox is vol zou ik zo zeggen.
Dus eerst maar eens de prullenbak leegmaken daarna, als dat niet genoeg is, mails verwijderen.

Scrapheap · 14 apr 2020

Of je mail instellen op pop3 i.p.v. imap, dan heb je dat probleem van een volle mailbox niet....

kostenzer · 15 apr 2020

Dat klopt, maar het is niet mijn mailbox die vol is.

554: 5.2.0 MXIN603 DMARC validation failed.

kostenzer

Terugkerende gebruiker

OctaFish

Verenigingslid

kostenzer

Terugkerende gebruiker

RogerS

Meubilair

kostenzer

Terugkerende gebruiker

OctaFish

Verenigingslid

kostenzer

Terugkerende gebruiker

Scrapheap

Meubilair

kostenzer

Terugkerende gebruiker

dorado

Moderator

kostenzer

Terugkerende gebruiker

OctaFish

Verenigingslid

RogerS

Meubilair

kostenzer

Terugkerende gebruiker

Scrapheap

Meubilair

kostenzer

Terugkerende gebruiker

Nieuwste berichten

Wij waarderen jouw privacy