Re: maildrop choking on double angle brackets in the 'In-Reply-To:' header

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============5524538340786367956==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-489013-1771381374-0001";
    micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 8bit

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_ripper.email-scan.com-489013-1771381374-0001
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thomas Schwinge writes:

>
>     [...]
>     Matching /^list-id:\s+.*<([a-z=C3=A4=C3=B6=C3=BC=C3=9F0-9&()*+._-]+=
)>$/ against X-Mailer: =20
> git-send-email 2.34.1
>     Not matched.
>     Matching /^list-id:\s+.*<([a-z=C3=A4=C3=B6=C3=BC=C3=9F0-9&()*+._-]+=
)>$/ against In-Reply-To:
>     Not matched.
>     [...]/shared/.mailfilter-sort(129): Search of ^list-id:\s+.*<([a-=20
> z=C3=A4=C3=B6=C3=BC=C3=9F0-9&()*+._-]+)>$ =3D 0
>     [...]/shared/.mailfilter-sort(130): Operation: logical or, left han=
d =20
> side=3D0
>     [...]/shared/.mailfilter-sort(130): Operation: logical or, evaluati=
ng =20
> right hand size.
>     [...]
>
> Notice that this (a) doesn't properly print the full header line in
> '[...] against In-Reply-To:', and (b) terminates matching at that point=
,
> therefore not considering the 'List-Id: <linux-kernel.vger.kernel.org>'
> header following later.
>
> Even if maybe double angle brackets in the 'In-Reply-To:' header are
> non-conforming (?), aborting the matching in that case doesn't seem
> desirable behavior?

No, that is unlikely, the reason must be something else. I do not see any =20
specific handling of in-reply-to: headers. It just looks like maildrop =20
thinks the headers end there.

Take the sample message, replace its contents with a single blank line, =20
leaving the headers, and create a sample mailfilter containing just that =20
expression. Verify that this unexpected behavior still occurs.

Now start removing the headers, checking and verifying that the observed =20
results are the same, until a minimal reproducible example is isolated, t=
hen =20
show what you've got.



--=_ripper.email-scan.com-489013-1771381374-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCaZUifgAKCRCKYPgoojZS
4kNyAQCeMgSUbwlxUTdR/4OrCKoekwivQZ/Ypv/tJerAMRzoQwD/ek454ZNSbIwI
sNdFKiLUuO7LWQ12eNPmAXQal64DJgY=
=IM1r
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-489013-1771381374-0001--


--===============5524538340786367956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============5524538340786367956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Courier-maildrop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/courier-maildrop

--===============5524538340786367956==--