Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: ding@gnus.org
Subject: Re: resending bounces: DKIM and Message-ID:
Date: Fri, 03 Nov 2023 17:14:16 +0100	[thread overview]
Message-ID: <87o7gahl0n.fsf@dataswamp.org> (raw)
In-Reply-To: <rmi34xn2fg4.fsf@s1.lexort.com>

Greg Troxel wrote:

> I found a behavior problem that I think is a bug in both
> gnus and opendkim. Headers that are supposed to be added by
> the originating MTA are not removed, so the resent message
> has odd content: duplicate DKIM header, and the same
> Message-ID

Not an answer to your situation but FWIW I had problems with
DKIM in the past, I don't remember how I solved it but here
are a bunch of commands and URLs related to that whole thing:

#! /bin/zsh
#
# this file:
#   https://dataswamp.org/~incal/conf/.zsh/mail
#
# DMARC issue:
#   https://en.wikipedia.org/wiki/DMARC
#   https://mailarchive.ietf.org/arch/msg/ietf/kL24edUthAOuHuwK3ZnpFkCXduI
#
# discussion and commands:
#   http://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/msg00476.html
#   http://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/msg00477.html
#   http://lists.gnu.org/archive/html/help-gnu-emacs/2019-05/msg00481.html
#
# (rfc 7489)
#   "Domain-based Message Authentication, Reporting, and Conformance (DMARC)"
#   <https://datatracker.ietf.org/doc/html/rfc7489>
#
# (rfc 8616)
#   "Email Authentication for Internationalized Mail"
#   <https://datatracker.ietf.org/doc/html/rfc8616>

dig-srv () {
    local srv=$1
    nslookup -type=mx $srv
    dig $srv mx
}

DMARK_ZOHO=_dmarc.zoho.eu

dig-zoho () {
    dig $DMARK_ZOHO txt +short
}

host-zoho () {
    host -t txt $DMARK_ZOHO
}

test-zoho () {
    local server=pop.zoho.com
    local port=995
    local server_port=${server}:${port}

    echo "socat"
    socat - OPENSSL:${server_port}

    echo "\nopenssl"
    openssl s_client -quiet -connect $server_port

    echo "\ngutls-cli"
    gnutls-cli --port $port $server
}

-- 
underground experts united
https://dataswamp.org/~incal



  reply	other threads:[~2023-11-03 17:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 12:23 Greg Troxel
2023-11-03 16:14 ` Emanuel Berg [this message]
2023-11-03 23:14 ` Eric Abrahamsen
2023-11-05 15:55   ` Greg Troxel
2023-11-05 19:30     ` Eric Abrahamsen
2023-11-07  0:53       ` Greg Troxel
2023-11-07  1:57         ` Emanuel Berg
2023-11-07  3:15           ` Emanuel Berg
2023-11-07 13:49           ` Greg Troxel
2023-11-07 13:59             ` Emanuel Berg
2023-11-07  3:38         ` Eric Abrahamsen
2023-11-11 16:58           ` Greg Troxel
2023-11-19 19:44             ` Eric Abrahamsen
2023-11-19 21:36               ` Dan Christensen
2023-11-20  0:01                 ` Greg Troxel
2023-11-10 16:38         ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7gahl0n.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).