Re: [exim] Thread-Index header too long
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) > > with about 1200 chars. > > As a longterm goal in handling this and the References: header, > which can similarly grow, how about a bug just to document the > issue and relevant info such as the syntaxes of these headers? > > There could be one already; I recall a discussion somewhere about > what to do with References: but not where it was. Discussed several times, in particular, https://lists.exim.org/lurker/thread/20190416.032757.fefb1cbb.en.html#i20190416.032757.fefb1cbb > A useful > suggestion was of a Usenet practice of retaining the first element > and the last couple, on the assumption that later ones are appended > as the list grows. In my practice there were many examples where Outlook 10+ generates binary garbage inside References: header. I suspect these incidents reflect memory corruptions (due to bugs in some Outlook versions), rather then problems in logical formatting. I can't recall similar corruptins with Thread-Index, but it's better to check for them. -- Eugene Berdnikov -- ## 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/
Re: [exim] Thread-Index header too long
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, which can similarly grow, how about a bug just to document the issue and relevant info such as the syntaxes of these headers? There could be one already; I recall a discussion somewhere about what to do with References: but not where it was. A useful suggestion was of a Usenet practice of retaining the first element and the last couple, on the assumption that later ones are appended as the list grows. -- 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/
Re: [exim] Thread-Index header too long
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: The one I have is 1000 chars w/o the header field > name and w/o the line ending terminator. It then continues on the next > (indented) line, which is ok. Are you asking how to disable the Exim rejection of these lines? If so, perhaps the snippet below from my configuration may help. Several sites triggers this problem today, and I'm not sure it is a reasonable default behaviour any more. Fortunately it is possible to disable. # https://blog.dhampir.no/content/exim4-line-length-in-debian-stretch-mail-delivery-failed-returning-message-to-sender # oneflow.com emails trigger the following: # 2022-02-28 12:16:31.812 [2285693] 1nOe11-009ac1-DL H=a3-3.smtp-out.eu-west-1.amazonses.com [54.240.3.3]:38433 I=[178.174.241.107]:25 X=TLS1.2:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_128_CBC__SHA1:128 CV=no SNI=uggla.sjd.se F=<0102017f400bcc94-9e0850cc-cd93-4e2b-adfe-c4058370ae10-000...@eu-west-1.amazonses.com> rejected after DATA: maximum allowed line length is 998 octets, got 4852 IGNORE_SMTP_LINE_LENGTH_LIMIT=t /Simon signature.asc Description: PGP signature -- ## 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/
Re: [exim] Thread-Index header too long
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 and w/o the line ending terminator. It then continues on the next (indented) line, which is ok. -- Heiko signature.asc Description: PGP signature -- ## 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/
[exim] Thread-Index header too long
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 bounce message,
which in turn has an oversized header then too.)
Yes, we could reject it in the DATA ACL already, but I'm not asking how
to block it.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: F69376CE -
signature.asc
Description: PGP signature
--
## 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/
