Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Hyperkitty attachments

by Eric Broens

Mark, thanks for the prompt reply. Most of the posts on one of the mailinglists, dedicated to astrophotography, have large pictures attached. It would be good to offload these from the database to a bigger HDD for space constraints (DB is running on SSD). I rather like to keep the occasional 'regular' attachments posted on the other mailinglists in the DB. Best regards, Eric -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 10 December 2025 20:05 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty attachments On 12/10/25 1:24 AM, Eric Broens via Mailman-users wrote: > > Hyperkitty provides the possibility to store attachments on the disk > by the config parameter HYPERKITTY_ATTACHMENT_FOLDER. > > Is it possible to export attachments to disk if they are stored in the > DB, and have them linked into the archived mail? Yes, `django-admin attachments_to_file` does that. Note that depending on your installation the `django-admin` command might be named `mailmanweb` or `manage.py` or something else. > Is it possible to decide per mailinglist if attachments should be > stored in DB or on disk? No. > If not, I would like to request this feature. Can you explain your use case that makes this desirable? It seems to me that storing attachments in the DB or in the file system is a system administrative decision, and normally at least, attachments are only available to end users via the HyperKitty UI regardless of where they are stored. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ 4DBBE3B55RDUBAK26N2AR5XB6VMQMRWX/ This message sent to eric.broens(a)skynet.be

2 months, 1 week

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Michael.Sanderson＠ubc.ca

Mark, thanks for your response. It is perhaps non-fatal, but we do have a different number of templates processed. This is from a successful run with django-allauth==0.57.0. Note the different count of templates from the “failed” processing and this one. (venv) [mailman@rubytears ~]$ mailman-web compress Compressing... done Compressed 2 block(s) from 124 template(s) for 1 context(s). Is this compression of web content that will served to clients? Compressed data would be preferred over non-compressed to decrease data volume, but non-compressed will be served if compressed isn’t available? Michael Sanderson > On Nov 7, 2023, at 7:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > [CAUTION: Non-UBC Email] > > On 11/7/23 16:26, Michael.Sanderson(a)ubc.ca wrote: >> Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get >> (venv) $ mailman-web compress >> Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html >> done >> Compressed 2 block(s) from 78 template(s) for 1 context(s). > > > I don't think this is fatal, but I have reported it at https://github.com/pennersr/django-allauth/issues/3513 > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to michael.sanderson(a)ubc.ca

2 years, 3 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Abhilash Raj

On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: > On 09/21/2017 01:29 PM, Andrew Hodder wrote: > > > > I keep getting around this by creating symlinks to the pid file and then > > the stop works, but it's getting silly. It seems like mailman just assumes > > CWD + /var/ + master.pid must be the location. Once I realized this, I > > found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since > > it'd then add /var/master.pid). But that seems a little nonsensical. > > > That is the normal expected behavior if devmode is enabled. Check your > configs for this. I don't think `devmode` has anything to do with this, it only disables sending out emails by accident and routes all emails to a pre-defined address. Haven't looked at the relevant portion of the source so I might be wrong. In the absence of any configuration file in pre-defined locations[1], Core will always generate a `var/` directory under $CWD with basic configuration and use it to track a running mailman instance (logs, db, pid file etc). Ideally, you should place your configuration file at one of the locations that it looks and specify a `[paths.custom]` directive in there to make sure it knows where to put everything. See [2] for more details. [1]: http://docs.mailman3.org/en/latest/config-core.html#configuring-mailman-core [2]: http://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-… > -- > 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/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 5 months

[MM3-users] Re: templates

by Christian

