Appearance
Generic IMAP
This guide explains how to connect any IMAP-compatible email server to MyEmailVault.
Setup Steps
1. Create an Ingestion Source
In MyEmailVault, navigate to Ingestions and click Create New. Select Generic IMAP as the provider.
2. Configure the Connection
Fill in the following fields:
| Field | Description |
|---|---|
| Name | A descriptive label for this source (e.g., "Work Email - IMAP"). |
| Host | The IMAP server hostname (e.g., imap.your-provider.com). |
| Port | The IMAP server port. Typically 993 for TLS connections or 143 for unencrypted. |
| Username | Your email address or the username required by your provider. |
| Password | Your email password or App Password. |
| TLS | Enable this toggle for encrypted connections (recommended). Most providers require TLS on port 993. |
| Allow Insecure Certificate | Enable this only if your server uses a self-signed or otherwise untrusted TLS certificate. Leave disabled for production mail servers. |
3. Save
Click Save to create the ingestion source. MyEmailVault will attempt to connect to the IMAP server and begin importing your emails.
Recommendations
- Use App Passwords when available. Many providers (Gmail, Outlook, Yahoo, etc.) require or strongly recommend App Passwords for third-party IMAP access. Check your provider's documentation for instructions.
- Always use TLS. Unencrypted IMAP connections transmit credentials and email content in plain text. Only disable TLS if you are connecting to an internal server on a trusted network.
Source Statuses
After saving, the ingestion source will display one of the following statuses:
| Status | Meaning |
|---|---|
| Importing | The initial bulk import is in progress. |
| Active | Import is complete and continuous sync is running. |
| Paused | Sync has been manually paused. |
| Error | The connection failed or an import error occurred. Check the source details for the error message. |
Troubleshooting
- Connection refused: Verify the host and port. Ensure the server allows IMAP connections and that no firewall is blocking the port.
- Authentication failed: Double-check your username and password. If your provider requires App Passwords, generate one and use it instead of your regular password.
- Certificate error: If the server uses a self-signed certificate, enable the Allow Insecure Certificate toggle. Otherwise, ensure the server's TLS certificate is valid.