On Thu, Nov 21, 2024 at 10:00:11AM -0500, e...@gmx.us wrote: > On 11/20/24 15:31, gene heskett wrote: > > On 11/20/24 15:16, gene heskett wrote: > > > On 11/20/24 11:24, e...@gmx.us wrote: > > > > On 11/20/24 10:20, Greg Wooledge wrote: > > > > > On Wed, Nov 20, 2024 at 10:13:20 -0500, e...@gmx.us wrote: > > > > > > Just for kicks: > > > > > > This line has no trailing spaces. > > > > > > This line has one trailing space. > > > > > > This line has two trailing spaces. > > > > > > > > > > In the message I received, none of these lines have any trailing > > > > > spaces. > > > > > > > > Dangit. > > > > > > What folks don't seem to get, is that the character preceding the "-- " > > > needs to be a line feed, as does the character /after/ the space, IOW, on > > > a line by itself. > > > > Which is what I am sending from latest t-bird in what I think is plain text, > > as below, and it works, my too long comment is not greyed out in the > > incoming echo from the listserver. You should see it incoming but not in a > > reply you make that quotes my msg for context. Your agent is supposed to > > throw it away, not retransmitting it again and again. > > Your sig separator arrived as "-- " not "--=20". Why the difference?
Look at the MIME structure of the message. The one might have a transfer encoding of "8bit" or similar, the other probably "quoted-printable". a transfer encoding "text/plain", the other is most probably "quoted-printable". ISTR I already tipped you off in this direction. Look up MIME in Wikipedia, it's really worth it! > Also, yours works and mine doesn't, and we're both using a recent Tbird. > What could we be doing differently? No idea about TBird's inner life. Cheers -- t
signature.asc
Description: PGP signature
