On Mon, 2002-09-30 at 16:21, Dean Brissinger wrote: > I figured it out. I also seem to have stumbled across a bug in the > process. When calling popper from inetd the first option I give it is > always ignored. When I supply an option before the -f option, it reads > my config file and works great (ignoring whatever I put before -f). So > I added '-c -f popper.conf' to fix my problem.
Post your inetd config line for qpopper. Perhaps the most common error made with inetd: One only lists the program once in the in config file instead of twice. The first instance is the path that inetd will pass to exec(). The second instance is the argv[0] value that the program will see. Most programs ignore argv[0] and start processing their parameters starting with argv[1], but you probably left out the argv[0] name, so qpopper is intepreting the first parameter as its own name, and hence ignoring it.
