At 2:02 PM -0400 7/22/02, Lisa Casey wrote: > Hi Folks, > > I have bulletins enabled on my system, but so far I've only sent three ;-) > > I created one this morning and realised that when I pop it using Outlook > Express, the date on it is 1/22/02, so it landed way up somewhere in my > inbox. > > The name of the file in /var/pop/bull is: 000103.message_7-22-02 > > My system date is: > i2000# date > Mon Jul 22 13:04:40 EDT 2002 > > and the first few lines of this bulletin are: > >>From localhost!qpop Mon Jul 22 13:47:00 2002 > Date: Mon, 22 July 2002 13:47:00 > From: Lisa Casey <[EMAIL PROTECTED]> > Subject: Changes to our mail server > > So why is it being put in my inbox with a date of 1/22/02???
Qpopper doesn't alter the Date header. I'd suggest setting up a test user, making sure that user has no bulletins yet, and doing a full debug trace of the Qpopper session. That way you can see the bulletins being processed, and the actual text being sent to the client. Or, for a much easier test, try a different client (such as Eudora) and see if that fixes it. 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-path>'. 4. Send inetd (or xinetd) a HUP signal. (Steps 3 and 4 are only needed if you use inetd (or xinetd). In standalone mode, you can add '-d' or '-t <tracefile-path>' to the command line directly.) (In either standalone or inetd mode, if you use a configuration file you can add 'set debug' or 'set tracefile = <tracefile>' to either a global or user-specific configuration file instead of steps 3 and 4.) This causes detailed tracing to be written to the syslog or to the file specified as 'tracefile'. Note that you can enable debug tracing for only the test user by either running a separate instance of Qpopper on a different port, or by creating a per-user configuration file to enable debug tracing for that user. --