In March when I started troubleshooting my lists, you stated: "Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read?" There are no other templates listed in either Postorius nor in Mailman's var/templates (as I stated, I do not even lave a 'lists' subdirectory under Mailman's var/templates). My subscribers are not receiving message distributions from my lists, even while some of them are listed in the archives. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 10:58 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 10:33, Christian via Mailman-users wrote: > I'm having issues with my lists. For each list I have created a > template [ list:user:action:subscribe ]which has a prospective > subscriber have to consent to list rules before they are subscribed. > This template I created is listed in Postorius for each list. I have > noticed that there are no other templates listed in Postorius. Furthermore, there is no 'lists' > subdirectory under Mailman's var/templates/. When you set a template in Postorius it saves it in the postorius_emailtemplate table in the database and tells Mailman core to get the template from Postorius via a URI to a Postorius API. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ This message sent to csa(a)web-analysts.net

2 years, 9 months

[MM3-users] Re: new list not working

by Christian

Mail.log Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian(a)naturalintelligence.us> to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 2:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 14:32, Christian via Mailman-users wrote: > When I ran > > mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org > > I did receive a list of subscribers for the new list I created, not > just the owner or moderator. > > Upon closer examination, another of my longtime working lists is also > not working. Similar behavior as the new list I created in that I see > the message has been archived, but not distributed to the subscribers. What do your MTA logs show? -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ EOYMZXS4WPQGLDLVVWOGC67WY576665F/ This message sent to csa(a)web-analysts.net

2 years, 11 months

[MM3-users] Re: no access to Postorius web pages after upgrade

by Mark Sapiro

On 10/22/23 10:53, David Newman wrote: > Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, > Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go > OK. Mailman3 lists work as expected, and admins can log in via Django. > > However, any attempt to reach lists, domains, users, etc. now returns a > 404 Not Found error. All the Postorius stuff worked as expected before > the upgrade. > > In the nginx server logs, any Hyperkitty and Postorius URLs are now > appended to /opt/www/roundcubemail, which is this web server's root > directory but not the root for Mailman3 (I run Roundcubemail and MM3 on > the same server; don't judge me :-). > > Here is the nginx error, with obfuscation of client and server info: > > 2023/10/22 10:43:24 [error] 2264140#2264140: *135 > "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No > such file or directory), client: 1.2.3.4, server: lists.example.com, > request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", > referrer: "https://lists.example.com/mailman3/listinfo" Here you are trying to get https://lists.example.com/postorius/domains/, but (see below) > And here are the relevant bits of the Nginx config. Again, this worked > before the upgrade. > > server { > > listen 443 ssl http2; > server_name lists.example.com; > root /opt/www/roundcubemail; > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /mailman/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } Above you have defined proxying for the paths beginning with /mailman3/, /archives/, /mailman/ and others, but not /postorius/ or /hyperkitty/. Note that /mailman/ will get to Django, but probably won't work unless you have something like ``` path('mailman3/', include('postorius.urls')), ``` or possibly ``` re_path('mailman3?/', include('postorius.urls')), ``` in your urls.py (default mailman_web/urls.py) > Also, I'm not sure if it's relevant but after upgrading, the migrate > command throws a warning like this: > > (venv) mailman@mail10:~$ mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you > don't care about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't > care about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > No migrations to apply. This is an issue with MariaDB and MySQL. It can result in more processing because of the lack of an index or possibly a database operation succeeding that should fail because of the unsupported constraint, but these shouldn't affect operation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: spf/dkim/dmarc

by Christian

Using https://www.spf-record.com/ I have checked my SPF records which are reported as 'SPF check passed'. My DKIM also passes various test suites. Yet, Google is still rejecting mailman messages to any and all gmail users. I have even filled out their short form for delisting at https://support.google.com/mail/contact/bulk_send_new all to no avail. Example of block logfile message: May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: to=<billb6951(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: [192.46.218.224]. To best protect our users from spam and 550-5.7.26 phishing, the message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - gsmtp (in reply to end of DATA command)) Could the hard fail policy be implicated in the gmail rejection? Other than readdressing my server, is there anything else I can do? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, May 17, 2023 11:50 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc On 5/17/23 07:20, Odhiambo Washington wrote: > > You can only have 1 SPF record. For a domain. But as Jeremy Stanley noted, mail.ccalternatives.org and lists.ccalternatives.org are different domains and it is fine for each to have its own spf record. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ WAUVS6WWYOYQBJGIDP3HK6L3NHM4RGHF/ This message sent to csa(a)web-analysts.net

