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

[MM3-users] Re: /hyperkitty/list/ shows "example.com" / mailman3 archives not updated

by Mark Sapiro

On 5/17/20 6:05 AM, patrick-mailinglists(a)whonix.org wrote: > /hyperkitty/list/ shows "example.com". Not the actual domain name that I configured. How can I fix this? Ensure that your actual domain is listed in the Django admin interface under Sites. Then ensure that your SITE_ID setting in your Django settings is correct. This is tricky because the site id might not be what you expect. You have to look in your database at the django_site table[1]. This table contains one row per site with columns id, domain and name, and the id values don't necessarily match what you'd think from looking at Sites in the Django admin interface. > I would not mind too much about hyperkitty showing "example.com". But the more important issue is that mailman3 archives are not updated. Therefore I guess it's a symptom of a more important issue. I doubt that these things are related. > E-mails to the list are delivered to e-mail subscribers, though. Seems only the web part is broken. What's in Mailman's log (var/logs/mailman.log) and are the messages all queued in var/archivers/hyperkitty/spool? If so, mailman-hyperkitty can't communicate with hyperkitty. Ensure that the settings in mailman-hyperkitty.cfg are correct. base_url: needs to be a URL that can access hyperkitty and api_key needs to match the MAILMAN_ARCHIVER_KEY setting in your Django settings except that it's quoted in the Django settings and not in mailman-hyperkitty.cfg. > Using Debian buster mailman3 packages. In configuration folder /etc/mailman3 I cannot find any textual string saying "example.com". > (`grep -r -i example /etc/mailman3`) > Therefore I don't know where mailman3 gets "example.com" from. Please see <https://wiki.list.org/x/12812344> [1] other ways to get this are a) increment the SITE_ID setting until you find the one that works or b) in a django admin shell do from django.contrib.sites.models import Site for site in Site.objects.all(): print('id: {}, name: {}, domain: {}'.format( site.id, site.name, site.domain)) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128)

by Mark Sapiro

