Matus UHLAR - fantomas wrote:
>> That is to say, it should be checked that
>> those milters don't rely on further peculiarities of sendmail than
>> the milter interface proper.
>
> we could check if those milters work with postfix (some do) and if they have
> changes towards postfix compatibility in ChangeLog ,,,
I only looked at opendkim. I found no ChangeLog. However, that milter
uses functions such as smfi_getsymval to look up symbols like
"{daemon_name}" and "{auth_type}", in order to establish whether a
message has been submitted in a MSA-like fashion and hence has to be
signed. Although libmilter is presented in a MTA-neutral fashion, the
doc at https://www.milter.org/developers/api/smfi_getsymval defines
that function as
char* smfi_getsymval(SMFICTX *ctx, char *symname);
*Get the value of a sendmail macro.*
http://www.postfix.org/MILTER_README.html#macros also documents this
use. It requires either a full blown sendmail emulation layer, or a
thorough analysis of the milter to determine how to make it work with
minimal efforts. For example, the xxfi_envrcpt callback is only used
to check per-recipient signing options; as it always returns
SMFIS_CONTINUE, it may more easily be called from a global filter with
prerecorded values. Such slovenly global filter might then also work
for spamd, but not for greylisting.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
