[heroes] Is there any particular need for [...] to be followed by two spaces instead of one?
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no. -- Per Jessen, Zürich (11.6°C) Member, openSUSE Heroes
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char. Question: what is the new incantation for subscribing as "nomail"? Too often I forget that on this list I subscribed with my opensuse.org alias, and my mail is thus held for moderation. The possible commands that the "help" request mentions are: confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. and these headers: List-Help: mailto:factory-request@lists.opensuse.org?subject=help List-Post: mailto:factory@lists.opensuse.org List-Subscribe: mailto:factory-join@lists.opensuse.org List-Unsubscribe: mailto:factory-leave@lists.opensuse.org -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting. I think it was just an extra blank that snook in during the migration.
Question: what is the new incantation for subscribing as "nomail"?
You subscribe, then you log in to mailman, pick the list and disable mail delivery. -- Per Jessen, Zürich (13.6°C) Member, openSUSE Heroes
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
I think it was just an extra blank that snook in during the migration.
Question: what is the new incantation for subscribing as "nomail"?
You subscribe, then you log in to mailman, pick the list and disable mail delivery.
Ah, ok. Curious there is no direct command by mail. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
Question: what is the new incantation for subscribing as "nomail"?
You subscribe, then you log in to mailman, pick the list and disable mail delivery.
Ah, ok. Curious there is no direct command by mail.
I don't think there is one, I haven't found one. -- Per Jessen, Zürich (14.2°C) Member, openSUSE Heroes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
Is there any particular need for [whatever] in list subject lines to be followed by two spaces instead of one? It breaks alphabetic listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having. I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHYEARECADYWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX66eFRgcY2FybG9zLmUu ckBvcGVuc3VzZS5vcmcACgkQtTMYHG2NR9WspACfaYHyMxYPBCViSs80ESvgdjDV 8gAAn05idJ0yWoJYf/hg16YXx90Ohm5Q =d56d -----END PGP SIGNATURE-----
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote:
Felix Miata wrote:
> Is there any particular need for [whatever] in list subject lines > to be followed by two spaces instead of one? It breaks alphabetic > listing of/by subject lines. --
I can't imagine there is any particular need for two instead of one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon. -- 真実はいつも一つ!/ Always, there's only one truth!
On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 11.52, Per Jessen wrote: > Felix Miata wrote: > >> Is there any particular need for [whatever] in list subject lines >> to be followed by two spaces instead of one? It breaks alphabetic >> listing of/by subject lines. -- > > I can't imagine there is any particular need for two instead of > one, no.
I didn't even notice that change, I sort by threads and date. But now that I know I see it. I have looked at other mail lists using mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. composed on 2020-11-13 20:13 (UTC+0100):
Neal Gompa wrote:
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
+1 Thanks to Per for removing the extra space! -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On Fri, Nov 13, 2020 at 2:14 PM Carlos E. R.
On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote:
Carlos E. R. wrote: > On 13/11/2020 11.52, Per Jessen wrote: >> Felix Miata wrote: >> >>> Is there any particular need for [whatever] in list subject lines >>> to be followed by two spaces instead of one? It breaks alphabetic >>> listing of/by subject lines. -- >> >> I can't imagine there is any particular need for two instead of >> one, no. > > I didn't even notice that change, I sort by threads and date. But > now that I know I see it. I have looked at other mail lists using > mailman and those I looked do not have that extra char.
Yeah, it's a bit weird. Heh, actually I think I may just have fixed it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
DMARC messages are already not going to have them, and it makes no sense if a full third (at least) of emails aren't going to get them anyway. It's easier to drop them so that you *know* you can't rely on those broken heuristics. -- 真実はいつも一つ!/ Always, there's only one truth!
On 13/11/2020 20.27, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 2:14 PM Carlos E. R.
wrote: On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 13/11/2020 14.00, Per Jessen wrote: > Carlos E. R. wrote: >> On 13/11/2020 11.52, Per Jessen wrote: >>> Felix Miata wrote: >>> >>>> Is there any particular need for [whatever] in list subject lines >>>> to be followed by two spaces instead of one? It breaks alphabetic >>>> listing of/by subject lines. -- >>> >>> I can't imagine there is any particular need for two instead of >>> one, no. >> >> I didn't even notice that change, I sort by threads and date. But >> now that I know I see it. I have looked at other mail lists using >> mailman and those I looked do not have that extra char. > > Yeah, it's a bit weird. Heh, actually I think I may just have fixed > it for this list. Check out this posting.
Yes. But it broke threading, which is weird. The subject content should have nothing to do with proper threading headers, but perhaps Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
DMARC messages are already not going to have them, and it makes no sense if a full third (at least) of emails aren't going to get them anyway. It's easier to drop them so that you *know* you can't rely on those broken heuristics.
Then you will have people like me not seeing posts, or answering in the wrong list, because we will not know what list is each post. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Fri, Nov 13, 2020 at 3:11 PM Carlos E. R.
On 13/11/2020 20.27, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 2:14 PM Carlos E. R.
wrote: On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote:
Carlos E. R. wrote: > On 13/11/2020 14.00, Per Jessen wrote: >> Carlos E. R. wrote: >>> On 13/11/2020 11.52, Per Jessen wrote: >>>> Felix Miata wrote: >>>> >>>>> Is there any particular need for [whatever] in list subject lines >>>>> to be followed by two spaces instead of one? It breaks alphabetic >>>>> listing of/by subject lines. -- >>>> >>>> I can't imagine there is any particular need for two instead of >>>> one, no. >>> >>> I didn't even notice that change, I sort by threads and date. But >>> now that I know I see it. I have looked at other mail lists using >>> mailman and those I looked do not have that extra char. >> >> Yeah, it's a bit weird. Heh, actually I think I may just have fixed >> it for this list. Check out this posting. > > Yes. But it broke threading, which is weird. The subject content > should have nothing to do with proper threading headers, but perhaps > Thunderbird is being "clever" - yes, that is, Alpine was not fooled.
Correct threading is done on message-ids. It doesn't make sense, even if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
DMARC messages are already not going to have them, and it makes no sense if a full third (at least) of emails aren't going to get them anyway. It's easier to drop them so that you *know* you can't rely on those broken heuristics.
Then you will have people like me not seeing posts, or answering in the wrong list, because we will not know what list is each post.
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client. If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch. -- 真実はいつも一つ!/ Always, there's only one truth!
On 13/11/2020 21.24, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 3:11 PM Carlos E. R.
wrote: On 13/11/2020 20.27, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 2:14 PM Carlos E. R.
wrote: On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote: > Carlos E. R. wrote: >> On 13/11/2020 14.00, Per Jessen wrote: >>> Carlos E. R. wrote: >>>> On 13/11/2020 11.52, Per Jessen wrote: >>>>> Felix Miata wrote: >>>>> >>>>>> Is there any particular need for [whatever] in list subject lines >>>>>> to be followed by two spaces instead of one? It breaks alphabetic >>>>>> listing of/by subject lines. -- >>>>> >>>>> I can't imagine there is any particular need for two instead of >>>>> one, no. >>>> >>>> I didn't even notice that change, I sort by threads and date. But >>>> now that I know I see it. I have looked at other mail lists using >>>> mailman and those I looked do not have that extra char. >>> >>> Yeah, it's a bit weird. Heh, actually I think I may just have fixed >>> it for this list. Check out this posting. >> >> Yes. But it broke threading, which is weird. The subject content >> should have nothing to do with proper threading headers, but perhaps >> Thunderbird is being "clever" - yes, that is, Alpine was not fooled. > > Correct threading is done on message-ids. It doesn't make sense, even > if there are more blanks in Subject, anyone could ruin the threading.
But Thunderbird is obviously not only using the message-ids, but also considers the subject. That may explain the problem Felix is having.
I suggest asking about this in the general list, maybe we can find some method to disable this Th. behaviour.
Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
DMARC messages are already not going to have them, and it makes no sense if a full third (at least) of emails aren't going to get them anyway. It's easier to drop them so that you *know* you can't rely on those broken heuristics.
Then you will have people like me not seeing posts, or answering in the wrong list, because we will not know what list is each post.
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client.
It is not machine filtering, it is visual cues that break, when all the posts are in a single folder.
If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch.
Well, they could use a secondary mail address on mail lists. Or we could change to put the mail list address in the "To" field, which is what some other lists do. As it is, leaving the subject line intact for those users that have dmarc is acceptable to me. I will deal with Thunderbird getting confused. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Fri, Nov 13, 2020 at 3:33 PM Carlos E. R.
On 13/11/2020 21.24, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 3:11 PM Carlos E. R.
wrote: On 13/11/2020 20.27, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 2:14 PM Carlos E. R.
wrote: On 13/11/2020 18.30, Neal Gompa wrote:
On Fri, Nov 13, 2020 at 9:54 AM Carlos E. R.
wrote: > On Friday, 2020-11-13 at 15:28 +0100, Per Jessen wrote: >> Carlos E. R. wrote: >>> On 13/11/2020 14.00, Per Jessen wrote: >>>> Carlos E. R. wrote: >>>>> On 13/11/2020 11.52, Per Jessen wrote: >>>>>> Felix Miata wrote: >>>>>> >>>>>>> Is there any particular need for [whatever] in list subject lines >>>>>>> to be followed by two spaces instead of one? It breaks alphabetic >>>>>>> listing of/by subject lines. -- >>>>>> >>>>>> I can't imagine there is any particular need for two instead of >>>>>> one, no. >>>>> >>>>> I didn't even notice that change, I sort by threads and date. But >>>>> now that I know I see it. I have looked at other mail lists using >>>>> mailman and those I looked do not have that extra char. >>>> >>>> Yeah, it's a bit weird. Heh, actually I think I may just have fixed >>>> it for this list. Check out this posting. >>> >>> Yes. But it broke threading, which is weird. The subject content >>> should have nothing to do with proper threading headers, but perhaps >>> Thunderbird is being "clever" - yes, that is, Alpine was not fooled. >> >> Correct threading is done on message-ids. It doesn't make sense, even >> if there are more blanks in Subject, anyone could ruin the threading. > > But Thunderbird is obviously not only using the message-ids, but also > considers the subject. That may explain the problem Felix is having. > > I suggest asking about this in the general list, maybe we can find some > method to disable this Th. behaviour. > Gmail does the same thing. It is planned to remove the subject prefix entirely, so this problem will go away soon.
Causing others that are worse, IMO.
DMARC messages are already not going to have them, and it makes no sense if a full third (at least) of emails aren't going to get them anyway. It's easier to drop them so that you *know* you can't rely on those broken heuristics.
Then you will have people like me not seeing posts, or answering in the wrong list, because we will not know what list is each post.
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client.
It is not machine filtering, it is visual cues that break, when all the posts are in a single folder.
If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch.
Well, they could use a secondary mail address on mail lists. Or we could change to put the mail list address in the "To" field, which is what some other lists do.
I wanted to use the latter option, but Per and Stasiek disagreed, and Gerald didn't particularly like it either.
As it is, leaving the subject line intact for those users that have dmarc is acceptable to me. I will deal with Thunderbird getting confused.
The subject prefix is going to be removed because it's not worth it to mangle for only some people and not others. -- 真実はいつも一つ!/ Always, there's only one truth!
Neal Gompa wrote:
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client. If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch.
It was "flipped" on 12 December. I have yet to see any fall-out. -- Per Jessen, Zürich (7.7°C) Member, openSUSE Heroes
Per Jessen wrote:
Neal Gompa wrote:
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client. If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch.
It was "flipped" on 12 December. I have yet to see any fall-out.
Duh ... November. -- Per Jessen, Zürich (7.2°C) Member, openSUSE Heroes
On 14/11/2020 19.54, Per Jessen wrote:
Per Jessen wrote:
Neal Gompa wrote:
I'm sorry. The best I can suggest is to use the headers to filter more aggressively in your client. If SUSE wasn't turning on DMARC reject for suse.com emails, we could leave the configuration as-is now. But they are, and are quite antsy to flip the switch.
It was "flipped" on 12 December. I have yet to see any fall-out.
Duh ... November.
suse.com DMARC recommends quarantine, not reject
participants (6)
-
Bernhard M. Wiedemann
-
Carlos E. R.
-
Carlos E. R.
-
Felix Miata
-
Neal Gompa
-
Per Jessen