Fog Creek Software
Discussion Board




FogBUGZ mail problem (again?)

Hi,

We installed FogBUGZ and started “playing” with it – to understand the capabilities. And…

The problem we went into:
At the beginning the software implemented bugs sent by mail – above our expectations. Way above.
In fact, we were quite impressed off how smooth it went. Everything was perfect and we could even print a whole lifecycle of a bug with al the relevant attached images.
P-E-R-F-E-C-T.

And then it stopped!
The system stopped importing emails. We checked and all the mails are still on the mail server.
Answers to predicted questions:
1. No mails contain any attachment.
2. Some mails are using plain test and some HTML
3. We double checked all the mail settings and everything seems to work fine – we can receive these mails using regular mail client (we checked Outlook).
4.  The Dispatcho log says the following:

.
.
.
http://support.company.com/fogbugz/dispatcho.asp?ixMailbox=3
Setting normal (non-secure) mode
Attempting to log in
Connected...
Num Messages...
5
Publishing...
5
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
4
Com Error in PublishMessageToURL: The virtual circuit was reset by the remote side executing a "hard" or "abortive" close. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close".  This error may also result if a connection was broken due to "keep-alive" activity detecting a failure.  This error is also be reported under Windows 2000 when a UDP packet is sent to a host with no service open on the specified port.
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
3
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
2
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
1
Com Error in PublishMessageToURL: An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. PowerTcp will close the connection when this error is encountered.
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
CheckMail...
CheckMail...
.
.
.
.
http://support.company.com/fogbugz/dispatcho.asp?ixMailbox=3
Setting normal (non-secure) mode
Attempting to log in
Connected...
Num Messages...
5
Publishing...
5
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
4
Com Error in PublishMessageToURL: The virtual circuit was reset by the remote side executing a "hard" or "abortive" close. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close".  This error may also result if a connection was broken due to "keep-alive" activity detecting a failure.  This error is also be reported under Windows 2000 when a UDP packet is sent to a host with no service open on the specified port.
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
3
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
2
404
<html><head><title>Site Not Found</title></head>
<body>No web site is configured at this address.</body></html>
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
Publishing...
1
Com Error in PublishMessageToURL: An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. PowerTcp will close the connection when this error is encountered.
Error: PublishMessageToURL returned False. ASP file did not return 'OK'
CheckMail...
CheckMail...
CheckMail...
.
.
.

Marom
Monday, June 14, 2004

You probably either moved or changed the DNS name of your fogbugz server.  Go into the mailboxes screen and update the hostname in the URL field so that dispatcho can find the dispatcho.asp file!

If you load that URL there in a web browser you will probably get a page not found.  You should get a 500 error (the script errors out if you run it with no arguments, but at least you know its in the right place).

Michael H. Pryor
Fog Creek Software
Monday, June 14, 2004

Marvelous

You’re THE M-A-N !!!

That fixed it.

I had to submit the IP address of the mail server instead of using the DNS name (otherwise it didn’t recognize the server’s address) and the IP address (instead of using the DNS name) of the server maintaining the FogBUGZ installation and add to this address the suffix ‘/fogbugz’ (as it’s not the default web site of this server).
meaning: I ended up in submitting the following (in the field marked ‘FogBUGZ URL:’ 172.16.50.130/fogbugz.

I suppose that this “bug” is originated in the FogBUGZ installation program…?

So…
You can either modify you installation
or
You can provide a decent explanation in your FAQ page.


Thanks anyway.


Me.

Marom
Tuesday, June 15, 2004

*  Recent Topics

*  Fog Creek Home