check that you've got enough smtp ports available. I've seen our queue
build like that when we hit tcpservers default 40 smtp sessions limit.
(On a side note am i correct in saying that tcpservers 40 default is not
the same as concerrency remote)?
is port 25 slow to respond?
and how about syslog, is it eating a lot of cpu?
+ + + + + + + + + + + + + + + + + + + +
Spark Sistemas
- presentado por IWCC Argentina S.A.
Tel: 4702-1958
e-mail: [EMAIL PROTECTED]
+ + + + + + + + + + + + + + + + + + + +
- eric
User JAMES escribi�:
>
> On Tue, 17 Aug 1999, Chris Johnson wrote:
>
> > On Tue, Aug 17, 1999 at 03:14:06PM -0400, User JAMES wrote:
> > >
> > >
> > > I used qmHandle and can see no real pattern as to which emails aren't
> > > working. I've sent qmail-send serveral ALRM signals, rebooted, etc, to no
> > > avail; syslog shows no errors that appear relevant.
> >
> > I'll be the first to say it: what's in the logs? There you'll find a reason as
> > to why a message was deferred.
>
> Like I said, it doesn't show anything that I can see:
>
> Aug 17 14:02:03 richard2 qmail: 934912923.663159 end msg 274702
> Aug 17 14:02:10 richard2 qmail: 934912930.571908 new msg 274702
> Aug 17 14:02:10 richard2 qmail: 934912930.573256 info msg 274702: bytes
> 780 from <[EMAIL PROTECTED]> qp 20832 uid 1825
> Aug 17 14:02:12 richard2 qmail: 934912932.925614 new msg 274705
>
> > Also, before sending an ALRM to qmail-send, run /var/qmail/bin/qmail-tcpok.
>
> I did, per the FAQ...
>
> anything else?
