<commit_before># tb-migrate-login-info

Migrates saved login information between servers (POP3, IMAP, and SMTP)

## Usage

Give migration rule for servers via preferences.
For example, if you are using an MCD configuratin file (autoconfig.cfg or something), then:

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.0",
         "pop3:mail.example.com => pop3:mail2.example.com");
lockPref("extensions.migrate-login-info@clear-code.com.migration.1",
         "imap:mail.example.com => imap:mail2.example.com");
lockPref("extensions.migrate-login-info@clear-code.com.migration.2",
         "smtp:mail.example.com => smtp:mail2.example.com");
~~~

You can also migrate login information between different type servers, like:

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.1",
         "pop3:mail3.example.com => smtp:mail3.example.com");
~~~

You can specify authorization method for migration target, like;

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.1",
         "pop3:mail3.example.com => smtp:mail3.example.com (authMethod=passwordCleartext socketType=alwaysSTARTTLS)");
~~~

Possible values for `authMethod` and `socketType` are listed at [MailNewsTypes2.idl](https://dxr.mozilla.org/comm-central/source/mailnews/base/public/MailNewsTypes2.idl).
<commit_msg>Use short version for example<commit_after># tb-migrate-login-info

Migrates saved login information between servers (POP3, IMAP, and SMTP)

## Usage

Give migration rule for servers via preferences.
For example, if you are using an MCD configuratin file (autoconfig.cfg or something), then:

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.0",
         "pop3:mail.example.com => pop3:mail2.example.com");
lockPref("extensions.migrate-login-info<EMAIL>.migration.1",
         "imap:mail.example.com => imap:mail2.example.com");
lockPref("extensions.migrate-login-info<EMAIL>.migration.2",
         "smtp:mail.example.com => smtp:mail2.example.com");
~~~

You can also migrate login information between different type servers, like:

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.1",
         "pop3:mail3.example.com => smtp:mail3.example.com");
~~~

You can specify authorization method for migration target, like;

~~~
lockPref("extensions.migrate-login-info@clear-code.com.migration.1",
         "pop3:mail3.example.com => smtp:mail3.example.com (authMethod=password socketType=STARTTLS)");
~~~

Possible values for `authMethod` and `socketType` are listed at [MailNewsTypes2.idl](https://dxr.mozilla.org/comm-central/source/mailnews/base/public/MailNewsTypes2.idl).

{'fraction_non_alphanumeric': 0.14237031427489588, 'fraction_numerical': 0.014388489208633094, 'mean_word_length': 4.963882618510158, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 15, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 8, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7260839', 'n_tokens_mistral': 874, 'n_tokens_neox': 862, 'n_words': 166}