[heroes] [List migration] Nomail subscription doesn't work
Hi, due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration. Can this please be corrected? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
On Sat, Nov 28, 2020 at 9:23 AM ASSI <Stromeko@nexgo.de> wrote:
Hi,
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
To configure subscription without mail delivery, you can do that by going to https://lists.opensuse.org/manage/lists/ From there, you can select the mailing list to manage and select to update list options and turn off mail delivery there. -- 真実はいつも一つ！/ Always, there's only one truth!
Neal Gompa wrote:
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
To configure subscription without mail delivery, you can do that by going to https://lists.opensuse.org/manage/lists/
From there, you can select the mailing list to manage and select to update list options and turn off mail delivery there.
Which part of "without an account" was unclear? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
ASSI wrote:
Neal Gompa wrote:
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
To configure subscription without mail delivery, you can do that by going to https://lists.opensuse.org/manage/lists/
From there, you can select the mailing list to manage and select to update list options and turn off mail delivery there.
Which part of "without an account" was unclear?
It was entirely clear, just not possible. -- Per Jessen, Zürich (1.0°C) Member, openSUSE Heroes
ASSI wrote:
Hi,
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
Not really, mailman does not use the same concept of a "nomail" list. Instead you can log on to the mailman web interface, navigate to the list and address you want and disable mail delivery. -- Per Jessen, Zürich (2.1°C) Member, openSUSE Heroes
On 28/11/2020 16.27, Per Jessen wrote:
ASSI wrote:
Hi,
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
Not really, mailman does not use the same concept of a "nomail" list. Instead you can log on to the mailman web interface, navigate to the list and address you want and disable mail delivery.
There is a problem there, when you have two mail address, one "mail" and one "nomail". Mailman Settings / List-based preferences Does not say to which email each line applies to. And when changing a delivery setting, it errors: Invalid Parameter "delivery_status": Accepted Values are: enabled, by_user, by_bounces, by_moderator, unknown. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. wrote:
On 28/11/2020 16.27, Per Jessen wrote:
ASSI wrote:
Hi,
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
Not really, mailman does not use the same concept of a "nomail" list. Instead you can log on to the mailman web interface, navigate to the list and address you want and disable mail delivery.
There is a problem there, when you have two mail address, one "mail" and one "nomail".
Mailman Settings / List-based preferences
Does not say to which email each line applies to. And when changing a delivery setting, it errors:
Invalid Parameter "delivery_status": Accepted Values are: enabled, by_user, by_bounces, by_moderator, unknown.
Please just report it. I have sofar had no problems enabling no delivery. -- Per Jessen, Zürich (1.3°C) Member, openSUSE Heroes
On 28/11/2020 19.06, Per Jessen wrote:
Carlos E. R. wrote:
On 28/11/2020 16.27, Per Jessen wrote:
ASSI wrote:
Hi,
due to the list migration I recognized that I was no longer subscribed to the support mailing list. So I subscribed (again), but none of the documented ways of getting a "nomail" subscription without an account works with the new list software. the feature itself must still be there b ecause the other lists did not suddenly start to send email (thankfully) after the migration.
Can this please be corrected?
Not really, mailman does not use the same concept of a "nomail" list. Instead you can log on to the mailman web interface, navigate to the list and address you want and disable mail delivery.
There is a problem there, when you have two mail address, one "mail" and one "nomail".
Mailman Settings / List-based preferences
Does not say to which email each line applies to. And when changing a delivery setting, it errors:
Invalid Parameter "delivery_status": Accepted Values are: enabled, by_user, by_bounces, by_moderator, unknown.
Please just report it. I have sofar had no problems enabling no delivery.
ticket to admin? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <4571fbd2-a7cb-c9ae-c240-e6b6f41daacb@Telcontar.valinor> On Saturday, 2020-11-28 at 20:51 +0100, Carlos E. R. wrote:
On 28/11/2020 19.06, Per Jessen wrote:
Carlos E. R. wrote:
On 28/11/2020 16.27, Per Jessen wrote:
...
Not really, mailman does not use the same concept of a "nomail" list. Instead you can log on to the mailman web interface, navigate to the list and address you want and disable mail delivery.
There is a problem there, when you have two mail address, one "mail" and one "nomail".
Mailman Settings / List-based preferences
Does not say to which email each line applies to. And when changing a delivery setting, it errors:
Invalid Parameter "delivery_status": Accepted Values are: enabled, by_user, by_bounces, by_moderator, unknown.
Please just report it. I have sofar had no problems enabling no delivery.
ticket to admin?
I reported <https://progress.opensuse.org/issues/80566> The reply was: «This is quite obviously a bug, and I suspect postorius doesn't expect you to subscribe with more than one address to a mailing list. I would report that upstream to https://gitlab.com/mailman/postorius/-/issues, since mailman handles this just fine otherwise» If "mailman handles this just fine", is there some mail command to access these options directly without postorious? - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHYEARECADYWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX89nohgcY2FybG9zLmUu ckBvcGVuc3VzZS5vcmcACgkQtTMYHG2NR9UpMACfesUusN9Y5zXkl+w4/KRt4YYx +5IAniY85a3+RzDIWn2YDe1nIJBuSCdj =bkeY -----END PGP SIGNATURE-----
Am Di, 8. Dez, 2020 um 12:46 P. M. schrieb Carlos E. R. <carlos.e.r@opensuse.org>:
I reported <https://progress.opensuse.org/issues/80566>
The reply was:
«This is quite obviously a bug, and I suspect postorius doesn't expect you to subscribe with more than one address to a mailing list. I would report that upstream to https://gitlab.com/mailman/postorius/-/issues, since mailman handles this just fine otherwise»
If "mailman handles this just fine", is there some mail command to access these options directly without postorious?
Sadly no, and in the same vain the mailman api can't be public to expose those options, it's only available to postorius and hyperkitty inside the mailman vm. The only real way to get this fixed is to fix it in postorius. LCP [Stasiek] https://lcp.world
On 08/12/2020 12.54, Stasiek Michalski wrote:
Am Di, 8. Dez, 2020 um 12:46 P. M. schrieb Carlos E. R. <>:
I reported <https://progress.opensuse.org/issues/80566>
The reply was:
«This is quite obviously a bug, and I suspect postorius doesn't expect you to subscribe with more than one address to a mailing list. I would report that upstream to https://gitlab.com/mailman/postorius/-/issues, since mailman handles this just fine otherwise»
If "mailman handles this just fine", is there some mail command to access these options directly without postorious?
Sadly no, and in the same vain the mailman api can't be public to expose those options, it's only available to postorius and hyperkitty inside the mailman vm. The only real way to get this fixed is to fix it in postorius.
I don't have an account at gitlab. I'm trying to create one, and it insists on me creating a group. I tried "ninguno" (Spanish for none), with several variations, it refuses (says it is taken). Worse, I see it is going to ask me later for my project later. To create my first project. I need help. Isn't there someway to post a bug there for a plain user? This is not friendly :-/ -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 08/12/2020 19.30, Carlos E. R. wrote:
On 08/12/2020 12.54, Stasiek Michalski wrote:
Am Di, 8. Dez, 2020 um 12:46 P. M. schrieb Carlos E. R. <>:
I reported <https://progress.opensuse.org/issues/80566>
The reply was:
«This is quite obviously a bug, and I suspect postorius doesn't expect you to subscribe with more than one address to a mailing list. I would report that upstream to https://gitlab.com/mailman/postorius/-/issues, since mailman handles this just fine otherwise»
If "mailman handles this just fine", is there some mail command to access these options directly without postorious?
Sadly no, and in the same vain the mailman api can't be public to expose those options, it's only available to postorius and hyperkitty inside the mailman vm. The only real way to get this fixed is to fix it in postorius.
I don't have an account at gitlab.
I'm trying to create one, and it insists on me creating a group. I tried "ninguno" (Spanish for none), with several variations, it refuses (says it is taken). Worse, I see it is going to ask me later for my project later. To create my first project.
I need help.
Isn't there someway to post a bug there for a plain user? This is not friendly :-/
Being stuck, I left the page open. Then I noticed I had received a confirmation email. I just clicked on it, and it asks me to fill my issue. Going ahead. <https://gitlab.com/mailman/postorius/-/issues/460> -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 08/12/2020 20.08, Carlos E. R. wrote:
On 08/12/2020 19.30, Carlos E. R. wrote:
On 08/12/2020 12.54, Stasiek Michalski wrote:
Am Di, 8. Dez, 2020 um 12:46 P. M. schrieb Carlos E. R. <>:
I reported <https://progress.opensuse.org/issues/80566>
...
Sadly no, and in the same vain the mailman api can't be public to expose those options, it's only available to postorius and hyperkitty inside the mailman vm. The only real way to get this fixed is to fix it in postorius.
I don't have an account at gitlab.
...
Mailman people now want you admins to provide them with logs and data. I don't have access to those. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Am Di, 8. Dez, 2020 um 10:04 P. M. schrieb Carlos E. R. <carlos.e.r@opensuse.org>:
Mailman people now want you admins to provide them with logs and data. I don't have access to those.
I would ask you that you reproduce the bug so I can capture those logs LCP [Stasiek] https://lcp.world
Stasiek Michalski wrote:
Am Di, 8. Dez, 2020 um 10:04 P. M. schrieb Carlos E. R. <carlos.e.r@opensuse.org>:
Mailman people now want you admins to provide them with logs and data. I don't have access to those.
I would ask you that you reproduce the bug so I can capture those logs
I reproduced it this morning, around 09:50. I am not sure which logs to look at though. I have updated Carlos' ticket. -- Per Jessen, Zürich (2.8°C) Member, openSUSE Heroes
On 09/12/2020 11.11, Per Jessen wrote:
Stasiek Michalski wrote:
Am Di, 8. Dez, 2020 um 10:04 P. M. schrieb Carlos E. R. <carlos.e.r@opensuse.org>:
Mailman people now want you admins to provide them with logs and data. I don't have access to those.
I would ask you that you reproduce the bug so I can capture those logs
I reproduced it this morning, around 09:50. I am not sure which logs to look at though. I have updated Carlos' ticket.
I was trying to reproduce the issue, when I found out that my second subscription to this mail list was gone. Only my o.o alias was there. I have just subscribed again. However, when I look under the "list based preferences tab", I have o.o alias delivery enabled, delivery mode regular. telefonica delivery ( ), delivery mode regular. The radio buttons for telefonica account delivery are empty. Then I look under "address based preferences" and all buttons show empty for my three addresses. I try change settings on telefonica: Address telefonica Delivery status enabled Delivery mode regular Receive own postings yes Acknowledge posts no Hide address no Receive list copies (possible duplicates) yes Preferred language English USA. Save at 11:36 UTC. No error message. Now to the list based preferences tab. No change. I set delivery to disabled on telefonica account. Save at 11.37 UTC Got error: Invalid Parameter "delivery_status": Accepted Values are: enabled, by_user, by_bounces, by_moderator, unknown. Changes were not accepted. I now look under the Subscriptions tab: list subs. addr del. mode role heroes oo alias regular member heroes telefoni none member heroes telefoni none nonmember Do you want all this email in the ticket? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Carlos E. R. writes:
If "mailman handles this just fine", is there some mail command to access these options directly without postorious?
Mailman version 2 had these options via the request interface, but it seems that for whatever reason version 3 didn't implement that part of the request interface. Now, a few of those settings obviously should/could not be implemented via the mail request interface, but for most other things this seems like a sad regression (and a major misunderstanding about how mailing lists are used in reality). Also, as the conversion scripts show plainly enough, there is an interface to connect to these options via API, it just hasn't been wired in. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
On 08/12/2020 14.44, ASSI wrote:
Carlos E. R. writes:
If "mailman handles this just fine", is there some mail command to access these options directly without postorious?
Mailman version 2 had these options via the request interface, but it seems that for whatever reason version 3 didn't implement that part of the request interface. Now, a few of those settings obviously should/could not be implemented via the mail request interface, but for most other things this seems like a sad regression (and a major misunderstanding about how mailing lists are used in reality). Also, as the conversion scripts show plainly enough, there is an interface to connect to these options via API, it just hasn't been wired in.
Mailman devs should have done a few polls. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (6)
-
ASSI -
Carlos E. R. -
Carlos E. R. -
Neal Gompa -
Per Jessen -
Stasiek Michalski