Terry,

> I had previously setup a submission port using dkimproxy separate from
> amavis to test DKIM signing and verification, and it worked well.
> However once I found out that 2.6.2 implemented DKIM as well without the
> problems of breaking signatures after spam and virus scanning, I got all
> giddy and decided to go for it.
>
> I read the instructions in the release notes and the user documentation
> on the website, but apparently somewhere along the way I've gone wrong.
> I've beaten myself black and blue going over my amavis.conf file, but I
> still don't see the DKIM headers in any messages I send.

> With logging level 2 turned on for amavis, I get logs like the following:

With log level 5 search for "dkim: " in the log, which will give you
the reason for not signing. My guess is the 'originating' flag is not
turned on, i.e. that @mynetworks does not include your sending client's
IP address ('originating' can also be turned on by a policy bank,
for more control). This would show as "dkim: not signing inbound mail"
in the log.

  Mark

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
AMaViS-user mailing list
[email protected] 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to