On Sun, 15 Dec 2024, Exim Bugzilla via Exim-dev wrote:
> https://bugs.exim.org/show_bug.cgi?id=3071
>
> --- Comment #3 from exim-bugs@??? ---
> (In reply to Jeremy Harris from comment #2)
>> The cutthrough facility uses the verify callout machinery (recipient, with
>> the use_sender option) to place the ongoing connection.
>>
>> Changing the envelope sender would be a breaking change. I think supporting
>> this will need an option on the ACL control=cutthrough_delivery -
>> perhaps "/sender=transport", with "original" signifying the existing
>> behaviour of using the received envelope-from?
>
> Docs don't mention anything about the sender address, do they? There are some
> limitation mentioned, but non of them apply to the sender address.
>
> I'd assume that people using cutthrough_delivery with SRS would expect SRS to
> be applied with cutthrough_delivery, and myself I'd certainly appreciate a way
> to set envelope sender upon cutthrough_delivery.
I would not expect to use SPF or SRS with cutthrough-delivery,
just as i would not expect a secondary MX to do SPF.
> I like the proposed idea. Would sender=transport also take into consideration
> errors_to router settings (as those would affect the transport's return_path)?
>
> But this bug can be fixed simply by documenting that envelope sender does not
> change.
although, earlier you said:
> FWIW more options could be affected...
--
Andrew C. Aitchison Kendal, UK
andrew@???
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
