At 08:42 PM 1/6/03 +0100, you wrote:
> > > Ensure the 'too_old' setting in dnews.conf is set to a reasonable
value,
> > > e.g. 5 days.
> >
> >There are no setting like too_old in dnews.conf....must this be there ?
>
>
> Yes, and should be set to about 10, so add that setting to dnews.conf.
>
> If the problem persists you should be getting an error in dnews.log
> like this:
>
> ....item: Invalid date or too old={DATE shown here} <xxxx>
dnews.log
=======
06 20:19:06 2:info: getmail: Incoming MID
(<[EMAIL PROTECTED]>)
06 20:19:06 2:info: too_old 0<1041016746 days 10
06 20:19:06 2:warn: item: Invalid date or too old={}
<[EMAIL PROTECTED]>
06 20:19:06 2:error: getmail: Local store failed, [EMAIL PROTECTED]
<[EMAIL PROTECTED]>, 6-1-2003 -
20:17:39 - Apache-server (80) - 192.168.0.3 offline., Message is too
06 20:19:06 2:info: getmail: <--[7] +OK message 1 deleted
CU, Rob
Hmm, it seems the mail server is putting a blank date header in the
message, very odd, if you could send us your email address and platform
we could try doing a build with a setting to force a valid date header.
Chrisp.
