and with all due respect, this will not help. Well it won't help for the short term, but may be a long term solution if it fits with your way of business as TU2 stated.
The exchange public and private stores are databases, and like many other databases, the database files will GROW themselves dynamically, but they will NOT shrink themselves dynamically.
One can delete every email and/or you can copy everything to .pst files, but if you look at the priv1 database files, you'll see that this will not make the file sizes of the priv1.* database files any smaller.
To shrink the file sizes after some massive delete or migration, you'll have to run ESEUTIL /D, another offline process, but this will require that you have sufficient capacity on the volume to create a second copy of the priv1.* database files as the defrag progresses, or move the files temporarily to a volume where there's sufficient capacity for 2 copies of the subject files where you can run the ESEUTIL /D command.
Your best bet for a short term fix is to find some files you can delete or move off of the volume (Have you moved your Windows swap/page file to a different volume?, this will require a reboot). Ccleaner, free download from www.ccleaner.com has a great tool for deleting unnecessary files and will not require a reboot.
Next, at some appropriate maintenance window or non-production hours, and you can do this as soon as tonight, back up your exchange database and relocate the database files to another volume using the Exchange System Manager.
Speaking of backups, is the %programfiles%/exchsrvr/mdbdata directory filled with E00*.log files? If so, you don't have an exchange-aware backup process happening and this too can explain why the volume is filling. You can TEMPORARILY and with caution, move the oldest of said log files to another volume. I say "with caution" because if you don't have a current exchange backup and you need to restore your exchange database, these log files may be needed to restore your exchange database. Now are you completely confused?