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

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Thanks for the hints. It looks to be a file permission problem. I am not sure what the right persommions should be inside he container. Is there a command for checking file permissions, like the Mailman 2's command check_perms? I couldn't file one. Mark Sapiro wrote: > Something is going wrong in this process in DigestRunner. Is > DigestRunner running? Yes: 43 mailman 2:05 /usr/local/bin/python /usr/local/bin/runner -C /etc/mailman.cfg --runner=digest:0:1 > Is there anything in Mailman's digest or shunt > queues? As of /opt/mailman/core/var/queue/digest/ and /opt/mailman/core/var/queue/shunt/ no, but there is three files in /opt/mailman/core/var/queue/bad/ -rw-rw---- 1 root root 398 Oct 10 14:42 1539175326.8246331+4b7e80db0d22f01c2d4363e323320fcd34560657.psv -rw-rw---- 1 root root 398 Oct 11 12:11 1539252672.3947155+ae2631d9f6514d74c77a38f09f821ee71515f9d9.psv -rw-rw---- 1 root root 398 Oct 11 12:24 1539253469.5928977+15b0842462ddd3abcac8d688e5bbb195b07409bc.psv They seems to be binary, buy strings reveal: mailman.email.message Message policy email._policybase Compat32 _headers _unixfrom _payload _charset preamble epilogue defects _default_type text/plain listid test.lists.example.com digest_path =/opt/mailman/var/lists/test.lists.example.com/digest.1.9.mmdf volume digest_number version _parsemsg If that reveals anything. > Is there anything logged in Mailman's 'mailman' log? It seem to say PermissionError: [Errno 13] Permission denied, but inside the container, the directoried in /opt/mailman/var/queue is drwxrwx--- 2 mailman root 4096 Mar 14 2018 archive drwxrwx--- 2 mailman root 4096 Oct 12 10:14 bad drwxrwx--- 2 mailman root 4096 Mar 14 2018 bounces drwxrwx--- 2 mailman root 4096 Mar 14 2018 command drwxrwx--- 2 mailman root 4096 Oct 11 10:24 digest drwxrwx--- 2 mailman root 4096 Oct 12 10:07 in drwxrwx--- 2 mailman root 4096 Mar 14 2018 nntp drwxrwx--- 2 mailman root 4096 Oct 12 10:07 out drwxrwx--- 2 mailman root 4096 Oct 12 10:07 pipeline drwxrwx--- 2 mailman root 4096 Mar 26 2018 retry drwxrwx--- 2 mailman root 4096 Mar 14 2018 shunt drwxrwx--- 2 mailman root 4096 Oct 10 12:32 virgin Henrik Rasmussen

7 years

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

Running into some nasty issues. I have a structure like this, installed as a package in the workspace once installed by pip in the venv: mailman_customizations/ __init__.py hooks.py <-- plugin definition in here as MailmanCustomizations for class name handlers/ __init__.py handlers.py <-- custom handler in here pipelines/ __init__.py pipelines.py <-- custom pipelines which implement the handlers here. However, whenever I specify this in config with this clause: [plugin.MailmanCustomizations] class: mailman_customizations.hooks.MailmanCustomizations enabled: no ... I get a hard load error on "ModuleNotFoundError: No module named 'MailmanCustomizations'" To confirm this is a Python module/class, I did a pure python shell with `from mailman_customizations.hooks import MailmanCustomizations` and it properly imports that class, so I'm not sure where to go from here in debugging. Thomas On 10/24/23 11:55, Thomas Ward via Mailman-users wrote: > Perfect, that should make things easier for me to install. > > Thank you kindly for all your support everyone! > > > Thomas > > > On 10/24/23 11:54, Mark Sapiro wrote: >> On 10/24/23 8:20 AM, Thomas Ward via Mailman-users wrote: >>> >>> This means I can install the code to anywhere on `sys.path` that the >>> system can detect and it does not need to be in the Mailman3 >>> library/directory space in the venv? >> >> Yes, as long as Mailman can import the class defined for the plugin >> in mailman.cfg, it will work. >> > _______________________________________________ > 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 teward(a)thomas-ward.net

