Search results for "Postorius" - Mailman-users

Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/3/22 04:53, mhazan(a)mandint.org wrote: > > working on that plugin, i have found where to inserts the various > setting, however it's not clear what types and possibles value are > excepted for each ? ie "advertised" is bool True/false, but what about > "default_member_action" ? i've tried hold 'hold' "hold" all throw error > when trying to apply the style. from mailman.interfaces.action import Action mlist.default_member_action = Action.hold > i cannot find the types in the > documentation and all the other non bool settings. Look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for an example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Ron / BCLUG

Keith Christian wrote on 2024-05-24 16:41: > pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? As I understand it, mailman-hyperkitty get installed into the venv, but django and postorius are pulled in as a dependency of mailman-web (I believe?) I don't seem to see any SASS modules when I run `pip list | grep -i sass` in the venv. This handled the SASS stuff: > sudo apt install python3-dev python3-venv sassc lynx I created a file called `requirements.txt` which I use thusly in the venv: `pip install -r requirements.txt` I don't know if I can attach it to messages to the list, so I've included it below: ===%<--- requirements.txt --->%=== mailman mailman-web mailman-hyperkitty ## PyMySQL is used in the database connection def in mailman.cfg: ## PyMySQL ## ## For mailman-web migrate with MySQL, mysqlclient is required! ## mysqlclient ## PostgreSQL: psycopg2-binary uwsgi ## Wheel is advised, but (mostly) works without. wheel ## module error on missing "xapian_backend" when running ## `mailman-web update_index_one_list` ## ## ## ModuleNotFoundError: No module named 'xapian_backend' ## ## Requires separate build process (and wheel): see docs xapian-haystack Hopefully I'm not too wrong in what I've posted. rb

2 years, 3 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stephen J. Turnbull

