On 2006-03-04 at 00:48 -0800, Christian Gregoire wrote:
Thanks a lot for the hints. I'll give it a try.
The Exim author's hint, lower the retry time, is even better for almost
all circumstances. I should've thought back to why we do things as we
do.
For us, our front-end hosts can also
On 2006-03-03 at 10:12 -0800, Christian Gregoire wrote:
The problem is that when A gets a host error from B for some reason,
all messages destined to B are queued. And when retry time has come, A
sends all messages to B at once, whose load average rises, so leading
Sendmail to refuse
On Fri, 3 Mar 2006, Christian Gregoire wrote:
The problem is that when A gets a host error from B for some reason,
all messages destined to B are queued. And when retry time has come, A
sends all messages to B at once, whose load average rises, so leading
Sendmail to refuse connections. So
Hello guys,
Given that Exim uses host-based retrying, I bump into the following issue.
I have a front-end SMTP server (A) running Exim, dedicated mainly to virus
scanning, which then routes cleaned messages to the server holding mailboxes
(B) running Sendmail.
incoming connections --- A
On 2006-03-03 at 10:12 -0800, Christian Gregoire wrote:
The problem is that when A gets a host error from B for some reason,
all messages destined to B are queued. And when retry time has come, A
sends all messages to B at once, whose load average rises, so leading
Sendmail to refuse
