Thanks for the leads...

Turns out I was mistaken about the hardware. This machine is actually an
older PIII with only 256MB of memory. System usage shows memory at 100%
although I can still run commands and generally navigate so I don't
think this is the real issue.

I've increased the concurrencyremote with no effect. It looks like the
queue is stuck with all AOL bounces. I'm not sure why it's choking on
this, perhaps AOL is throttling us?! Has anyone else seen this behavior?

Normally I wouldn't care how long it takes to process these, but they
are in the queue ahead of legit email that is trying to go out.
Actually, I don't quite understand why BOUNCES would be in the SEND
queue at all?!

becouse is a bounce of a mail your are sending. It's very strange these days to get a bounce afterwards with an email, it's too spammer tempting. The bouce is done in the same connection you make to the other server, at smtp level.

-----Original Message-----
From: Rick Macdougall [mailto:[EMAIL PROTECTED] Sent: Monday, May 08, 2006 12:26 PM
To: [email protected]
Subject: Re: [toaster] Mail Queue...

Damian Barry wrote:
Looks like mostly "default settings", are there unix settings I should
check also?

We have a T1 here, 1300+ kbps up (which is 99% available off hours
when
we run, and probably 95% available all other times).

Damian

[EMAIL PROTECTED] bin]# ./qmail-showctl
qmail home directory: /var/qmail.
concurrencyremote: (Default.) Remote concurrency is 20.

Increasing your concurrencyremote will help a lot. You'll have to play with the value depending on the size of out going messages and available

bandwidth but I'd try upping it to 50 and restarting qmail-send and see how that works.

Edit /var/qmail/control/concurrencyremote and just but 50 on the first line, then svc -t /service/qmail-send

Check your bandwidth and increase or decrease as needed.

Regards,

Rick

Reply via email to