Register a scan-to-fax MFP

On-prem multifunction printers (Sharp, Ricoh, etc.) can scan-to-email, and Faxart can turn that email into an outbound fax. Because a device can’t sign in, it is authorized by its source IP and sends under a per-device caller ID, so it never borrows a user’s fax identity.

How it works

The SMTP intake checks the sending IP against a registry of MFP sources. A registered device’s scan is accepted and faxed under that device’s configured caller ID; an unregistered IP is rejected.

flowchart LR
  M[Copier scan-to-email] --> I[SMTP intake]
  I --> C{Source IP<br/>registered?}
  C -- no --> R[Reject 550]
  C -- yes --> F[Fax out under<br/>device caller ID]

Steps

1. Open the SMTP admin tab and add an MFP intake source: the device’s source IP, a name, and the caller ID it should fax under.
2. Configure the copier to scan-to-email to your fax domain, addressing the fax number as the local part.
3. Scan a test page and confirm it faxes out under the device caller ID. The registry is consulted live, so you can add a device without a restart.

Encryption

Require TLS on the intake (FAXART_SMTP_REQUIRE_TLS) so device scans arrive encrypted; a plaintext attempt is then refused.

Deploy note

The SMTP intake runs as a separate image from the main API on the same Dockerfile. When you change intake behavior, rebuild both or the intake runs stale.

See also

• Send a fax from email
• Configuration reference