CF10 Update Notification Email Fails to send

Question

In CF10 under Server Update, you can have it send an email to notify you if there are any updates available.  Unfortunately, the format of the "From" value in not a valid email format so I get the following error in the exception.log
com.sun.mail.smtp.SMTPSendFailedException: 501 5.1.7 Invalid address
The undelivered mail looks like this.  Any way to make the from value from a valid email address instead of just "ColdFusion"?
type:  text/html; charset=UTF-8
server:  redacted.redacted.com:25
from:  ColdFusion
to:  [email protected]
subject:  New Update Available for ColdFusion Server
X-Mailer:  ColdFusion 10 Application Server
body:  1 updates available for ColdFusion Server(version: 10,0,0,282913)<br/>
body:                                          <p><table width="100%" cellspacing="5">
body:  
body:                                                    <tr ><td width="100%"><b>ColdFusion 10 Update 4</b><br/>
body:  
body:  If the version of your ColdFusion 10 installation is 282462, ensure that you have applied the mandatory update
body:  available at http://www.adobe.com/support/coldfusion/downloads_updates.html before applying this update.
body: 
body:  The ColdFusion 10 Update 4 includes several important bug fixes.
body:  For a complete list of fixes included in this update, click "Read More".
body: 
body:  IMPORTANT: After applying the update, reconfigure the connectors using wsconfig tool. It is in {cf_install_home}/cfusion/runtime/bin
body: 
body:  Note that this update is cumulative and includes fixes from previous updates.</td>
body:                                                    </tr>
body:                                                    <tr><td width="1" bgcolor="#FFFFFF"></td></tr>
body:  
body:                                          </table></p><br/>
body:                                          Login to ColdFusion Administrator to get more details and install updates.

Answer 1

i am currently working with adobe coldfusion technical support on this issue
Adobe is aware of  the bug below
https://bugbase.adobe.com/index.cfm?event=bug&id=3373350