The stupid Python stdlib logging module doesn't handle unicode at
all. If debugging is turned on, and SAFELOGGING is disabled, the
incoming emails are logged. If they have any unicode characters,
processing of the emails stops due to UnicodeDecodeErrors.

Apparently, Transifex only displays comments which are for the string
being translated, and only one string is viewed at a time. Sigh.

 * THANKS to Phoul on IRC for pointing out the issue with how Transifex
   handles TRANSLATOR comments.

These are somehow the old strings from before the UIs were revised. It
seems the automated Transifex updater scripts didn't create a new PO
file for Korean… that or I did something wrong. Either way, we can still
use *some* of these strings, so we should add them.

 * THANKS to ilbe123, cwt96, Dr.what, and pCsOrI.

 * THANKS to LinuxChata and ghostishev.

 * THANKS to volkangezer.

 * THANKS to Communia, Humberto Sartini, Anastasia01, and recognitium.

 * THANKS to hoek, yodaa, maxxx, and sebx.

 * THANKS to Ann Boen, erwindelaat, guryman, and BBLN.

 * THANKS to plazmism.

 * THANKS to Random_R.

 * THANKS to Lunar.

 * THANKS to dark_yoshi and strel.

 * THANKS to pappasadrian.

 * THANKS to trantor and unknwon_anonymous.

 * THANKS to autofunk78 and DavidNielsen

 * FIXES #12122. This string wasn't getting extracted to the PO template
   file, lib/bridgedb/i18n/templates/bridgedb.pot.

 * FIXES part of #12122.

We don't need to test for conditions which might raise a
``twisted.protocols.tcp.CannotListenError``, we just need to ensure that
we exit if we can't bind to the port for the email server.

Some of them were taking a *really* long time on some hosts,
particularly these two:

   - test_SMTPAutoresponder_reply_transport_invalid
   - test_SMTPAutoresponder_reply_transport_valid

 * ADD a new unittest, test_checkDKIM_good_dunno(), to
   test_email_dkim.py, which checks that a received email with two
   ``X-DKIM-Authentication-Results:`` headers (the first one good, the
   second ``dunno``) properly returns False.

 * FIXES #12091. Actually, it doesn't. It just proves that the changes
   in my `fix/9874-automate-email-tests` branch fix #12091. Either way,
   it's fixed, these unittests prove it.

 * ADD new unittest test_checkDKIM_dunno() to test_email_dkim.py which checks
   that a ``X-DKIM-Authentication-Results: dunno`` header properly returns
   False.

We should specifically check that a received email containing a

    X-DKIM-Authentication-Results: dunno

header doesn't successfully pass the domain checks called in
SMTPAutoresponder.runChecks().

 * CHANGE test_SMTPAutoresponder_runChecks_badDKIM() into
   test_SMTPAutoresponder_runChecks_DKIM_dunno() and
   test_SMTPAutoresponder_runChecks_DKIM_bad().