Skip to content

Multi-platform Docker container with utilities to process Mailbox files and Maildir directories (mail, mutt, mail-parser...).

License

Notifications You must be signed in to change notification settings

leplusorg/docker-mail

Mailbox

Multi-platform Docker container with utilities to process Mailbox files and Maildir directories (mail, mail-parser, mutt...).

Dockerfile Docker Build Docker Stars Docker Pulls Docker Version CII Best Practices OpenSSF Scorecard

Example

Let's say that you want to know the number of messages in a Maildir folder in your current working directory:

Mac/Linux

docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/mail messages maildir

Windows

In cmd:

docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/mail messages maildir

In PowerShell:

docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/mail messages maildir

Software Bill of Materials (SBOM)

To get the SBOM for the latest image (in SPDX JSON format), use the following command:

docker buildx imagetools inspect leplusorg/mail --format '{{ json (index .SBOM "linux/amd64").SPDX }}'

Replace linux/amd64 by the desired platform (linux/amd64, linux/arm64 etc.).

Sigstore

Sigstore is trying to improve supply chain security by allowing you to verify the origin of an artifcat. You can verify that the image that you use was actually produced by this repository. This means that if you verify the signature of the Docker image, you can trust the integrity of the whole supply chain from code source, to CI/CD build, to distribution on Maven Central or whever you got the image from.

You can use the following command to verify the latest image using its sigstore signature attestation:

cosign verify leplusorg/mail --certificate-identity-regexp 'https://github\.com/leplusorg/docker-mail/\.github/workflows/.+' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'

The output should look something like this:

Verification for index.docker.io/leplusorg/xml:main --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The code-signing certificate was verified using trusted certificate authority certificates

[{"critical":...

For instructions on how to install cosign, please read this documentation.

Request new tool

Please use this link (GitHub account required) to request that a new tool be added to the image. I am always interested in adding new capabilities to these images.

Packages

No packages published

Contributors 2

  •  
  •