On 25/01/2020 17:46, Jeremy Harris via Exim-users wrote:
> On 22/01/2020 12:43, Graeme Fowler via Exim-users wrote:
>> It took 35 seconds to do the initial non-delivering queue run while parsing
>> and routing each message on the queue, then started delivering them.
> So that's 35ms per message.
On 25 Jan 2020, at 17:46, Jeremy Harris via Exim-users
wrote:
> Of interest in that debug output - there's a consistent 6 or 7ms pause
> just after "Renaming spool header file". This is where exim has just
> written a spool file under a temporary name; it renames it to the final
> name and then
On 18/01/2020 21:39, Maeldron T. via Exim-users wrote:
> Now the only problem left is that I believe the worker processes connect to
> the smarthost for every message one by one.
Another thing to be aware of, if your mails are given to exim on this
first server using a commend-line (not SMTP
On 22/01/2020 12:43, Graeme Fowler via Exim-users wrote:
> I’ll send you a link to one separately.
Thanks.
> In short: generated a queue of just over 1000 messages with identical
> sender/recipient couplet but subject and message body varying, with Exim
> doing no queue running, then ran ‘exim
On 22 Jan 2020, at 09:51, Jeremy Harris via Exim-users
wrote:
> That part in also interesting to me, as I get too little feedback
> from production users. I'd really like to get a debug-output sample
> from that startup phase.
I’ll send you a link to one separately.
In short: generated a
On 22/01/2020 00:15, Maeldron T. via Exim-users wrote:
> 1. When I tried to run the queue worker with the -qq option, it didn’t
> start sending the emails for maybe fifteen minutes. There was not much disk
> activity by exim (I checked it with top -m io -o total). I have no idea
> what it was
On 22/01/2020 01:19, Viktor Dukhovni via Exim-users wrote:
> [ I hope it is not out of line to mention a related Postfix capability
> on this list when a user appears to be looking for something to meet
> a need that does to appear to be directly supported by Exim, apologies
> otherwise... ]
On Wed, Jan 22, 2020 at 01:21:08AM +0100, Maeldron T. via Exim-users wrote:
> I’m not sending spam, hence the emails are personalized. Even more, they
> are confidential. Unfortunately, the only thing that helped was turning off
> the SSL on the internal (sending) server. I can’t keep it like
Hello Jeremy,
thank you.
I have another two servers for the high priority emails.
Limiting the connections won’t make exim send more than one email per
connection.
I’m not sending spam, hence the emails are personalized. Even more, they
are confidential. Unfortunately, the only thing that
Thank you for the answer.
I’m using queue_only_load on the smarthost and I used to have queue_only =
true on the internal server.
The -qq isn’t a solution for multiple reasons.
1. When I tried to run the queue worker with the -qq option, it didn’t
start sending the emails for maybe fifteen
On 20/01/2020 11:17, Graeme Fowler via Exim-users wrote:
> Put your first SMTP server in queue only mode, using 'queue_only = true' in
> your main configuration. This will prevent immediate delivery.
Other things you might consider:
- if this initial system is being fed with commandline-source
On 18 Jan 2020, at 21:39, Maeldron T. via Exim-users
wrote:
> Now the only problem left is that I believe the worker processes connect to
> the smarthost for every message one by one.
>
> I didn’t find anything in the documentation (current 4.x version) that
> seemed to allow me to tell the
On 18/01/2020 21:39, Maeldron T. via Exim-users wrote:
> Now the only problem left is that I believe the worker processes connect to
> the smarthost for every message one by one.
Do you do two-stage queue-runs (the -qq option)?
--
Cheers,
Jeremy
--
## List details at
13 matches
Mail list logo
