Category Archives: General

Bug tracking and error tracking tools

This post explores how bug tracking or error tracking tools helps software developers to record, capture and track errors. They also help you improve your customers experience with the product over time.

We have many customers using Mail Attachment Downloader PRO and FREE versions in over 140+ countries.

Error tracking with

We started using Airbrake.IO for error tracking, however Airbrake had very limited search and segmentation capabilities. This made it tough to understand the how, the when and the why when errors occur.

Trakerr.IO is a powerful new application error intelligence platform that combines a bug tracking or error tracking service with full stacktraces capture and an application analytics service under a single unified platform. Error tracking with Trakerr.IO

We can then use this error information that we collect to understand what is causing errors in the application and get to root cause quicker.

By using the Trakerr.IO platform we were able to cut down 90% of our errors that users may have experienced improving the overall reliability of the product.

How to track errors and collect them?

When applications experience errors,  they usually reside locally in logs.

Trakerr.IO offers a C# SDK that allowed us to start sending errors from our application to Trakerr.IO in a matter of minutes.

Trakerr then enables us to group these errors so we can assess how many of these occurred and how often they happened. The sample image below shows how this grouping occurs.

group errors

By sending errors with full stack traces we were then able to assess how users experience errors, how many users experienced the error and which ones we need to focus on to fix it.

Get to root cause quicker

Getting the stack traces to a central location like Trakerr was the first step. But to understand what may have caused it, we also track what features were enabled within the product when the error occurred.

For example, we know that when an error occurred, did that issue occur when the user was using IMAP, POP3 or Exchange one of the three protocols the program supports.

We can also track various other metrics like when a download completes the number of successful and failed downloads for that session.

Having access to the full stack traces as well as user configuration information enables software developers to quickly understand how that error may have happened. They can also see what a user may have done or how a user may have configured the product that resulted in an error.

Segment errors or bugs

Trakerr.IO allows you to segment errors based on various environment variations, for example, based on Operating System or by Application Version.

segment errors

We can easily see how a new application version or build affected the number of errors that may have happened.

Get notified on mobile

When new builds are released, we often keep a close look on the number of errors that occur.

If there are new errors or the number of errors go over a certain threshold we get a notification on our Slack channel about the error so we can quickly address them.

This way we try to catch errors before they start impacting a large number of customers.


There are various bug tracking or error tracking tools in the market today but there are very few that capture both errors and events.

Trakerr.IO allowed us to instrument our application quickly with the Trakerr SDK to get our application to start sending events quickly. This enabled us to cut down 90% of errors that users were facing with little development effort.

If your development team has not invested time in error tracking tools such as Trakerr.IO it would be wise to spend some time investigating tools such as this to see how they may be able to cut down on time required to track and fix errors.

Note about privacy to our users: For any error or event tracking solutions described in this blog post, never uses the error tracking data we send for marketing purposes or will share this information with third-parties. We also try to make sure that any personally identifiable information such as email addresses are not directly sent to error tracking solutions instead they are anonymized.  For more, check out our privacy policy.

Posts about Mail Attachment Downloader

Some interesting how-to links and posts for further exploration:

Contact us

Contact us if you have any questions, suggestions about this post or contents of this post.

Email actions: unzip, convert or decrypt PDF and run a script

Setup email actions such as unzipping an email attachment, converting the email attachment to pdf and running a script easily with Mail Attachment Downloader PRO Server.

This post will show you how to setup a rule to Unzip a file, then convert the unzipped .docx or decrypt a .pdf and then run a script.

In the Actions section, do the following:

  1. Select ‘After saving attachment‘ from the tree view on the left. Note that even though this says ‘After saving attachment‘, you can run actions on the body of the email as well which will be downloaded as an attachment when you click on the ‘Save email text’ checkbox.
  2. Click on Add button -> After saving attachment -> Unzip files and select any options as shown below. You can enter which specific files you want to unzip in the box which can also include wildcards or regular expressions. If you have multiple, separate each file or wildcard by a new line.automate email actions: unzip_files
  3. Select Unzip files from the tree view on the left. This is necessary to create a sub action under unzip files so every unzipped file runs the remaining action. You can also specify which files to unzip in the previous step. Now click on Add -> After saving attachment ->  Document conversion. Fill in the conversion details by clicking on the Add Conversion button. Note: You can also choose to decrypt the unzipped file if the source file was a PDF by providing the password to decrypt the file.automate email actions: madpro3_convert
  4. Select Document conversion from the tree view on the left. Then Add -> After saving attachment -> Run command line. Enter details to run a command line. In this case we are running a .bat file with the filename of the converted file – {FILENAMEEXT} in the screenshot below now represents the converted filename now from the previous step and not the original saved filename. automate email actions: madpro3_pda_runbat

That’s it.

If you have questions or need additional actions, please contact us and we can help assess feasibility.