In some instances ASSP 1.9.1.8(1.1.01) will change the original message's Message-ID header by prefixing it with "assp." followed by an alphanumeric string. I think this happens when a message is received from a host listed in localDomains. I'm not sure what the purpose of the Message-ID modification is.
If the message has been signed using DomainKeys and Message-ID is a header included in the signature (recommended by RFC 4871 and default for OpenDKIM) the Message-ID change will invalidate the signature. An error message in the sendmail mail log will be created: Jan 9 15:51:27 domain.com sendmail[10092]: [ID 801593 mail.info] q09KpRVM010092: Milter insert (1): header: Authentication-Results: domain.com; dkim=fail (verification failed)\n\[email protected] header.b=ut6J4Ex+;\n\tdkim-adsp=unknown Jan 9 15:51:27 domain.com opendkim[2943]: [ID 632817 mail.info] q09KpRVM010092: s=mail d=other.domain.com SSL error:04077068:rsa routines:RSA_verify:bad signature Jan 9 15:51:27 domain.com opendkim[2943]: [ID 614597 mail.notice] q09KpRVM010092: bad signature data A solution is to exclude Message-ID from the signature. In opendkim.conf: OmitHeaders Message-ID. Is there a way to modify ASSP so this doesn't happen? Nikola Lazic ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
