The Mailbox connector lets people print by sending an email. OptimiDoc monitors a dedicated inbox, and every message it finds is turned into a print job attributed to the sender -- ideal for mobile and guest printing, where installing a driver or reaching the internal network is impractical. This is distinct from the Email destination used by scanning, which sends documents out by SMTP; the Mailbox connector receives email to print.
Screenshot: Mailbox connector configuration
Overview
Unlike the browse-on-demand connectors, the Mailbox connector is actively polled: the OptimiDoc Service connects to the mailbox every 30 seconds over IMAP or POP3 and processes any new messages. Attachments -- and, optionally, the message body -- become print jobs that enter the normal pull print workflow.
Common use cases include:
-
Mobile printing from phones and tablets by emailing an attachment
-
Guest and visitor printing without network access or an account
-
Automated printing of documents emailed by other systems
How It Works
-
The OptimiDoc Service polls the mailbox every 30 seconds. (After repeated connection errors it backs off progressively and resumes automatically once the mailbox is reachable again.)
-
For each message, OptimiDoc identifies the owner in two steps: first it matches the email subject against a user's login; if that fails, it matches the sender's From address against a user's registered email.
-
If no user matches and Allow guests is enabled, a temporary guest account is created from the sender's address (valid for the configured number of days, in the assigned department).
-
The sender's print permission on this connector is checked; unauthorised senders are rejected.
-
Each attachment is submitted as a print job. Unless Only attachments is enabled, the email body itself is also printed.
-
Jobs pass through the rules engine and quota checks and wait for release like any other pull print job.
Note: a mailbox may instead be linked to a scan workflow, in which case incoming attachments are routed into that workflow (mobile capture) rather than printed.
Configuration
Create the connector and its connection in the React interface:
-
Navigate to Printing > Print Connectors and click Add Connector.
-
Enter a Name (e.g. "Print by Email") and select Mailbox from the Type dropdown.
-
On the Configuration tab, complete the settings below.
Connection Settings
|
Setting |
Description |
|---|---|
|
Server |
The mail server hostname (e.g. |
|
Port |
The mailbox port (e.g. |
|
Inbox Type |
IMAP or POP3. IMAP is recommended for its server-side message management. |
|
Authentication |
Login & password, Google OAuth 2.0, or Microsoft 365 OAuth 2.0. |
|
Username |
The mailbox address / login (required for both password and OAuth modes). |
|
Password |
The mailbox password (Login & password mode only). Stored encrypted. |
|
Client ID / Client Secret |
The OAuth application credentials (OAuth modes only), followed by the Authorize step. |
|
Use SSL/TLS |
Encrypt the connection. Strongly recommended. |
-
On the Access Rights tab, assign the connector to the Groups whose members may print by email.
-
Click Save. For an OAuth mailbox, reopen the connector and click Authorize to complete sign-in.
Guest and Attachment Options
These options control the mobile-print behaviour of the mailbox. From the release following 26.07 they are part of the Mailbox form in the React interface — the guest fields appear when Allow guests is switched on. In 26.07 and earlier they were configurable only in the legacy interface (/old).
|
Option |
Description |
|---|---|
|
Allow guests |
Accept mail from senders who are not existing users, creating a temporary guest account for each. |
|
Only attachments |
Print only the attachments and ignore the message body. |
|
E-mail subject / E-mail body |
The confirmation message sent to guests (shown when guests are allowed). |
|
Account expiration |
How many days a guest account remains valid (default 7). |
|
Assign to department |
The department that new guest accounts are placed in. |
Modern Authentication
Microsoft 365 and Google increasingly disable basic (password) IMAP/POP3 access. Use Microsoft 365 OAuth 2.0 or Google OAuth 2.0 for those providers: supply the application Client ID and Client Secret, keep the mailbox address in Username, save, and click Authorize.
Troubleshooting
|
Issue |
Resolution |
|---|---|
|
Cannot connect to the mail server |
Verify Server, Port, and Use SSL/TLS, and that the OptimiDoc server can reach the mailbox (firewall). |
|
Authentication failed |
For Microsoft 365 / Google, switch to OAuth and complete Authorize; basic authentication may be blocked by the provider. |
|
Jobs not attributed to the right user |
The subject must match a user's login, or the sender address must match a user's email. Otherwise enable Allow guests. |
|
Body prints unexpectedly |
Enable Only attachments to ignore the message body. |
Related articles