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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is what I did: (env2) [mailman@localhost mailman-suite_project]$ python2 manage.py runserver Performing system checks... System check identified no issues (0 silenced). July 21, 2017 - 20:50:29 Django version 1.11.3, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > 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: Installing mailman 3

by Rafael Mora

How do I tell mailman to connecto to postfix? Is mailman able to use the smtp I use for our emails service with hostgator? Instead of using postfix?? Thanks El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > 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: Could not locate column in row for column 'user.id'

by Mark Sapiro

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

5 years, 1 month

[MM3-users] Re: Problems with shunted Mails

by Mark Sapiro

On 4/19/22 03:47, Stephan Krinetzki wrote: > Hi all, > > we currently have a problem sending to an email list. The mailing list is an announcement list and is therefore moderated. The mail also arrives for moderation. However, when the mail is released, it is not delivered, but moved to the shunt queue. The error after an unshunt attempt in the log: > > Apr 19 12:31:43 2022 (17967) Uncaught runner exception: 'NoneType' object has no attribute 'email' > Apr 19 12:31:43 2022 (17967) Traceback (most recent call last): > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 176, in _one_iteration > self._process_one_file(msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/runner.py", line 269, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", line 50, in process > handler.process(mlist, msg, msgdata) > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/handlers/member_recipients.py", line 85, in <genexpr> > if member.delivery_status == DeliveryStatus.enabled) > AttributeError: 'NoneType' object has no attribute 'email' > Apr 19 12:31:43 2022 (17967) SHUNTING: 1650364303.8361175+08bb48ae877019e8a4c9dff8024c1270782fceb3 > > Any hints how we can solve the problem here? One of the list's regular members has no associated address record. I don't know how this can happen. You could find the member with mailman shell, e.g. ``` 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 mbr in m.regular_members.members: ... if mbr.address is None: ... mbr.subscriber ... mbr.user ... mbr.user.addresses ... mbr.user.preferred_address ... ``` You might be able to fix this with something like ``` >>> for mbr in m.regular_members.members: ... if mbr.address is None: ... mbr.address = mbr.user.preferred_address or member.user.addresses[0] ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 01:24, Onyeibo Oku wrote: > > Good Morning Everyone, > > I installed and managed mailman 2 for about two years. I am now > ready to try Mailman 3. The documentation for version 2 was lucid and > this forum was quite helpful in the past. > > Now I'd like to proceed with installating MM3 but I doubt my > understanding of the docs. It seems to assume that users will know what > to do. > > Okay, don't laugh! I just want to be sure what I am doing. Does the > following sequence resemble the proper steps? As Eggert says, we aren't laughing ... > 1. Download the source from a git repo (I understood that one) > 2. Create a virtual environment (venv perhaps ... not stated explicitly) > 3. activate the virtual environment > 4. from the git project root, run: ./mailman start Step 4 is premature. More below. > I know, its stupid. I had to ask. Not stupid ... > It would really build my confidence > someone would confirm the above steps or counter then with something > very explicit. What about process ownership? Do I need to have a unix > mailman user? What else do I need to get mailman up and running > before proceeding to configuration. Ahaa! I perused the config docs a > bit. Where can I find the .cfg file? As Eggert suggests, see https://docs.mailman3.org/en/latest/install/virtualenv.html and follow that. You don't need to download the source from GitLab. Following that doc will get the latest releases from PyPI via pip. Those are still somewhat out of date - we really should make new releases - so if you want the latest from GitLab, there are a couple of ways to do it. Perhaps the easiest is to just run the various `pip install` commands as documented and then upgrade Mailman core in your venv with ``` pip install --upgrade git+https://gitlab.com/mailman/mailman@master ``` and update the various mailman web packages with ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` where xxx is mailman-web, mailman-hyperkitty, django-mailman3, postorius, hyperkitty. I.e., run it 5 times, once for each value of xxx. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed

by Shashikanth Komandoor

Thank you Mark Sapiro. As per your suggestion, I have gone through the mentioned URLs and understood that the command "mailman notify" is responsible to send the periodic notifications to the owners of the list which of course should be as part of the cron job list (but it is not in my case). FYI, I am using mailman 3.2.3. And in my case, when I run the command "mailman notify" I am getting an error saying that the command "notify" is not present. *(venv3) [root@mailman3 commands]# mailman notifyUsage: mailman [OPTIONS] COMMAND [ARGS]...Try "mailman -h" for help.Error: No such command "notify".* And I also saw the help menu of mailman where I don't find any command displaying "notify" and its explanation. I don't understand where I had done wrong. Could you please help me in this regard? On Thu, Jan 23, 2020 at 11:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > > Hi, > > > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was > working > > fine. But I found that I am not getting daily summary notifications for > > which I learnt after browsing through different websites, there should be > > an entry of *checkdb* in the cron job list. > > > checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman > notify` > > > > But I did not find any such nor I don't find any cron job updated > after > > the installation of mailman 3. > > > See > < > https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > > If you installed Mailman from a package and the cron's weren't > installed, report this to the packager. > > -- > 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, 7 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 09:55, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > 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 lmtp runner did not start because at some point it had died and restarting Mailman won't restart a runner that died and was marked to not restart. You need to stop Mailman and make sure when mailman is stopped that there are no files in mailman's var/locks/ directory (remove any that are there) and then start Mailman and lmtp runner should start. As to why it died in the first place, there should be something in mailman.log from the time it died. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: dedicated mailman3 list server on Ubuntu 18.04 LTS - questions after installation

by Mark Sapiro

On 08/05/2018 03:37 PM, John Seifarth via Mailman-users wrote: > > The installation allows me to sign into the web interface, create a host, create mailing lists, and mass subscribe members. When members send email to the list address, the server sends the messages normally to the other members of the list. That's the good news. That's cool. You have raised a lot of questions and I don't have time now to deal with them all. Maybe others can help. I will say a few things now and maybe more to follow. > However, when I look at the list archives, there are no posts. I deliberately mass-subscribed an invalid address, and I can see in /var/log/mail.log that the message bounces, but I get no notification, nor do I see any bounce info when I look at the member info. About Archiving: Are you running django qcluster <http://docs.list.org/en/latest/config-web.html#running-the-task-queue-requi…> and all the scheduled tasks <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>? About Bounce processing: Bounce processing is not functional in Mailman 3 yet. > 5) DKIM and DMARC > > I’ve got OpenDKIM running on inet:12345@localhost and OpenDMARC running on net:54321@localhost. > > How can I get mailman to use these milters and sign messages? How should DMARC munging be configured when signing? Your outgoing MTA should be doing the signing, not Mailman. Your signing outgoing messages won't help with DMARC if Mailman alters the message in any way, e.g. by subject prefixing, content filtering or addition of list headers and/or footers. Minimum DMARC settings would be DMARC mitigation action -> Replace From: with list address and DMARC Mitigate unconditionally -> No > 6) Is there an overview of how mailman3 works? > > Is there documentation which explains the path of an incoming post through the system, including initial reception, list processing, sending to members, processing bounces, and archiving posts? All the docs are at <http://docs.list.org/en/latest/> You may want to see <http://mailman.readthedocs.io/en/latest/src/mailman/docs/8-miles-high.html> amongst the many other things you'll find there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Is this the problem?????: # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Shouldn't DEBUG be FALSE?? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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: Is there an example of a complete installation for https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-install (ie. standard installation)?

