2.0.1

[2.0.1] - 2025-03-12

Fixed

• Fixed accidentally publishing windows/arm64 binary as windows/amd64

2.0.0

[2.0.0] - 2025-03-12

With this release, mailcow-exporter becomes part of the official mailcow organization, which
means some things are renamed. Also, a bit of modernization was done on the codebase.

Breaking Changes

• In order to simplify usage and prevent security issues, configuration can no longer
  be provided as URL parameters - it must be set either through environment variables
  or CLI flags when starting the exporter.
• The exporter now uses a token to secure access by default. See the README for the new
  recommended setup.
• The following CLI flags have been renamed:
  • --defaultHost is now --host
  • --apikey is now --api-key
• Docker images have moved from dockerhub to ghcr.io/mailcow/prometheus-exporter

When previously using the following prometheus config:

scrape_configs:
  - job_name: 'mailcow'
    static_configs:
      - targets: ['mailcow-exporter-hostname:9099']
    params:
      host: ['mail.mycompany.com']
      apiKey: ['abc123']

You must now start the exporter either with --host=mail.mycompany.com and --api-key=abc123
or MAILCOW_EXPORTER_HOST=mail.mycompany.com and MAILCOW_EXPORTER_API_KEY=abc123. The
prometheus config can be reduced to the following:

scrape_configs:
  - job_name: 'mailcow'
    static_configs:
      - targets: ['mailcow-exporter-hostname:9099']
    params:
      token: ['abc123']   # Please read the section about token authentication in the README

Added

• --scheme can now be provided via CLI flag

Docker images

• ghcr.io/mailcow/prometheus-exporter:2
• ghcr.io/mailcow/prometheus-exporter:2.0
• ghcr.io/mailcow/prometheus-exporter:2.0.0

1.3.1: BUGFIX | Use dynamic number type for mailbox API response

Fixed

• A recent version of mailcow changed the type of a property from a string to an int. This
  release adds support for newer mailcow versions returning an int while preserving functionality
  on older mailcow versions that return a string.

1.3.0

Added

• New scheme option to allow API requests via http. (Thank you maximbaz)

1.2.0

[1.2.0] - 2020-09-06

Added

• New rspamd metrics. Requires an up-to-date mailcow version as it uses a brand new API endpoint.

1.1.3

[1.1.3] - 2020-09-06

Fixed

• Errors in single providers will no longer translate to errors in the whole exporter.
  Instead, the new mailcow_exporter_success and mailcow_api_success metrics will then
  be set to 0. This is done to make the exporter provide metrics, even if parts of it fail.

1.1.2

[1.1.2] - 2020-09-05

Fixed

• non-200 API responses (such as authorization errors) no longer throw an obscure JSON
  marshalling error, but a more helpful message. In general, API error messages contain
  a lot more information now, which makes finding issues in ones setup easier.

1.1.1

[1.1.1] - 2020-09-05

Fixed

• mailcow_container_start accidentally reported a static value

1.1.0

[1.1.0] - 2020-09-05

Added

• Meta information about the mailcow API requests
• Container information
• Help texts

Hello World

Initial release. Main change from the pre-1.0 versions:

commit e9f6a0bcd6d8f5db652919e5dab98d5decf6b93c
Author: Johannes Hertenstein <[email protected]>
Date:   Sat Sep 5 13:52:06 2020 +0200

    !!! CLEANUP | Move host & apiKey to query parameters
    
    This moves the host & apiKey used for the metrics into query parameters
    instead of static command line arguments / environment variables. This
    is done in order to use the same mailcow-exporter instance for multiple
    targets while keeping the configuration in the prometheus config files.
    
    If you are updating from an earlier version, you will have to move these
    values from environment / command line arguments into your prometheus
    configuration as shown in the README file.