There are Some Rules in the Universe that you Cannot Break…
    

Like the speed of light for example (for now anyway) and the airspeed velocity of an unladen swallow (see here).
  

For entirely different reasons however, the creators of the Yellowverse have imposed upon us, the little creatures inhabiting this world, different kinds of limits. Like, for example, the 32k limit on text field.
   

Sometimes, creative developers have found work around or coded around that issue … but there are other times where it just plain hurts and you can’t do nothin’ about it.
   

Point in Case: Hitting The Limit Of 32k When Adding Mail Rules To A Server Configuration Document
   

When adding 1 new mail rule to your server configuration document, you get this nasty error (click on the image below to see a bigger version):
 
   

 
So, what can you do when this happens? Not much really. You can try a few things however to make some room:
   

• Review all the mail rules in your server configuration document. Remove all those that aren’t needed anymore.
• Review and check if you could combine some rules together.
• Review and check if can make any rules “smaller”, for example if you had a rule that said “journal when sender is jsmith@whatever.com” you can change it to just “journal when sender is jsmith”.
• If you can, journal everything that is sent and received on your server (it might make the size of your mail journal file increase incredibly fast however).
     

But There Might Be a Glimmer of Hope
  

I opened a ticket with Lotus Support and the support rep created SPR #KGEW84SR3T to add “when Sender or Any Recipient Contains” as an option when creating mail rules.
   

So, if you are like me and you’ve hit the limit, I recommend that you also open a PMR with Lotus Support to ask them to change the way Mail Rules are saved along with Server Configuration Documents.
  

Thanks for reading!
   

Marc