mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 00:46:03 +03:00
[GH-ISSUE #1143] Domain MX check should make sure MX domain resolves to Modoboa instance #944
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#944
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 @brylie on GitHub (Jun 18, 2017).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1143
Impacted versions
Steps to reproduce
Current behavior
Modoboa reports that the MX settings are 'green' (i.e. OK) when, in fact, the MX settings resolve to a different server.
Expected behavior
Modoboa would show 'yellow' status when MX resolves to wrong server. 'green' status should only show when MX is configured and resolves to Modoboa instance.
Video/Screenshot link (optional)
@tonioo commented on GitHub (Jun 19, 2017):
The MX check currently works as follows:
Is it clearer?
@brylie commented on GitHub (Jun 20, 2017):
Yes, but may still be misleading. In effect, if someone has misconfigured their MX record, they might still see a green label. Simply checking that MX is declared does not ensure that it is pointing to the Modoboa server, hence the recommendation for a warning tag if MX points to a different server. Just a thought.
@tonioo commented on GitHub (Jun 20, 2017):
And if you define a list of allowed MX values through the admin panel (parameters) ?
@brylie commented on GitHub (Jun 20, 2017):
That makes sense. Is there a way to do that by default, to assist new admin users?
@tonioo commented on GitHub (Jun 21, 2017):
Not yet... I guess a configuration wizard would be the best but it can be long to develop. Maybe a documentation?
@brylie commented on GitHub (Jun 21, 2017):
Yeah, good (inline or in-context) documentation is usually a win for end-users. 😺
@tonioo commented on GitHub (Aug 18, 2017):
@brylie Hi, where would you add this documentation?
@brylie commented on GitHub (Aug 18, 2017):
Perhaps an MX section on the Configuration page?
@almereyda commented on GitHub (Oct 17, 2023):
I didn't expect this feature to exist. I think it will be good to even consider to split the developer and administrator (installation, configuration) documentation from the end user (instance administrators, domain administrators, simple users) documentation and highlight at this from an appropriate place.
The Spinx documentation is sometimes very technical to read, and not very appealing. A more visual approach for the latter audiences will greatly help in identifying such configuration options.
Eventually configuring this option should even be part of a default secure configuration example in the documentation of the Modoboa installer.
@Spitfireap commented on GitHub (Oct 17, 2023):
Well I can assure you that is not fun to write Shpinx doc :). At least it is not suited for writing sweet documentation other than the technical one.
I was writing a detailed guide on how to tune the installer and startup the deployment of an instance but it is on hold for now while we're working on the rspamd release.
Please tell if you wish to contribute on writing such doc !
@almereyda commented on GitHub (Oct 17, 2023):
I would like to contribute to writing end-user oriented documentation for Modoboa's four main audiences as seen from the frontend: Simple users, Domain administrators, Resellers and Super administrators.
I would even change the wording of these audiences a bit, and reorder them by degree of power in the New Account UI, with power-levels increasing to the bottom, and also in so Simple users are the default on top of the list:
No simple, as no other kind of type User is available.
People and power users understand this term intuitively.
"Super" feels a bit elitist here
But don't allow me to overtake this issue. Should I open a new ticket for end-user documentation, and make some proposals (of technical documentation generators) how that could look like?
I came here via https://github.com/modoboa/modoboa/projects/4 and this is tagged documentation, why the discussion may be worthwhile, but not focused on the original subject anymore. Given the few tickets remaining in that board, maybe this would also be an appropriate moment to start one of the new Project boards about documentation? They are much more accessible.
https://github.com/modoboa/modoboa/projects
@Spitfireap commented on GitHub (Oct 19, 2023):
You can open a Github discussion but the easiest way would be to come to the discord server. The link is available on the Readme ;).
@almereyda commented on GitHub (Oct 19, 2023):
Discord, my anti-love. I'm coming.