Search results for "Postorius" - Mailman-users

Re: Link to account

by Mark Sapiro

On 4/11/23 12:04, Lars Bjørndal wrote: > Thanks a lot. Maybe I've done a mistake, it doesn.t work. > > At the bottom of /etc/mailman3/settings.py I have: > > ROOT_URLCONF = 'urls' > > `cat /etc/mailman3/urls.py` > > [...] > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), > ] > > In Apache config for the domain, I now have: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" > ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" > ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" > ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" > ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" > </IfModule> > > Restarted mailmanweb, httpd and mailman3. > > If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. > > So what's wrong, do you think? You followed https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… literally. The literal instructions where to access everything via URLs like https://mydomain.org/lists/.... If you were to replace `lists` with `mailman3` everywhere in the abpve, you would then access HyperKitty via a URL like https://list.punktskriftutvalget.no/mailman3/archives/ and Postorius via https://list.punktskriftutvalget.no/mailman3/mailman3/ If that's not what you want, it's more complicated and some things might not be possible. What exactly do you want for access to Postorius, HyperKitty, user accounts, user profiles and the Django admin UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: Installing mailman 3

by Rafael Mora

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty I don't understand... this is the trace when I click Login from Postorius to HyperKitty [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 What should I check? El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

Re: Introducing Mailman Web project

by Abhilash Raj

On Mon, Mar 25, 2019, at 5:25 PM, Ralph Seichter wrote: > * Abhilash Raj: > > > For this reason, I decided to combine all the projects together into > > a Django project which can be easily installed and run: > > > > $ pip install mailman-web > > # Export Settings for commands to just work. > > $ export DJANGO_SETTINGS=mailman_web.settings > > $ django-admin migrate > > $ django-admin runserver > > I've tried things a bit differently so I can use the latest version from > GitLab, and Things Go Boom(TM): > > $ python3.7 -m venv venv > $ . venv/bin/activate > $ pip install -U pip setuptools > $ git clone https://gitlab.com/mailman/mailman-web.git > $ cd mailman-web/ > $ cp docs/mailman-web-example.toml mailman-web.toml > $ pip install . > $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate > Traceback (most recent call last): > [...] > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/views/user.py", line 34, in <module> > from postorius.models import List, MailmanUser > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/models.py", line 223, in <module> > class EmailTemplate(models.Model): > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/django/db/models/base.py", line 95, in __new__ > "INSTALLED_APPS." % (module, name) > RuntimeError: Model class postorius.models.EmailTemplate doesn't > declare an explicit app_label > and isn't in an application in INSTALLED_APPS. > > Did I miss something? So, that's my fault ;-) The example configuration is actually not a working example, but only used for demonstrating how to write a TOML config. But I see that it actually should be a valid configuration, I'll open an issue and fix that. Can you instead remove mailman-web.toml and then again try: $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate This should mostly probably work :) -- thanks, Abhilash Raj (maxking)

7 years, 1 month

Re: How to subscribe members without sending unsubscribe message

by Stephen J. Turnbull

Flo via Mailman-users writes: > Thank you. I don't why I don't find these things in Postorius > easily? There's a common saying among user interface developers that "'intuitive' just means 'what you're used to'". It's not a "you" problem, it's that people have different notions of where such things "should be found" based on their unique experiences. In this case, the "mass subscription" tool has controls for all the things you might care about, including the welcome message. The "mass removal" tool does not, but once you've used "mass subscription", a control for the goodbye message is a reasonable expectation. I think we should add it: https://gitlab.com/mailman/postorius/-/issues/638 -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 3 weeks

Re: lmtp runner not starting

by Odhiambo Washington

