This is not really a lucee issue, its a RFC / Mail transport issue.
You should not directly send email from any lucee box to the world, unless you are provisioning that box with a proper DNS MX record and conditionally want that box to receive email as per the RFC compliance, red path and other anti-spam service measures, just do not do it.
you can use lucee to send email via nearly any third party service, but what I have found is its easier to use a relay server. You can even set up your lucee instance to run postfix, sendmail, hmail, mercury mail, mail enable, to name a few.
create your account on the relay server. Your relay server can be your internal properly setup MX , SPF, DKIM mail server or forward to what that does.
Because this is what is happening with your mail
Lucee box spins up and fires off email
lucee pulls the localhost name from the OS
The mail server on the other end considers the email as a bogus non compliant traffic and does what ever policy they have set for bad actors and spam.
as for the tag, this works for us.
Note, As above I use a relay server hosted locally then pushes this out to our mail server
<cfset mailFrom="DO NOT REPLY <DONOTREPLY@mydomain> " >