David Villeger writes:
> That's true. But so what? Shouldn't qmail just queue these messages?
That's what it's doing. That *is* the entry point to the queue. It's
where qmail-queue dumps new messages.
> What is the function of these directory anyway (todo, intd, mess, ...). I
> couldn't find any info on this. Why don't todo and intd have the same
> multidirectory structure as remote,...?
Don't know. I have a patch on www.qmail.org to fix it. I think that,
in theory anyway, todo and intd are intended to be small holding
areas. Essentially they're there so that qmail-send knows what mail
it has and hasn't routed. Dan let drop a hint that in qmail 2.0,
there won't be a distinction between local and remote mail, so perhaps
he's fixing this problem?
Where it kills you is when qmail-queue dumps mail faster than
qmail-send can take it out, or when qmail-send isn't running.
> The disks seem OK. Memory is certainely an issue. Each
> qmail-remote eats 1.5 megs (virtual mem, 1 megs resident) and there
> is only 128 megs on the machines.
Wow. That's a lot. On a customer's Linux server, it's only 800 and
368. I'd heard that sparc binaries are bigger, but 2X bigger sounds
like a lot. Sounds like you need a machine with *lots* more memory.
Are you *ever* swapping to disk? Add memory until it stops swapping.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.