2 years

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Shashikanth Komandoor

Hi Mark, Thank you for your response. And sorry for not giving you complete information as I am not sue what to share with you. I am using Postgresql-11.7 as my backend database. The below is the structure of the address table in* mailman *database: mailman=# \d address; Table "public.address" Column | Type | Collation | Nullable | Default ----------------+-----------------------------+-----------+----------+------------------------------------- id | integer | | not null | nextval('address_id_seq'::regclass) email | character varying | | | _original | character varying | | | display_name | character varying | | | verified_on | timestamp without time zone | | | registered_on | timestamp without time zone | | | user_id | integer | | | preferences_id | integer | | | Indexes: "address_pkey" PRIMARY KEY, btree (id) "ix_address_email" UNIQUE, btree (email) "ix_address_preferences_id" btree (preferences_id) "ix_address_user_id" btree (user_id) Foreign-key constraints: "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES preferences(id) "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) Referenced by: TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL TABLE "autoresponserecord" CONSTRAINT "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" FOREIGN KEY (address_id) REFERENCES address(id) The below is the structure of *user* table: mailman=# \d user; Table "public.user" Column | Type | Collation | Nullable | Default -----------------------+-----------------------------+-----------+----------+---------------------------------- id | integer | | not null | nextval('user_id_seq'::regclass) display_name | character varying | | | password | character varying | | | _user_id | uuid | | | _created_on | timestamp without time zone | | | is_server_owner | boolean | | | _preferred_address_id | integer | | | preferences_id | integer | | | Indexes: "user_pkey" PRIMARY KEY, btree (id) "ix_user__user_id" btree (_user_id) "ix_user_preferences_id" btree (preferences_id) Foreign-key constraints: "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES preferences(id) Referenced by: TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) mailman=# \dn List of schemas Name | Owner --------+---------- public | postgres (1 row) mailman=# select * from user; user ---------- postgres (1 row) *The above command output is not showing any fields. But if use the table as public.user (schema.tablename) with select command, it is showing the data. But without schema name this table is not showing those fields. Not sure if this the expected behavior or not.* I have not done any changes. Few days back I made DR machine up as I am taking primary into maintenance. The entire database was running streaming replication and I even kept the /var/lib/mailman directory in sync where all the components are installed. Please let me know if any more things I need to share. On Mon, Jul 27, 2020 at 7:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:56 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.1 and in built > postfix > > version 2.10.1-6 on RHEL 7.5 in production environment from the past 2 > > months almost. > > > > From the past few days, I found my server is responding to the users > > very slowly and throwing the Server Error page (of course getting the > > required page after multiple refreshes) for almost every click on the > > postorius pages (not yet observed on hyperkitty front end which in fact > is > > not so important for me as of now). > > > > During that time, I observed in the mailman.log an error message > saying > > "Could not locate column in row for column 'user.id'". The complete > > traceback log is attached with the mail. The error message is generated > for > > almost all the lists and all the clicks. > > > I don't understand what's going on. I suspect some kind of database > corruption, but I don't know what. > > The traceback indicates Mailman is getting the Members of a list and in > this process is trying to get the display_name for a member. The > member's subscriber attribute doesn't have a display_name so it is > trying to get is from the member's user attribute so it is trying to get > the user record for the member's email address via > IUserManager.get_user(). This in turn gets the Address record for the > email address and returns it's user attribute. > > This leads to the > > sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for > column 'user.id'" > > error which I don't understand. There is no table with a 'user.id' > column. user.id refers to the id column in the user table which comes > from the user_id column in the address table which should be a reference > to the id column in the user table, not a reference to ay 'user.id' > column. > > What is your backend database and what is the structure of the address > table in that database. Have you done any kind of direct database query > that might have affected this? > > -- > 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 & Regards, Shashi Kanth.K 9052671936

5 years, 3 months

[MM3-users] Re: OS upgrade - anything to take care of?

by Ruth Ivimey-Cook

