The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---> We just had our developer meeting and want to do branch the next release > soon. I just want to coordinate the release planning here, the full > meeting notes will be published later. > > Do we still have some important bugs we should really fix in master or > anything which could be blocking for the release? > Any objections to this plan? >From my side there are three pending patches to upstream projects. 1. Fix: Correction for IPv6 handling in libnetfilter_queue (packages) This is currently pending with Netfilter https://patchwork.ozlabs.org/project/netfilter-devel/patch/a355cb9d-9b07-4d62-a228-a37c2660c...@apple.com/ 2. Feature: Adding ICMP support to libnetfilter_queue (packages) This is accepted by Netfilter, but has not made it into a release yet https://git.netfilter.org/libnetfilter_queue/commit/?id=662c8f44d53492d2e0ebd430dadef12d580ec330 3. Feature: Extending Dnsmasq with conntrack based DNS query filtering. This is currently pending with Dnsmasq, and will also need a minor addition to OpenWrt's dnsmasq.init file. http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q1/014661.html These three patches should eventually get into OpenWrt as well. For 19.07 it seems that the preferred approach is to only backport select patches instead of updating the entire component. Is it still possible to integrate new libnetfilter_queue / Dnsmasq releases into OpenWrt 21.02 once the patches have been accepted, or do you prefer the patches to be submitted to OpenWrt separately before the branch to 21.02? Etan
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
