Send Email through External Email Service permission is not like the others

having some fun today with the permission Send Email through External Email Service

if deliverability is not set to ‘all email’ the perm doesnt show in the UI at all.
ok…enable deliverability, enable perm, turn off deliverability.

if deliverability is not set to ‘all email’ the permission is not retrieved in a perm set retrieve
ok…enable deliverability, run retrieve, turn off deliverability.

if deliverability is not set to ‘all email’ in the target org , the deployment fails.   so…this means that i have to enable deliverability in the target org for any deployment of this perm set forever?!?!?!?

as if that wasnt enough fun for one day - on top of deliverability, you have to enable the actual feature to send via gmail/outlook in the target org.  just deliverability enabled still throws deployment error.

I even tried to disable deliverability after enabling the feature and still got the error….not surprised, but worth a shot in case someone actually thought about this before casting whatever their hex on your org.

also when you toggle the checkbox in setup on the email - Send through External Email Services node, there is no save option. but if you click somewhere else too quickly, which there is no way to know how long that is, then it doesnt save your setting bc its too busy doing this async nonsense to work its magic….

but hey the perm is enabled on all standard profiles….so just use those right…tho really the min access one prob should work for everything. except when they still enable bloatware for it…