On 20/01/2020 12:37, Lars Schimmer via Exim-users wrote:
>> For a start, you can't affect the envelope. The docs says this.
>
> Hmpfg, overread this. thank you.
> But without changing the envelope, it will not help much with SPF on
> receiver side, as the wrong sender is in the envelope?
On 2020-01-18 16:55, Jeremy Harris via Exim-users wrote:
> On 18/01/2020 15:43, Lars Schimmer via Exim-users wrote:
>> On 18/01/2020 11:37, Jeremy Harris via Exim-users wrote:
>>> On 18/01/2020 10:18, Lars Schimmer via Exim-users wrote:
Any ideas?
>>>
>>> headers_rewrite, a generic transport
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
Hello,
I’m sending out millions of emails from a server on a regular basis.
The emails go to a single a smarthost that handles the delivery. I played a
lot with the configuration about how many queue workers should be running
and how many connections the smarthost should accept.
Now the only
