I have gone over my configuration with a fine tooth comb, but considering I put 
them together it is not surprising I can’t spot anything


O have been trying to locate opendkim action in my log file.  It appears that 
that the  mail is being reviewed but now header added



postfix/submission/smtpd[52375]: milter8_send: milter inet:localhost:8891
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_name = inet:localhost:8891
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_version = 6
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_actions = 273
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_events = 1050370
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_non_events = 0
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_state = 4
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_conn_timeout = 30
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_cmd_timeout = 30
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_msg_timeout = 300
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_action = accept
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: send attr 
milter_macro_list = 0
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: dummy
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: dummy
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
value: (end)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: (list terminator)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: (end)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: dummy
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: dummy
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
value: (end)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: (list terminator)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: (end)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: status
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: status
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
value: 0
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: (list terminator)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: (end)
Oct 25 12:45:14 triggerfish postfix/submission/smtpd[52375]: > 
c-73-150-178-106.hsd1.nj.comcast.net[73.150.178.106]: 354 End data with 
<CR><LF>.<CR><LF>
Oct 25 12:45:14 triggerfish postfix/cleanup[52466]: E7D08CB4AA4: 
message-id=<f6267446-d5ec-4b56-b7ab-ceb34297d...@kasdivi.com>
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: status
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: status
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: input attribute 
value: 0
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: reason
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: reason
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: input attribute 
value: (end)
Oct 25 12:45:15 triggerfish postfix/qmgr[52120]: E7D08CB4AA4: 
from=<ja...@kasdivi.com>, size=2250, nrcpt=1 (queue active)
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: public/cleanup 
socket: wanted attribute: (list terminator)
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: input attribute 
name: (end)
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: > 
c-73-150-178-106.hsd1.nj.comcast.net[73.150.178.106]: 250 2.0.0 Ok: queued as 
E7D08CB4AA4
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: abort all milters
Oct 25 12:45:15 triggerfish postfix/submission/smtpd[52375]: milter8_abort: 
abort milter inet:localhost:8891

The thing that concerns me is the appearance of “dummy”

Any thoughts any one/?
> On Oct 24, 2019, at 11:29 AM, Jason Hirsh <kasd...@mac.com> wrote:
> 
> Thank you  for the quick response
> 
> 
> I am 99% certain they are…I had the OpenDkim running for about a week and did 
> not change those (I think0
> 
> Trusted Hosts
> 
> 127.0.0.1
> localhost
> example.com <http://example.com/>
> example1.com <http://example1.com/>
> 
> 
> 
> KeyTable
> 
> default._domainkey.example.com 
> <http://domainkey.example.com/>:default:/usr/local/etc/opendkim/keys/example.com.com/default.private
>  <http://example.com.com/default.private>
> default._domainkey.example1.com 
> <http://domainkey.example1.com/>:default:/usr/local/etc/opendkim/keys/example1.com/default.private
>  <http://example1.com/default.private>
> 
> SigningTable
> 
> *@example.com default._domainkey.example.com <http://domainkey.example.com/>
> *@example1.com default._domainkey.example1.com 
> <http://domainkey.example1.com/>
> 
> In my maillog.  I did find something a little strange response to an outgoing 
> message
> 
> 
> Oct 23 18:26:14 triggerfish opendkim[5845]: E0C34CB4A69: key retrieval failed 
> (s=zendesk1, d=lightandmotion.com <http://lightandmotion.com/>): 
> 'zendesk1._domainkey.lightandmotion.com 
> <http://domainkey.lightandmotion.com/>' record not found
> Oct 24 10:23:10 triggerfish opendkim[5845]: 9B3A8CB4A69: s=verifier201208 
> d=port25.com <http://port25.com/> SSL 
> Oct 24 11:02:02 triggerfish opendkim[5845]: 93C75CB4A9A: s=verifier201208 
> d=port25.com <http://port25.com/> SSL 
> Oct 24 11:18:43 triggerfish opendkim[5845]: 4AADACB4A99: key retrieval failed 
> (s=zendesk1, d=lightandmotion.com <http://lightandmotion.com/>): 
> 'zendesk1._domainkey.lightandmotion.com 
> <http://domainkey.lightandmotion.com/>' record not found
> 
> Light and Motion was who the message was going to and has no presence in my 
> mail system
> 
> 
> Is this log entry a clue??
> 
> 
>> On Oct 24, 2019, at 10:50 AM, Dominic Raferd <domi...@timedicer.co.uk 
>> <mailto:domi...@timedicer.co.uk>> wrote:
>> 
>> On Thu, 24 Oct 2019 at 15:28, Jason Hirsh <kasd...@mac.com 
>> <mailto:kasd...@mac.com>> wrote:
>>> 
>>> I am trying to revive my OpenDKIM installation. I had it working but 
>>> managed to break it when I updated my ports.  It is running but not signing 
>>> outgoing messages
>>> 
>>> My main.cf configuration relative to OpenDkim is
>>> 
>>> smtpd_milters =  inet:localhost:8891
>>> non_smtpd_milters =  $smtpd_milters
>>> milter_default_action = accept
>>> 
>>> My OpenDkim.conf is
>>> 
>>> AutoRestart             Yes
>>> AutoRestartRate         10/1h
>>> LogWhy                  Yes
>>> Syslog                  Yes
>>> SyslogSuccess           Yes
>>> Mode                    sv
>>> Canonicalization        relaxed/simple
>>> ExternalIgnoreList      refile:/usr/local/etc/opendkim/TrustedHosts
>>> InternalHosts           refile:/usr/local/etc/opendkim/TrustedHosts
>>> KeyTable                /usr/local/etc/opendkim/KeyTable
>>> SigningTable            refile:/usr/local/etc/opendkim/SigningTable
>>> SignatureAlgorithm      rsa-sha256
>>> Socket                  inet:8891@127.0.0.1 <mailto:8891@127.0.0.1>
>>> UMask                   022
>>> UserID                  opendkim:opendkim
>>> TemporaryDirectory      /var/tmp
>>> 
>>> As I stated it is running... But not signing from a test site...
>>> 
>>> Any thoughts would be appreciated
>> 
>> Are files /usr/local/etc/opendkim/TrustedHosts, KeyTable and
>> SigningTable set up correctly? Do you need to use KeyTable and
>> SigningTable - this is a more complex setup; standard setup uses
>> parameters Domain, Selector and KeyFile - see
>> http://www.opendkim.org/opendkim-README 
>> <http://www.opendkim.org/opendkim-README>.
> 

Reply via email to