setup: - two users (A and B) in address book - user A is set to allow only inline pgp mails - user B is set to allow only pgp/mime mails problem: if you write a mail to both users and select one of the two protocols, the mail is send without feedback to the user. However, kmail fails to encrypt the mail to the user with the other protocol. Therefore the mail is unreadable, if you select inline pgp for user b and it is unreadable for user a if you select pgp/mime. possible solutions: 1. Inform the user that it is not possible to send an encrypted mail to both users at once 2. Send the mail in different protocol versions to the different users. I think that solution 2 is the best approach. Maybe there should be a warning to the user and the possibility to abort. The second approach might interfere with bug 121692. Reproducible: Always
i dug a bit deeper and found out that solution 2 is already implemented, when selecting "all" as encryption standard in to compositor window. it is sending two mails too both of the people, but i guess it is not possible otherwise, since mail standard does not allow to add another "to" email address without actually sending it to this address (afaik). -> therefore this bug is only about showing a warning if the selected encryption standard is not compatible with all recipients and may give an option to use the "all" method.
still valid for 5.3.1
Actually the "To" Line has nothing to do with the concrete recipients ( that's how BCC) works. So It is not a problem to show a To line with both recipients and still send two different mails to user a and b. Don't know if we should show the user user a warning or not.