Cisco Bug: CSCup97047 - Granular control of Mail Flow Policy capability "rate limit by ender"
Nov 11, 2016
- Cisco Email Security Appliance
Known Affected Releases
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 firstname.lastname@example.org= 10 and email@example.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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases