After moving to a new mail app, it can feel as if your address book has followed you when familiar names appear as you type. But a recipient suggestion is not necessarily a saved contact: it may come from previous messages or another source the app can access. Check both separately before relying on them. A brief, deliberate test can show what the new app recognizes, what information you still need to import, and whether a suggested address is actually the one you intend to use.
The useful bits
- Treat autocomplete suggestions and saved contacts as separate things to check.
- Test with a familiar recipient, then inspect the full address before selecting it.
- Do not assume old recipient history was transferred if suggestions are missing.
Know what you are testing
Autocomplete is the list that appears while you enter a recipient in a message. A contacts list is a collection of saved people or addresses that you can browse or search separately. An app may draw suggestions from contacts, earlier messages, an account’s stored recipient history, or data available on the device. Which sources it uses depends on the app and its setup.
That means a familiar name in the suggestion list does not prove that your contacts were migrated. The name might be attached to an address you used before, while the contact record itself is absent. The reverse can happen too: a person may be in your contacts even if the app does not suggest them as you type.
Check contacts before composing
Open the new app’s contacts area, if it has one, and look for a person you recognize. Search by name and, if you know it, by email address. Check that the displayed address is complete and current. If the app has no separate contacts area, check the address book or contact service you intended to use with it; do not treat the compose window as a complete directory.
If a person is missing, find out where your original contacts were stored and whether they were included in the migration. Mailbox messages and contacts can be separate data. Use the new app’s supported contact-import or account-connection process if available, and follow its instructions rather than assuming that moving messages also moved contact records.
Run a low-risk autocomplete test
Start a new message and enter a few characters from a familiar recipient’s name or address. Pause for the suggestions, then inspect the full address shown for any likely match. A display name alone is not enough to confirm the destination. If several people share a name, compare the address with a message you trust or a separately verified contact record.
Do not send a test message to an address you have not confirmed. You can select a suggestion to inspect it, then remove the recipient and discard the draft. If you want to verify delivery, send only to an address you control or have permission to contact, and check the received message there.
You type “Jordan” and see “Jordan Lee.” Before selecting it, check whether the address matches the one you expect, such as jordan.lee@example.com. If you cannot verify it, leave the recipient blank and check your contact records instead.
Interpret missing or unexpected results
No suggestion does not necessarily mean the migration failed. The new app may not have access to the old app’s recipient history, or it may only suggest addresses after you use them in its own environment. A suggestion that does appear may come from a source other than your imported contacts. Treat both outcomes as clues, not proof.
If a suggestion is wrong, avoid choosing it just because the name looks familiar. Check whether an outdated address is saved in contacts, whether multiple entries exist, or whether the app is showing a different person with the same name. Correct the saved record where you can, and verify the address again before sending.
Keep migration and account setup distinct
If you are moving to BITTU Mail, remember that it is powered by BITTU ICLOUD. Account actions, including sign-in and recovery, go through mail.bittuicloud.com. Moving or setting up a mailbox does not, by itself, establish that an older app’s contacts or recipient suggestions are available in the new one. Check the relevant contact source separately.
For a mail app that needs manual connection details, BITTU Mail’s IMAP server is mx1.bittuicloud.com on port 993 with SSL/TLS. SMTP uses the same host on port 465 with SSL/TLS or port 587 with STARTTLS and authentication; use the full mailbox address as the username. Never use port 25 for a mail app or accept a certificate warning. These connection settings help configure mail access; they do not confirm that contacts or autocomplete history transferred.
A quick confirmation checklist
Before relying on recipient suggestions for everyday mail, make one pass through the two separate checks. Confirm that a contact record exists where expected, then see whether typing its name produces a suggestion with the matching full address. If one check succeeds and the other does not, you have identified a difference to investigate rather than a reason to guess.
- Find a familiar person in the contacts source you intend to use.
- In a draft, type part of that person’s name and inspect the full suggested address.
- Remove the recipient without sending if you cannot verify it.
- If suggestions are absent, check the migration source or the app’s supported contact setup; do not assume old recipient history came along.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction