Can't find Unicode Property definition in BoxTrapper
I have one user who is getting mail failures in BoxTrapper. The message is (user-specifics removed):
This is WHM 11.46.1 (build 4) under CloudLinux 6.6. This account was imported from another server with a cpbackup. I've validated every rule in the user's whitelist for syntax. The only reports I can find with this message date from 2008. Really at a loss for what to try next.
[2014-12-18 15:11:47 -0500] die [Internal Death while parsing 876397] Can't find Unicode property definition "i" at /usr/local/cpanel/Cpanel/BoxTrapper/CORE.pm line 205, line 59.
at /usr/local/cpanel/Cpanel/BoxTrapper/CORE.pm line 205, line 59.
Cpanel::BoxTrapper::CORE::BoxTrapper_checklist("white", "/home/*****/etc/*****.com/*****", "***from address***", ARRAY(0xc2b848), ARRAY(0xc2b860), "test") called at bin/boxtrapper.pl line 157
Can't find Unicode property definition "i" at /usr/local/cpanel/Cpanel/BoxTrapper/CORE.pm line 205, line 59.
[A fatal error or timeout occurred while processing this directive.]This is WHM 11.46.1 (build 4) under CloudLinux 6.6. This account was imported from another server with a cpbackup. I've validated every rule in the user's whitelist for syntax. The only reports I can find with this message date from 2008. Really at a loss for what to try next.
-
I've validated every rule in the user's whitelist for syntax.
How many rules does the user have setup? if only a few, it might be easy enough to remove / re-add one by one.0 -
The user has 1409 whitelist rules. I could do a binary search and get it in 11 passes, given that it's only one rule that's causing the problem. I can set that up in a test account and test at will, but I was hoping to avoid that. This is a reseller who recently switched over to us and this is the second issue we've had with mail loss due to BoxTrapper's inability to gracefully handle this kind of error. I was hoping for a more automated diagnose/repair process. 0 -
Found the offending rule. Still wish there was a more graceful failure mode here. 0 -
]Found the offending rule. Still wish there was a more graceful failure mode here.
Hello :) I am happy to see you were able to address the issue. Feel free to open a feature request for better failures on BoxTrapper: Submit A Feature Request Thank you.0
Please sign in to leave a comment.
Comments
4 comments