Well, noticed no mail came into my server and could see they were stuck on my mailcleaner with the error “SMTP error from remote mail server after initial connection… 421 4.3.2 Service not available”
As always I just set up an recieve connector to listen on port 25, but as it turns out, Exchange 2013 really doesn’t like that, when I have frontend/edge services reciding on my hub transport server as well – Meaning I have all (two) roles on the same server.
Anyway, problem is that Exchange 2013 comes preconfigured to accept mails, including a connector to recieve on port 25. It apparently does not like when I created a new custom hub-connector listening on the same port as the front-end connector.
Solution for me was to simply just delete my new custom connector, but that only works for me because connections to my server are filtered by my Firewall.