Trigger's maximum size?

[niumar]

I need compose a very large trigger. It is a result of a karnaugh map with 5 variables.

It should not trigger only when user1 or user2 or user3 login on a server between 8:00h and 18:00h. These users in other time or other users in any time should trigger an action.

These complex condition gives me the trigger showed below

({Template_Linux_Vpn:login.access.regexp(user1)}=0 &
{Template_Linux_Vpn:login.access.regexp(user2)}=0&
{Template_Linux_Vpn:login.access.regexp(user3)}=0)
|
({Template_Linux_Vpn:login.access.regexp(user1)}=0 &
{Template_Linux_Vpn:login.access.regexp(user2)}=0&
{Template_Linux_Vpn:login.access.time(0)}<080000)
|
({Template_Linux_Vpn:login.access.regexp(user1)}=0 &
{Template_Linux_Vpn:login.access.regexp(user2)}=0&
{Template_Linux_Vpn:login.access.time(0)}>180000)
|
({Template_Linux_Vpn:login.access.regexp(user1)}=0 &
{Template_Linux_Vpn:login.access.regexp(user3)}=0&
{Template_Linux_Vpn:login.access.time(0)}<080000)
|
({Template_Linux_Vpn:login.access.regexp(user1)}=0 &
{Template_Linux_Vpn:login.access.regexp(user3)}=0&
{Template_Linux_Vpn:login.access.time(0)}>180000)|
|
({Template_Linux_Vpn:login.access.regexp(user2)}=0 &
{Template_Linux_Vpn:login.access.regexp(user3)}=0&
{Template_Linux_Vpn:login.access.time(0)}<080000)
|
({Template_Linux_Vpn:login.access.regexp(user2)}=0 &
{Template_Linux_Vpn:login.access.regexp(user3)}=0&
{Template_Linux_Vpn:login.access.time(0)}>180000)

Part of it, when I inserted it on Zabbix, is cut. I think this is becouse it is too large.
So, when I exclude one of the users from the condition, the trigger becomes smaller and enters full in Zabbix. And works fine.

So finaly, is there a way to increase the trigger size?

[Alexei]

I think you could use a little bit more advanced regexp's to make it smaller. Trigger expressions are currently limited by 255 characters, I'm afraid there is easy way to make it larger.