==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====

Hello,
CentOS - MySQL - Admin Pro current.
New build on certain date which resulted in various Amavis DB schemas. 

Initial install with postmaster@sub.domain_name.tld created.
Production system another datacenter.
Rsycn mail across.
Production systems did NOT have the sub.domain_name.tld in the system and thus not postmaster either.
Did Mysql dump of production and restore to new system.  Same versions of software BUT the repo for Amavisd DB has updated to new release, either your RPM or they released... 

Run: postqueue -p

See email for root@sub.domain_name.tld and even postmaster@sub.domain_name.tld. 
Review of email seems to be log data from backupscripts, etc. 

Remove all mail. 
Attempted to add sub.domain_name.tld to system along with a postmaster@sub.domain_name.tld. 

However, postqueue -p still shows email with ID* as if hung in processing.  Will not flush and does not deliver to said address once created in iRedAdmin-Pro. 

So, where, what to correct the issue?
What has occurred in installing such system/scenario causing failure?
What is the best practice to use for initial domain_name during install and/or use of subdomain?

Thank you.