That’s not what I meant… How did you have the certificate issued from Let’s Encrypt in the first place. Did you use Certbot? Some other command-line tool? A tool built into some web GUI?
That's the problem. Your mailserver is presenting a certificate that says "I am a valid certificate issued by Let's Encrypt for the domain mail.wam360.com". So, when you connect to mail.bizweb360.com, your client says "well, this certificate isn't valid for the domain I'm connecting to!" If you use both -d flags, you will get a certificate that says "I am a valid certificate issued by Let's Encrypt for the domains mail.wam360.comandmail.bizweb360.com", to which clients connecting to either domain will accept as valid.
You will need to apply the certificate generated with both names after you create it and use/renew this one going forward.