Search results for "Postorius" - Mailman-users

Re: Welcome Message

by brian＠emwd.com

Abhilash Raj wrote: > If the URL for template is wrong, or Postorius is down for whatever reason, > the subscription will fail with the error that you saw before. Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That is not wrong. I am confident of that. It is back to "http://mailman-web:8000". I can successfully ping mailman-web:8000 from bash. > > I logged out of Postorious and subscribed using the > > subscribe form on > > the info page and the change to the welcome template showed up. So it > > looks like being logged in as admin while trying to subscribe someone > > was what was causing the problem. Is that a bug I discovered? > I suspect stopping-restarting and re-creating the template (idk, if you > really did that) might have something to do with it. I am not sure if this > is a bug unless you can reliably reproduce this. This error is absolutely reproducible. It even impacts other list admins who are trying to use a custom welcome message and subscribing a member while logged into Postorious. Everything else is working fine on this server and I followed your directions precisely when I set this server up. Please help. Thanks, Brian

7 years, 2 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/17/21 6:52 AM, Andreas Barth wrote: > Just from the top of my head, for example I want to differentiate > between private, member and public lists. So if a member logs in, they > see more lists than a non-member. This is currently not possible, not > too big a deal (all member lists are currently configured as private) > but of course would be nice. Also archiv access should be aligned with > these permissions. What I have done with Affinity is design everything around roles. Roles are List Owner, Moderator, and List Member. So when a registered user logs in they will see: All their lists that they have a role in and an icon assigned to each role that they play. Those lists are shown at top. Below their lists associations, public lists are shown. These they do not have a associations with for the logged in user. Here is an image in what I am referring to: https://www.mailmanhost.com/wp-content/uploads/2021/02/Screenshot_2021-02-1… Is the above image what you are thinking about? If it is then I do think that is possible with Postorius with some customization. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

1 year

Re: Add member to a list by email

by Mark Sapiro

On 11/12/24 02:00, via Mailman-users wrote: > Hello, > > I'm trying to add members by email with the following content. > > Recipient: testlist-request(a)xxxxxxxx.de > Email content: join address=max.mustermann(a)xxxxxxxx.de > > After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? You can use the email `confirm` command to confirm the request, but you need the token associated with the request to confirm it, and there is no good way to find it as it is not in the confirmation request notice sent to the list admins. To not require moderator confirmation at all, you can set the list's subscription policy. Normally, subscriptions should require confirmation by the user, a list admin or both. You can set it to require neither, but this is normally a bad idea if list addresses are accessible from outside your local network as it allows anyone to subscribe anyone else by spoofing their address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Eric Vyncke