On Sat, Apr 1, 2023 at 7:55 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > This morning I upgraded the mailman3 installation of the less traffic > server I have: a bunch of lists, with very slow traffic. > > (see pip lists at the end) > > I sent test mails to a pair of lists, but none were distributed or > archived. postorius seemed working well. First I thought it was some I > did wrong in the upgrade procedure, but then I realized the lmtp runner > was not running. > > I followed old messages about similar problem (many of them in this same > mailman-users list), but I cannot see what is wrong. There is no error > logged in mailman.log. the mailman.cfg of the lmtp is the default (and > was working at least a pair of weeks ago) > > *-*-*-*-*-*-*-*-* from mailman.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: localhost > smtp_port: 25 > configuration: python:mailman.config.postfix > > *-*-*-*-*-*-*-*-* > > There is no one listening in port 8024. I tried changing the port (to > 9024), with the same results. > > postfix seems working well. I's just there is nothing listening on port > 8024 because lmtp runner is not running :) > > (from maillog): > > connect to 127.0.0.1[127.0.0.1]:8024: Connection refused > > (another simple test) > > root@www:/usr/local/mailman3 # telnet localhost 8024 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > > I'm running out of ideas. Any clue to somewhere to dig in? > > > *-*-*-*-*-*-*-*-*-*-* runners started > > Apr 01 17:24:40 2023 (4681) out runner started. > Apr 01 17:24:40 2023 (4680) virgin runner started. > Apr 01 17:24:41 2023 (4679) command runner started. > Apr 01 17:24:42 2023 (4688) retry runner started. > Apr 01 17:24:43 2023 (4686) in runner started. > Apr 01 17:24:44 2023 (4683) digest runner started. > Apr 01 17:24:44 2023 (4684) nntp runner started. > Apr 01 17:24:45 2023 (4682) archive runner started. > Apr 01 17:24:46 2023 (4685) bounces runner started. > Apr 01 17:24:47 2023 (4687) task runner started. > Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries > Apr 01 17:24:48 2023 (4678) pipeline runner started. > Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests > Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages > Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries > > *-*-*-*-*-*-*-*-*-* pip lists with versions installed > > root@www:/usr/local/mailman3 # pip list | grep mailman > django-mailman3 1.3.9 > mailman 3.3.8 > mailman-hyperkitty 1.2.1 > mailmanclient 3.3.5 > > root@www:/usr/local/mailman3 # pip list | grep django > django-allauth 0.51.0 > django-appconf 1.0.5 > django-compressor 4.0 > django-extensions 3.2.0 > django-gravatar2 1.4.4 > django-haystack 3.2.1 > django-mailman3 1.3.9 > django-picklefield 3.1 > django-q 1.3.9 > djangorestframework 3.13.1 > > root@www:/usr/local/mailman3 # pip list | grep postorius > postorius 1.3.8 > > Bumping either mailman|lmtp loglevel to DEBUG might help find out. [logging.lmtp] level: debug And I think you can debug everything with (untested): [logging.here] level: debug And restart mailman. Maybe?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

Re: Accept these non-members

by Lars Bjørndal

Again, thank you for your reply! You wrote: > On 3/6/26 12:52, Lars Bjørndal wrote: [...] > > > > I have an announce only Mailman3 list. When I log into the web interface > > > > as an admin user, and go to the specified list, and choose Settings, I find > > > > the Message Acceptance tab. There, I find the edit field Accept these > > > > non-members. But this field is empty, although I know that some people > > > > have permissions and are able to post to this list. How can I find the > > > > list of these non-members and add more people or delete someone? [...] > > > These are nonmembers whose moderation action is accept or defer. If your > > > Postorius is >= 1.3.6, and the number of nonmembers is manageable you can > > > just view the nonmembers list in Postorius and see their moderation action. [...] > > > Otherwise a `mailman shell` interaction like > > > ``` > > > $ mailman shell -l list.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.example.com mailing list > > > > > > for nm in m.nonmembers.members: > > > ... if nm.moderation_action in (Action.accept, Action.defer): > > > ... print(f'{nm} {nm.moderation_action}') > > > ... > > > > > > > > > ``` > > > will print those nonmembers with Action.accept or Action.defer. All addresses, both addresses that I know has sent messages to the list and others, are marked as MemberRole.nonmember> Action.defer When I view non-members in postorius, I get some differences: Some ar marked: Regular List default, and others Regular Default processing. The list is imported from Mm 2.1 a long time ago. I don't know if that matters. > > What's the difference between Action.accept and Action.defer? > > > Action.accept accepts the message immediately with no further checks. > Action.defer passes the membership checks but still goes on to check other > things like > > mis-addressed email commands > messages with implicit destination > messages with too many explicit recipients > messages that are bigger than a specified maximum > messages with no, or empty, Subject headers > messages with digest Subject or boilerplate quote > messages matching a bounce_matching_header line Hm, this is a mystery to me. Is there othere places I can search for addresses that are aloud to send to the list? Thanks, Lars

