readqf: cannot open ./d* (including last MailScanner)

[Ramon]

>I have just disable the sendmail -q cron and am waiting for MS to
> >process the mqueue, if the messages get delivered we've got it.
> 
> It doesn't attempt to run the whole queue, it just does a delivery attempt 
> on each of the messages it has just placed in the outgoing queue. You still 
> need something like
>          sendmail -q15m
> in order to regularly run your queue. But you never need a cron job as 
> well, that's just repeating what the "sendmail -q15m" does anyway.

OK, it's better to do sendmail -q10m than the cron job but, how can I
detect which sendmail is having problems processing the queue and
failing with "SYSERR(root): readqf: cannot open ./d*" every time?.

It can be the queue runner (or the cron job) or the sendmail run by MS
in the delivery attempts. There's no other sendmail process working in
/var/spool/mqueue, the other is configured in QueueOnly to
/var/spool/mqueue.in

Does someone know how could I make that sendmail does not send the error
message to my users? I get tons of that messages, and even more with the
today's last version,

Thanks!

Ramon

> >
> > >
> > > If the automatic sendmail queue processing happens after MS has put a 
> > given
> > > qf+df pair, but before it issues the manual sendmail, the auto sendmail 
> > will
> > > deliver the message and the manual sendmail will fail ('cause its list of
> > > queue files is manually created within MS).
> >
> >So the readqf error message is from the sendmail invoked by MS, isnt it?
> >
> > >
> > > I'd say you shouldn't care about that... Otherwise, you can try putting
> > > MailScanner in queue mode:
> > > Delivery Method = queue
> >
> >If what I've just done does not work I will try this.
> >
> >
> >Thanks!
> >
> >Ramon Acedo
> >
> > > El 6 Oct 2003 a las 12:10, Ramon escribió:
> > >
> > > > Hello,
> > > >
> > > > My config:
> > > >
> > > > - MailScanner-4.11-1 but today I have tried too MailScanner-4.24-5 and
> > > >   the errors has increased considerably (may be because it's faster?)
> > > >
> > > > - mcafee
> > > >
> > > > - Sendmail 8.12.3-6.6
> > > >
> > > > - Linux Kernel 2.4.22
> > > >
> > > > I've got lots of this annoying error in my logs and although
> > > > the messages are sent correctly sendmail generates an error mail
> > > > to the sender for every message with this log. I woudn't care about
> > > > this cause as I said all the messages are sent but my users complain
> > > > about the error messages they receive.
> > > >
> > > > An example:
> > > >
> > > > ------------------------------------------------
> > > >
> > > > grep h95LST48031790: mail.log
> > > >
> > > > Oct  5 23:28:30 avant sm-mta[31790]: h95LST48031790:
> > > > from=<julianov57 at hotmail.com>, size=1659, class=0, nrcpts=1,
> > > > msgid=<BAY7-F88YEIEktho3sD0000c56e at hotmail.com>, proto=ESMTP,
> > > > daemon=MTA, relay=bay7-f88.bay7.hotmail.com [64.4.11.88]
> > > >
> > > > Oct  5 23:28:40 avant sm-mta[31815]: h95LST48031790:
> > > > to=<sf2 at manyanet.org>, delay=00:00:10, xdelay=00:00:00, mailer=local,
> > > > pri=120651, dsn=2.0.0, stat=Sent
> > > >
> > > > --> Here the message has been sent but...
> > > >
> > > > Oct  5 23:28:49 avant sendmail[31827]: h95LST48031790: SYSERR(root):
> > > > readqf: cannot open ./dfh95LST48031790: No such file or directory
> > > >
> > > > After sending it seems to trying to process it again!!
> > > >
> > > > Oct  5 23:28:49 avant sendmail[31827]: h95LST48031790:
> > > > to=<sf2 at manyanet.org>, delay=00:00:19, xdelay=00:00:00, mailer=local,
> > > > pri=120651, dsn=5.2.3, stat=Service unavailable
> > > >
> > > > Oct  5 23:28:49 avant sendmail[31827]: h95LST48031790: h95LSn62031827:
> > > > DSN: Service unavailable
> > > >
> > > > ---------------------------------------------------
> > > >
> > > > In the list archives are some people asking about this error but I think
> > > > there's no solution yet.
> > > >
> > > > If I'm not wrong MailScanner puts the scanned messages from mqueue.in to
> > > > mqueue and then a 'sendmail -q -OQueueDirectory=/var/spool/mqueue'
> > > > process this queue. Could it be that mailscanner put first the mail
> > > > header (./q*) and then the data (./d*) if the time between the copy of
> > > > the header and the data would be substantial (for example 1 or more
> > > > seconds) that would explain the problem, but I don't know how to monitor
> > > > this.
> > > >
> > > > It's not a fs lock problemm I have updated to kernel 2.4.22 where the
> > > > flock() is now Posix 2001 compatible (actually from 2.4.21 is
> > > > compatible).
> > > >
> > > > Today I have upgraded to MailScanner 4.24-5 but there were many more
> > > > readqf error messages so I've downgraded after some hours (the rest
> > > > worked perfectly and faster! ;-)
> > > >
> > > > We'll keep trying to find out a solution, any help would be appreciated.
> > > >
> > > > Ramon Acedo.
> > > >
> > >
> > >
> > > --
> > > Mariano Absatz
> > > El Baby
> > > ----------------------------------------------------------
> > > Marriage is a fine institution - but I'm not ready for an institution.
> > >       -- Mae West
> >--
> >Ramon <ramon at linux-labs.net>
-- 
Ramon <ramon at linux-labs.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20031006/b78473a3/attachment.bin