Since WildApricot only supports sending mail from our domain, we also use a separate e-mail provider to allow both sending and receiving mail in our domain using standard mail applications and web clients. I expect that the situation is the same for most organizations using WildApricot.
In order to improve security, to hinder spamming and to prevent our domain mail from being blacklisted, we would like to add DKIM validation for that alternate. provider.
However, like WildApricot (and most mail providers) our mail service is hard-wired to use the DKIM selector "default". This is understandable, since they have no reason to assume that a large portion of their users would be using an additional mail service to send mail.
Unfortunately, Wild Apricot also insists on using the DKIM selector “default”, even though it is clear that most users will need an auxiliary mail service. Please either:
1. Change Wild Apricot's mail service to use a unique selector, e.g."wildapricot", instead of "default".
or
2. Allow the choice of a site-specific DKIM selector.