Guest

Preview Tool

Cisco Bug: CSCup97047 - Granular control of Mail Flow Policy capability "rate limit by ender"

Last Modified

Nov 11, 2016

Products (1)

  • Cisco Email Security Appliance

Known Affected Releases

8.0.1-023 8.5.6-073

Description (partial)

Symptom:
What product(s) do you want this change to affect?
Ironport ESA C160

What version of the product (AsyncOS, PostX, IEA, plug-in, etc) are you currently using?
Ironport ESA C160

Please describe how the current limitation(s) impact your business.
Currently within the Mail Flow Policies (MFP) there is the ability to rate limit by senders.  This capability is provided across the board for all connections being classified into the SenderGroup and the associated MFP. 
Describe how the system's behavior could change or be enhanced to facilitate your business needs.
Customer is asking for granularity (sender) to apply limits across a specific domain depending on the sender.  Example: enoforce limits across the domain but allow for different limits  user1@domain.com= 10 and user2@domain.com = 20  
If you have a particular vision for how this would be implemented in the user interface, please outline that.
As soon as possible/

Conditions:
Currently within the Mail Flow Policies (MFP) there is the ability to rate limit by senders.  This capability is provided across the board for all connections being classified into the SenderGroup and the associated MFP.
Bug details contain sensitive information and therefore require a Cisco.com 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.