Clone workflow has a hard coded preservation of System Properties starting with glide.email and glide.pop3

The clone workflow maintains a hard coded preservation of all system properties starting with glide.email and glide.pop3 even if no preserver for those properties exists on the instance.

1. On the target instance, remove the name starts with "glide.email" and name starts with "glide.pop3" conditions from the "Core Instance Properties" data preserver.
   2. On the target instance, modify the system properties with names starting with glide.email and glide.pop3.
   3. Request a clone.
   4. Once the clone is complete, verify on the target instance that the changes of the system properties have been preserved.
   
   

This is not a product defect and is working as designed. 

Properties starting with glide.email and glide.pop3 are hardcoded to be preserved on the Clone Target.