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 2022-09-13 21:56, Jo-Philipp Wich wrote:
Hi,
IMHO changing, in /etc/config/network:
"config interface" -> "config network"
"config device" -> "config interface"
would eliminate this semantic inconsistency and bring the naming
convention more in line with what Rich referred to in his comments
above.
This cannot be done in a sane manner though as it would render future
versions
entirely backwards incompatible.
Renaming `config interface` to `config network` makes sense and can be
implemented easily. However we would still need to treat `config
interface` as
synonym for it in the forseeable future in order to retain
compatibility,
which means that we cannot reuse `interface` for something else.
So changing `config interface` to `config network` would be possible
assuming
that `config device` remains `config device` (or is renamed to
something other
than `interface`).
At the same time, the `wifi-iface` section type in /e/c/network should
be
changed to `wifi-network` in order to remain consistent.
When you are at this level of changes and redefining and reusing names,
normally it is time to reconsider the complete thing.
I would suggest something like a JSON file based config with versioning
so that later changes can be done in a forward compatible way.
With some clever scripts, not too exotic existing configurations can be
converted automatically, just like was done with the switch to DSA.
Just my 2 cents..
Bas.
~ Jo
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--- End Message ---
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
