Frequently Asked Questions



  • I installed Tagwolf, but it doesn't appear in Outlook 2010?

    If you don't see Tagwolf in Outlook after installation, you are very likely running Outlook 2010 64-bit edition. The current version of Tagwolf only runs in Outlook 2010 32-bit edition (and also in Outlook 2007 and 2003 which are always 32-bit).

    64-bit Outlook users might be interested to learn that the 64-bit edition of Tagwolf has entered beta testing and a final version will be available in the near future.

    How do I know that I have Outlook 2010 64-bit?
    -> You can check which version it is by going to the Outlook File tab, then click Help, and look for the "About Outlook" section to the right of your screen. Then look for the Outlook version number. It should say "64-bit" at the end

  • Can I use Tagwolf to file my emails to Gmail folders/labels?

    In short, the answer is yes, but there are some caveats, especially with Outlook 2010:

    • You need to use IMAP as the protocol for accessing your GMail mailbox.
    • Moving emails to folders can be slow over IMAP, depending greatly on the speed of your internet connection. Your mileage may vary.
    • If you are using Outlook 2010, you need to make a configuration change, in order to avoid having emails ending up in the Deleted Items folder instead of the target folder. Please see below for instructions on how to do that.
    • You have to be aware of the special character of folders in GMail, which might seem confusing at first:
      • Actually there is no such thing as GMail folders. There are only GMail labels. However, GMail labels are represented in Outlook as folders.
      • This means that any email with label "X" in GMail, will appear to be "in" folder "X" in Outlook.
      • Filing an email to an Outlook folder "X" will cause the email not to move, but rather to get the label "X" slapped on to it, and to lose the label "Inbox" at the same time.
      • This also, and perhaps confusingly, means that an email can be "in" two or more folders at once, if you apply two or more labels to it!
      • Another possibly confusing thing: if you delete an email from a folder "X", it is not deleted at all, but just loses the "X" label. So, after delete, it could still be present in other folders when it has the label for those other folders.

    Workaround: Configure Outlook 2010 to make Tagwolf work with GMail labels
    • Click on the "File" tab in Outlook 2010
    • Click on the large "Account Settings" button, and select "Account Settings" from the dropdown menu. You should now see a list of mail accounts
    • Select your GMail mail account in the list
    • Click "Change" in the toolbar above the list
    • Click the “More Settings” button in the lower right corner
    • Click the “Deleted Items” tab
    • You should find that the option "Move deleted items to the following folder on the server" is selected
    • Change this to “Mark Items for deletion but do not move them automatically”

    Why is this configuration change needed?
    • Without this configuration change, when any add-in (such as Tagwolf) asks Outlook to move an email to an Outlook folder corresponding to a Gmail label, Outlook will actually not move the email to that folder, but will move it to the Deleted Items folder instead. This is a bug in Outlook 2010, which we cannot solve in Tagwolf.
    • However, the bug disappears after making the configuration change.

    Please note: this configuration change affects how you can manually delete GMail messages in Outlook:
    • When you manually delete GMail messages in Outlook, they no longer move to the Outlook trash folder as before.
    • Instead they just seem to be removed from whatever folder you happen to be performing the delete in.
    • So "delete" in Outlook gets a new meaning here, and becomes "remove the GMail label for the current folder from the email". The email itself is not deleted by this action as far as we know.
    • While perhaps confusing, this is still logical since, in GMail, a message never "sits in" a folder, but just gets a folder label slapped onto it. A message can therefore even be in multiple GMail folders at once, since it can have multiple labels at once.
    • What happens if you delete the email from every last GMail folder? (i.e. remove all labels?) Well, in that case it should still be present in the GMail "All Mail" folder.
    • It seems also to be the case that you cannot permanently delete a message from "All Mail" from within Outlook. At least not with the regular Outlook delete buttons/keys. If we try this, the message is apparently immediately restored to the "All Mail" folder.

    So, how do you delete then a GMail message in Outlook?
    • What does seem to work in Outlook is to drag and drop a message to the GMail Trash folder. GMail seems to interpret this as a soft-delete request. And as soon as the GMail trash is emptied, the message should be permanently gone.
    • And of course, deleting a message within the GMail web interface still works as well.

    Please note that the above statements are just some empirical observations we made on a limited test setup. We cannot speak for Microsoft or Google about how the Outlook-GMail interaction was intended to work and cannot make guarantees about its stability. The only thing we can say is that Tagwolf will always use the official Outlook API to move messages, which is provided by Microsoft expressly for this purpose. If Outlook then does the right thing, everything should be OK.

  • How do I upgrade from Tagwolf 1.0 to 1.5?

    Upgrading is easy (and free for existing 1.0 users).
    Just install Tagwolf 1.5 over your existing Tagwolf 1.0 and it should reuse your existing settings and training.

    Please note: it is not possible to downgrade to previous Tagwolf versions without reverting to factory settings.
    So, after a downgrade you are required to retrain Tagwolf on your folder structure.
    Luckily this is rarely a big problem since Tagwolf typically reaches maximum precision again after a few filing sessions.

  • Can Tagwolf automatically label my Gmail emails?

    This is not a scenario we thoroughly test nor support, but in theory Tagwolf could assist you with applying Gmail labels if you are accessing Gmail using Outlook (over IMAP). This works by moving email messages from the Gmail inbox to Gmail IMAP folders that represent Gmail labels.

    While this sounds neat in theory, there are some serious caveats however. We observed that (at least with Outlook 2010) programmatically moving an email message to a Gmail IMAP folder can cause that email to land in the Deleted Items folder instead. This is not a bug we can solve in Tagwolf, but is rather a problem within either Outlook 2010 or the Gmail IMAP protocol implementation. Also, moving emails to Gmail folders over IMAP tends to be very slow.

    A workaround for the deleted item problem with Outlook 2010 is described in this FAQ , including some background information.

    Please see also this FAQ about using Gmail with Tagwolf in general.

    Please note that Gmail IMAP behaviour is not under our control and could change in the future. Your mileage may therefore vary.

  • Can I use Tagwolf with my Gmail emails?

    Yes you can in principle, but this is not a scenario we thoroughly test nor support.

    Tagwolf can handle most email or folders that are accessible through Outlook. So if you have configured your Outlook to access your Gmail account (typically via IMAP), Tagwolf can theoretically access your Gmail email just like any other email. For instance, you should theoretically be able to file emails from your Gmail inbox to folders in an Outlook .pst file.

    There are issues however with filing email messages from the Gmail inbox to Gmail label folders (at least when using Outlook 2010) so we do not recommend this.
    See also this post for more info.

    The procedure for accessing your Gmail through Outlook is available on the Google website:
    For Outlook 2007 and 2010 :
    For Outlook 2003:

    Please note that Gmail IMAP behaviour is not under our control and could change in the future. Your mileage may therefore vary.

  • I installed Tagwolf but no folders appear in the tag cloud

    This is normal, because Tagwolf needs to acquire and maintain knowledge about which emails you file (or have filed) to which folders. Immediately after the installation it doesn’t have that knowledge yet and therefore it is unable to present you with any folders in the tag cloud.

    There are two ways of providing the information about your folders to Tagwolf: “learning as you go” and “bulk training”.
    When you choose for “Learning as you go”, you can simply continue to file emails as you have done before installing Tagwolf. The difference is that Tagwolf will see that you are filing emails and will ask you questions like "Add 'Any Folder Name' as destination folder where items can be filed to?" Each time you answer “yes” to that question, you will see that folder appearing on the tag cloud from then on.
    The advantage of this approach is that you don't have to take any initiative to train Tagwolf. The disadvantage is that it can take a while before it has gathered sufficient data, which is why you can also use “bulk training.“

    In “bulk training” you can train a whole hierarchy of folders in one operation. For this, go to the task pane and navigate to "Home", "Options". In the "Tagwolf Options" dialog click on the "Folders" button. You should now see a tree view, listing all existing folders. Select the top folder of a hierarchy of folders that you want Tagwolf to learn. Then click on that folder and select "Make this and all subfolders...", "Destination Folders". This will mark each folder in that hierarchy as a possible destination for filing mails to. By doing this the actual training has not happened yet, you just marked folders to be trained. The actual training will happen when you press the "OK" button to close the options dialog. This allows you to change your mind and/or make corrections to individual folders before training.

    For more information consult the Tagwolf user manual, section “Getting Started.”

  • Does Tagwolf support the 64-bit version of Outlook 2010 and 2013?

  • Are MS Exchange Public Folders supported by Tagwolf?

    In Tagwolf 1.0 MS Exchange Public Folders are not yet supported as source or destination folders. If there is sufficient demand for this feature we will look into incorporating this in a future release.
    Please send us feedback if public folder support is important to you.

    Update: Tagwolf 1.5 adds experimental support for filing to Public Folder Favourites.

    Tagwolf did not support this until now since it was not trivial to achieve acceptable filing and training performance with public folders. A compromise has now been found that allows Tagwolf to support filing to public folder favourites. These are a subset of public folders of your choice, which are typically cached locally on your disk and can be accessed also when offline. You can easily add public folder favourites by right-clicking on a public folder and selecting "Add to favourites". In the same way you can also add multiple public folders to your favourites at once, by pressing the "Options>>" button in the add-to-favourites dialog and selecting options for adding subfolders at the same time.

    Please note that this is still an experimental feature, and awaiting user feedback. By default support for public folders is therefore disabled and you must explicitly enable it in Tagwolf Options should you wish to use it. For more information on how to set this up, please see the General Options topic in the Tagwolf user guide.

  • My Norton antivirus refuses to download Tagwolf. Help!

    Recent versions of Symantec Norton antivirus/internet security use a reputation-based system which tends to flag new or little used files as a threat, even if there is no evidence of malware at all. You can recognise this by the words "Suspicious.Insight" and/or "WS.Reputation" in the alleged threat name. This effectively amounts to a "guilty until proven innocent" approach.

    When this happens to perfectly harmless files such as downloads on (which we thoroughly check for malware before publication) this is called a false positive.

    While we are all for a safer internet, we also regret this inconvenience for our users, and we take preventive measures by whitelisting our downloads at Symantec which should prevent this problem from happening.
    However there can always be a delay between our publishing of the file and the whitelisting by Symantec to become effective. Therefore you might experience such a false positive when downloading Tagwolf.

    In that case, these are the things you can do:
    1. Make sure you have the latest updates for your antivirus and try again
    2. If that doesn't help, try retrieving the blocked file from quarantine using these instructions from Symantec OR briefly disable Norton antivirus during download and installation of Tagwolf
    3. Report the false positive to Symantec using this form (your voice counts!) and/or to us.

    In case you don't wish to take our word for it (which we understand), we recommend to check for yourself. For instance, you could use the highly regarded free online antivirus scan at to check the tagwolf downloadable installer for any threats before executing it. This applies over 40 different virus scanners and should result into zero issues found.

    In addition, we routinely do an identical check before publishing any downloads and the report of our scan can be consulted here.

    For further information please consult Symantec's clarification of their reputation-based system.

  • Does Tagwolf work with Outlook Express?

    No, you need the Microsoft Outlook that comes with Microsoft Office. Tagwolf 1.0 supports version 2003, 2007 and 2010.

  • Do I need an MS Exchange mailbox to use Tagwolf?

    No, you just need Microsoft Outlook. Tagwolf works with non-Exchange mailboxes too. We have successfully used Tagwolf with POP3 accounts, IMAP accounts and Hotmail HTTP accounts. Also, Tagwolf works fine with folders in personal folder files (.pst), also called Outlook Data Files.

    Also, if all you want to do is file emails from one folder to another folder within a .pst file, or from one .pst file to another then a mail account is not even needed.

  • My Exchange mailbox access is slow. Can I fix that?

    Possibly. For MS Exchange mailboxes there is a setting called "Cached Exchange Mode". If this setting is disabled, Outlook will need to access the Exchange mail server for every operation (paging through mail, opening mail, ...). If the network is slow, this feels like a slight delay everytime you do something in Outlook. Tagwolf does not work optimal in this case, since it has to access your mail over the network as well in that situation.

    The solution is to enable Cached Exchange mode, which creates a local copy of your mailbox on your computer and synchronises this continuously with the server. This gives a much more snappy performance, also if you are not using Tagwolf.

    We have included instructions on how to enable Cached Exchange Mode in the Tagwolf User Guide here

  • Does Tagwolf store data on the mail server?

    No. Tagwolf 1.x stores all of its internal data (any settings and all of the things it has learned in order to predict folders for you) in a local file on your computer under your personal application settings folder. This file is only accessible by you or by administrators on your PC, and is encrypted. Of course, if you choose so and your environment supports it, your emails can be stored on your mail server if file your emails to a folder within your online mailbox.

  • Does Tagwolf modify my email?

    Not unless you tell it to. Tagwolf 1.x has been designed to treat your email as read-only as much as possible. The only occasion where Tagwolf modifies your email is when you ask Tagwolf to move an email to a folder. At that moment it changes the folder location of the email (obviously) and optionally it also marks the email as read (if you enabled this in the options dialog).

    In addition, Tagwolf fixes a problem with certain older versions of Outlook. There can be rare cases where Outlook 2003 erroneously sets the received date of a mail to the current date after moving an email message. Tagwolf will try to fix this when this happens.