I am a Zivver admin
Configure and manage Zivver
Export data via FTP
Introduction
Export all Zivver messages that were sent and received by your organization for archiving purposes. This method allows you to export all messages via an FTP connection. The FTP method is a legacy approach and is not recommended for new exports. For organizations with a large number of messages, we recommend using the API method to export messages with a Python script. For smaller organizations with a limited number of messages, we recommend using the Zivver WebApp method to export all messages in a ZIP file via a Zivver message.
Requirements
We recommend using FileZilla as the FTP client with its default connection settings, as this is known to work best with our platform. FileZilla supports the required setup:
- Host: ftp.zivver.com
- Encryption: Explicit TLS
- Port: 21
- Passive Ports: 60000–60999 (only required when using Passive Transfer Mode)
How to connect
- Create a support ticket to have the export of all messages enabled for your organization.
Please include theFTPmethod in your request.
After the export of all messages is enabled for your organization, you can start the export process:
- Log in to the Zivver WebApp.
- Click
Organization Settings.
- Expand
General.
- Click Organization account.
- Scroll down to Export user data.
- Copy the Host.
- Open your FTP client and paste the copied Host.
- Go back to Export user data.
- Copy the User name.
- Open your FTP client and paste the copied User name.
- Generate a Zivver API key.
- In your FTP client, use the generated API key as the password for the FTP connection.
- Make sure the connection uses port 21.
- Make sure the connection uses Explicit TLS for encryption.
- Make sure that logging is enabled and stored locally for future reference.
- Test the connection.
You are now connected to Zivver via FTP. You can download Zivver messages as unencrypted .eml files.
Organizing the message files
Messages are stored as EML files and include any additional attachments. The messages are exported unencrypted, which means that you do not need a Zivver Client to read them.
In the export file, messages are sorted by account, then by month, by conversation, and by message. An example of the folder structure is:
v3
└── Account: johndoe@example.com
└── Month: 202407
└── Conversation: 20240705T120226Z_ee7f2e3j-w51j-642k-yt65-r3fb1233f07w
└── Message
├── 0001_20240705T120226Z.eml
├── 0002_20240711T091921Z.eml
└── 0003_20240711T092203Z.eml
FAQ
Error: 530 Authentication failed
When you try to connect and receive a530 Authentication failed response, this can have multiple causes:- If this is your first attempt: connecting via FTP to your Zivver organization is probably still disabled by default. Please create a support ticket to have it enabled.
- If you successfully used FTP export before but suddenly get this error: the API key might have been deleted or become invalid. The API key is used as the password for the FTP connection. Please check and generate a new one if needed.
Error: The data connection could not be established (ECONNREFUSED)
You can connect via FTP to your Zivver organization, but you cannot transfer any messages. You receive the errorThe data connection could not be established: ECONNREFUSED - Connection refused by server.This problem might occur when the FTP client is set to use Passive Transfer Mode, but the FTP connection cannot be established via the port range 60000–60999. You may need to allow the FTP client in your firewall or proxy to reach ftp.zivver.com via this range.
Error: Critical file transfer error
The errorCritical file transfer error can occur when attempting to transfer a .eml file that is suddenly missing. This might happen during a large FTP export if the revocation date for a message has passed.Some messages are missing or empty in the conversation folder
If you notice that some messages are missing in the folder of a specific conversation, this can have different reasons:- The message was revoked. Revoked messages can no longer be read, so the file is empty in the FTP export. You will see the word
DELETEDin the file name. - The message was received by an employee before your organization had its own Zivver organization, and that employee never re-opened the message while having a Zivver account as part of your organization. In that case, the message is still encrypted with the guest key. Only when the employee re-opens the message with a Zivver account will the keys be replaced with account keys, allowing admins of your organization to export these messages via FTP.
Some accounts are missing in the FTP export
If you notice that some accounts are missing in the FTP export, this can have multiple causes:- The account is a guest account and not part of your Zivver organization (yet). Please check how many accounts can be adopted for domains claimed by your organization.
- A master key reset was performed, but the missing users did not log in afterward. Ask those users to log in.
Is the FTP connection secure?
The FTP connection requires Explicit TLS. This means the FTP client first connects and then establishes a secure SSL/TLS connection.How can encrypted messages be exported unencrypted?
The FTP connection requires a generated API key to connect. This API key is used to decrypt the encrypted messages so they can be exported unencrypted.How large will the FTP export be?
If your FTP client supports file queuing, you can queue the completev3 folder. The FTP client will then show the total size of the queued files.