A mailbox setup note can save time when you configure a mail app, move to a new device, or ask an authorised administrator for help. It should be a map of the setup—not a spare key to your account. Record stable, non-secret facts such as your email address, server settings and the date you checked them. Keep the note somewhere private, and leave passwords, one-time codes and recovery secrets out of it. A quick review after setup can confirm that the details are useful without making the account easier for someone else to access.
The useful bits
- Record addresses, server settings and relevant plan or workspace context—not credentials.
- Store the note in a private place with access limited to you or authorised people.
- Verify each setting against current account instructions; never record passwords or one-time codes.
Decide what the note is for
Start by naming the task the note should support: setting up a mail app, restoring your configuration on another device, or explaining the account context to an authorised workspace administrator. A note with a clear purpose is easier to keep accurate and less likely to collect unnecessary personal information.
Record your full mailbox address and, if relevant, the domain or workspace it belongs to. You can also note whether it is a personal or business mailbox and the plan or storage allocation shown for your account. BITTU Mail personal mailboxes start with 500 MB; Business Starter, Standard and Premium provide 10, 20 and 50 GB per mailbox respectively. Availability and account configuration can vary, so treat the account itself as the current reference if a plan detail changes.
Write down connection details carefully
If you use an app outside the web mailbox, save the server information you need to re-enter its settings. BITTU Mail's IMAP server is mx1.bittuicloud.com on port 993 with SSL/TLS. SMTP uses the same server on port 465 with SSL/TLS or port 587 with STARTTLS; outgoing mail requires authentication, and the username is the full mailbox address. Do not use port 25 for a mail app. Never accept a certificate warning to make a connection work.
These are configuration facts, not login credentials. Your note may say which connection option you chose, but do not write down the password used to authenticate. If the app reports a certificate warning, stop and check the server name and security settings rather than bypassing the warning.
Keep credentials out, even temporarily
Never put your mailbox password, a one-time passcode (OTP), or a recovery code in the setup note. Do not add them as a comment, screenshot, photo, email draft or “temporary” placeholder that someone could mistake for a real credential. A one-time code is meant to be used for its intended sign-in or verification step, not saved for later.
If you need to sign in while following your notes, enter credentials only in the appropriate sign-in flow. BITTU Mail sign-in, registration, account recovery and account actions go through mail.bittuicloud.com. The public website, bittumail.tech, is separate from that account-actions address. Do not send real passwords or OTPs to an assistant or include them in a support message.
Choose a private place and limit access
Store the note where it is not publicly shared and where access is limited to people who genuinely need the setup information. A private, access-controlled digital note or a paper record kept in a secure place may work; choose based on how you manage your other sensitive records. Avoid a shared household document, an open team folder, or an unprotected note on a device others can use.
For a work mailbox, separate personal connection notes from information intended for a workspace administrator. Share only the non-secret details needed to solve the specific issue, and use a channel your organisation authorises. Workspace controls depend on role, plan and provisioning state, so do not assume every user can inspect or change domain or mailbox settings.
Add context that will help later
A few small details can make a note more useful without turning it into an account dossier. Include the device or mail app you configured, the date you last confirmed the settings, and whether you use IMAP or another supported access method. You may record the account recovery address or phone only if you need that reminder, the information is appropriate to store, and the note remains private. Do not record recovery codes or the contents of private verification messages.
If an administrator may need to help, note the mailbox address and a brief description of the issue, not unrelated message content. For example, “Outgoing mail fails from my phone” is more useful and less revealing than copying a private email thread into the setup record.
Use a checklist, then confirm the note
After saving the note, compare it with the account information and the settings currently entered in your app. Confirm the mailbox address is complete, the server spelling and port match, the security method is recorded accurately, and the username is the full mailbox address. Then check that no password, OTP or recovery code appears anywhere in the note. If you revise a setting, update the date so you know when it was last checked.
A successful check means the note can guide you without supplying a secret: you can locate the right account page, enter the listed non-secret connection details, and complete sign-in separately through the proper authentication flow. If a setting is rejected or a certificate warning appears, do not guess or weaken security; recheck the details and seek help through an authorised route.
Mailbox: [your full address] Purpose: [phone mail-app setup] App/device: [app and device] IMAP: mx1.bittuicloud.com, port 993, SSL/TLS SMTP: mx1.bittuicloud.com, port [465 SSL/TLS or 587 STARTTLS] SMTP authentication: required; username is full mailbox address Last checked: [date] Password, OTP, recovery code: not recorded
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