Mark, While the venv will to a degree isolate you, my experience of the upgrade from 18 to 20 was that python3.6 was uninstalled and 3.8 installed. In this scenario, the mailman3 installation is subsequently broken because there is no python to run. It *is* possible to reinstall python3.6 after the dist upgrade is complete, and I would presume that after doing so mailman3 would probably resume ok. In my case I decided to continue using 3.8, which meant, in essence, rebuilding my mailman3 install -- not fun given my state of knowledge. I would therefore appreciate some guidance on performing the upgrade from 3.6 to 3.8 with the minimum of fuss. [I am not sure, but it could be possible to install python3.8 while using Ubuntu 18, so that the dist upgrade never breaks anything. Worth exploring.] Ruth On 13/05/2021 19:02, Mark Sapiro wrote: > On 5/13/21 7:25 AM, Torge Riedel wrote: >> today I upgraded one of two servers from Ubuntu 18.04 to 20.04 and - >> besides some minor config updates - postfix & dovecot worked well >> afterwards. >> >> So I am very optimistic that the upgrade of the second server from 18.04 >> to 20.04 will also work fine. But the second server is running MM3 >> (installed in venv) and I saw that on upgrade Python 3.8 is installed. >> >> Is there anything I have to take care of? Anything to do / change in venv? > The venv will still run whatever Python it was built with. That's what > virtualenvs are for - to isolate the software therein from external changes. > > You shouldn't need to do anything in the venv for Mailman to continue. > > -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 5 months

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

by Danil Smirnov

Yes, confirmed, and it seems that the page at https://mailman.server/accounts/password/reset/done/ is also missing styling due to this bug. On Tue, Nov 21, 2023 at 9:41 PM Jered Floyd <jered(a)convivian.com> wrote: > > I believe this is correct, and will need to be fixed on the Mailman side. > The practical effects seem to be -- for me at least -- that any of the > pages for social logins fail to receive any template styling. > > --Jered > > ----- On Nov 8, 2023, at 10:01 AM, Jeremy Stanley fungi(a)yuggoth.org wrote: > > > On 2023-11-07 19:46:01 -0800 (-0800), Mark Sapiro wrote: > > [...] > >> I don't think this is fatal, but I have reported it at > >> https://github.com/pennersr/django-allauth/issues/3513 > > > > We've been seeing the same thing in our deployment, I just hadn't > > found the time to look into it yet. Looks like upstream won't-fixed > > it, so I guess it was an intentionally backward-incompatible change > > and the template files will need some minor reworking? > > -- > > Jeremy Stanley > > > > _______________________________________________ > > 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 > _______________________________________________ > 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 danil(a)smirnov.la >

1 year, 11 months

[MM3-users] Re: Cannot show archives

by qiuhong su

Mark Sapiro wrote: > On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > > > > > Register user > > > > Login > > > > Create new Domain > > > > Create new List > > > > Subscribe to the list > > When I try to send email to the list by run command: echo “test email” | mail –s “test > > email” test(a)example.com > > User test can receive this email, but I cannot find it on Archives, and other members > > cannot receive this email too. > > > > > > You say "User test can receive this email". Is test(a)example.com a user > or the list's posting address? > If you are saying that test(a)example.com should be the list's posting > address, but the mail is instead delivered to the user test(a)example.com, > you have not set up your MTA to properly deliver list mail to Mailman. > See https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html. After check MTA settings, still cannot resolve this issue. I create a new list "list1", and after subscribe it, send an email to list1(a)example.com And then check ./var/archives/hyperkitty/spool/, ./var/messages Both are empty. Click "Archives" it will access http://example.com/hyperkitty/, and show "No archived list yet." Could you help me? Here is my mailman.cfg: ------------------------------------------------------------------ [mta] verp_configurations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 lmtp_host: example.com lmtp_port: 8024 smtp_host: example.com smtp_port: 25 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes -------------------------------------------------------------------------------- My mailman-hyperkitty.cfg, example.com can be resolved to 10.0.0.120 -------------------------------------------------------------------------------- [general] base_url: http://10.0.0.120/hyperkitty api_key: SecretArchiverAPIKey -------------------------------------------------------------------------------- In mailman-suite settings.py, already add '10.0.0.120' to MAILMAN_ARCHIVER_FROM MAILMAN_ARCHIVER_FROM = ( '127.0.0.1', '::1', '10.0.0.120' )