Stefan Bauer writes: > No matter what i try, mailman still only connects without STARTTLS: Earlier you wrote: > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a STARTTLS command first', 'postorius(a)lists.mydomain.tld') > Request Method: POST > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > Django Version: 2.2.12 This looks like Django errors, not Postorius (Mailman). So this is something Django is doing, not Mailman (including Postorius). I'm not sure why Django is sending email (somebody made a password reset request seems likely, but I'm not that familiar with Django authn stuff). Anyway, if it's internal to Django, it would not consult Mailman's configs. This recent StackOverflow seems relevant: https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… HTH Steve

4 years, 10 months

Re: Changing default message limit (max_message_size)

by Abhilash Raj

On Mon, May 27, 2019, at 8:23 AM, Mark Sapiro wrote: > On 5/27/19 12:05 AM, roger(a)reasonal.com wrote: > > I found the field in settings that would appear to do this, but it just throws an error for whatever I give it ("An error occured**: Unknown attribute: max_message_size"). > > This should be fixed at > <https://gitlab.com/mailman/mailman/merge_requests/329>. > > Perhaps you need to update your Docker images > <https://asynchronous.in/docker-mailman/> That's right. You are probably using a new version of Postorius but not of Mailman Core. Please make sure the container images you have are updated. > > Also, see > <https://gitlab.com/mailman/postorius/issues/246#note_69323948> for a > not about changing this via `mailman shell` (withlist), but see the > subsequent comment about `quit()` > > > > PS As a suggestion, may be a good idea to indicate what units it's expecting... bytes? kB? Nybbles? > > Reported at <https://gitlab.com/mailman/postorius/issues/362>, thanks. > > > PPS ** Psst: occurred with two r's... > > Reported at <https://gitlab.com/mailman/postorius/issues/361>, thanks. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

7 years, 3 months

Re: Python 3.13 compatibility

by Thomas Krichel

Hi gang, On mailman import21, I hit the error TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol I found the earlier thread, where Mark wrote > This is https://gitlab.com/mailman/mailman/-/issues/1190 fixed for > Mailman 3.3.11 by https://gitlab.com/mailman/mailman/-/merge_requests/1309 I have (venv) mailman@darni:~$ mailman version GNU Mailman 3.3.9 (Tom Sawyer) I tried (venv) mailman@darni:~$ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web to no avail, the TypeError is not fixed and the version is the same. ok, so I need to spell out a version. Trying pip install -U mailman==3.3.11 postorius django-mailman3 hyperkitty mailman-web 3.3.11 appears not to be available pip install -U mailman==3.3.10 postorius django-mailman3 hyperkitty mailman-web yields the familiar problem with the nntplib. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13" I had earlier gotten around this by installing its successor, standard-nntplib, and it is still there. (venv) mailman@darni:~$ pip3.13 install standard-nntplib Requirement already satisfied: standard-nntplib in /usr/local/mailman/venv/lib/python3.13/site-packages (3.13.0) That used to work for 3.3.9. But the 3.3.10 version may have no verbiage to say that the nntlib is replaced by standard-nntplib Now I seem to have managed to hose my environment. (venv) mailman@darni:~$ mailman version Traceback (most recent call last): File "/usr/local/mailman/venv/bin/mailman", line 3, in <module> from mailman.bin.mailman import main File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/bin/mailman.py", line 25, in <module> from mailman.core.initialize import initialize File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/core/initialize.py", line 29, in <module> import mailman.config.config File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/config/__init__.py", line 20, in <module> from mailman.config.config import Configuration File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/config/config.py", line 32, in <module> from mailman.utilities.modules import call_name, expand_path File "/usr/local/mailman/venv/lib/python3.13/site-packages/mailman/utilities/modules.py", line 23, in <module> from pkg_resources import resource_filename, resource_listdir ModuleNotFoundError: No module named 'pkg_resources' What now? -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22213th day.

5 months, 3 weeks

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Hi Steve, thank you for your time. Thats it :) Works now. I had to set it in /etc/mailman3/mailman-web.py After first logon, django tries to send a mail to confirm email address. Nov 10 08:44:56 mal02 postfix/qmgr[2893767]: 9255C5E0BE2: from=<postorius(a)lists.mydomain.tld>, size=920, nrcpt=1 (queue active) Nov 10 08:44:56 mal02 postfix/smtpd[879486]: disconnect from localhost[::1] ehlo=2 *starttls=1* mail=1 rcpt=1 data=1 quit=1 commands=7 This now works with STARTTLS. Hoooray :) Am Di., 9. Nov. 2021 um 16:50 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > No matter what i try, mailman still only connects without STARTTLS: > > Earlier you wrote: > > > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a > STARTTLS command first', 'postorius(a)lists.mydomain.tld') > > Request Method: POST > > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > > Django Version: 2.2.12 > > This looks like Django errors, not Postorius (Mailman). So this is > something Django is doing, not Mailman (including Postorius). I'm not > sure why Django is sending email (somebody made a password reset > request seems likely, but I'm not that familiar with Django authn > stuff). Anyway, if it's internal to Django, it would not consult > Mailman's configs. This recent StackOverflow seems relevant: > > > https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… > > HTH > > Steve > >

4 years, 10 months

Syncing Real Name between user account and membership

by Stephen J. Turnbull

Andreas Barth writes: > a user was mass-subscribed (with a wrong name) and now registered > and changed his name via the web interface but the list entry is > not changed. I don't recall the design discussion, but I'm pretty sure that this distinction was intentional. The idea was that people might want to have different display names associated with different addresses (eg, you probably don't want your User display name associated with an address you use on anonymized lists). I'm not sure that option has any merit in practice. @ Abhilash: Since Postorius doesn't provide a way to manage address-specific display names, we should probably have Postorius propagate display name changes. I believe that is normally what the user wants. What does everybody think?

5 years, 9 months

Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by Brett Delmage

On Thu, 26 Aug 2021, Stephen J. Turnbull wrote: > However, it turns out that bots are almost as good at solving captchas > as humans, and they can retry a lot faster. Captchas are also really > horrible from an accessibility perspective. I have to disagree. I previously put a captcha on a Joomla website which stopped 100% of all bogus account signup attempts. What was it ? "How many letters are in the word 'jazz'"? This captcha is fully accessible, too. If there's a captcha problem out there, it's because too many people just use the same old, same old - which is worth the bots cracking because it is used everywhere. Or they use google catcha crap, tracking vistors without permission and invading their privacy. Brett

5 years

Re: User management page [was: Changing subscription address]

by Stephen J. Turnbull

Abhilash Raj writes: > Typo :( Page in Postorius is what I meant to say. :D No problemo, mon, I just did it too -> > Is that necessarily required? Every user in Django has a corresponding > user in Core, but the converse isn’t true and I am not sure if that is even > required. I meant "accessed from Postorius or HyperKitty." :-) > You will be able to see: > - Does the user have a Django account? > - All Subscriptions for the User > - All addresses of the User > > You will be able to perform following actions: > - Add or remove a user’s address > - Verify or un-verify an address > - Set any address as primary for the user > - Update display name of the user > - Update address on any of the subscriptions I don't think we *need* a Django account for what I'm thinking of. I do think that creating the account on User access from Postorius might make the implementation logic simpler. > What I am on fence about: > - Provide a full blown preferences menu to the admin for that user. This > will also make the UI extremely complex to see and implement. Wait to decide on that until I have a mockup or maybe a full MR. > But, when you have an account in Django with a different email > (email2) and a different Mailman user (user2) and you add a second > email (email1) to your account and are able to prove ownership by > verifying the address, Django will ask Core to add that second address > (email1) to your Mailman user (user2) and absorb “user1”. This > process is already implemented. Good. > However, if two Django accounts are created for “user1” and “user2” > then situation becomes more tricky and currently we don’t have a > way to resolve that short of delete one of the accounts and add the > addresses to other account. Delete "that" and add its attributes to "this" is what I had in mind. Again, thanks for explaining the existing logic. Steve

5 years, 6 months

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Abhilash Raj

On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: > Abhilash Raj: > > On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: > >> Hey Abhilash, > >> > >> Thanks a lot for your work on mailman3! > >> > >> Abhilash Raj: > >>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. > >>> > >>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that > >>> I can think of is non-member management in Postorius. > >>> > >>> New releases are available on PyPI[3][4]. > >> > >> For earlier releases, you provided GnuPG signature files to > >> cryptographically verify that the release files were not tampered with. > >> > >> I couldn't find such signature files for the two latest releases. Would > >> you mind adding them? When packaging for Debian, I prefer to check the > >> GnuPG signatures before uploading new releases. Also, the signature > >> files get uploaded to the Debian archive as well so they can be checked > >> by everybody. That way we can cryptographically proof that the Debian > >> package is based on the original tarball that got packaged and signed by > >> upstream. > > > > > > Ah, sorry about that. I completely forgot about that. > > > > I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. > > Thanks a lot, that would be awesome. I'll wait for it before doing the > Debian package uploads. If it is not possible to upload signatures, I'll bump up patch versions and push out new tarballs with signatures. > > Just to let you know: we're close to soft freeze in Debian, so in order > to get those uploads into the next stable release (Buster), they'll have > to be uploaded rather soon. Can you give a rough estimate on how long do we have before the freeze? > The same holds for other pending releases of Mailman3 components: Just > in case you plan to do new upstream releases anytime soon, it's still > possible to upload them to Debian in time for Buster. I'll see if we can get other releases out too. Core doesn't yet have any backwards incompatible changes, so I might end up bumping minor version and doing a new release. Not sure much has changed in other components, but I can do a release if there are enough changes. -- thanks, Abhilash Raj (maxking)

7 years, 7 months

Mailman-users search results for query "Postorius"