I can edit SPF records from the Admin account (as TXT) but not from a Client account. It appears to be as described in this bug report. But that is shown as fixed: https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4051 Is it a ISPConfig or Admin bug?
This is the relevant commit: https://git.ispconfig.org/ispconfig/ispconfig3/-/commit/378d8326bfb5b5713caf74c370dd14fd547f9c21 I don't know what the thought behind this is, maybe @florian030 can explain?
My guess is the reasoning is that you can break mail delivery for your domain by messing up spf records, so the client is forced to use the SPF wizard to create a single, syntactically valid spf record - but that admin is presumed to know that they're doing and allowed to edit the txt record directly if the so choose. It looks like the "Edit as TXT record" button should probably be hidden from non-admin users, but otherwise the functionality is quite nice in current ISPConfig versions.
The irony here - was it was the Admin who had made an mistake in the SPF record and the expert client couldn't edit it out.
Funny. They should be able to use the spf wizard to fix it? It could the wizard not parse the record and loaded no data? In that case, just enter everything again to recreate.
