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 helped was turning off
the SSL on the internal (sending) server. I can’t keep it like that. Or,
maybe I can, if I make a VPN or SSH tunnel connection between the internal
server and the smart host. The messages will sill be sent one by one, but
at least the SSL connection overhead won’t be there while it will be secure.
M
On Mon, Jan 20, 2020 at 12:47 PM Jeremy Harris via Exim-users <
exim-users@???> wrote:
> 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 messages,
> rather than SMTP-source: use -odq for this big-batch feed. Then the
> entire config needs not be queue_only, leaving a lower-latency service
> for other work.
>
> - limit the number of concurrent connections to the smarthost in the
> initial system's transport. That way you automatically get queuing
> as soon as the peak load batch starts up.
>
> - If the messages in the batch are not personalised, use multi-recipient
> messages (use bcc, not cc or multiple-to - to avoid cross-recipient info
> leakage). This is a _big_ win for your initial-to-smarthost load.
>
> --
> Cheers,
> Jeremy
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
