Corrupted or blank emails on SmarterMail

I’m have been dealing with Smartermail for many years, probably since V3. The common issue that I’ve been experiencing with SmarterMail is blank and corrupted emails. I’m sure I’m not the only one and if you have googled they were many similar incidents.

I do not have an obvious reason but it has been observed this has happened on IMAP accounts and only on “busy” machine and less likely to happen on the more powerful servers with good IO and less populated servers. Nonetheless, if this is happening to you, try the following,

The blank items indicate that the users mailbox.cfg file became corrupt for their inbox. This can be corrected by performing the following steps:

1. Stop the SmarterMail service and ensure mailservice.exe terminates successfully.
2. Navigate to the users inbox folder, for example C:SmarterMailDomainsdomain.comusersUserIDMailInbox
3. Remove the mailbox.cfg file.
4. Start the SmarterMail service.
5. Sign in as the user, and there should no longer be any blank
messages.

 

VPS with Ploop

To understand the benefits of having PLOOP On OpenVZ container (Linux VPS), we need to knows what are the limitations of the traditional file system on VPS.

  • Since containers are living on one same file system, they all share common properties of that file system (it’s type, block size, and other options). That means we can not configure the above properties on a per-container basis.
  • One such property that deserves a special item in this list is file system journal. While journal is a good thing to have, because it helps to maintain file system integrity and improve reboot times (by eliminating fsck in many cases), it is also a bottleneck for containers. If one container will fill up in-memory journal (with lots of small operations leading to file metadata updates, e.g. file truncates), all the other containers I/O will block waiting for the journal to be written to disk. In some extreme cases we saw up to 15 seconds of such blockage.
  • Since many containers share the same file system with limited space, in order to limit containers disk space we had to develop per-directory disk quotas (i.e. vzquota).
  • Since many containers share the same file system, and the number of inodes on a file system is limited [for most file systems], vzquota should also be able to limit inodes on a per container (per directory) basis.
  • In order for in-container (aka second-level) disk quota (i.e. standard per-user and per-group UNIX dist quota) to work, we had to provide a dummy file system called simfs. Its sole purpose is to have a superblock which is needed for disk quota to work.
  • When doing a live migration without some sort of shared storage (like NAS or SAN), we sync the files to a destination system using rsync, which does the exact copy of all files, except that their i-node numbers on disk will change. If there are some apps that rely on files’ i-node numbers being constant (which is normally the case), those apps are not surviving the migration
  • Finally, a container backup or snapshot is harder to do because there is a lot of small files that need to be copied.

 

In order to address the above problems OpenVVZ decided to implement a container-in-a-file technology, not different from what various VM products are using, but working as effectively as all the other container bits and pieces in OpenVZ.

The main idea of ploop is to have an image file, use it as a block device, and create and use a file system on that device. Some readers will recognize that this is exactly what Linux loop device does! Right, the only thing is loop device is very inefficient (say, using it leads to double caching of data in memory) and its functionality is very limited.

Benefits

  • File system journal is not bottleneck any more
  • Large-size image files I/O instead of lots of small-size files I/O on management operations
  • Disk space quota can be implemented based on virtual device sizes; no need for per-directory quotas
  • Number of inodes doesn’t have to be limited because this is not a shared resource anymore (each CT has its own file system)
  • Live backup is easy and consistent
  • Live migration is reliable and efficient
  • Different containers may use file systems of different types and properties

In addition:

  • Efficient container creation
  • [Potential] support for QCOW2 and other image formats
  • Support for different storage types

 

This article is extracted and found at : https://openvz.org/Ploop/Why

Outlook 2013 IMAP Sync Troubles

Recently, I’m experiencing issue with IMAP Sync troubles with my Outlook2013. Many articles point to  the direction on the update KB2837618 and KB2837643 were released by Microsoft on 12 Nov 2013 that might have caused the hiccups. However, I don’t recommend un-installing these updates as they add some IMAP improvements and you’ll have a better IMAP experience with these updates.

I personally recommend these methods;
The first, and I reckon this is the most effective method is to add Inbox to the IMAP root.
To do this, go to File, Account Settings and double click on your affected IMAP account. Click “More Settings” button then switch to the “Advanced” tab.
In the Root folder path field type Inbox. Exit the dialog and perform a send and receive.

However, there are 2 things you need to take note of;
a. If the Inbox is not your root folder, setting Inbox as the root won’t work, as it will hide all of the other folders.
b. The rules and alerts with folders specified will be disabled due to errors that these locations are no longer exist.

If that doesn’t work, try disabling the option to show only subscribed IMAP folders.
Right click on the IMAP Inbox folder and choose IMAP folders. At the bottom of the dialog is an checkbox for When displaying hierarchy in Outlook, show only the subscribed folders. Remove the check then close the dialog to return to Outlook. Click Send and Receive.