• 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.

Email Addresses Wrong on Aliased Domain

Toxalot

Basic Pleskian
I have mydomain.com and then I have mydomain2.com which is an alias for mydomain.com. The settings for Synchronize DNS zone with the primary domain, Mail service, and Web service are all enabled.

I set up an email address on mydomain.com with a forward but no mailbox. I later realized their was a typo in the address and fixed it.

I was looking at the virtual alias table (in reference to another post http://forum.parallels.com/showthread.php?t=263793) and noticed that there is an entry for typo (at) mydomain2.com and none for corrected (at) mydomain2.com. I haven't tested sending to these addresses yet as I have not completed the move and DNS still resolves to old site, but I can't imagine that email sent to corrected (at) mydomain2.com would be delivered without an entry in the virtual alias table.

Questions
1) Will this cause a problem? Or does the forward take affect before the virtual alias table is checked? Where does the mail server check for forward info?
2) If I use postmap to update the virtual alias table manually to correct this, will the change stick? I assume the file will be overwritten by Plesk and I'm wondering where the source data is and if it's correct. Will doing this have any bad side effects? Is their a better way to fix this?
3) Is this a bug or is there something I am missing?
 
Renaming an email address sometimes has issues, though works for most times on Plesk. So I recommend, you delete that email address and just create a fresh new one ...Since afterall it does not store any mail so you have nothing much to loose.
 
I think I fixed it, but here's an explanation of what happened and what I did so maybe it can help someone else.

I deleted and recreated the address. Upon inspecting the virtual table, I still had one entry for corrected (at) mydomain.com and one entry for typo (at) mydomain2.com. So I deleted the address and inspected the virtual alias table. corrected (at) mydomain.com was gone but typo (at) mydomain2.com was still there.

I created the address once again. The virtual alias table is not in alphabetical order and difficult to scan visually so I sorted it and noticed that I had 3 entries:
corrected (at) mydomain.com
corrected (at) mydomain2.com
typo (at) mydomain2.com

I can't be sure, but I probably had all 3 even before deleting and recreating the address. I just didn't notice because it wasn't next to the others.

So I don't have to worry about undeliverable mail. The only issue that remained was that typo (at) mydomain2.com was still a valid address. Normally, that wouldn't be a big deal. But another address was changed because it got huge amounts of spam. I don't want spamtarget (at) mydomain2.com to remain a valid address.

I manually removed spamtarget (at) mydomain2.com from virtual alias table. I used the GUI to change an email address (on a domain that doesn't have a domain alias) to have Plesk overwrite my changes to see what happened. Upon inspecting the virtual alias table, it seems that spamtarget (at) mydomain2.com has been permanently removed.
 
Back
Top