How to configure DomainKey/DKIM in Mavericks Server?

Question

I tried to follow the guid from TopicDesk (http://http://topicdesk.com/downloads/tutorials/160-implementing-domainkeys-dkim -on-os-x-10-8-x-mountain-lion-with-server-2-x) on 10.9. 
My DNS is setup correctly (tested using the testing tools at domainkeys.sourceforge.net) and all is tested good.
I test that everything is registered correctly on the server with:
sudo -u _amavisd -H amavisd -c /Library/Server/Mail/Config/amavisd/amavisd.conf testkeys
and it passes, and I can successfully extract my public key with:
sudo -u _amavisd -H amavisd -c /Library/Server/Mail/Config/amavisd/amavisd.conf showkeys
When I receive signed messages, I can see the headers, but when I send email, I don't see any evidence that my email was signed by DKIM process.
how can I troubleshoot this an verify that amavisd is configured correctly?
I wonder also if the topicdesk.com article is incomplete.
Any help would be much appreciated!

Answer 1

Sorry for not getting back to you.  Yes, I too had to do the full implementation.  this is because the second listener is used.
I already had this in my amavisd.conf
$interface_policy{'10026'} = 'ORIGINATING';
I did not add an new policy_bank, but I did change the order around a bit from the default.
$policy_bank{'ORIGINATING'} = {  # mail supposedly originating from our users
  originating => 1,  # declare that mail was submitted by our smtp client
  bypass_spam_checks_maps => [1],
  allow_disclaimers => 1,  # enables disclaimer insertion if available
  # notify administrator of locally originating malware
  virus_admin_maps => ["virusalert\@$mydomain"],
  spam_admin_maps  => ["virusalert\@$mydomain"],
  warnbadhsender   => 1,
  # force MTA conversion to 7-bit (e.g. before DKIM signing)
  smtpd_discard_ehlo_keywords => ['8BITMIME'],
  # forward to a smtpd service providing DKIM signing service
  forward_method => 'smtp:[127.0.0.1]:10027',
  # Other special treatment of locally originating mail
  bypass_banned_checks_maps => [1],  # allow sending any file names and types
  terminate_dsn_on_notify_success => 0,  # don't remove NOTIFY=SUCCESS option
Even though the amavd.conf was already setup mostly correct, and expected port 10027 for the originating poicy_bank, postfix was not configured with a listenning channel on port 10027, so I added one (per the topicdesk example) by adding this to my master.cf:
127.0.0.1:10027 inet n  -       y       -       -       smtpd
   -o content_filter=
   -o smtpd_tls_security_level=none
   -o smtpd_delay_reject=no
   -o smtpd_client_restrictions=permit_mynetworks,reject
   -o smtpd_helo_restrictions=
   -o smtpd_sender_restrictions=
   -o smtpd_recipient_restrictions=permit_mynetworks,reject
   -o smtpd_data_restrictions=reject_unauth_pipelining
   -o smtpd_end_of_data_restrictions=
   -o smtpd_restriction_classes=
   -o mynetworks=127.0.0.0/8
   -o smtpd_error_sleep_time=0
   -o smtpd_soft_error_limit=1001
   -o smtpd_hard_error_limit=1000
   -o smtpd_client_connection_count_limit=0
   -o smtpd_client_connection_rate_limit=0
   -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_m ilters
   -o local_header_rewrite_clients=
   -o smtpd_milters=
   -o local_recipient_maps=
   -o relay_recipient_maps=
But really, all of this is in the topicdesk blog.  The key was you have to do a full implementation, you cannot stop where they suggest you can stop.