[PR #1796] [CLOSED] FIX: relaydomain: next hop should matched with the domain's actual MX list #2295

New issue

Closed

opened 2026-02-27 12:10:20 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 12:10:20 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/modoboa/modoboa/pull/1796
Author: @tsabi
Created: 12/1/2019
Status: ❌ Closed

Base: master ← Head: master-mx-check-relayhost-fix

📝 Commits (4)

1a1a732 Add Eclipse/PyDev files to gitignore
1e5fcb6 Fix: invalidate MXs
999effd FIX: relaydomain MX list should matched with the actual domain's MX list
7c890b2 FIX: good floating IP MX record check for a relay domain

📊 Changes

2 files changed (+53 additions, -2 deletions)

View changed files

📝 .gitignore (+2 -0)
📝 modoboa/admin/management/commands/subcommands/_mx.py (+51 -2)

📄 Description

FIX: relaydomain: next hop should matched with the domain's actual MX list

If you create a relaydomain, than the DKIM and SPF checks are useful,
because they check that in the domain's data you really have good
config. But the MX check is not useful, because it tries to match with
your valid MX list (setted globally in the config panel), what is a good
behavior for a handled domain, but for a relay domain it is not.

This modification modifies the MX record checking methodology that it
checks if your relay hop is setted as a MX receiver for that domain, so
with the MX red/green tag on your dashboard you can check that you
forward your emails into the good target server or not.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/modoboa/modoboa/pull/1796 **Author:** [@tsabi](https://github.com/tsabi) **Created:** 12/1/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master-mx-check-relayhost-fix` --- ### 📝 Commits (4) - [`1a1a732`](https://github.com/modoboa/modoboa/commit/1a1a732bde0e50bb067bf8cbb155d5835c444eb0) Add Eclipse/PyDev files to gitignore - [`1e5fcb6`](https://github.com/modoboa/modoboa/commit/1e5fcb654fa8760039d5ada064d84edefd0859b4) Fix: invalidate MXs - [`999effd`](https://github.com/modoboa/modoboa/commit/999effd6cf9348ae253fb53c7bb2784776369dfa) FIX: relaydomain MX list should matched with the actual domain's MX list - [`7c890b2`](https://github.com/modoboa/modoboa/commit/7c890b21fe9541f767539f09cb6122e5b6052952) FIX: good floating IP MX record check for a relay domain ### 📊 Changes **2 files changed** (+53 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+2 -0) 📝 `modoboa/admin/management/commands/subcommands/_mx.py` (+51 -2) </details> ### 📄 Description FIX: relaydomain: next hop should matched with the domain's actual MX list If you create a relaydomain, than the DKIM and SPF checks are useful, because they check that in the domain's data you really have good config. But the MX check is not useful, because it tries to match with your valid MX list (setted globally in the config panel), what is a good behavior for a handled domain, but for a relay domain it is not. This modification modifies the MX record checking methodology that it checks if your relay hop is setted as a MX receiver for that domain, so with the MX red/green tag on your dashboard you can check that you forward your emails into the good target server or not. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>