2 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 12:18 -0700 on May 12, 2016: > On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. > > > This format vs. plain text digests was a user option in Mailman 2. > > > > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. > > > The core still supports the same plain text and MIME format digests and > the same individual subscriber and per-list default formats as did > Mailman 2. The issue is none of these things are exposed in Postorius. > > If you subscribe to digests on this list, you will receive the > 'encapsulated' MIME format because the lists mime_is_default_digest > setting is True, but currently that has to be set through the > bin/mailman shell tool. > > > > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? Thanks for the info - and Barry's reply as well. I understand that MIME digests are supported in Mailman 3 - that's what I'm using (and thanks, Barry, for the info that Summary Digests is the same right now). My quibble is that the multipart/digest encapsulation level is gone. Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > The MIME format of MIME digests should roughly be: > > multipart/mixed > text/plain (the digest heading) > text/plain (the TOC) > message/rfc822 > message-1 > message/rfc822 > message-2 > ... > text/plain (footer) But mm 2 had: multipart/mixed text/plain (the digest heading) text/plain (the TOC) multipart/digest <--- this is the part that's gone in mm3 message/rfc822 message-1 message/rfc822 message-2 ... text/plain (footer) So was that removal intentional, a bug or ?? Maybe you're saying there is definitely an unexposed (in Postorius) knob for that in mm3. > > It is the intent that Postorius will eventually expose all these > settings. We're not there yet. At present you could possibly do this by > interacting with mailmanclient, although I'm not certain the settings > are exposed there. You can do it via bin/mailman shell if you have > access and know what you're doing (see > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) > > If you file an issue at > <https://gitlab.com/mailman/postorius/issues/new>, it might help > expedite this. Okay.

9 years, 11 months

Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > Then if collapse_alternatives is True (settable here or in Postorius), > any multipart/alternative parts will by replaced by the first, > presumably text/plain, sub-part. > > Finally, if convert_html_to_plaintext is True (settable here or in > Postorius), any remaining text/html parts will be converted to plain > text by lynx or whatever is configured as html_to_plain_text_command in > mailman.cfg. > This will ensure that filter_action is applied only to those messages > which have no text/plain or text/html parts. Great, that helped for the content. Thanks. Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. If that doesn't work, we have talked about deleting the list and add it from scratch. Is the any prolems (with left overs from the old imported list), when deleting the list from Postorius? /Henrik Rasmussen

6 years, 11 months

Re: Email discard

by Mark Sapiro

On 4/1/23 08:33, qro(a)xs4all.nl wrote: > Hi > > I have a good working mailman3 list server with 3 mailing lists. > 2 of them work OK, but 1 has a little odd behaiver > > If a non member send an email it will discard while the setting in /postorius/lists/list.name.nl/settings/message_acceptance shows Hold for moderation > > A snip from var/mailman3/mailman.log > Apr 01 10:48:32 2023 (49342) DISCARD: <4359976d-d4bb-9b30-0901-c842aa1fecb3(a)xs4all.nl>; ['The message is not from a list member'] > > Changing and saving a other choice makes no difference. > > Where can I look more to find a solution? (in mysql?) In Postorius, find the nonmember in the Users->Non-Members list. Does that nonmember have a moderation action of discard. Also, what's in Postorius->Settings->Message Acceptance->Discard these non-members? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: Hiding the "subscribe without creating an account"

by Mark Sapiro

On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: > > Is there a configuration option that does this, or was it a custom change made in > the templates? Was the change made to reduce fake registrations? Did it work? It was added in Postorius 1.3.9. See the UI section at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 Yes, the change was made in an attempt to reduce fake registrations. We haven't really studied it's effectiveness. It seems to help somewhat, but it also seems that bots may already have a template to POST so removing it from the UI is not a complete solution. There is also a lot of email to innocent third parties and non-existent addresses from attempts to register them for an account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Mailman-users search results for query "Postorius"