Changes

 * We present the Thunderbird presents configuration we found parameters to the user before we create for the accountuser’s review and approval.* Most users today (mid‐2009) use no SSL unencrypted channels and no "secure auth", because that's send unencrypted passwords. Secure email service is too cumbersome to set up without knowing arrange when the user doesn’t know which combination works, and official . Official instructions are usually imcomplete and incomplete or outdatedor both. So, people The result is that users are already sending their password passwords in the clear, leaving the attacker just has to sniff itwith the relatively easy task of sniffing those passwords. With this feature, if If the attacker feeds a bad malicious configuration parameters to Thunderbird and we use that Thunderbird uses those parameters (worse our worst case scenario here), the attacker leaves fairly obvious traces and has runs a very high risk of being detecteddetection. Compared to passively In contrast with passive sniffing, this is active transgression presents a fairly high bar.* The risk exists only in the moment when the user creates the account, not during daily normal login(or, likely, more frequent) authentication.* For comparison: Addons/Extensions or downloads of EXEs Add‐ons, extensions and inscrutable, executable code pose a far, far larger greater riskthan do the mechanisms under review.