increasing pop timeout

...snip...

I still don't see how fetchmail will solve my isses. As far as I can tell, it does NOT act as a pop server (which my 3rd party progam requires).

OK. I didn't want to have to explain the whole thing. So here's the rest of the story:

I have FogBUGZ (from FogCreek) installed on a Win2000 server. Great bug tracking program. Does everything I want it to and more (web bases, etc.).

One of its features it the ability to pull e-mail from a pop server. This e-mail is then fed into it's database, and viewable via the web client. It can be used with a varity of dtabases (Jet, MS SQL Server, etc.). For reasons beyond my control, we are using MySQL.

Occationally, one of our users will send in a screen shot of the problem they are having to the support account (5 Meg+ .bmp - no, I can not LART the users involved).

When FogBUGZ receives one of these e-mail message, it processes it (how and what I don't know - its a black box to me) and feeds it into the database. The whole thing runs about 5 minutes (that may be because of MySQL, but I don't have the option of changing that), and at the same time leaves the connection to the pop server open (the message has already been completely downloaded - its just waiting until it's done insterting the message in the database before it closes the connection). When that finnishes, FogBUGZ tries to delete the message that it was processing, and then closese the connection.

In the mean time, the pop server times out and closes the connection. This leave FogBUGZ high and dry; which errors out, and then starts pulling e-mail from the server again. The first one it finds (of course) is the 5 meg e-mail message again, and the whole process goes into an infinite loop until I manually delete the first message.

Beause the configuration I have (MySQL on Win2000) is non-standard (instead of the default MS Jet-Access on Win9x-2K-XP-etc.), I highly doubt I can convince FogCreek to spend days trying to figure this out and-or optimise their system to make it fast enough to handle the screen shots my non-technical users are generating.

My solution is to adjust the pop server so that it will wait for FogBUGZ to close the connection propperly. If I can tell the pop server that it should wait for 10 minutes before timing out, all the better. I don't care about the overhead that that one extra ipop3d instance puts on my server for that time.

S.