FlexConfirmMail

This is an extended version of the addon "Confirm Mail". You can define "exceptions" for confirmation.

For Regular Users

You can define "exceptions" and "extra conditions" for confirmation of message sending operation. Some features depend on the native messaging host, please download/install it from the latest release page for 3.x and later (4.0.2 for example).

This has an intelligent reconfirmation mode: *reconfirms only on cases with higher risk of miss-sending *, for example; there are added recipients, message body is copied from another existing message sent to different recipients, very long text is copied from external application, and so on. Moreover this has ability to show more reconfirmations with various conditions.

And, this has a "delayed send" feature also, like "send after 5 seconds after confirmation". This will give you one more chance to cancel sending.

Exceptional Domains

If you put some domains to the "exceptional domains" list and you try to send a mail to an address in the list, an extra confirmation dialog will be shown. It will be useful in a case like: your SMTP server always encrypts your mail automatically but there are some exceptions.

Exceptional Attachment Suffixes

If you put some "file extension"s to the "exceptional attachment suffixes" list and you try to send a mail with an attachment including a suffix in the list, an extra confirmation dialog will be shown. It will be useful in a case like: your SMTP server always encrypts attachments but there are some exception file types.

Exceptional Keywords for Attachment Filenames

If you put some notifiable keywords to the "exceptional attachment names" list and you try to send a mail with an attachment including a term in the list, an extra confirmation dialog will be shown. It will be useful in a case like: your company has a policy to use special terms like "confidential" for some special attachemnt files.

Blocked domains

If you put some dangerous domains to the "blocked domains" list and you try to send a mail with an attachment including a term in the list, the operation will be canceled always. It will be useful in a case like: your company maintains a list of dangerous recipient domains.

For System Administrators

This addon supports Managed Storage. You can override any configs via GPO, policies.json and/or managed storage manifest. For example, if you use the policies.json:

{
  "policies": {
    "3rdparty": {
      "Extensions": {
        "flexible-confirm-mail@clear-code.com": {
          "internalDomains": [
            "clear-code.com"
          ],
          "skipConfirmationForInternalMail": true
        }
      }
    }
  }
}

It will help you to create such an managed storage manifest with exported configs: FlexConfirmMail options => "Development" => Check "Debug mode" => "All Configs" => "Export". (Please remind that you should remove "debug":true from the managed manifest.)

For Developers

How to run automated unittest?

1. Create an XPI including unittest, with the command make unittest.
2. Install the built XPI.
3. Open the browser console or the developer tool for the Thunderbird itself.
4. Run openDialog('chrome://confirm-mail/content/unittest/testRunner.html', '_blank', 'chrome,all').

How to do manual test?

1. Open sample.eml with Thunderbird.
2. Hit Ctrl-E to edit the mail as a new message.
3. Try to send it.

How to build the native messaging host and its installer?

Prepare Windows 10 + WSL and macOS environments. On Windows:

1. Install and setup Golang on your Linux environment.
   • On Ubuntu 22.04LTS: you may just run sudo apt install golang-go gox gcc-aarch64-linux-gnu
2. Install go-msi https://github.com/mh-cbon/go-msi via an MSI to your Windows environment.
3. Install WiX Toolset https://wixtoolset.org/releases/ to your Windows environment.
4. Set PATH to go-msi (ex. C:\Program Files\go-msi) and WiX Toolset (ex. C:\Program Files (x86)\WiX Toolset v3.11\bin).
5. Run make host. Then .exe files and a batch file to build MSI will be generated.
6. Double-click the generated webextensions\native-messaging-host\build_msi.bat on your Windows environment. Then two MSIs will be generated.

And, on macOS:

1. If you need to distribute notarized pkg, prepare these things:
   • Install XCode. (You may need to update the macOS before that.)
   • Create your personal Apple ID (assume it is myname@example.com) and join to the Apple Developer Program. (*Payment required)
   • Create an application password named as Pkg Signing. Assume that the generated password.
   • Create a cerficate signing request.
     1. Open "Keychain Access (キーチェーンアクセス)": "Finder" => "Application (アプリケーション)" => "Utilities (ユーティリティ)" => "Keychain Access (キーチェーンアクセス)"
     2. In the menubar: "Keychain Access (キーチェーンアクセス)" => "Certificate Assistant (証明書アシスタント)" => "Request a Certificate From a Certificate Authority (認証局に証明書を要求)"
     3. Fill fields with your Apple ID (email addressm) and your company name (assume it is My Company). The email field of the CA can be blank.
     4. Click "Save to Disk (ディスクに保存)" and "Continue (続ける)".
     5. A file named as CertificateSigningRequest.certSign will be saved. Store it somewhere.
   • Create a certificate for code signing.
     1. Go to the Apple Developer Portal and transit to the Certificates, IDs, & Profiles.
     2. Click Create a certificate.
     3. Choose Developer ID Application - This certificate is used to code sign your app for distribution outside of the Mac App Store. and click Continue.
     4. Choose Previous Sub-CA.
     5. Click Choose File, choose CertificateSigningRequest.certSign you've created and click Continue.
     6. Click Download Your Certificate to download the certificate file developerID_application.cer.
     7. Double-click downloaded developerID_application.cer to import it to the Keychain Access.
     8. In a terminal, run security find-identity -v | grep -E -o '(Developer ID Application:[^"]+") to get the certificate name. Assume that it is Developer ID Application: My Company (XXXXXXXXXXX). The part "XXXXXXXXXX" is your team ID.
   • Create a certificate for signing to installer packages.
     1. Go to the Certificates, IDs, & Profiles again.
     2. Click Create a certificate.
     3. Choose Developer ID Installer - This certificate is used to sign your app's Installer Package for distribution outside of the Mac App Store. and click Continue.
     4. Choose Previous Sub-CA.
     5. Click Choose File, choose CertificateSigningRequest.certSign you've created and click Continue.
     6. Click Download Your Certificate to download the certificate file developerID_installer.cer.
     7. Double-click downloaded developerID_installer.cer to import it to the Keychain Access.
     8. In a terminal, run security find-identity -v | grep -E -o '(Developer ID Installer:[^"]+") to get the certificate name. Assume that it is Developer ID Installer: My Company (XXXXXXXXXXX).
   • Configure your shell (with ~/.bashrc or ~/.zshrc) as:

     export APPLE_ID="myname@example.com"
     export APP_CERT_NAME="Developer ID Application: My Company (XXXXXXXXXXX)"
     export PKG_CERT_NAME="Developer ID Installer: My Company (XXXXXXXXXXX)"
     

2. Copy built darwin directory to the local storage of your macOS environment.
3. Open a terminal window.
4. cd to the copied darwin directory.
5. Run build_pkg.sh. Then a .pkg file will be generated.
   • You'll see some authentication dialogs to access the Keychain Access or login as Pkg Signing, if you prepared APPLE_ID, APP_CERT_NAME and PKG_CERT_NAME as described above and you ran the build_pkg.sh on a macOS desktop environment. The built file .signed.pkg is notarized, so you should distribute it instead of the unsigned version.