On 10/13/20 1:11 AM, r.woithe(a)callassoftware.com wrote: > Hello, > System: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.5 (default, Jul 28 2020, 12:59:40) [GCC 9.3.0] > > all this runs on Ubuntu 20.04. > Our mailman3-web.log file is full of this error.Traceback: > > 00:00:17 [Q] ERROR reincarnated pusher Process-1:731365 after sudden death > 00:00:17 [Q] INFO Process-1:731366 pushing tasks at 3061233 > Process Process-1:731366: > Traceback (most recent call last): > File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap > self.run() > File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run > self._target(*self._args, **self._kwargs) > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 300, in pusher > task = SignedPackage.loads(task[1]) > File "/usr/lib/python3/dist-packages/django_q/signing.py", line 28, in loads > return signing.loads(obj, > File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 38, in loads > return serializer().loads(data) > File "/usr/lib/python3/dist-packages/django_q/signing.py", line 44, in loads > return pickle.loads(data) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 1: ordinal not in range(128) > > Is there a patch or workaround for this error or we are the one and only? This is a qcluster issue. Without knowing what it is that qcluster is looking at that is causing this, I have no idea what the problem is. You could try disabling qcluster. You probably have something like ``` Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } ``` in settings.py. You can comment out or remove this or I think you can just put `del Q_CLUSTER` in settings_local.py. Possibly this will avoid the error or move it somewhere else where we can get more information. Possibly you can also get more information on the error by implementing a simple error reporter for qcluster. See <https://django-q.readthedocs.io/en/latest/errors.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

YEEEES! At last!!! I can see the web UI. Now I´m getting this message in the web UI: Something went wrong Mailman REST API not available. Please start Mailman core. Where do I configure the REST API ????? Thank you El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > 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, 1 month

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Franklin Weng

Yes, it is checked. Mark Sapiro <mark(a)msapiro.net> 於 2019年10月30日週三 11:19 寫道： > I haven't read this thread in detail. I've been off line for 3 days due > to a Public Safety Power Shutoff, but my first question is if you go the > the Pustorius web UI for the list(s) and look at Settings -> Archiving > -> Active archivers, is hyperkitty checked? > > -- > 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/ >

5 years, 10 months

[MM3-users] Re: Shorted Subjects in Mailman

by Mark Sapiro

On 7/26/22 03:44, Stephan Krinetzki wrote: > Victoriano Giralt wrote: >> On mar, 2022-07-26 at 10:09 +0000, Stephan Krinetzki wrote: >>> Hi, >>> Hi, >>> i tried now with a Postfix 3.x -> Mailman >>> Postfix has en extremely useful setting called debug_peer_list where >> you can list addresses of machines whose messages you are interested in >> and the level of detail can be set with debug_peer_level. this will >> result on very detailed logging of the SMTP conversation. >> But, before resorting to this very invasive method, I'd put messages on >> the HOLD queue and inspect them with postcat, before releasing them to >> be passed to Mailman. this way, you will be able to see if the subjects >> are cur "before" reaching Mailman. >>> Original to Mailman: https://pastebin.com/c4BHeEkJ >>> Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- >> LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= >>> After Recieving: https://pastebin.com/JG0NKbjq >>> Subject: =?utf-8?q?=5BJaninsliste=5D_=5BSAV- >> LINUX=5D_Notice_from_Sophos_Anti-Virus_on_server=2Eexample=2Ecom?= >> Both of then show the same Subject: header. > > In https://pastebin.com/c4BHeEkJ, Line 79+80 it says > > `Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on server.example.com > [DEMO1]` In the original message you posted at https://pastebin.com/c4BHeEkJ, the continuation line `[DEMO1]` is not indented and is thus not a continuation of the Subject: header but is a separate line. It appears that several other continuation lines are also not indented, so I can't tell what the original message to Mailman actually looked like. However, I did a test injecting directly to Mailman a message with ``` Subject: [SAV-LINUX] Notice from Sophos_Anti-Virus on server.example.com [DEMO1] ``` on a German language test list with subject prefix [Janinsliste] and I get the same result, I.e. the RFC 2047 encoded ``` Subject: =?utf-8?q?=5BJaninsliste=5D=5BSAV-LINUX=5D_Notice_from_Sophos=5FAnti-Virus_on_server=2Eexample=2Ecom?= ``` so this is definitely a Mailman bug (or a bug in the underlying Python email package. Thank you for the report. I have created https://gitlab.com/mailman/mailman/-/issues/1021 for this issue. -- 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

[MM3-users] Re: Newbie hyperkitty question

by Mark Sapiro

On 1/11/22 8:27 AM, Stephen Daniel wrote: > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. In Postorius, in the list's `info` view can you click the Archives button and see archived messages? That's HyperKitty. If the messages aren't there with the hyperkitty archiving option enabled, check `mailman.log` for why. Also do messages from the list have an Archived-At: header? > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. No this says the prototype archiver is working. It says nothing about Hyperkitty. > So, this opens up a raft of questions on hyperkitty: David Newman has answered some of this, but ... > - How do I tell if hyperkitty is actually running? It doesn't actually run. it is a Django web UI and a web API that serves things on request. > - Does hyperkitty have a web-UI for admins or users? How would I access > it? See above. > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? No, not really. > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? Messages are kept forever unless you do something to delete them. HyperKitty's messages are stored in the database configured in the DATABASES setting in your Django settings. How you backup the database depends on the database manager. You already found the prototype archiver's messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 1/6/22 3:25 PM, gordon(a)dickens.com wrote: > > How do I uninstall the Debian version and then reinstall with the venv and web instructions so that all of my mailing lists and configuration data are preserved? I may elect to go that route if I can preserve all of my mailing list and data and you think that would be a quicker route to a solution. Is there a simple way to do this? It's probably not "simple", but here's how I would do it. First, follow https://docs.mailman3.org/en/latest/install/virtualenv.html to install Mailman in a virtualenv. You can use `list` as the Mailman user rather than `mailman` if you like. The doc uses Postgreql as the database manager, but you want to use whatever the current DBM is because you will want to use the existing database which is where all the list configuration, membership and archives are. One gotcha here is the instructions tell you to create /etc/mailman3/mailman.cfg and the Debian package already puts its mailman.cfg there. The Debian mailman.cfg may actually be appropriate although it puts things in different places, e.g. /var/lib/mailman3 instead of /opt/mailman/mm/var. The Debian package puts its Django settings in /etc/mailman3/mailman-web.py and the virtualenv doc puts them in /etc/mailman3/settings.py. You need to reconcile the differences keeping in mind that the recommended settings.py imports most settings from the mailman-web project and only contains things you want to change locally. The basic idea is you want the virtualenv install to use the existing databases and /var/lib/mailman3 stuff so you preserve all your existing list stuff. It probably involves several gotchas that might be difficult to resolve if you are less than intimate with the details of a Mailman installation. I actually spun up a small Ubuntu 20.04 droplet and installed the mailman3-full package to see what things looked like, but I destroyed it without examining the contents of some of the files or I might know more. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Hyperkitty using wrong email address in archive view

by Mark Sapiro

On 5/16/23 01:42, peter(a)chubb.wattle.id.au wrote: > Hi Folks, > I notice that for people with multiple email addresses, the email > address that appears as the 'FROM' address in the hyperkitty > archive is not the primary address, nor is it the address that the > email actually came from, but the address that was created first. > (Hyperkitty version 1.3.7) Where exactly do you see this address? Normally, if the From: header of the mail contains a display name, it is that name which is displayed as the author of the email. The display is only an address if the From: header of the mail had no display name or if it had a display name which was an email address as in From: user(a)example.com <user(a)example.com> > When I click on that from address in the archive view, I see all > the email addresses for the user -- these do not match up with the > ones in the django admin screen from .../admin/account/emailaddress/ Because they are not the Django user's email addresses, they are the Mailman user's email addresses. > When I see 'User profile for Fred Frog' > it shows obsolete addresses (not subscribed, not in the Django > profile for the user). Again these are the Mailman user's addresses. The Mailman users are listed at the Users tab on the top Postorius nav bar. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? The user can do it at https://example.com/accounts/email/ but the admin can't do it from Postorius. A site admin can do it via REST or `mailman shell`. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? Again, where do you see this? You may want to download that thread and see what that shows as the From: header of the email. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/22/23 04:47, Andrew Hodgson wrote: > > Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. > > However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. There is only one DSN that mentions several users (I haven't received that, but I don't need it). Mailman will process that as a bounce for each mentioned user. Now, when that results in delivery being disabled for the users, the admin receives a separate notice for each user. Each notice should have the DSN attached, but the issue is when the first notice is processed, the saved DSN is deleted from the message store, so it isn't available for the subsequent notices. This is now https://gitlab.com/mailman/mailman/-/issues/1101 > The message returned from Google was: > > user(a)gmail.com > 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' > 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' First, these appear to be due to some issue between the Server at PAVPR08MB9257.eurprd08.prod.outlook.com and the Server at gmail-smtp-in.l.google.com rather than gmail actually rejecting the message. Second, these are delayed bounces. PAVPR08MB9257.eurprd08.prod.outlook.com has been retrying the message for some time (perhaps as much as 5 days) and has finally given up and returned the bounce. Thus, you will probably see more of these from older messages as they finally bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Recently active discussions - Hyperkitty

by Mark Sapiro

On 5/31/24 13:06, Sam Darwin wrote: >> Are there messages with Date: headers in the last month? > > Well, there are definitely many messages from the last month. > > Hyperkitty, for each message, shows in the upper-right hand corner of the message "30 May 2024" "29 May 2024" "20 May 2024 3:00pm" and so on. Each message has a date shown. Those dates should be the ones used for recent threads. > "Threads by Month" is populated with messages from the last month. > "All Threads" is populated with messages from the last month. > However, "Recently Active Discussions" is empty. > > That is not conclusive regarding "Date: headers". But wouldn't "Threads by Month" use the same date information? Yes. Perhaps the hyperkitty recent_threads_cache job can fix this, but it is one of the jobs run daily by cron (assuming cron is running them) so after 24 hours, it should have run. > By the way, during the import "Message 04b901d993ca$d6cf3180$846d9480$(a)gmail.com failed to import, skipping" and "psycopg2.OperationalError: SSL connection has been closed unexpectedly". I'm guessing that was one message reported on two lines with the psycopg2... line indented 4 spaces. > However, the import continues past those errors. For example: Yes, that's a report that the one message with Message-ID: <04b901d993ca$d6cf3180$846d9480$(a)gmail.com> failed to import, but it doesn't affect the rest of the import. > It all eventually completes with exit code 0. Generally, successful. So it's unclear if a skipped message is the cause. It isn't, but the "psycopg2.OperationalError: SSL connection has been closed unexpectedly" message is curious. I would find that message in the mbox file and try to run the import again with a mbox containing just the one message with a --since option early enough to not skip it and also the --no-sync-mailman option to avoid that time consuming process which only will update HyperKitty's Sender record for this sender with Mailman core's user_id if it hasn't already been done for this sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Search results for query "sapiro"