Instead of logging on to each of your external email accounts, you can retrieve all your accounts’ email messages directly from Zimbra. It’s one of those things you just expect to work with an enterprise ready solution like Zimbra. Still, one customer using the Zimbra mobile web client informed me that he had to use the webmail client to retrieve new messages from external accounts, before they became available on his phone. After checking the server logs I could confirm that the mobile web client did indeed not poll any email messages from external accounts.
Zimbra allows you as the administrator to schedule polling from external accounts to avoid having users doing this manually. It’s done on the COS level, and this is how:
From the Zimbra Administration interface, navigate to “Home” => “Configure” => “Class of Service” => “Selected COS” => Advanced ["Data Source"]
From the “Data Source” fields you may now change the polling intervals for POP3 and IMAP. The default value “unlimited” just indicates that no scheduled job is defined or running. Change the polling values to something sensible (meaning you don’t want to hit external servers every other minute) and apply the changes. On Zimbra 8.x this change will roll out immediately without any need to manually restart services.
To check if its working as expected you can do a grep for “ScheduledTask” on the mailbox.log with the command:
I bought BioShock on a Steam sale once upon a time and finally got around to playing it. However, a few minutes into the game I realized that the lack of sound was not due to my character going deaf from an initial explosion. After trying to tweak the sound settings without any success I came to realize that BioShock is rather old as it was released back in 2007. Thus, it’s not exactly certified for Windows 8. A quick fix was to run the game in compatibility mode for Windows XP (Service Pack 3) which immediately brought the in-game sound back to life.
One way of doing this is as follows:
From Steam’s Game library” right click on BioShock and select properties, then select the tab called “Local files” and finally click the button labeled “Browse local files”. You’ll now find yourself in the game directory. Navigate down the “Builds” and “Release” folders and finally right click “Bioshock.exe” (the game executable) and select properties. Then select the “Compatibility” tab and tick “Run this program in compatibility mode for: Windows XP (Service Pack 3)”. Click “Apply” and you’re all set. A quicker way to locate Bioshock.exe would obviously be to just search for the file.
The game performs great in XP compatibility mode and after ten hours of playing it has only crashed twice. That’s all right in my book.
Windows 8.1, 64-bit
Intel Core i7 3770K 3.50GHz
GeForce GTX 680
Version: Luna (4.4)
Build id: I20140606-1215
PHP Development Tools (PDT) 184.108.40.206406110111
After upgrading my workstation to Slackware 14.1 with KDE 4.10.5 as my default desktop, I was left with some issues regrading my new Eclipse Luna installation. Notably the tooltip was unreadable with its black background color, and much worse, the code assist would not render any HTML whatsoever.
Fixing the dark tooltip background:
After searching through most of Eclipse’s menus and settings, it became evident that the easiest solution would be to change the tooltip background color by using KDE’s application appearance setting. Navigate to “System Settings” => “Application Apperance” => “Colors” => “Colors” => “Color set: Tooltip” and pick a lighter background. There might be a more sophisticated way of doing this on a per-app basis but it evaded me.
Fixing HTML rendering for the Code Assist:
Eclipse uses SWT which is an open source widget toolkit for Java designed to provide efficient, portable access to the user-interface facilities of the operating systems on which it is implemented. Further, the SWT Browser widget is used to display HTML documents. It is designed to provide a basic and portable API sufficient for essential HTML browsing and rendering on the platforms on which it is implemented. On a Linux system, this means GTK.
Since I used the SlackBuilds repository to install Eclipse with all dependencies I believed I had everything covered. However, after reading this information at the aforementioned SWT FAQ, I learned that Eclipse Luna (4.4) uses GTK 3 by default. Thus I needed to configure WebKitGTK+ with GTK3. The simple solution is to pick up webkitgtk3 from the SlackBuilds repository and install it alongside or instead of webkitgtk.
As a simple PDT user with limited understanding of the inner workings of Eclipse, I got to admit I might start looking for a more simplistic IDE. At least I’ll be hesitant to upgrade to any new major release.