by Mark Sapiro

On 2/1/22 14:34, matt(a)fes.org wrote: > It's close, the config contents are good, but doesn't appear to be using the standard installation locations...or I missed some things? The issue is there is no `standard` installation. > For instance, my mailman.cfg is in /etc/mailman3/mailman.cfg) vs /opt/mailman/mm/mailman.cfg (from link you provided), same with settings.py and settings_local.py. "mailman info" shows "config file: /etc/mailman3/mailman.cfg". Also, don't have an /opt/mailman/mm/bin... This all depends on how Mailman is installed. For example, for my installations I create /opt/mailman/mm/bin where I put scripts that execute the corresponding mm/venv/bin/ commands after setting appropriate environment variables and/or with options pointing to config files, etc. But even ignoring that, a lot of locations depend on the chosen setting for layout: in the [mailman] section of mailman.cfg. That controls locations based on https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/mailman… where the `xxx` in `paths.xxx` is the value of `layout`. > This sort of illustrates my issues - trying to resolve problems is a challenge if my config/files/paths are incorrect. Comparing to a (formerly) working installation would clear up many of these issues and i think would be a great reference for anyone making the switch to mailman3. There is no `one size fits all` answer. I support three different production installations of Mailman 3 at lists.mailman3.org, mail.python.org and the server for my bicycling club. They are all quite similar, but they all differ in detail, in part because some were initially installed using the obsolete mailman-bundler package, and in part because two use Apache and one uses nginx. At least they all use gunicorn as the web wsgi server, but mail.python.org used to use Apache mod_wsgi, and uWSGI is another possible choice. If I gave you one of these as an example, it might cause you to make a bunch of changes that aren't in fact necessary, just because you and I have made different, equally valid choices. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Search results for query "sapiro"