2 years, 9 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

You're welcome. Thank you for all your hard work making Mailman 3 happen at all! I think django_allauth integration is again stable, but for now I'm pinning 0.58.2 + this patch. I'll test again once there is another release notification, but since I rebuild by container image every 2-3 weeks I am getting exhausted by surprises... --Jered ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/7/23 14:33, Jered Floyd wrote: >> >> FYI, The django-allauth author has proposed fixing both of these with an even >> simpler change, which is now upstream and queued for a future release. >> >> --Jered > > > Thank you again for your work on this. I can confirm that the patch > below fixes my issue with > https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. > > >> --- a/allauth/socialaccount/adapter.py >> +++ b/allauth/socialaccount/adapter.py >> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): >> provider_to_apps = {} >> >> # First, populate it with the DB backed apps. >> - db_apps = SocialApp.objects.on_site(request) >> + if request: >> + db_apps = SocialApp.objects.on_site(request) >> + else: >> + db_apps = SocialApp.objects.all() >> if provider: >> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) >> if client_id: > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 2 months

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Abhilash Raj

On Tue, Oct 20, 2020, at 12:27 PM, Mark Sapiro wrote: > On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > > I would like to populate list members via the Mailman 3 sync_members script. > > > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? > > > I'm not sure what version of Mailman core is in the Docker containers. > According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman > core is docker version 1.1.1 released Aug 9 2017 which is about the time > of MM Core 3.1.0 which is quite old and has neither a `mailman > syncmembers` (introduced in core 3.3.2) command nor the older `mailman > members --sync` option (introduced in core 3.3.1). There are `rolling > releases` <https://asynchronous.in/docker-mailman/#rolling-releases> > which should have these. NEWS file is very outdated, I should remove it. The containers have latest released version if you are using the 0.3 tags and as Mark mentioned, `mailman members --sync` option should work. > > > > Searching this list I found a reasonable approach: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Is there a different/preferred solution? > > > The script at > <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> > seems fine. The alternative is to update your Docker container to one > including the appropriate `mailman` sub-command. > > -- > 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)

5 years, 4 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 1:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On Jun 9, 2020, at 11:34 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>>> ./mm3-admin: line 6: 702058 Killed django-admin $@ >>>> >>>> Now what? >>> >>> >>> Run it as user `list`. >> >> >> Same. > > > It appears that the reference to line 6 is line 6 of your mm3-admin file > which is the `django-admin $@` command. So that command is being killed > by the OS for some reason, probably out of memory. > > Try this instead. > > import pytz > import datetime > start = datetime.datetime(2020, 1, 1).replace(tzinfo=pytz.UTC) > end = datetime.datetime(2020, 2, 1).replace(tzinfo=pytz.UTC) > # These are examples. The args are year, month, day. > # Pick dates for start and end that overlap the start of this issue. > from hyperkitty.models import Email > emails = Email.objects.filter(date__range=(start,end)) > for email in emails: > if email.content.find('\u200b'*5) >= 0: > print('Found in ml {}, hash {}'.format( > email.mailinglist.name, > email.message_id_hash)) > > This will make a much smaller query set than all the emails and should work. I was just writing another email - I had a suspicion on this and I was right: this is the Linux OOM killer in action. Jun 9 13:15:32 mail kernel: [1051406.859205] Out of memory: Killed process 712833 (python3) total-vm:2351156kB, anon-rss:2274112kB, file-rss:2236kB, shmem-rss:4kB, UID:38 pgtables:4616kB oom_score_adj:0 Jun 9 13:15:32 mail kernel: [1051407.042975] oom_reaper: reaped process 712833 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:4kB I set up a quick swapfile (there are 581,000 emails in this archive) and it came back with some hashes. I am tracking them down now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 8 months

Search results for query "sapiro"