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 ---On Wed, 2022-12-28 at 00:11 +0100, Rafał Miłecki wrote: > On 15.08.2022 12:30, Harm Berntsen via openwrt-devel wrote: > > 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. > > (...) > > > 5. Ensure the bootpartition variable is set to 0 in the U-Boot > > environment located at 0x30000 > > There should be really a Linux parser picking the correct set of > partitions. Such limitations make behaviour too much unpredictable if > not making it possible to brick a device. Thanks for your feedback! The fw_setenv tool from U-Boot can parse this format. My patch includes a uboot-envtools addition to make this change easy to do from OpenWrt initramfs. On the Wiki I also described the flashing process using a Raspberry Pi [1], also using fw_setenv. Although the bootloader supports A/B partitioning, my patch reduces to a single big A setup (for more storage space), so the only valid setting is bootpartition=0. Note that bootpartition=1 can be made to work, that would require changing the partition layout in the .dts and kernel boot parameters. I think there is little risk in bricking as the steps currently require you to directly connect to the flash chip. Once you can do that, creating/restoring back-ups is trivial. [1] https://openwrt.org/inbox/toh/arcadyan/astoria/we420223-99#flashing_openwrt
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