Humm after some more investigations, it seems that my mailman3 installation via debian packages is completely mixed up :-( This would explain the issue if the REST API is using 3.2.2 code and postorius is expecting 3.3.5... drwxr-xr-x 29 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman-3.2.2.egg-info drwxr-xr-x 8 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient-3.2.2.egg-info drwxr-xr-x 4 root root 4096 Apr 13 14:29 /usr/lib/python3/dist-packages/mailman_hyperkitty drwxr-xr-x 2 root root 4096 Apr 13 14:28 /usr/lib/python3/dist-packages/mailman_hyperkitty-1.1.0.egg-info drwxr-sr-x 30 root staff 4096 Apr 13 09:32 /usr/local/lib/python3.8/dist-packages/mailman drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman-3.3.5.dist-info drwxr-sr-x 9 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient-3.3.3.dist-info drwxr-sr-x 4 root staff 4096 Apr 12 20:47 /usr/local/lib/python3.8/dist-packages/mailman_web drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman_web-0.0.5.dist-info

3 years, 2 months

Postfix-Fehler mit mailman-web

by Jens Günther

Hello, I installed mailman with Docker already a while ago, now running v0.4.5 with: Mailman Core-Version 3.3.8 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.9 Postorius Version 1.3.8 Already a while I get this type of error: 2023-08-26T08:21:59.517986+02:00 postfix/smtpd[2843414]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.575145+02:00 postfix/smtpd[2843422]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.581227+02:00 postfix/smtpd[2843422]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<root(a)$mailman.mydomain.de> to=<root@localhost> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.581548+02:00 postfix/smtpd[2843422]: disconnect from unknown[192.168.176.6] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Where - $admin(a)mydomain.de is set in MAILMAN_ADMIN_EMAIL (mm-web) and as site_owner in mailman-extra.cfg (mm-core) and as DEFAULT_FROM_EMAIL in settings_local.py (mm-web) - $mailman.mydomain.de is set in SERVE_FROM_DOMAIN (mm-web) For me it seems, that mm-web-container is trying to send mail, but don't know why and which ... I can't reproduce it. Does anybody have a clue on wehere I can have a look what happens ... and how to change it? Thank you, Jens.

2 years, 9 months

Re: Where to find disabled members?

by Mark Sapiro

On 11/4/24 19:28, Bill Oliver wrote: > > a) See who is disabled, and > b) un-disable them by hand > > or... do I just have to wait seven days for them to automatically get > un-disabled? They do not get automatically re-enabled ever the user or you has to manually re-enable delivery. For an individual user, in Postorius you can click the user in the members list and see their delivery status and reset it. To deal with the whole list membership for a list, you can do ``` $ shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` If you just want to list them ``` >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, Thank you for your thoughtful responses to my call for a removal of the core vs. Django disconnect. From your responses it appears that my suggestion my issues were caused by the Mailman Core was not based in reality. Instead, the issue is how Postorius interacts with the Core. My apologies for overreaching, as the cause of my issues is not an issue to me. Keeping Core a simple list manager is fine, if Postorius is easy to use and does the expected. As a Subscriber, you are able to do switch emails in subscriptions from your options page. The URL to which is displayed in the List's Summary page when you are logged in. Yes, it requires an approval if the list's settings are set to moderate but that is going to be fixed, see this issue[1]. It is quite simple IMO to fix this one, if someone wants to take this up. Well, it’s more than that. Based on the current setup, I have asked my subscribers who want to change their subscription addresses to: a. Create an account if you do not already have one. b. Go to the user profile page. c. Select ‘E-mail Addresses’. d. Add the new e-mail to the user profile. e. Wait for the verification notice and verify the new address. e1. If it does not show send email to hansen(a)rc.org <mailto:hansen@rc.org> to get the email verified manually. f. Sign in to the account again and to the user profile (or refresh the page if not signed out). g. Select the new address as the primary address. h. Click on ‘Manage Lists’ i. For each list you are subscribed to: i1. Select the list i2. Click ‘List Options Page.’ i3. Pull down the ’Select Email’ menu. i4 Select your new email. i5. Press ‘Change email used for subscription. i6. When the moderator contacts you, explain that you are just changing your email. i6.1. If the moderator is late, send a reminder or send email to hansen(a)rc.org <mailto:hansen@rc.org> to bypass the moderator. Most people choke on these instructions, so I have unfortunately resorted to just asking them to subscribe the new address and forget about the old. This is not good for our reputation when the old addresses start bouncing. So, in more detail: I would like to ask my subscribers who want to change their address to: a. Create an account if you did not already have one. b. Go to the user profile page. c. Select ‘E-mail Addresses’. d. Select an existing address e-mail listed the user profile. e. Press new button ‘Change address’. f. When page refreshes, enter the new e-mail address. g. Press ‘Apply.' d. Wait for the verification notice. d1. If it does not show send email to hansen(a)rc.org <mailto:hansen@rc.org> to get the email verified manually. In other words, in addition to ‘Make Primary’ and ‘Re-send Verification’ and ‘Remove’, another button says: ‘Change Address’ or’ ‘Replace Address’ or some such. This button brings up another page that looks the same, but instead of ‘Add E-mail Adress’ is says : Enter New E-mail Address’ and instead of ‘Add E-mail’ is says: ‘Apply’. Then the page refreshes back to the original page, but the new address is now replacing the old address. Optionally, it can show the old address still with a ‘pending change’ until verification. Further, when the new address is verified, all lists get updated with the new address replacing the old address and all settings associated with the old address are now associated with the new address. No moderator or admin involvement needed (other than d1). You are able to sign in via web and manage your email and subscriptions. The preferences also work exactly how you described above where the lower level override the default and/or upper level settings. To some extent that is true, Abhilash, and I appreciate that. The above (address change) is a missing piece in that picture and I look forward to seeing it added, if you have time. Yours, Allan Hansen hansen(a)rc.org > On Jun 14, 2020, at 0:19 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Mark Sapiro writes: > >> Then the people who developed the web based management UI (Postorius) >> and archive UI (HyperKitty) chose to develop those within a Django >> framework and Django has its own concept of User separate from Mailman >> Core and that is where the disconnect occurs. >> >> It's not that Mailman Core lacks what you want. It's that Django doesn't >> use it. > > I think that's mostly right, in terms of the features that users miss. > However, as far as I know, Mailman core does lack facilities for > identification, authentication, and authorization of connections to > the REST API. And that means that the front ends have to handle > this. I would guess that's why the web interfaces are built around > Django user authentication. > > I think it would be possible to have somewhat tighter integration > between the Django "web users" and the Mailman core User objects, but > it's not necessarily going to be trivial. > > I see that Abhilash is pretty optimistic, but I fear this this is > going to be a long-tail situation where we're going to be seeing core > user vs. web-gui user integration issues in 2030 (maybe by then only 1 > every 450 days ;-). I have some ideas, maybe in a couple weeks I can > sketch them out. > > Steve > _______________________________________________ > 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/

6 years

Re: Python 3.5 support?

by Abhilash Raj

On Wed, Jul 22, 2020, at 2:10 PM, Joel Lord wrote: > I'm looking through the recent changes to Core and Postorius and I keep > spotting what looks like removal of the test cases for Python 3.5. Is > the next release going to be dropping support for 3.5? Is this because > 3.5 is going EOL shortly or because there are changes in the upcoming > release that actively will not work on 3.5? I've tried to hold off on dropping support for 3.5 for as long as I can, the last release even though supported 3.5 in Core, didn't in Django apps(specifically, Hyperkitty). The main reason to drop support is that our dependencies have started dropping off support. For now, there is nothing in the Mailman source code that blocks 3.5, but that could change soon since I've really been waiting to use f'strings and other exciting features. Also, Debian and Fedora do have 3.7 or 3.8 in them at this point, so I am hoping this won't be a huge issue. > > -- > Joel Lord > _______________________________________________ > 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)

5 years, 11 months

Re: Default moderation for new members

by Mark Sapiro

On 11/14/19 7:37 AM, Seth Seeger wrote: > > I’m loving Mailman3 so far! Great work on it. Thank you. > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. In Postorius set Settings -> Message Acceptance -> "Default action to take when a member posts to the list" to Hold for moderation. This is the action which will be taken for a post from a member whose individual Moderation is List Default as it is for all new members. Then when a post from that member is held, if you click the subject in the held messages view, a dialog opens showing the message content with Accept, Reject and Discard buttons and a dropdown list you can use to set that member's Moderation to Default processing. Default processing is generally what you want as it bypasses the moderation hold but still applies other tests such as header filters, administrivia, implicit-dest, max-recipients, max-size, etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Mailman-users search results for query "Postorius"