I have mailinbox installed on box.randome.camp, serving email for randome.camp domain and and another personal domain. (Every works fine I am very happy with mailinabox !)
I have sympa (mailing list tool) on another server at listes.randome.camp
I have set up a relay postfix, so mail send from listes.randome.camp are relayed by box.randome.camp.
Sending mail works good. Server can send email to differents email adress, no issue
My issue is when I send email to @listes.randome.camp
listes.randome.camp never receive email.
mailinabox is handling all my dns.
so I have entered an A and mx entry :
listes.randome.camp A 184.108.40.206
listes.randome.camp MX 10 listes.randome.camp.
So I added firstname.lastname@example.org for catch allreceving email.
Now the issue, is when I send an email from ma mail client to the mailing liste, email@example.com, email goes to the inbox of firstname.lastname@example.org
email never reach listes.randome.camp, the sympa server, for processing (and beeing send to listes member)
For syamp to work, it need to be able to receive email I think …
It appears that Sympa is designed to send directly to the internet …
When I check with dig it looks as it should be and displays the MX records, so I suspect this is an issue with the tool that you are using to check with. However, at this point the MX records are incorrect. More later…
In my first response, I stated correctly that you were sending emails to the Sympa server, but assumed incorrectly that you wanted them to be sent to the MiaB server.
So to correctly do this, remove the user on the MiaB box for email@example.com – I am not sure which user you added. If more than one, remove them all.
Then on the Custom DNS page enter listes in the Name (subdomain) box with the dropdown set to randome.camp.
At present you have 2 MX records for listes.randome.camp - one pointing to MiaB and the other to the Sympa server. This is not correct. You need just the one for listes.randome.camp.
I do not understand how and where you have:
Nowhere in the Sympa documentation does it state to do this so I am wondering what you are doing here?
Not relay it to box.randome.camp as Sympa is expecting mail to be delivered locally per the transport maps defined within postfix on that server, per the documentation. If you are relaying mails destined for listes to the MiaB, it is going to be intercepted by the MiaB server and dealt with appropriately. Appropriately being defined from the perspective of the MiaB server, not the Sympa server.
You also need to set rDNS on the Sympa server at Hetzner or most providers will reject your emails. And you’ll need to set a TXT SPF record as well in DNS for `listes.randome.camp’.
So my conclusion is that you have created a level of complexity that is not supported by Sympa, for a reason that is not apparent…
Hello, Thank you for taking the time to answer me.
In sympa documentation, they just want a MTA running.
I though about using postfix as a relay, to send email through miab, because miab as good configuration and email comming out of Miab as good reputation and is not seen as spam.
On sympa mailing list, in french, there are multiple user having their “thrusted” mail server on one vps, and sympa on an another vps, and local mta on sympa machine relaying to the mail server.
That’s where the idea comes from.
I agree, that is not correct.
It seems as soon as you create a user on a domain/subdomain, Miab creates the mx rules.
as you can see in the screen shot, It is not user configured.
So I deletted user : firstname.lastname@example.org
there are no user nor alias on miab with @listes.randome.camp on miab
I have check DNS on MIAB, looks good now.
After few minutes, Dig mx results looks also good :
When the right conditions are met, correct. Sadly the underlying VPS provider has a lot to do with it. Much less MiaB specifically.
I see and this makes sense. It could work fine, just not so much with MiaB being involved, since MiaB wants to control DNS as well. But even if you could overcome that, MiaB requires there to be an account (or alias/catchall) for the from address, so that makes things difficult, actually impossible, I believe.
I do see that my AnyMXrelay SMTP relay may be something that could help those users you mentioned as long as the mailing lists are double-opt in and can be rate limited to a max of 300 per hour sending.