• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Quick question regarding how to handle email for domain.com as well as sub.domain.com

B

brooks

Guest
If someone knows the answer to this I would appreciate it. What we have is:

mail -> ingress mail server -> hosting/mail server

The hosting/mail server running Plesk 10 is configured as:

hostname: host.domain.com
hosted domain: domain.com

mail is relayed via the inbound ingress mail server for [email protected] to host.domain.com. The server rejects the mail with the following error:

<<< 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual alias table
550 5.1.1 [email protected]... User unknown
<<< 554 5.5.1 Error: no valid recipients

If I change the hosted domain name to mail.domain.com and setup the ingress mail server to deliver to [email protected] it works but I don't really want my users to have to use the full domain name of "[email protected]" to login.

I tried to enable short names using:

./mailserver --set-account-type both

but I still see the following in the maillog:

checkmailpasswd: FAILED: test- short names not allowed from @ [::ffff:1.1.1.1]ERR: LOGIN FAILED, ip=[::ffff:1.1.1.1]

Isn't that the correct way to enable short names?
 
Back
Top