IMAP Base64 (RFC 3501)

Published

In this guide

This standards reference on Base64Encoding explains imap in plain language for developers and everyday users.

Everything important stays private: try the matching converter or tool in your browser — files and tokens are not uploaded.

Read the full English article below for code samples and edge cases, or switch language anytime from the menu. We keep expanding translations from real user feedback.

Try these private tools next

IMAP mailbox names that contain non-ASCII characters use modified UTF-7 (RFC 3501). Inside those names, a Base64-like alphabet encodes Unicode with two important differences from RFC 4648:

Value Standard Base64 IMAP variant
62 + +
63 / ,
Padding = required none

The / character is replaced with , because / is the IMAP hierarchy separator. Padding is omitted so mailbox names stay compact.

Example

ASCII mailbox names need no encoding. A name with non-ASCII characters embeds &…- segments where … is IMAP Base64 of UTF-16BE bytes.

When developers need this

  • Debugging mailbox names returned by IMAP servers in Europe (umlauts, accents, Cyrillic).
  • Migrating mailboxes between providers.
  • Writing IMAP clients that round-trip international folder names.

Use the standard detector to recognise IMAP Base64, then normalize to standard Base64 or decode with the IMAP standard selected.

常見問題

Does this page upload my data?

No. Articles are static. Linked tools run locally in your browser unless a feature explicitly needs a network relay.

Can I request a translation or a new tool?

Yes — use the private feedback form. We prioritize what users ask for across languages.

What is the fastest way to try imap?

Open the homepage Base64 converter or the related tools linked on this page and paste a sample.

相關工具與指南

留言 (0)

對「IMAP Base64 (RFC 3501)」有問題、想法或發現錯誤嗎?歡迎留言、為工具評分或回覆他人。

目前還沒有留言,歡迎搶先分享您的意見!

發表留言

為此工具評分:
Esc
↑ ↓ 移動↵ 開啟Esc 關閉