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 ---
My intention with this patch is to fix a bug in how firewall3 handles
forked child failures when exec fails. Since firewall3 is still used
in many legacy/third-party solutions that cannot easily upgrade to
fw4, I believe this fix is warranted for the community at large.

The specific process where we encountered this bug was within
fw3_hotplug when it attempted a call to hotplug-call.

On Wed, Dec 24, 2025 at 5:22 AM Jonas Lochmann <[email protected]> wrote:
>
> I am curious: What kind of subprocess is invoked that fails sometimes?
>
> Another question: Why do you use firewall3 and not firewall4? If there
> is no reason for staying at firewall3, upgrading could maybe solve this.
>
> > I have submitted a pull request for firewall3 to fix a bug where child
> > processes fail to terminate if an exec operation fails.



--
Stacy Corcoran
Software Engineer
406 E 3rd Ave | San Mateo, CA 94401
[email protected]  | verkada.com


--- End Message ---
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to