[cobalt-users] Reconfiguring Qpopper with tracing

[Greg <gcaron@xxxxxxxxxxxx>]

We've been having an intermittent attachment problem on our RAQs. When 
customers send Excel files some of them are getting stripped or corrupted. 
I've contacted Qualcomm about this and while they don't think it is there 
problem, they suggested the following:

------------------------------------------------
To enable tracing in Qpopper:
1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t tracefile'.
4. Send inetd a HUP signal.
This causes detailed tracing to be written to the syslog (if you used '-d') 
or to the file specified as 'tracefile'.

You might want to put this Qpopper on a different port, and configure the 
receiving Eudora to use that port.
------------------------------------------------

Does anyone know if Qpopper was originally configured with debugging turned 
on? I made the edits to the inetd.conf file and HUP'd the inetd daemon but 
was unable to get any logs going. I know my way around unix enough to be 
dangerous but not enough to know how safe or dangerous configuring Qpopper 
from the source would be on a Cobalt RAQ3.

Anyone having any thoughts or suggestions?

Thanks
Greg Caron
Site Administrator
SimpleServers.com