Dispatcho: Email isn't being pulled into FogBugz

In FogBugz version 3.x,  the Dispatcho service collects mail from POP3 mailboxes and forwards it on to FogBugz through HTTP to be opened as a new bug (or attached to an existing bug by using the case number in the subject line).  If this service is not working for you, please follow the checklist below to try and find the problem.  Read more about this service and how to set it up manually if you need to.
  1. Double check all dispatcho settings.  Mail checking interval/username/password/etc..  Make sure the interval for checking mail is not set too high.
  2. Check to make sure the dispatcho service is running.  Windows: Check the services control panel for the "Fog Creek Software Dispatcho Service" and make sure the status says "Running".
  3. From the FogBugz server, use a POP3 client such as Outlook Express to log on to Dispatcho mailbox. (Do not use an IMAP client for this.) Can you see the messages?  If you cannot see a few messages in the mailbox (and you have tried sending some test email), your mail server may not be configured correctly.  Please configure the mailbox correctly first and then continue with the checklist.
  4. Do you have NT Authentication turned on for your site?  If so, you need to turn it off for the dispatcho.asp file.  In the Internet Services Manager, select the dispatcho.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. Is the Dispatcho service using a valid FogBugz URL? Open a browser on the FogBugz server. Log into FogBugz as an admin and click on Site. Copy the "FogBugz URL" and paste that into a browser. If the page does not load, or if you get any prompt of any kind, you have a problem that needs to be resolved. The dispatcho service uses this URL to access your FogBugz installation. Therefore this URL must be reachable from the web server itself, since that's where the service is running, and with no user prompts, since the service is incapable of responding to a user prompt. You can change this URL to something else right here on the site page. The solution for this problem will depend on the specifics of your environment (e.g. DNS settings, connectivity, etc.).
  7. Are you using Secure POP3?  If so, you must log into the server as FogBugz and THEN install your security certificate.  You can make sure this is correctly installed by running Outlook Express when logged on as the FogBugz user.  You should not be prompted when you connect to the mail server.  If you are prompted (about whether to trust the certificate or not), the security certificate is not properly installed.  (Rebooting the system may be what's needed.)  
  8. Look in the registry under HKLM\Software\Fog Creek Software\FogBugz\[path to fogbugz install]\dispatcho.  There should be keys numbered 1, 2, 3, etc.. for each mailbox you have.  Look at the properties of those keys.  Take notice of the URL value for each key.  Using that URL, start Internet Explorer ON THE FOGBUGZ SERVER and double check that you can reach that fogbugz URL.  This is the URL that dispatcho.asp uses to publish the messages to FogBugz.  It's OK if you get an ASP error here, as long as it actually REACHES that file and does not give you a 404 Not Found error.

To troubleshoot this further, please follow the steps in the following article: Enable the FogBugz Log Files

If you have tried all of the above suggestions and Dispatcho is still not function correctly, please email our technical support group to research the problem further.