Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #274563 > unrolled thread
| Started by | Eben King <eben@gmx.us> |
|---|---|
| First post | 2024-11-16 18:40 +0100 |
| Last post | 2024-11-20 18:00 +0100 |
| Articles | 20 on this page of 45 — 16 participants |
Back to article view | Back to linux.debian.user
BD backup? Eben King <eben@gmx.us> - 2024-11-16 18:40 +0100
Re: BD backup? Arno Lehmann <al@its-lehmann.de> - 2024-11-16 18:50 +0100
Re: BD backup? eben@gmx.us - 2024-11-16 19:50 +0100
Re: BD backup? Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-11-16 23:30 +0100
Re: BD backup? eben@gmx.us - 2024-11-16 23:40 +0100
Re: BD backup? Max Nikulin <manikulin@gmail.com> - 2024-11-17 03:30 +0100
Re: BD backup? Jean-François Bachelet <jfbachelet@free.fr> - 2024-11-17 00:40 +0100
Re: BD backup? eben@gmx.us - 2024-11-17 20:10 +0100
Re: BD backup? Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-11-18 02:00 +0100
Re: BD backup? Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-11-18 02:20 +0100
mail sig separator (was Re: BD backup?) "Jonathan Dowland" <jmtd@debian.org> - 2024-11-19 11:30 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-19 16:10 +0100
Re: mail sig separator (was Re: BD backup?) Eric S Fraga <e.fraga@ucl.ac.uk> - 2024-11-19 16:30 +0100
Re: mail sig separator (was Re: BD backup?) Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2024-11-19 16:30 +0100
Re: mail sig separator (was Re: BD backup?) "Jonathan Dowland" <jmtd@debian.org> - 2024-11-19 16:40 +0100
Re: mail sig separator (was Re: BD backup?) "Jonathan Dowland" <jmtd@debian.org> - 2024-11-25 22:10 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-20 01:50 +0100
Re: mail sig separator (was Re: BD backup?) <tomas@tuxteam.de> - 2024-11-20 06:40 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-20 16:20 +0100
Re: mail sig separator (was Re: BD backup?) Greg Wooledge <greg@wooledge.org> - 2024-11-20 16:30 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-20 17:30 +0100
Re: mail sig separator (was Re: BD backup?) The Wanderer <wanderer@fastmail.fm> - 2024-11-20 17:40 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-20 18:10 +0100
Re: mail sig separator (was Re: BD backup?) Charles Curley <charlescurley@charlescurley.com> - 2024-11-20 18:30 +0100
Re: mail sig separator (was Re: BD backup?) <tomas@tuxteam.de> - 2024-11-20 19:00 +0100
Re: mail sig separator Felix Miata <mrmazda@stanis.net> - 2024-11-20 21:00 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-20 21:20 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-20 21:40 +0100
Re: mail sig separator (was Re: BD backup?) John Crawley <john@bunsenlabs.org> - 2024-11-21 05:50 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-21 07:20 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-21 07:20 +0100
Re: mail sig separator (was Re: BD backup?) John Crawley <john@bunsenlabs.org> - 2024-11-21 11:10 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-21 16:10 +0100
Re: mail sig separator (was Re: BD backup?) <tomas@tuxteam.de> - 2024-11-21 16:20 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-22 00:40 +0100
Re: mail sig separator (was Re: BD backup?) Greg Wooledge <greg@wooledge.org> - 2024-11-22 01:10 +0100
Re: mail sig separator (was Re: BD backup?) gene heskett <gheskett@shentel.net> - 2024-11-22 07:10 +0100
Re: mail sig separator (was Re: BD backup?) Max Nikulin <manikulin@gmail.com> - 2024-11-21 04:20 +0100
Re: mail sig separator (was Re: BD backup?) Max Nikulin <manikulin@gmail.com> - 2024-11-21 16:30 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-21 17:10 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-21 17:20 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-21 17:50 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-21 20:40 +0100
Re: mail sig separator (was Re: BD backup?) eben@gmx.us - 2024-11-20 17:40 +0100
Re: mail sig separator (was Re: BD backup?) <tomas@tuxteam.de> - 2024-11-20 18:00 +0100
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
| From | eben@gmx.us |
|---|---|
| Date | 2024-11-20 17:30 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKVKy-ahwz-21@gated-at.bofh.it> |
| In reply to | #274701 |
On 11/20/24 10:20, Greg Wooledge wrote: > On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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. > If I had to guess, I would guess that Thunderbird is composing HTML > email, and then translating it to plain text, with trailing spaces > being lost during that translation. Including the trailing space on > the signature separator. Makes sense. Does anyone using Thunderbird _not_ get trailing spaces stripped, or is it just me? > Just to double-check, Your tests all worked. However, I looked at the the copy of the previous message I received, and all the tests (including the one with no trailing spaces) had one trailing whitespace character. So my attachment that showed a correct separator was invalid. I saved the email in question (Tbird only saves as *.eml, whatever that is) and the test lines all ended with CR LF, no spaces. Same deal in the copy in my "sent" folder. So the stripping is happening locally.
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2024-11-20 17:40 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKVUd-ahzD-13@gated-at.bofh.it> |
| In reply to | #274703 |
[Multipart message — attachments visible in raw view] — view raw
On 2024-11-20 at 11:24, eben@gmx.us wrote: > On 11/20/24 10:20, Greg Wooledge wrote: >> If I had to guess, I would guess that Thunderbird is composing >> HTML email, and then translating it to plain text, with trailing >> spaces being lost during that translation. Including the trailing >> space on the signature separator. > > Makes sense. Does anyone using Thunderbird _not_ get trailing > spaces stripped, or is it just me? I don't (see signature below), but it may be worth noting that I am using an *ancient* version of Thunderbird, because of UI/UX changes in the meanwhile which I'm not willing to tolerate. It's far from impossible that changes in more recent Thunderbird versions might have broken this. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | eben@gmx.us |
|---|---|
| Date | 2024-11-20 18:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKWng-ahYG-5@gated-at.bofh.it> |
| In reply to | #274706 |
On 11/20/24 11:37, The Wanderer wrote: > On 2024-11-20 at 11:24, eben@gmx.us wrote: > >> On 11/20/24 10:20, Greg Wooledge wrote: > >>> If I had to guess, I would guess that Thunderbird is composing >>> HTML email, and then translating it to plain text, with trailing >>> spaces being lost during that translation. Including the trailing >>> space on the signature separator. >> >> Makes sense. Does anyone using Thunderbird _not_ get trailing >> spaces stripped, or is it just me? > > I don't (see signature below), but it may be worth noting that I am > using an *ancient* version of Thunderbird, because of UI/UX changes in > the meanwhile which I'm not willing to tolerate. It's far from > impossible that changes in more recent Thunderbird versions might have > broken this. This is true. What version? BTW I received your separator as "--=20". But that's once saved as eml. Onscreen it looks fine, and the signature is greyed out. Anyone know how to get a pure text version, if such a thing exists?
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2024-11-20 18:30 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKWGC-ai57-17@gated-at.bofh.it> |
| In reply to | #274709 |
On Wed, 20 Nov 2024 12:08:02 -0500 eben@gmx.us wrote: > Anyone know how to > get a pure text version, if such a thing exists? Possibly storing one's emails in maildir format. Each email is its own raw text file. Suitable grepping or use of mairix or the like should then locate particular messages. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-11-20 19:00 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKX9D-aieS-5@gated-at.bofh.it> |
| In reply to | #274709 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Nov 20, 2024 at 12:08:02PM -0500, eben@gmx.us wrote: > On 11/20/24 11:37, The Wanderer wrote: > > On 2024-11-20 at 11:24, eben@gmx.us wrote: > > > > > On 11/20/24 10:20, Greg Wooledge wrote: > > > > > > If I had to guess, I would guess that Thunderbird is composing > > > > HTML email, and then translating it to plain text, with trailing > > > > spaces being lost during that translation. Including the trailing > > > > space on the signature separator. > > > > > > Makes sense. Does anyone using Thunderbird _not_ get trailing > > > spaces stripped, or is it just me? > > > > I don't (see signature below), but it may be worth noting that I am > > using an *ancient* version of Thunderbird, because of UI/UX changes in > > the meanwhile which I'm not willing to tolerate. It's far from > > impossible that changes in more recent Thunderbird versions might have > > broken this. > > This is true. What version? > > BTW I received your separator as "--=20". But that's once saved as eml. This is quoted-printable. Most probably the way the mail was transported. I guess it's the "rawest" it gets. Cheers -- t > Onscreen it looks fine, and the signature is greyed out. Anyone know how to > get a pure text version, if such a thing exists? Reality is... complicated. Very [1] much so. Cheers [1] https://en.wikipedia.org/wiki/MIME -- t
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@stanis.net> |
|---|---|
| Date | 2024-11-20 21:00 +0100 |
| Subject | Re: mail sig separator |
| Message-ID | <JKZ1M-ajoU-15@gated-at.bofh.it> |
| In reply to | #274709 |
eben composed on 2024-11-20 12:08 (UTC-0500): > BTW I received your separator as "--=20". But that's once saved as eml. > Onscreen it looks fine, and the signature is greyed out. Anyone know how to > get a pure text version, if such a thing exists? Where is your .sig coming from? If it's in a plain text file that TB automatically attaches, I would expect the standard "-- " to be inserted ahead of it, as is done in SeaMonkey, from which TB was forked, at least if composing in plain text. I have no familiarity with TB use, or HTML composition. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-20 21:20 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKZl7-ajKf-9@gated-at.bofh.it> |
| In reply to | #274703 |
On 11/20/24 11:24, eben@gmx.us wrote: > On 11/20/24 10:20, Greg Wooledge wrote: >> On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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. [...] Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-20 21:40 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JKZEt-ajQL-5@gated-at.bofh.it> |
| In reply to | #274723 |
On 11/20/24 15:16, gene heskett wrote: > On 11/20/24 11:24, eben@gmx.us wrote: >> On 11/20/24 10:20, Greg Wooledge wrote: >>> On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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. > > [...] > > Cheers, Gene Heskett, CET. 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. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | John Crawley <john@bunsenlabs.org> |
|---|---|
| Date | 2024-11-21 05:50 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JL7iF-aoEv-1@gated-at.bofh.it> |
| In reply to | #274724 |
On 21/11/2024 05:31, gene heskett wrote: > 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. > > Cheers, Gene Heskett, CET. My TB is behaving exactly like yours in this respect. Your sig is shown greyed-out and is automatically removed when I reply to your post (like this). Meanwhile my sig is correctly added and (I've just checked) sent to another account's inbox with the trailing space after -- intact. So nothing here to blame on TB, at least for mail being sent between Thunderbirds. -- John
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-21 07:20 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JL8HL-apJJ-1@gated-at.bofh.it> |
| In reply to | #274734 |
On 11/21/24 01:10, gene heskett wrote: > On 11/20/24 23:46, John Crawley wrote: >> On 21/11/2024 05:31, gene heskett wrote: >>> 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. >>> >>> Cheers, Gene Heskett, CET. >> >> My TB is behaving exactly like yours in this respect. Your sig is >> shown greyed-out and is automatically removed when I reply to your >> post (like this). >> > Which is how it should be. > >> Meanwhile my sig is correctly added and (I've just checked) sent to >> another account's inbox with the trailing space after -- intact. >> And that one above did nothing because it was mid-line, w/o the /r-- /r that triggers all this. It will be interesting how the above is treated when echo back from the server, which was the other half of my point. ;o) >> So nothing here to blame on TB, at least for mail being sent between >> Thunderbirds. >> > That (sigh) was my point. That doesn't affect the dozens of miss- > configured email agents here that violate those SOP's for text emails. > <y list of groups I sort email into is about 2 screens tall but tirds > filters for debian-user still miss-sorts them, a lot. Some sent to > debian-user, some send to the full fqdn, And it still leaves about 10-20 > an hour in the inbox or in junk with a perfectly good address. Which > filter rule is miss-firing is a puzzle w/o enough clues to solve. > > Cheers, Gene Heskett, CET. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-21 07:20 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JL8HL-apJJ-3@gated-at.bofh.it> |
| In reply to | #274734 |
On 11/20/24 23:46, John Crawley wrote: > On 21/11/2024 05:31, gene heskett wrote: >> 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. >> >> Cheers, Gene Heskett, CET. > > My TB is behaving exactly like yours in this respect. Your sig is shown > greyed-out and is automatically removed when I reply to your post (like > this). > Which is how it should be. > Meanwhile my sig is correctly added and (I've just checked) sent to > another account's inbox with the trailing space after -- intact. > > So nothing here to blame on TB, at least for mail being sent between > Thunderbirds. > That (sigh) was my point. That doesn't affect the dozens of miss-configured email agents here that violate those SOP's for text emails. <y list of groups I sort email into is about 2 screens tall but tirds filters for debian-user still miss-sorts them, a lot. Some sent to debian-user, some send to the full fqdn, And it still leaves about 10-20 an hour in the inbox or in junk with a perfectly good address. Which filter rule is miss-firing is a puzzle w/o enough clues to solve. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | John Crawley <john@bunsenlabs.org> |
|---|---|
| Date | 2024-11-21 11:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLcil-aslj-3@gated-at.bofh.it> |
| In reply to | #274738 |
On 21/11/2024 15:10, gene heskett wrote: > That doesn't affect the dozens of miss-configured email agents here that violate those SOP's for text emails. <y list of groups I sort email into is about 2 screens tall but tirds filters for debian-user still miss-sorts them, a lot. Some sent to debian-user, some send to the full fqdn, And it still leaves about 10-20 an hour in the inbox or in junk with a perfectly good address. Which filter rule is miss-firing is a puzzle w/o enough clues to solve. > My mail filter for debian-user seems to be working OK, everything sent to the right place. Maybe it's because I have fewer filters than you (31 in the Local Folders section) or could it be because I consolidate all accounts into Local Folders, but FWIW the filter is: Match all the following List-Id is <debian-user.lists.debian.org> Perform these actions Move Message to Deb user on Local Folders --- I still haven't figured out the difference between setting filters on Local Folders vs for individual mail accounts though. -- John
[toc] | [prev] | [next] | [standalone]
| From | eben@gmx.us |
|---|---|
| Date | 2024-11-21 16:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLgYF-av8E-3@gated-at.bofh.it> |
| In reply to | #274724 |
On 11/20/24 15:31, gene heskett wrote: > On 11/20/24 15:16, gene heskett wrote: >> On 11/20/24 11:24, eben@gmx.us wrote: >>> On 11/20/24 10:20, Greg Wooledge wrote: >>>> On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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? Also, yours works and mine doesn't, and we're both using a recent Tbird. What could we be doing differently?
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-11-21 16:20 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLh8l-avbO-5@gated-at.bofh.it> |
| In reply to | #274754 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Nov 21, 2024 at 10:00:11AM -0500, eben@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, eben@gmx.us wrote: > > > > On 11/20/24 10:20, Greg Wooledge wrote: > > > > > On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-22 00:40 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLoWd-azW6-13@gated-at.bofh.it> |
| In reply to | #274754 |
On 11/21/24 10:00, eben@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, eben@gmx.us wrote: >>>> On 11/20/24 10:20, Greg Wooledge wrote: >>>>> On Wed, Nov 20, 2024 at 10:13:20 -0500, eben@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? > The =20 tells me its been converted to html style encoding some where. Might be your settings, might be the mail server you are using. IDK and haven't a clue. > Also, yours works and mine doesn't, and we're both using a recent Tbird. > What could we be doing differently? > > . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-11-22 01:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLppg-aAkX-5@gated-at.bofh.it> |
| In reply to | #274770 |
On Thu, Nov 21, 2024 at 18:32:38 -0500, gene heskett wrote: > The =20 tells me its been converted to html style encoding some where. No, =20 is "quoted printable" encoding. It's extremely common for email; it can be used whenever the source content is HTML or plain text or a calendar invitation or any other textual material which might not fit within the 7-bit ASCII encoding. If the message were HTML encoded, you would have seen %20, not =20.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-11-22 07:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLv1D-aDOB-11@gated-at.bofh.it> |
| In reply to | #274771 |
On 11/21/24 19:01, Greg Wooledge wrote: > On Thu, Nov 21, 2024 at 18:32:38 -0500, gene heskett wrote: >> The =20 tells me its been converted to html style encoding some where. > > No, =20 is "quoted printable" encoding. It's extremely common for > email; it can be used whenever the source content is HTML or plain text > or a calendar invitation or any other textual material which might > not fit within the 7-bit ASCII encoding. > > If the message were HTML encoded, you would have seen %20, not =20. > > . And I learn something Greg, thanks. Now all I have to do is remember it, Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-11-21 04:20 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JL5Tz-anXZ-3@gated-at.bofh.it> |
| In reply to | #274701 |
On 20/11/2024 22:20, Greg Wooledge wrote: > Content-Type: text/plain; charset=us-ascii > On Wed, Nov 20, 2024 at 10:13:20 -0500, eben wrote: >> Content-Type: text/plain; charset=UTF-8; format=flowed >> This line has one trailing space. [...] > This line has two leading and two trailing spaces. I think, format=flowed is important here. It may be disabled in Thunderbird, but it may interact with line width limit and in some cases it might be necessary to explicitly wrap lines ([Ctrl+R] for selection). Flowed format allows readers to rewrap paragraphs to smaller width (unfortunately Thunderbird rewraps even to fill really wide windows). Eben, you may try to inspect sources of your messages ([Ctrl+U]) from sent and draft folders. -- A directly typed signature
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-11-21 16:30 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLhi1-aveU-11@gated-at.bofh.it> |
| In reply to | #274733 |
On 21/11/2024 10:11, Max Nikulin wrote: > Eben, you may try to inspect sources of your messages ([Ctrl+U]) from > sent and draft folders. Interesting, signature separator is lost by gmane, see w3m -m 'nntp://news.gmane.io/gmane.linux.debian.user/622024' however it is present in USENET group and web archive <https://lists.debian.org/debian-user/2024/11/msg00532.html> Gmane does not strip signatures separated by "--=20" or if it is not format=flowed Content-Type.
[toc] | [prev] | [next] | [standalone]
| From | eben@gmx.us |
|---|---|
| Date | 2024-11-21 17:10 +0100 |
| Subject | Re: mail sig separator (was Re: BD backup?) |
| Message-ID | <JLhUJ-avHB-5@gated-at.bofh.it> |
| In reply to | #274699 |
On 11/20/24 10:13, eben@gmx.us wrote: > Just for kicks: > This line has no trailing spaces. > This line has one trailing space. > This line has two trailing spaces. OK, I changed "mail.html_compose" from true to false. Now to see if it makes a difference: This line has no trailing spaces. This line has one trailing space. This line has two trailing spaces.
[toc] | [prev] | [next] | [standalone]
Page 2 of 3 — ← Prev page 1 [2] 3 Next page →
Back to top | Article view | linux.debian.user
csiph-web