docs: panel statusu nie moze odsylac do nieopublikowanej paczki - #163
Merged
Merged
Conversation
The status panel offered `npx zerosmtp-check` as the way to test from your own network. That package returns 404 from the npm registry: publish-npm.yml requires an NPM_TOKEN secret, the repository has no secrets at all, and the workflow has never run once. Sending a reader to a command that fails is worse than offering nothing, and on a page whose whole argument is that the service is verifiably up it is the most expensive place to be wrong. Replaced with two one-liners that need no install and are already in the troubleshooting guide - Test-NetConnection on Windows, openssl s_client elsewhere. Both open the connection and send no mail. Publishing the CLI is worth doing, but it needs a credential that has to be created by a person.
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.
Panel guzika stanu proponował
npx zerosmtp-checkjako sposób na test z własnej sieci. Ta paczka zwraca 404 z rejestru npm.Znalezione przy pierwszym przebiegu nowego
security-director:publish-npm.ymlwymaga sekretuNPM_TOKENhttps://registry.npmjs.org/zerosmtp-check→ 404Odesłanie czytelnika pod polecenie, które padnie, jest gorsze niż nieodesłanie go nigdzie — a na stronie, której cały argument brzmi „verifiably up", to najdroższe możliwe miejsce na pomyłkę. Błąd był mój, wszedł wczoraj w #159.
Zamiast tego
Dwa jednolinijkowce bez instalacji, obecne już w przewodniku troubleshootingu:
Test-NetConnection mx.msgwing.com -Port 587openssl s_client -starttls smtp -connect mx.msgwing.com:587Oba otwierają połączenie i nie wysyłają poczty.
Decyzja dla Ciebie
Opublikowanie CLI jest warte zachodu —
npx zerosmtp-checkto jedyny artefakt tego projektu, który ktoś uruchamia i podaje dalej. Wymaga jednak automation tokena z npmjs.com wstawionego jako sekretNPM_TOKEN. Poświadczeń nie tworzę i nie wprowadzam — to musi zrobić człowiek.