Version 1.4.2 released.

I am not updating the Debian package on Gitlab. If this package is one day of interest, I will create a package on Github and keep it in sync with the releases.

Ola! If you would like mxcheck to be included in Kali, you should follow the template documented at https://www.kali.org/docs/tools/submitting-tools/, to provide us with basic information about the tool. It helps us to have a quick overview, and as we evaluate tool requests on a regular basis, we'll decided if yes or no we want to include it in Kali.

The packaging part for this tool is trivial, bit even though, it doesn't mean that we want to include it in Kali. Packages need maintenance, from the moment we include it, we must maintain if and fix it if ever it breaks.

Thanks!

Hi! Thanks for your comment and I will happily follow the template.

[Name] - mxcheck

[Version] - v1.4.2 (versions match git tags)

[Homepage] - https://github.com/steffenfritz/mxcheck

[Download] - https://github.com/steffenfritz/mxcheck/releases

[Author] - Steffen Fritz (ampoff)

[Licence] - GPL v3 - https://www.gnu.org/licenses/gpl-3.0.en.html

[Description] -

mxcheck is an info scanner for e-mail servers.

• It checks DNS records: A, MX, PTR, SPF, MTA-STS, DKIM,
• the AS Number and AS Country,
• the support of StartTLS and the certificate,
• open ports: 25, 465, 587
• if the service is listed by blacklists
• and whether the server is an open relay

[Dependencies] - mxcheck is written in go and distributed as a statically linked, fat binary. For the blacklist check eleven external blacklist services are requested.

[Similar tools] - None standalone tools I am aware of, only externally hosted services like mxtoolbox

[Activity] - It started in October 2018 and is still actively developed and maintained in January 2023

[How to install] - mxcheck can be compiled by go build. To include version and build hash into the binary the included Makefile should be used with make build.

[How to use] - ./mxcheck -s 2600.com There is also an Asciicast https://asciinema.org/a/471229

[Packaged] - Tried my best https://gitlab.com/fritzsf/mxcheck-debian/-/tree/kali/master/debian

@kali-team, please could this be packaged up.

Update:

[Version] - v1.5.0 (versions match git tags)

Info Update:

[Homepage] - https://mxcheck.fritz.wtf/

[Version] - v1.5.1 (versions match git tags)
[Homepage] - https://mxcheck.fritz.wtf/

Update:

[Version] - v1.5.2 (versions match git tags)

Update:
[Version] - v1.5.2-1 (versions match git tags)

This is a dependencies update.

New version, v1.6.0. Added TLS version check: https://github.com/steffenfritz/mxcheck

Package drafted/available for peer review. There is 1 dependency that has to be imported to Kali before mxcheck can be built/distributed:

• https://gitlab.com/Arszilla/golang-github-jamesog-iptoasn
• https://gitlab.com/Arszilla/mxcheck

Just a quick feedback: If you want to get feedback/issues etc., from users on Kali, maybe find an alternative -v output, as it lacks details:

┌──(root㉿faa79509345f)-[~]
└─# mxcheck -v

mxcheck --  Copyright (C) 2019-2024  Steffen Fritz --  version:  build: 

This program comes with ABSOLUTELY NO WARRANTY.
This is free software under GPL-3.0, and you are welcome to 
redistribute it under certain conditions. See license file.

Hello,

thanks for your feedback and the drafted package!

The version and build values are set by make, using "build". If it eases thinks I could set them directly in the code.

However, besides that, I will add the sourcecode repository and issue tracker, good point. While I will apply OpenSSF to mxcheck, the whole issue process will be streamlined.

The version and build values are set by make, using "build". If it eases thinks I could set them directly in the code.

The package is built via the following Debian rule:

#!/usr/bin/make -f

%:
    dh $@ --builddirectory=_build --buildsystem=golang

override_dh_auto_install:
    dh_auto_install -- --no-source

This depends on dh-sequence-golang i.e. dh-goloang. Refer to https://manpages.debian.org/testing/dh-golang/Debian::Debhelper::Buildsystem::golang.3pm.en.html#build regarding the "build" stage. If you have an idea on how we can provide the version/build info to this process, feel free to share.

I added the version string directly in the source and removed the build sha1 fingerprint as it would change in any case.

If you could sync again against upstream, the -v flag prints the correct version and gives a URL to where file bugs and feature requests.

Hi again,

can you sync against upstream? That would be great.

Thanks!

I've uploaded the package and should be ready in kali-rolling in a few days
https://gitlab.com/kalilinux/packages/mxcheck