# Use the App

The Web console is the free management surface for your outpost. The official App connects to that outpost for notifications and authorized content. Keep using your email client to compose, reply and manage mail itself.

## Check monitoring and delivery

In the outpost Web console, use Overview to inspect mailbox connections, subscribed folders and recent deliveries. Check a specific mailbox when its connection fails. Delivery history records the channel's outcome; an accepted request means the next service accepted it, while the phone's notification settings and downstream delivery still determine display.

For native push, inspect the per-phone result as well as the event. Grant iOS notification permission and check Focus, notification summaries and network access when a phone remains quiet.

## Add a mailbox in the App

App management requires Pro, management authorization from the outpost owner, and a trusted HTTPS connection. To connect the App, follow [Connect the App](connect-app.md).

1. In Settings, open your connected outpost and tap **+** in its mailbox section.
2. Enter the mailbox name, IMAP server, port, username and app password. The connection uses TLS; adjust the connection limit in the server settings when needed.
3. Tap **Test and Scan** to verify the connection and discover folders. Credentials go directly to your own outpost.
4. Select the folders to monitor, then save. The mailbox and selected subscriptions take effect together; scanning only previews the available folders.
5. New folders are checked every five minutes. After saving, open a folder’s settings to change its check mode. Configure the outpost’s [notification channel](notifications.md) and send a test notification.

If your authorization covers mailboxes only, the App offers a connection test and lets you save the mailbox first. Ask the owner for folder management access before configuring monitoring.

If testing or saving fails, check the reported connection or permission error and try again. Keep the form open to retain your entries.

## Read from a notification

After [connecting the App](connect-app.md), the owner can grant content access independently of configuration permissions. Opening an eligible notification asks your outpost for the message. The phone must reach the confirmed HTTPS address, and the message must still exist in the authorized folder.

Remote images can contact the sender's server. Use the App's image-loading controls deliberately. The outpost processes body content in memory for the request and excludes it from notification history and diagnostics.

Once the body is readable, the App asks your outpost to mark that message as read in the mailbox. This also applies when opening a locally cached body. If synchronization fails, the body stays readable and the failure is recorded silently in the App’s event log. Reopen the message after reconnecting to try again. Receiving, previewing or dismissing a notification leaves the mailbox read state unchanged. Local notification read/unread status is managed separately.

The App caches successfully loaded bodies for offline reading using iOS complete file protection and excludes them from system backups. Deleting a notification, clearing or expiring history, or removing its outpost deletes the related cached body. Remote images remain controlled separately and may need a network connection.

## Configure previews

Third-party notification previews default to off. Subject previews expose the subject to the selected notification provider; webhook payloads can also include the sender. Mailbox and folder labels are included in both modes. Native notifications encrypt sender and subject separately for the paired phone. See [notification channels](notifications.md) for exact payloads and retry behavior.

## Restore purchases

Use **Restore Purchases** on the Pro or Support page. Automatic purchase checks stay silent; a manual restore may ask you to authenticate with Apple. Pro and one-time support are restored separately. A purchase recovery restores entitlements; your outpost's mailbox and folder settings remain on the server.

Restore valid purchases on a new device using the same Apple purchase identity. Existing devices keep access, and any number of devices can use the restored purchase. If restoration fails, check the Apple account used for the purchase and your network connection, then try again or contact support.

On a new device, create a new outpost invitation and scan it to authorize management, free message access and native notifications. Purchase recovery keeps the old device eligible to use its purchase. Device private keys, local history, message caches and outpost credentials stay on their respective devices.

## Diagnose and share a report

Check runtime logs around the failed operation and export the console's redacted diagnostics when reporting a problem. Review folder names and any additional screenshots before sharing. Provide the outpost version, approximate time, affected action and error code.

Clearing history or logs is a deliberate data action; read its confirmation first. A fresh test and a new message provide a useful checkpoint after changes.