Unable to increase the maximum encryption size to 25MB

[Greg Muszynski]

The new version 8.0.1 of Cisco IronPort Email Security Appliances promises that we can increase the default encrypted message size from 10 MB the old max to 25 MB, however when we try to do this on either our C370 or our C660 using either the GUI or the CLI we are unable to do so.  There is no error per say, nothing happens when we click the Submit button in the GUI, and there is nothing to commit when we try to step through the CLI EncryptionConfig menu to increase it.

Are any of you experiencing the same problem, can you try changing the size and let us know what happens please?

[Robert Sherwin]

So - you are seeing similar --->

What is message tracking showing when you try to send a CRES designated/encrypted message through?

For mine - I have increased to allow a 25M encrypted email - and sent through:With headers, email body, and 15M attachment - that is 20.5MB total size... 21524331 bytes...

Thu Mar 13 14:26:08 2014 Info: ICID 951 ACCEPT SG UNKNOWNLIST match sbrs[none] SBRS rfc1918
Thu Mar 13 14:26:08 2014 Info: Start MID 842 ICID 951
Thu Mar 13 14:26:08 2014 Info: MID 842 ICID 951 From: <robsherw@cisco.com>
Thu Mar 13 14:26:08 2014 Info: MID 842 ICID 951 RID 0 To: <robsherw.cisco@gmail.com>
Thu Mar 13 14:26:15 2014 Info: MID 842 Message-ID '<A369491A-426B-4489-87CE-54BF435FD504@cisco.com>'
Thu Mar 13 14:26:15 2014 Info: MID 842 Subject '[ENCRYPT] 15m file'
Thu Mar 13 14:26:19 2014 Info: MID 842 ready 21524331 bytes from <robsherw@cisco.com>
Thu Mar 13 14:26:19 2014 Info: MID 842 matched all recipients for per-recipient policy mycisco_inbound_policy in the inbound table
Thu Mar 13 14:26:19 2014 Info: MID 842 was too big (21524331/1048576) for scanning by CASE
Thu Mar 13 14:26:29 2014 Info: MID 842 rewritten to MID 843 by add-footer filter 'Footer Stamping'
Thu Mar 13 14:26:32 2014 Info: Message finished MID 842 done
Thu Mar 13 14:26:32 2014 Info: MID 843 queued for delivery
Thu Mar 13 14:26:32 2014 Info: MID 843 enqueued for PXE encryption

Keep in mind - that you have to also have a Mail Flow Policy that allows the maximum message size to allow the same through... so, in my example - the message transpired through the UNKNOWNLIST, which is tied to my ACCEPTED mail flow policy --- in which, it is also set for 25M maximum message size.