6 years, 1 month

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thanks, already had a look at the issues and thought with the merge requests that it was solved :-) Maybe I have to update my mailman to 3.3.3 so that it does!? Or is it that you are saying that this hasn't been fixed but tried to and it didn't work!? Actually I see the logic of what you are talking about in the issues, but don't see if what happens with the code can be correct, since I'm unfortunately not a coder. Any other ideas how I could go on / help? This qould be a quite central feature for using mailman3 for us. Thanks anyway. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > On 3/19/21 6:38 AM, Jens Günther wrote: >> Thank you for your answer. I should have seen that in the Docs, but >> somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html >> >> I set it in the corresponding file, but unfortunately it doesn't work >> :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS >> works, changed here from '*' to 'localhost' and my example-domains, this >> works). It seems to be the same as this user describes (a while ago): >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host. > See these issues and MRs for more detail. > > https://gitlab.com/mailman/hyperkitty/-/issues/254 > https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs > https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs > https://gitlab.com/mailman/postorius/-/issues/394 > https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs >

4 years, 7 months

[MM3-users] Re: Hyperkitty messages stuck in spool

by Mark Dadgar

On Nov 19, 2021, at 5:47 AM, Andrew Hodgson <andrew(a)hodgson.io> wrote: > Stephen J. Turnbull wrote: > >> Mark Sapiro writes: >>> On 11/18/21 6:38 AM, Andrew Hodgson wrote: >>>> >>>> Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? >>> >>> I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. >> >> If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. > > Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. I had this same experience on Digital Ocean. The short-term fix was enabling swap and the long-term fix was upping my service level to something with more memory. Without swap, I don’t think 2GB is realistically sufficient to run a full mm3 instance. The cloud providers really don’t like you to run swap because it hammers their SSDs. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 11 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Abhilash Raj

Hi, $ docker-compose rm -f mailman-web $ docker-compose up -d mailman-web This will basically create a new container for Mailman-web, but, since the state of mailman-web is stored completely in database (database container), I am not sure how to reset *just* mailman-web without dropping mailman-core related tables too (they share the same database but have their own separate tables). The above command will get you a fresh copy of code running. You can potentially get the list of tables and drop them, or maybe Diango has some way to reset it's state from Django shell (python manage.py shell, from inside mailman-web will get you shell). I may have to look it up. Also, just by looking at the traceback, I am not sure about the exact error. I may have to debug more to arrive at a better conclusion, which I won't able to do until after this weekend. Thanks, Abhilash On October 18, 2017 1:27:21 PM PDT, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/18/2017 12:28 PM, Mark Sapiro wrote: >> On 10/18/2017 09:00 AM, Dmitry Makovey wrote: >>> >>> It seems like mailman-core is still operating properly, but for some >>> reason mailman-web is not. Can I reset mailman-web somehow to >re-initiate? >> >> >> I'm not very well versed in the docker images, but I think >mailman-web >> uses uWsgi and sending the uwsgi process a SIGHUP should do it. > >I think I didn't express myself clearly - I want to reset any saved >state for mailman-web - not just in-memory stuff. I've restarted my >setup several times with mailman-web having exact same problem every >time. > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 14/2/21 18:42, Mark Sapiro wrote: > On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I did some exploration this morning (Spain time) in the weblate >> statistics and archives and I found that the changes done from >> Victoriano and me were recorded. I did a screencopy of all that if >> someone has any doubt about it. I downloaded this files: >> >> -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po >> -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po >> -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po >> -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po >> >> The thing is that they differ from the .po installed via pip upgrade. >> Mostly, as said, postorius, hyperkitty and django_mailman3. > > The latest packages in PyPI (pip) were released on Feb 2 except for > django-mailman3 which was released on Jan 15. They don't include updates > after those dates. > And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages. But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction. My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems. Thanks. Thanks a lot.

4 years, 8 months

Search results for query "sapiro"