Why is a prefix for XMPP needed. The nice thing of XMPP is, your counterpart can use your email adress for email and instant messaging as well. No need for a subdomain. As i want to migrate my old xmpp to the mailcow ejabberd, how can i get rid of the prefix? I tried to leave the configuration field empty in the dns configuration of mailcow - but it cannot be saved without something in it.
EnglishPrefix forXMPP
I would to have the same, email same as xmpp-I’d, or that xmpp-I’d redirects to main domain if a mail is send to it 
Have something to say?
Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!
Было бы действительно удобно если адрес для XMPP будет такой же как для почты, такое можно реализовать?
Is certainly possible but the current configuration does not allow this 
Please take the trouble to translate your texts.
You need a certificate for the domain of your JID. For most people it’s not possible to point their domain.tld (sld) to mailcow, so we just go by a prefix by default.
I don’t think that’s what make XMPP nice tbh, I don’t actually care about a prefix and like a clean separation.
I totally agree on the Administration part. Having a clean separation for http upload, webinterface etc - there i’m totally fine with it. But for the JID i’ve never seen that in the wild someone using a separate subdomain. Some of my businesscards stating email/xmpp would be no longer valid…
I thought twice about it. I at least have on the main domains company.tld anyway a http redirect to a different subdomain www.company.tld - So I at least in my case wouldn’t mind handling mailcow the main domain also for certificates (as long as there can be a simple http redirect to www) to get the ability to use the main domain for xmpp. I think others could do so as well.
I will think about the ability to remove the prefix.
But please optional 
otherwise all must be changed again 
Yes, absolutely.
8 days later
Might that be a workaround? 
DNS configuration in Jabber/XMPP – Prosody IM is stating, that with the SRV RRs one can redirect the clients to another domain, where the XMPP server is hosted. In our case, the “other” server is just the sub-domain: prosody.im
_xmpp-client._tcp.example.com. 18000 IN SRV 0 5 5222 xmpp.example.com.
_xmpp-server._tcp.example.com. 18000 IN SRV 0 5 5269 xmpp.example.com.
They are also stating: The target domain MUST be an existing A record of the target server, it cannot be an IP address, and cannot be a CNAME record.
- Edited
it will be most likely not a workaround but the neccessary configuration for this case. as mailcow is hosting multiple domains. xmpp.example.com is our mailcow.
example.com is the domain that should be served. but the xmpp server on mailcow needs to know that it is responsible for example.com (he maybe knows but he’s responsible for im.example.com - but currently i cannot tell you are (also) responsible for example.com.
and in the text you quoted: Note about certificates: When requesting/generating certificates for your domain, you need your certificates to be valid for the virtual host name, not the domain that your SRV records point to. For more information see ‘Which domain?’ in our certificate documentation. So that’s what Note about certificates: When requesting/generating certificates for your domain, you need your certificates to be valid for the virtual host name, not the domain that your SRV records point to. For more information see ‘Which domain?’ in our certificate diekuh said already - that the certificates must be right for “example.com” in this case. So it’s not just redirecting to a different server, the different server needs the right certificates also.
No one is typing