Preview Tool

Cisco Bug: CSCvu90921 - [ENH] New variables added to the Headers FromName and FromDomain

Last Modified

Jul 20, 2020

Products (1)

  • Cisco Email Security Appliance

Known Affected Releases


Description (partial)

Feature Request Form filled by the customer.

What product(s) do you want this change to affect?

Cisco C100V
Cloud Email Security Appliance

What version(s) of the product(s) (AsyncOS, PostX, IEA, plug-in, etc) are you currently using in your organization?

Version: 13.0.0-392

Please describe how the current limitation(s) impact your business:

Would like to show users the senders actual email address of received emails but not give them the ability to click on it as a link in Outlook. Current variable is recognized by outlook as an email address and converts it to a link to that address. 

Describe how the system's behavior could change or be enhanced to facilitate your business needs:

I would like a way to break up the @from variable so that it isn’t recognized in Outlook. I think this could be done by creating new variables to break up the email address with so instead of @from create new variables

@fromname - nstefano
@fromdomain -

So I would put into my text resource?This email was sent from @fromname @ @fromdomain 

Or you could create a new variable that outputs it into a format the Outlook doesn’t recognize it as an email address. 

If you have a particular vision for how this would be implemented in the user interface, please outline that:

See the answer to the previous question. 

Feel free to leave any additional comments:

Thank you for your efforts and consideration of this request.

This is not a bug this is a planned enhancement please review the justification.

Current criteria only allow the use of the variables $From and $EnvelopeFrom, this makes the end-users able to click and get redirected to new email creation, this should be an option for the end-users and not get redirected directly.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.