On Jul 30, 2018 8:48 PM, ѽ҉ᶬḳ℠ <v...@gmx.net> wrote:
>
>
> >> Archlinux kernel 4.17.11 and its repo package opensmtpd 6.0.3p1-2
> >>
> >> messages sent from imap (dovecot) are not passed through dkimproxy
> >> whilst when sending from cli with swaks the dkim signature is added. It
> >> is apparent from the dkimproxy log that there is no attempt made to pass
> >> the message sent from imap.
> >>
> >> What I am missing?
> > Log output.
>
> Log (truncated to dkim essentials) for sending from cli with swaks:
>
>
> smtp: 0x561540925e20: STATE_HELO -> STATE_BODY
> smtp: 0x561540925e20: >>> 354 Enter mail, end with "." on a line by itself
> <<< [MSG] Date: Tue, 31 Jul 2018 01:21:39 +0000
> <<< [MSG] Subject: test Tue, 31 Jul 2018 01:21:39 +0000
> <<< [MSG] Message-Id: <20180731012139.012217@mail>
> <<< [MSG] X-Mailer: swaks v20170101.0 jetmore.org/john/code/swaks/
> <<< [MSG]
> <<< [MSG] This is a test mailing
> <<< [MSG]
> <<< [EOM]
> debug: 0x561540925e20: end of message, error=0
> debug: scheduler: evp:51be0555487bf73e scheduled (mta)
> debug: mta: querying MX for [relay:127.0.0.1,port=10027,mx]...
> debug: mta: [relay:127.0.0.1,port=10027,mx] waiting for MX
> debug: MXs for domain 127.0.0.1:
>         127.0.0.1 preference -1
> [connector:[]->[relay:127.0.0.1,port=10027,mx],0                              
>                                          
> x0]...
> de35c7da3274723c mta event=connecting address=smtp://127.0.0.1:10027
> host=localhost
> de35c7da3274723c mta event=connected
> debug: smtp: new client on listener: 0x56154091f410
> smtp: 0x561540935e30: connected to listener 0x56154091f410
> [hostname=mail, port=10028,
> tag=D                                                                       
> KIM]
> smtp: 0x561540935e30: STATE_NEW -> STATE_CONNECTED
> de35c7db27f5cb2c smtp event=connected address=127.0.0.1 host=localhost
> smtp: 0x561540935e30: >>> 250 HELP
> debug: mta-routing: route [] <-> 127.0.0.1 (localhost) is now valid.
> debug: mta: connecting with
> [connector:[]->[relay:127.0.0.1,port=10027,mx],0x20000]
> debug: mta: 0x56154094cfc0: handling next task for relay
> [relay:127.0.0.1,port=10027,mx]
> <<< [MSG] DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
> d=foo.bar; h=date
> <<< [MSG]       :to:from:subject:message-id; s=20171231;
> bh=ecGWgWCJeWxJFeM0urOV
> <<< [MSG]       WP+KOlqqvsQYKOpYUP8nk7I=;
> b=Nz8C2lJd1NPg8pRwLTLbb2iB1HZMaJe6BCFW
> <<< [MSG] X-Mailer: swaks v20170101.0 jetmore.org/john/code/swaks/
> <<< [MSG]
> <<< [MSG] This is a test mailing
> <<< [MSG]
> <<< [EOM]
> debug: 0x561540935e30: end of message, error=0
> smtp: 0x561540935e30: >>> 250 2.0.0: 724d461b Message accepted for delivery
>
>
> And now when sending from mail client - DKIM is jumped and not showing
> in the logs
>
> smtp: 0x56151e05be20: STATE_HELO -> STATE_BODY
> smtp: 0x56151e05be20: >>> 354 Enter mail, end with "." on a line by itself
> <<< [MSG] Subject: test
> <<< [MSG] Message-ID: <e0f7c56e-e766-9b29-eea7-083cfc5f3...@foo.bar>
> <<< [MSG] Date: Tue, 31 Jul 2018 03:33:06 +0200
> <<< [MSG] User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0)
> Gecko/20100101
> <<< [MSG]  Thunderbird/60.0
> <<< [MSG] MIME-Version: 1.0
> <<< [MSG] Content-Type: text/plain; charset=utf-8
> <<< [MSG] Content-Transfer-Encoding: 7bit
> <<< [MSG] Content-Language: en-GB
> <<< [EOM]
> debug: 0x56151e05be20: end of message, error=0
> debug: scheduler: evp:19bf6dd45e65c3d2 scheduled (mta)
> smtp: 0x56151e05be20: >>> 250 2.0.0: 19bf6dd4 Message accepted for delivery
> 5e7644f56363e9ee smtp event=message address=172.25.120.2

^^^^^^^^^^^^^^^^^^^^^^^^

> host=172.25.120.2 msgid=19bf6dd4 from=<mailad...@foo.bar>
> to=<f...@bar.com> size=551 ndest=1 proto=ESMTP
> smtp: 0x56151e05be20: STATE_BODY -> STATE_HELO
> debug: mta: received evp:19bf6dd45e65c3d2 for <f...@bar.com>
> debug: mta: draining [relay:bar.com] refcount=1, ntask=1, nconnector=0,
> nconn=0
> debug: mta: querying MX for [relay:bar.com]...
>
> >> config:
> > If this is the complete config you are missing an interface for incoming 
> > mail.
> >
> > listen on egress port submission auth <sometable> tag RELAY
> >
> > I like to tag it just to make sure unauthenticated stuff doesn't 
> > accidentally get through.
>
> Just posted the full config in a previous response to the thread, don't
> want to create a redundancy by repeating it.
>

I think the line in your config that specifies the above ip address is the 
cause. I think it should hit the skin relay rule first, but isn't. Bug? I would 
suggest commenting the line and see what happens. 

>
>
>
> --
> You received this mail because you are subscribed to misc@opensmtpd.org
> To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
>

Reply via email to