On Tue, 10 Feb 2009, SM wrote:
>> libdkim could be changed to report DKIM_STAT_CANTVRFY instead, indicating
>> to the calling application that a more permanent failure in verification
>> occurred. This would caused dkim-filter to immediately report a
>> verification error ("permerror") and pass the message instead of arranging
>> for a temp-fail of the message.
>
> Are we sure that this always results in a DKIM_STAT_CANTVRFY?
For dkim-filter, yes. Naturally, I can't speak for other applications
that use libdkim, but they're free to make such intepretations.
Another option would be to create a new DKIM_STAT return which
specifically indicates an error of this nature, such as
DKIM_STAT_OPENSSLERROR.
> If there was a permerror, this might not have been fixed.
So you're (generally) opting for leaving it as-is?
------------------------------------------------------------------------------
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
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
