Add zerosmtp-check to SMTP Testing - #43
Open
msgwing wants to merge 1 commit into
Open
Conversation
msgwing
added a commit
to msgwing/ZeroSMTP
that referenced
this pull request
Aug 29, 2026
…ple (#336) Two mistakes in one hour today, both from the same gap. #216 was closed as "we do not qualify" while a pull request to that exact list had been open for six days - adding zerosmtp-check to their command-line tools section, not to the Email Clients section the radar had matched and I had read. An hour earlier a second pull request to linsa-io was one command away from being opened, because the tracking issue did not know the first one existed. Directory entries are the measured channel here. free-for.dev sends 20 unique visitors in 14 days; every position this project holds in GitHub's own search sends 18, combined. An unwatched submission queue is an unwatched channel. Added as a sixth job to the workflow that already watches for things nobody noticed, rather than a twenty-second workflow file. It reports three things and opens an issue for only one of them: - a pull request open in somebody else's repository while the issue tracking it is closed. That is a contradiction - one of the two is wrong - and it is the case that cost us today, so it is the only case that raises an issue. - a pull request with no tracking issue at all. - no response for 21 days. Run against live data before committing, and it found four things nobody knew about: sdras/awesome-actions#882 27 days, no tracking issue jonathandion/awesome-emails#122 26 days, no tracking issue LlamaGenAI/awesome-free-saas#104 17 days, issue #203 closed Mindbaz/awesome-opensource-email#43 7 days, issue #208 closed The first version of that test reported all seven as orphans and zero contradictions, which was wrong and would have been believable. The issue list had come back empty because the subprocess read crashed on cp1250 decoding, so every match failed and the failure looked like a finding. A check that cannot read its own inputs reports absence, and absence is what this one exists to report.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
zerosmtp-checkunder SMTP Testing.It checks whether outbound SMTP works from the machine it runs on: TCP reachability, STARTTLS and implicit TLS, and whether AUTH is offered - against any host and port, not only our own.
npx zerosmtp-check, no install,--jsonfor monitoring.MIT, Node.js, published to npm with provenance. Disclosure: I maintain it.