schleuder will attempt to send email to an address it cannot encrypt messages to
Today I found a few messages stuck in my postfix queue. At first glance they just looked like the remote SMTP server was to blame, but upon closer inspection I realized I had fat-fingered an email address and subscribed firstname.lastname@example.org instead of email@example.com. The schleuder list had no key for the erroneous email address firstname.lastname@example.org, but was still attempting to send a message to the subscriber in spite of the following Send control list option being set:
Send encrypted only? Only send messages if they can be encrypted to their receiver.
I didn't think to crack open the message in the queue to verify what it was, but thinking through it logically I'd expect they were actual messages bound for the list and encrypted to the proper key for email@example.com, despite being emailed to firstname.lastname@example.org). Obviously this use case arose out of user error, but it got me wondering if there shouldn't be an extra check (perhaps as an option) that the key associated with a subscriber email has at least 1 matching email userID.