[opendmarc-users] Problems with 1.3.2~Beta0..deb and this mailing list failing DMARC

[Scott Kitterman]

On November 8, 2016 3:48:15 PM EST, Juri Haberland <juri at sapienti-sat.org> wrote:
>On 08.11.2016 21:34, Juri Haberland wrote:
>> I'd like to suggest at least the following tickets, which are all
>bugs in
>> 1.3.2-beta0 (or even older):
>> 
>> ticket  95 - SPF validation fail for ipv6
>> ticket 153 - duplicate dkim auth_result sections
>> ticket 165 - SPF Internal check fails on helo
>> ticket 166 - wrong report start and end times in DMARC reports
>> ticket 171 - inconsistent variable names: OPENDMARC_TEST_*
>> ticket 174 - Size limit is not stripped from ruf address
>> ticket 181 - fix for help output of opendmarc-reports
>> ticket 185 - Segfaults every connection attempts
>> ticket 186 - Bug in dmarcf_config_reload function
>> ticket 187 - compile and functional fix for SPF result logging (you
>already
>> have a slightly in your packages I assume)
>> ticket 188 - bug fix: don't delete zip file too early in
>opendmarc-reports
>
>Just added a new one that fixes a problem that was encountered by
>several
>people here on the list and elsewhere:
>ticket 193 - SQL strict mode compatibility
>
>> ticket 194 - bug: wrong DMARC state in Auth-Res header
>> ticket 195 - bug: Received-SPF: header results wrong
>> ticket 196 - bug: all messages are recorded in history file despite
>> RecordAllMessages = false
>> ticket 197 - remove one of the two MySQL DB schemata
>> 
>> The following is based on the patch Scott posted - I just created a
>ticket
>> for documentation purposes:
>> Ticket 189 - change documentation to be Debian-compliant
>> 
>> I really would like to see this patch in your packages, because
>without it
>> you can not reliably reject messages on DMARC fail, as so many
>mailing
>> lists are not DKIM clean (At lease Andreas Schulze an me are running
>this
>> patch in production for more than five month):
>> 
>> ticket 180 - Override MLM patch

I did upload opendmarc again this morning.  Once I'm back with my laptop, I'll mail the list of patches I included.

Generally, I stayed away from adding features and avoided things that looked like they only apply to the internal SPF code.  The Debian packages are built using libspf2.  I recommend everyone do that and not worry about the internal implementation.

Scott K