On Sat, Oct 22, 2022 at 02:35:28PM +0100, Jeremy Harris via Exim-users wrote:
> On 17/10/2022 22:58, Heiko Schlittermann via Exim-users wrote:
> > how do you deal whith incoming messages having a Thread-Index header (an
> > other header indicates that the originating MUA was MS Outlook 16.0)
> > wi
On 17/10/2022 22:58, Heiko Schlittermann via Exim-users wrote:
how do you deal whith incoming messages having a Thread-Index header (an
other header indicates that the originating MUA was MS Outlook 16.0)
with about 1200 chars.
As a longterm goal in handling this and the References: header,
whi
Heiko Schlittermann via Exim-users writes:
> Heiko Schlittermann (Mo 17 Okt 2022 23:58:03 CEST):
>> how do you deal whith incoming messages having a Thread-Index header (an
>> other header indicates that the originating MUA was MS Outlook 16.0)
>> with about 1200 chars.
>
> To be more precise: T
Heiko Schlittermann (Mo 17 Okt 2022 23:58:03 CEST):
> how do you deal whith incoming messages having a Thread-Index header (an
> other header indicates that the originating MUA was MS Outlook 16.0)
> with about 1200 chars.
To be more precise: The one I have is 1000 chars w/o the header field
name
Hi,
how do you deal whith incoming messages having a Thread-Index header (an
other header indicates that the originating MUA was MS Outlook 16.0)
with about 1200 chars.
The regular Exim config doesn't forward this (and probably can't bounce
it, as a copy of the headers would make it into the boun
