Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.
A FogBugz Mailbox collects mail from a POP3 or IMAP mailbox and pulls it into FogBugz to be opened as a new bug (or attached to an existing bug by using the case number in the subject line). If this is not working for you, please follow the checklist below to try and find the problem.
  1. Check your spam folder. By default, spam cases are hidden from view. Adding “show:spam” to the search query will allow spam cases to be displayed. If you find cases are being sent to spam you may want to train the Bayesian filter more.
  2. Double check all Mailbox settings.  Account name, Password, Mail server, and Port.
  3. Check to see if there are any Admin Notifications in FogBugz.

The rest of this guide is intended for FogBugz for your Server. If you are using FogBugz On Demand and are still having issues with your Mailboxes then please contact us.


  1. Check to make sure the FogBugz Maintenance Service is running.
    • On Windows servers: Check the services control panel for the “FogBugz Maintenance Service” and make sure the status says “Running”. If it is running, restart it, that may be all that’s needed.
    • On Linux/Mac servers: This is called the heartbeat.exe mono process. Log in as root and type ps -auxwww | grep heartbeat.
  2. Log onto the FogBugz web server as the FogBugz user, and verify that there are messages in the mailbox:
    • Option 1: use telnet to look at the list of messages. If you are on Windows 7 or Server 2008, you will need to enable telnet.
    • Option 2: use a POP3 client such as Outlook Express or Thunderbird to log onto the email account you have specified for this FogBugz mailbox. (Be careful of the different between POP3 and IMAP clients. Outlook is an IMAP client by default. Outlook Express is a POP3 client by default.) You must enter the exact same information as you have in step 1 above. Set this email retrieval account to leave messages on the server, then click “send and receive”. Can you see the list of messages on the mail server?  If you cannot see a few messages in the mailbox (and you have tried sending some test email to that address), your mail server may not be configured correctly.  Please work with the Administrator of the mailbox or mail server to configure the mailbox correctly and then continue with the checklist if neccesary.
  3. If you are using MS Exchange as your POP3 server, please see this article on Microsoft’s website. A FogBugz mailbox requires a POP3 or IMAP server.
  4. Do you have NT Authentication turned on for your site?  If so, you need to turn it off for the heartbeat.asp file.  In the Internet Services Manager, select the heartbeat.asp file, choose Properties. Then turn on anonymous access in the Directory Security tab and make sure the username and password are correctly set to the FogBugz user.
  5. Do you have enough licenses?  Log into FogBugz and click on the Licenses link in the upper right to make sure you have the correct number of licenses.
  6. Are you using Secure POP3 on Exchange? Microsoft Exchange servers have two certificates: one installed to use when someone access the web interface, and another that’s sent to POP3 clients. Make sure that you are using the correct certificate for the POP3 client and that your FogBugz server trusts the certificate author.
  7. Are you using SSL on your FogBugz website? Log onto the server as the FogBugz user. Bring up FogBugz in a browser. If you get a prompt about your certificate, this same prompt is being sent to the Maintenance Service (which is responsible for checking mail) except it has no way to click “accept”. To fix this, you will need to install the self-signed certificate as a Trusted Root Certificate Authority.
  8. Are you using MySQL as your database? Search your MySQL my.ini file for “max_allowed_packet”. If you find it, make sure it says: max_allowed_packet=32M If you don’t find it, add a new line at the bottom of the file that says:
    In older versions it may look like this:
    set-variable = max_allowed_packet=32M