Milter-greylist

10 \u043c\u0430\u044f 2015�\u0433. 7:10:45 CEST, "manu@... [milter-greylist]" <milter-greylist@yahoogroups.com> \u043f\u0438\u0448\u0435\u0442:
>Michael Grant mgrant@... [milter-greylist]
><milter-greylist@yahoogroups.com> wrote:
>
>> I see the following in my logs:
>> milter-greylist: DKIM failed: No signature
>
>Indeed if DKIM support is built in, milter-greylist evaluates it (and
>report the error in the logs) whatever your settings are. There is no
>way to get rid of it witout modifying the code.
>
>> I'm using milter-greylist on debian which is already compiled.  I
>don'
>> really want to build my own package, this would break updates.
>
>Well, I am going to introduce a fix, but how long does it take for
>Debian to update a package?

Also, would you update the stable or dev release? Likely, mainstream distros package the former while new goodies end up in the latter.

For end-users concerned with proper updates, it might make sense to port the distro (debian) compilation rules so that dev-releases can be installed as properly versioned packages and later overridden by eventual newer-numbered updates. In case of milter-greylist, I've committed extra configure-flags to simply append suffixes like vendor and build number to the version repoted by compiled MGL specifically to track in-house builds. It would be a karma bonus to submit these back to MGL project ;)

As for Debian, I played with DEBs at new work - not pretty nor simple underhood, compared to RPM spec-files or solaris SVR4 packages, but seems quite powerful anyway. Just takes a while to wrap the mind around their concepts and methods.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android