🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: pl.comp.mail.mta
Article #62942

Re: opendkim

#62942
From: Lemat
Date: Tue, 08 Dec 2020 06:50
72 lines
3669 bytes
W dniu 07.12.2020 o 22:40, Dżon pisze:
> W dniu 04.12.2020 o 16:10, Lemat pisze:
>> Elo,
>>
>> jest piątek a ja mam problem ze zrozumieniem:
>>
>> Return-Path: <fetc1@ci2.toservers.com>

>> Authentication-Results: me; spf=none (no SPF record)
>> smtp.mailfrom=ci2.toservers.com (client-ip=190.61.219.64;
>> helo=agur.toservers.com; envelope-from=fetc1@ci2.toservers.com;
>> receiver=me@me)
>> Authentication-Results: me; dmarc=none header.from=obsluga.klienta79174.pl
>> Authentication-Results: me; dkim=pass
>>      reason="1024-bit key; unprotected key"
>>      header.d=fetc.com.ar header.i=@fetc.com.ar header.b=kj+bDSSl;
>>      dkim-adsp=nxdomain; dkim-atps=neutral
>> X-Greylist: delayed 00:45:42 by SQLgrey-1.8.0
>> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
>> d=fetc.com.ar
>>      ; s=default; h=Sender:Content-Transfer-Encoding:Content-Type:Date:
>>      MIME-Version:Message-ID:Reply-To:From:Subject:To:Cc:Content-ID:
>>      Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
>>
>>      :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:
>>
>>      List-Subscribe:List-Post:List-Owner:List-Archive;
>>      bh=t12ckai1mdAFRMr6mJpGKgjvn0M94nzLFN29a4ScxKw=;
>> b=kj+bDSSlIraKWxwMa6QLdhiHia
>>      mKgABDsH7ObP71QjQ3ofpzlwG/jy8TvmCQzxqQtVgHFDSyDhP32DXxNgWb8/YAFuuAoBE33bzicZ5
>>
>>      cVcR/R14PJuVzipV86S+WY8Vg12Lh0SrTjoo473IcoV1HPsg9hH9hBqLUIGuYv8PzZvE=;

>> From: Obsługi Klienta <obsluga.klienta471832@obsluga.klienta79174.pl>

>> konfiguracja: opendkim+opendmarc jako miltry do postfixa
>>
>> opendkim zauwazył sygnaturę i ją zweryfikował, że poprawna
>> ALE we From jest domena obsluga.klienta79174.pl, która nie istnieje
>> a w syganturce dkim jest zupełnie inna domena: d=fetc.com.ar
>>
>> jak to ugryźć?
>>
> 
> Co oznaczają te informacje:
> 
> dkim-adsp=nxdomain; dkim-atps=neutral
> 
> ???
> 

czyli mówisz, aby ustawić niezerowe wartości w spamassassinie?

score DKIM_ADSP_ALL        3
score DKIM_ADSP_DISCARD    10
score DKIM_ADSP_NXDOMAIN   3

dla atps nie widzę nic ciekawego

ku potomności zostawię linka wyjaśniającego ADSP
https://en.wikipedia.org/wiki/Author_Domain_Signing_Practices

i zdanie:
DKIM, however, deliberately makes no binding between the DNS domain
    of the signer and any other identity found in the message.
https://tools.ietf.org/html/draft-kucherawy-dkim-atps-16

by wyjaśniało dlaczego opendkim jest takie ubogie.

-- 
Pozdrawiam
Lemat
Technical Details
Message-ID: <5fcf223f$0$527$65785112@news.neostrada.pl>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!news.samoylyk.net!aioe.org!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!newsfeed.neostrada.pl!unt-exc-01.news.neostrada.pl!unt-spo-a-02.news.neostrada.pl!news.neostrada.pl.POSTED!not-for-mail
References: <5fca516f$0$501$65785112@news.neostrada.pl> <5fcea159$0$526$65785112@news.neostrada.pl>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!news.samoylyk.net!aioe.org!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!newsfeed.neostrada.pl!unt-exc-01.news.neostrada.pl!unt-spo-a-02.news.neostrada.pl!news.neostrada.pl.POSTED!not-for-mail
Subject: Re: opendkim
Newsgroups: pl.comp.mail.mta
References: <5fca516f$0$501$65785112@news.neostrada.pl> <5fcea159$0$526$65785112@news.neostrada.pl>
From: Lemat <#@lemat.priv.pl>
Date: Tue, 8 Dec 2020 07:50:39 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <5fcea159$0$526$65785112@news.neostrada.pl>
Lines: 72
Message-ID: <5fcf223f$0$527$65785112@news.neostrada.pl>
Organization: Telekomunikacja Polska
NNTP-Posting-Host: 83.23.242.90
X-Trace: 1607410239 unt-rea-a-01.news.neostrada.pl 527 83.23.242.90:17565
X-Complaints-To: abuse@news.neostrada.pl
X-Received-Bytes: 3503
X-Received-Body-CRC: 817819714
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit