Failed Verifications and Warning Messages
While sending a mailing, if it is marked to be signed using DKIM/DomainKeys, then Aurea List Manager uses the domain of the From or Sender Header and add this to the selector defined on the DKIM/DomainKeys tab of the Site to request a public key. Aurea List Manager then attempts to match the retrieved public key to the private key on the DKIM/DomainKeys tab of the Site.
- If no public key can be retrieved, or if it cannot be matched to the private key in Aurea List Manager, then DomainKey signing cannot take place. Aurea List Manager issues a failure message.
- If the From field has a merge tag in it, then Aurea List Manager cannot verify the proper information before sending the mailing. In this case, Aurea List Manager sends the mailing with DKIM/DomainKey signing but issues a warning message.
When Aurea List Manager generates these warning or failure messages, they are logged in the Mailing transact log and the debug log. An email is also sent to any List Administrators on that list.
Some possible warning messages are:
.... "Mailing Id: 192 NOT SIGNING message with Domainkey signature header. DNS permanent failure for LM_DK_test512._domainkey.2k3.lyris.com'" In this case, there is matching public key in the 2k3.lyris.com DNS for the private key set up in the Site
.... "Mailing Id: 199 NOT SIGNING message with Domainkey signature header. LyrisDK::NetValidate: No DNS TXT record found for 'LM_DK_test512._domainkey.yahoo.com'" In this case, there is matching public key in the yahoo.com DNS for the private key set up in the Site
.... "Mailing Id: 116 SIGNING message with Domainkey signature header. Can not verify PUBLIC KEY because the From: contains a merge tag." In this case, it was impossible to tell if the From had a valid domain, since it contained a merge tag. LM will assume that the domain is valid and will send it out DK signed
....Mailing Id: 255 NOT SIGNING message with Domainkey signature header. LyrisDK::NetValidate: No DNS TXT record found for '_domainkey.lyris.com' In this case, the Selector was missing in the Site DK definition
....Mailing Id: 259 NOT SIGNING message with Domainkey signature header. Private key is bad. In this case, the Private Key is missing or bad in the Site DK definition