Plesk 11.x / Linux :: New Mailbox Variable From (Mail Account Updated) Event

PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE
Parallels Plesk, 11.5, .30_build115130819.13, Debian 7.0, Intel 64bit

PROBLEM DESCRIPTION
When triggering the events 'Mail account created' or 'Mail account modified' the returned variable NEW_MAILBOX will always state TRUE regardless of the mailbox option being ticked or not ticked on the 'New mail account' option located on the 'Mail' tab of a subscription.

STEPS TO REPRODUCE
1: Log in to plesk.
2. Select 'Tools & Settings'
3: Select 'Event Manager'
4: Select 'Add New Event Handler'
5: Select Event 'Mail account updated'
6: Enter in '/usr/bin/php /root/scripts/dbmail/mail_mod.php' to the Command box.

[Code] ....

ACTUAL RESULT

[NEW_MAILBOX] => true

EXPECTED RESULT

[NEW_MAILBOX] => false

ANY ADDITIONAL INFORMATION

I submitted this with parallels support and they stated that the variable NEW_MAILBOX will always return as TRUE regardless of if the mailbox option is ticked or not. They also stated the NEW_MAILBOX variable will be true regardless of any action taken on the panel with mail accounts.
The actual documentation on this variable is very sparse

Component name/description Old component value New component value
Mailbox old_mailbox new_mailbox

We previously had some code that would trigger on this variable and would create a mail account on our mail server with or without a mailbox.

if (!strcmp(getenv('NEW_MAILBOX'),"true") && !strcmp(getenv('OLD_MAILBOX'),"false")){
//Create a mailbox on the external mail service
}
if (!strcmp(getenv('NEW_MAILBOX'),"false") && !strcmp(getenv('OLD_MAILBOX'),"true")){
//Create a mail forwarder on the external mail service
}

At some point this variable has stopped working with newer versions of plesk. Having a variable that is always true regardless of what is done when creating a mail account seems pointless and requesting a new feature that was already there in older versions doesnt seem like something that should be requested on a new feature request.

QUESTION: Is there anyway to get this functionality restored other than requesting it gets re added via [URL] ....