Cyrus IMAP: broad application labels hide a mailbox service boundary
Cyrus IMAP is a mail server with authentication handled by Cyrus SASL. Its public services can include IMAP, POP3, Sieve, and administrative paths. An internet census can find a service label, but the service boundary and authentication policy determine what the observation means.
The measurements
ZoomEye returned 301 matches for app="Cyrus IMAP" and 233,612 for the broader app="Cyrus". The banner term banner="Cyrus" returned 386,468. The observations used sub_type=all, page 1, pagesize 1.
The broad application and banner counts are not interchangeable with a confirmed IMAP deployment. Cyrus is used in mail software and appears in banners for related products and components. The full product label is much narrower and should be the preferred starting point when the goal is a Cyrus IMAP inventory.
Mailbox access is the asset
Cyrus documentation says the server can provide TCP/IP services and can authenticate through Cyrus SASL. The IMAP listener commonly uses port 143 and Sieve uses port 4190, but ports are only hints. A service can use different ports, a proxy can front it, and a banner may be generated by an unrelated component.
Review the authentication mechanisms, TLS requirements, anonymous access, mailbox administration, and the network path to the service. Disable legacy cleartext mechanisms or require TLS before they are advertised. Protect the administrative path separately from ordinary user mail access.
Turn broad matches into a defensible list
For each owned candidate, verify the protocol exchange and the product version. Record the observed port, banner, and query. Use the full app label first, then inspect the broad label only as a secondary discovery source. Do not report every banner match as a Cyrus server.
Check the mailbox host inventory against the organization's mail domains and decommissioned systems. A stale server can still accept credentials and hold old mail. For active hosts, confirm the SASL backend, certificate lifecycle, and the accounts allowed to administer mailboxes.
Limits
ZoomEye can show that a broad product label is common and that a narrower label is much less common. It cannot prove that a host accepts a weak mechanism or that a mailbox is accessible. The operational value is a short list of owned mail services for protocol-level verification.
Top comments (0)