Re: maildropfilter and rfc5322 2.2.3 (Long Header Fields)

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.

--===============0339589740255428459==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-1732540-1767358310-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-1732540-1767358310-0001
Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

B writes:

> I'm not an email expert. rfc5322 is confusing because it says "Unfoldin=
g is =20
> accomplished by simply removing any CRLF that is immediately followed b=
y =20
> WSP". But this leaves a lot of questions. What about the WSP character =20
> itself? Is the mailer supposed to leave a trailing space/tab to achieve =20
> space between words?

The current behavior is based on this from the original RFC 822:

             The process of moving  from  this  folded   multiple-line
        representation  of a header field to its single line represen-
        tation is called "unfolding".  Unfolding  is  accomplished  by
        regarding   CRLF   immediately  followed  by  a  LWSP-char  as
        equivalent to the LWSP-char.

> When researching, I found a number of other discussions about this issu=
e in =20
> other projects, so it seems like it's been a contentious topic over the =20
> years.

Evolution of email standards over the years has been rocky. This is not t=
he =20
only problematic area, but probably the least troublesome one=E2=80=A6


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

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

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCaVe/ZgAKCRCKYPgoojZS
4lALAPwLhM7fXo08kNtFYnwb09NgpJ0l8VvoOffaya9d17ZZ0QD/VoHH87abIjhu
bZ5E0ZYJZGxQk4zjAQuKvxv8XtT8/AM=
=M3cG
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-1732540-1767358310-0001--


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


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

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

--===============0339589740255428459==--