mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 16:56:00 +03:00
[GH-ISSUE #151] Feature Request: Broken Link Checker #101
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mansoorkhan96 on GitHub (Aug 8, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/151
@axllent Thanks for creating this amazing tool.
This is a feature request to add an automated link checker that verifies all the links in an email are valid and return a 200 status code. Helpful to catch broken links while testing.
Thanks a ton ❤️
@axllent commented on GitHub (Aug 8, 2023):
That is an interesting idea! I'll give it some serious thought as I'm sure most wouldn't want all links automatically scanned by default (depending what types of mail they are scanning), but the ability to do a manual check could be a potential solution.
@mansoorkhan96 commented on GitHub (Aug 9, 2023):
@axllent Right, may be you could add some of sort of optional setting or configuration that defaults to false. So that users that need to scan broken links do not have to do it manually. It just runs for them every-time and give them an indication or warning sign.
I really appreciate your efforts towards betterment of this tool
Thanks.
@axllent commented on GitHub (Aug 9, 2023):
Yes, that was pretty much my thinking too. Default off, with the option to run it manually, and a toggle to run it automatically (like the HTML checker does).
@axllent commented on GitHub (Aug 16, 2023):
I have just released this feature in v1.8.2. Please have a play and let me know what you think?
@mansoorkhan96 commented on GitHub (Aug 16, 2023):
I have updated to latest and have checked. Looks good.
Thank you @axllent