-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation: Testing guide, simple with external tools #3457
Comments
|
i belive he requests that it should be included into mailcow |
No he is not, also it's me both times ;) |
So far I did not find any tool to test autoconfig capability (and its various forms) |
No interest? I hoped to collect more resources before writing the article |
|
Pretty detailed DNS test: https://intodns.com/ A pretty simple, but also effective test, is sending an email to a gmail address you may have and then viewing the source. SPF/DMARC/DKIM pass/fails are listed there as well. Some tools i consider useful not so much for immediate testing, but for monitoring: |
Thanks both!! |
[moved to the top] |
Added further links to the list above |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey Stalebot, please do not close yet. Thanks. |
Hey all,
My private mail server had one or the other issue over the years. The server ended up in a blacklist, the SSL certificate was not renewed, SPDIF was not or wrongly configured, etc....
Mail is a complex issue and it is not a simple task to maintain a flawless system while the environment changes from time to time.
On top of all it is not easy to check every aspect.
Yes, a fully automated checking routine would be amazing. Yes that would take some time and constant improvement to be useful.
I propose to collect a list of external services and simple instructions to check the different aspects of a mailcow setup. This list in documentation will help every user right away. It might furthermore spark ideas how to incrementally implement self-tests in mailcow, to replace the need for such a list eventually.
Example:
Check that your server can be reached and works properly: https://mxtoolbox.com/diagnostic.aspx
The result should look similar to this:
Check that your server is not on any major blacklist ...
Check SSL ...
...
Next steps
Is something like this already available?
I propose to collect a list of web services you guys use to check basic functionality of your mailcow systems and would suggest to be rather over-exhaustive than selecting the one tool that does not catch (PTR or any other random aspect). Just drop everything in the comments below and let's start a discussion where and in which form we want provide this list.
Any further thoughts?
The text was updated successfully, but these errors were encountered: