Question Mail server setup on subdomain for main domain

[andreyts]

Server operating system version

CentOS Linux 7.9.2009 (Core)

Plesk version and microupdate number

Plesk Obsidian 18.0.66 Update #2

Is it possible to setup mail server on subdomain (mail.example.com) but to use main domain (example.com) in email addresses? DNS is not problem.
I ask it because our hoster of main domain doesn't open 25 port but there is possibility to register mail domain on other hosting where Plesk is. But, I cannot find a valid way to add email addresses like [email protected] in subdomain. I just can do it for subdomain [email protected], that doesn't work for us.

I know it is possible in Plesk but cannot find/google any instructions about that.
Thanks.

 

[Kaspar]

This sounds like a use case for the new smarthost feature in Plesk. To use this, on your mail server (the one with the open port 25), you could create a regular mailbox. It shouldn't matter what domain you use or how you name the email address. The mailbox is basically only used to access the mail server from you other Plesk server on which Port 25 is blocked.

On the Plesk server for which port 25 you can use the login credentials of the mailbox for the Smarthost. You can configure the smarthost via Tools & Setttings > Smarthost. Obviously you'll need to select a port other than 25 for the connection to the sever your using as smarthost. Also don't forget to adjust the SPF records for the domain(s) accordingly.

Note that configuring a smarthost will route ALL email trough the smarthost (not just one domain).

Hope this helps.

 

[andreyts]

Ah, I already resolved this issue in other way but perhaps Smarthost might work.
What I did:

• Renamed Plesk server where 25 port is enabled to any valid name, for ex, "host.server.com" (main domain/host "server.com" already is there and DNS assigned).
• Created "example.com" mail host there and added mail accounts. No any subdomain is used, etc.
• Assigned MX record of "example.com" to "host.server.com", added SPF and DKIM records.

Mainly issue was in DNS settings since MX record cannot be assigned to IP, just to domain.