I changed the -T setting to 300 seconds and was still getting timeouts. Since I
regressed back to version 3, the timeouts ent way for the most part. I think
something is broken in the timeouts. It might be if a single message takes more
than the -T value, it times out.
Randall Gellens wrote:
> At 2:59 PM -0400 4/18/01, Lisa Casey wrote:
>
> > I have two questions that I feel are really simple and I ought to be able to
> > find the answer on my own, but after reading the INSTALL, the Administrators
> > Manual on the web site and the FAQ, I still don't really have a clue.
>
> The GUIDE.pdf file including in the distribution is currently more
> up-to-date than the one on the web site. This should be corrected
> soon.
>
> >
> > I'm getting quite a few error messages like this since I upgraded:
> >
> > Apr 17 22:05:37 i2000 -sR[11393]: lvann at 205.160.50.172
> > (205.160.50.172): -ERR
> > POP timeout from i2000.jellico.net
> >
> >
> > It's my understanding that I should increase qpopper's timeout value from
> > the default 2 minutes to something higher. Do I do this by adding a -T600 to
> > the pop3 line in my inetd.conf? (With 600 being 10 minutes, or 300 for 5
> > minutes). OR do I do this by changing the nowait in inetd.conf to
> > nowait.300 (for 5 min) or nowait.600 (for 10 minutes). I am confused here...
>
> You use either the 'T' command line flag, or the 'timeout' option
> in a configuration file. See the Administrator's Guide for full
> details.
>
> The inetd.conf option is in case you get errors from inetd where it
> thinks Qpopper is looping.
>
> >
> > I used the configuration option --enable-statistics, but didn't specify a
> > log file. I assumed qpopper would use either /var/log/messages or
> > /var/log/maillog for this but I cannot find these statistics messages in
> > either of these logs. Should I specify a log file? If so, where and how?
>
> You can specify an alternate log file using the 't' command-line
> flag or the 'tracefile' configuration file option. But you don't
> have to do that. You probably just need to update your syslog.conf
> file and specify where you want Qpopper's log messages to go. You
> specify by the log facility that Qpopper uses, which defaults to
> either 'mail' or 'local1', depending on your OS. You can also
> specify a facility using the '--enable-log-facility' configure
> flag, the 'y' command-line flag, or the 'log-facility'
> configuration file option. See the Administrator's Guide for
> details.
