>I just got word that their program does not shell out to spawn mail
>processes, but rather communicates directly with smtp, so unless they have
>some control over this, it doesn't look like I'll be able to call anything
>directly.
>
>Heh, the load average on this thing is averaging around 20 which is just
>bad.
>
>I just sent out 300 messages using qmail-remote in about 4 seconds.
>*sigh*, qmail remote is fast, but you have to pass it information like you
>state below, such as the prefer MX host, which over course a simple perl
>wrapper could find, but well...
>
>I still remember qmail being very fast on other servers. Why isn't my
>concurrentremote filling up? I see in logs an average of 1-3/75 and
>that's it.
It may be that your Java program is simply injecting one mail at a time (via
SMTP) and that is getting delivered before the Java prog is ready to inject
the next. It may also be that you're hitting an inbound SMTP concurrency
limit. How is your inbound SMTP connection managed? inetd, tcpserver, ?
To find out more, run qmail-qstat every 10 seconds while the Java prog is
running.
Post 2-3 minutes of this to the list.
Regards.
