mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #105] Add Readme section to check if everything is working fine #67
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#67
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 @jeromelaurens on GitHub (May 3, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/105
The README would benefit a lot a section for testing it.
For example :
Testing if mailpit is working with mailpit sendmail command
Create a text file containing the headers and the body of the email, for example,
email.txt:Next, run the following command in the terminal:
This command uses the
-tflag, which tellssendmailto read the "To", "Cc", and "Bcc" headers from the file to determine the recipients.Check on the UI : the email should be there
@axllent commented on GitHub (May 3, 2023):
Thanks for the suggestion. Given that there are several ways to use "sendmail" (using
mailpit sendmail..., symlinking mailpit to sendmail, using a system-installed sendmail binary, not to mention setting up PHP as an example), I think I'll simplify the README and add a link to a Wiki post (which I haven't created yet). If I don't do this then half the README will be just about testing sendmail :) Please leave this with me and I'll get this done soon, thanks.@axllent commented on GitHub (May 4, 2023):
Please have a read of this and let me know if you think that is helpful, thanks?
@jeromelaurens commented on GitHub (May 4, 2023):
The section is very good, but, in my humble opinion would benefit to be in a dedicated section or in a getting started or, better, at the end of the installation section of README (or link to the wiki in the installation section)
My use case was :
@axllent commented on GitHub (May 4, 2023):
Hi. I'm not sure you checked that link I posted? It is to a new dedicated Wiki page that explains it in more detail, including your suggestion. I wanted to check this new page before I update the README to point to this new wiki page.
@jeromelaurens commented on GitHub (May 4, 2023):
Yes I checked the link, of course, I even answered : "The section is very good"
The title is "SendMail testing".
When you are a newcomer, your use case is not "Sendmail testing" but "Check installation".
You don't care about
sendmailspecifically, you just want to finish the installation and send quickly an email and see it in the UI.With this documentation organization, again as a newcomer, you'll never find it.
It is just a feedback from a newcomer, maybe it is obvious to you, but not for a newcomer, I can assure.
Feel free to do whatever you want.
@axllent commented on GitHub (May 4, 2023):
My apologies, I obviously misunderstood. As a technical person I definitely would not call it "Check installation" as that suggests information regarding the installation of Mailpit on various systems - which I definitely do not want to cover (there are just too many different setups / platforms etc) . Your point about non-technical people finding the relevant information is duly noted though, and I will update the main README to be shorter and clearer, linking to the correct documentation. Thank you for your advise!