BUG REPORTING GUIDELINES

1) Submit Diagnostic Log
Use the "Help" > "Submit Bug Report" option in Digsby. This securely submits a diagnostic log to our servers. There is some information in this log such as contact names, aliases, etc. that are useful for diagnosing problems but content like messages, profiles, and especially passwords are not contained in this log.
In addition to sending the log, there is also a place for you to describe the issue you're experiencing. Please be as detailed as possible to help us reproduce the issue.  You can also use this feature if you experience a visual bug - the diagnostic log submitter allows you to add a screenshot to the bug report.

2) Check the Forums
Feel free to look around the forums for a workaround or other user and developer comments related to your issue. If you aren't sure whether the issue is a bug or something that can be resolved at your end please post on the forums to get help/feedback from the community. Please use the search feature. If you create a topic that has been discussed before, it will be closed and there might be a comment from an annoyed developer. ;-)

3) Report the Bug via Email
If you have an issue that cannot be resolved on the forums for some reason, please email bugs@digsby.com.  Be as specific as possible about what happened. We will either create a ticket or reply for follow up information.

1b) Email log files by hand (if 1 is not possible)
On occasion, a problem may be encountered before digsby has logged in.  This prevents access to the bug submission dialog.  In this case, in your email to bugs@digsby.com, please include any files in the following directory, if they exist.

on XP:
C:\Documents and settings\<username>\Local Settings\Application Data\Digsby\Logs\*

on vista:
C:\Users\<username>\AppData\Local\Digsby\Logs\*

P.S. If the log files are large, packing them in a zip/rar/tar.gz/tar.bz2/7z archive will probably reduce the size of the email attachment greatly.

Also, if you're submitting a bug in response to a forum topic, blog post, or in response to communication from any of us devs, a link to the post or mentioning a prior email in the bug report would be helpful.