Decide how to handle keys with one or more blanks within the mail addr part of a uid
Schleuder is currently not capable to find the correct key, if the lookup searches for a mail addr, e.g. if resending messages, if the key in question contains one or more blanks within the mail addr part of a uid.
The spec defines this part as an UTF-8 string, which, it seems, leaves room for interpretation.
Different implementations handle this differently: some do accept this, others do not. I just learnt that it's possible to create such keys via Thunderbird, while it's not via
We could either disallow such keys to be added to the keyring, although that might seem drastic, and would do 'harm' if people use such keys only for subscribers, e.g. resending is not of a concern.
Personally, I would like to get both (subscription vs. resending) 'in sync': Allowing such keys in general, or disallowing them; I'm leaning towards the later. If so, this might be a breaking change.
Any opinions wrt this topic?