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

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 3/21/19 3:02 AM, Malcolm Austen wrote: > > My only experience of MM3 is with Ancestry's 'RootsWeb' installation. > From the emails I can see a header "X-Mailman-Version: 3.1.0" but I > can't find anything to identify Postorius which is the only interface I > have to the system. Isn't there a footer at the bottom of wach page with something like: Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 > From symptoms seen and described by others, I have deduced that the > Postorius admin-per-user moderation options of "Default processing" and > "List default" mean that a user may be set (by default on the rootsweb > system!) to use the system default moderation settings rather than the > list default settings. New (non-)members always have Moderation set to List default. This means their posts are governed by the applicable Settings -> Message Acceptance settings. Setting a user's Moderation to Default Processing means that users posts will not be held/rejected/discarded/accepted immediately based on "Default action to take when a (non-)member posts to the list", but additional checks will not be bypassed. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. > Are my deductions correct? And if so, could this be the explanation of > the issue detailed in this thread? Setting a user's Moderation to Default Processing (or Accept) would bypass the list defaults and could be the explanation of this issue. When the non-member owner first posts to the list that address becomes a non-member of the list. I.e. it is in the roster of known non-members of the list and that non-member record could have had its Moderation set to Accept or Default Processing at some point which would explain why the posts are accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/9/20 12:16 PM, Jacob Bargery wrote: > Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" > > "Internal Server Error > The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" ... > This is a traceback I could find from another attempt: > > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API What are your Django settings for MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' Those match the defaults defined in mailman/config/schema.cfg [webservice] # The hostname at which admin web service resources are exposed. hostname: localhost # The port at which the admin web service resources are exposed. port: 8001 # Whether or not requests to the web service are secured through SSL. use_https: no # The administrative username. admin_user: restadmin # The administrative password. admin_pass: restpass If all that seems to match, what happens if you try telnet localhost 8001 If that doesn't work, but telnet 127.0.0.1 8001 works, there is some issue with `localhost` involving /etc/resolv.conf or /etc/hosts, most likely an ipv6 definition like ::1 localhost in the latter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: required cron entries?

by Mark Sapiro

On 12/31/20 2:49 AM, Andreas Barth wrote: > Hi together, > > as I found some mails in queue/shunt, I thought who should be running > them. See below. > On my (standard debian) reference system, there are no cron entries > for mailman3 but only for mailman3-web. The crons for Mailman core are discussed at <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs>. > Looking in the source code, there is a ./cron/crontab.in.in however > references to scripts in port_me/ directory. That's all old Mailman 2.1 stuff. ignore it. > Should I (still) install (parts of) the crontab? Or > are these functions handled elsewhere? Again, see <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs>. > Also, who picks up mails in queue/shunt? Or are they lost somehow? When processing of a message in Core throws an uncaught exception, the error is logged with a traceback in var/logs/mailman.log and the message's queue entry is saved in the /var/queue/shunt/ queue. These messages can be retried via the `mailman unshunt` command, but unless the underlying cause has been fixed, they will throw the same exception and be shunted again. Each shunted message requires manual inspection of the var/logs/mailman.log entry and possibly examination of the message via `mailman qfile /var/queue/shunt/....pck`. Some of these are spam messages which are somehow defective causing the exception, and these can just be manually removed from the shunt queue. I've seen a couple that are transient errors[1] that can just be successfully unshunted. The rest require some underlying issue to be fixed before they can be successfully unshunted. [1] In particular, I've seen an apparent race condition in building the list of recipients where we try to determine the delivery status for a member that is no longer a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Monday, November 6, 2017 8:52:25 AM EST Mark Sapiro wrote: > It looks like your Mailman user is 'list'. That is the user that should > be running mailman commands. Thanks! There is indeed a user "list". On Monday, November 6, 2017 10:06:49 AM EST Mark Sapiro wrote: > This may be "off the wall" but is the mailman you installed perhaps a > Debian/Ubuntu Mailman 2.1 package? If so, you are reading the wrong docs > and posting to the wrong list. It's Mailman 3.1.0 installed with pip. Pierre -- li ze te'a ci vu'u ci bi'e te'a mu du li ci su'i ze te'a mu bi'e vu'u ci

7 years, 7 months

[MM3-users] Re: What is the recommended format for mailbox interchange as files?

by Mark Sapiro

On 6/21/19 8:38 PM, J.B. Nicholson wrote: > > What is the recommended file format for mail archives to share? > > I ask because I often see mailman mailing list archives available as > some format of mbox file. I like this feature. I want to quickly import > a bunch of archived messages into my account so that I can read old > threads and get more discussion context anytime I need it. Some flavor of mbox is ubiquitous in the *nix world. The problem with this format is lines in the message body beginning with 'From '. Most modern software that writes mbox format files avoids this problem by somhow mangling such lines. The Python mailbox package will prefix such lines with '>' when writing a message to a mbox. Before Mailman 3, Mailman kept a cumulative archive in mbox format. Even after pipermail was included, the cumulative mbox was normally written and could be used to rebuild the pipermail archive or move the archive elsewhere. The problem is that the Python mailbox package didn't always mangle 'From ' lines in the body, so archive mboxes that go back many years are likely to have problems. A more robust mailbox format which is still a single file is MMDF format. This is similar to mbox with the addition that each message is preceded and followed by a line consisting of exactly four control-A bytes. I.e., there is one such line at the beginning and at the end of the file and two such lines between each message. Mailman 3 uses this format for the mailboxes that accumulate messages for digests. However, lot's of things including HyperKitty's importer and Mailman 2's bin/arch tool require input in mbox format. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/20/20 6:54 AM, Brian Carpenter wrote: > > Respectively, I think you are asking the wrong question here. The real > question is why isn't a display_name being removed when a list > subscriber is unsubscribed. I'd like to understand the real requirement. It seems to me that this issue has come up because a list admin wanted to change the display name shown in the membership roster for a user. Since there is currently no UI to do this, the list admin tried to do it by unsubscribing and resubscribing the user. That didn't work which led to this "unsubscribing a user should remove the user's information" thread, but the real issue is the lack of a UI for changing display names. It seems if that UI existed and was available, the "unsubscribing a user should remove the user's information" issue would never have been raised. So perhaps what we should be talking about is UIs for changing user information, what they would look like and who should be able to change what. Note that I personally am a member of many lists, an admin of multiple lists and a site admin for multiple mailman installations. I am well aware of the frustrations of list admins who wind up just doing it because it's way easier than instruction some users as to how to do it themselves. However, I don't think that is necessarily sufficient reason to hand over control of global, non-list specific user information to the admin of one particular list that the user happens to be a member of. Even in mailman 2.1, while a list admin could go to a user's options page for the list and change things, the "change globally" check boxes only worked for the user, not for the list admin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: logrotate

by Mark Sapiro

Please don't hijack threads. Post a new topic as an original post, not as a reply to an old thread. On 5/2/23 15:45, Christian via Mailman-users wrote: > I noticed that my mailman logfiles are not being rotated. I followed the > instructions in > https://mail.python.org/archives/list/mailman-developers@python.org/message/ > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Those instructions are for Mailman 2.1. > Now when I try and run logrotate I get the following error > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or > directory > error: stat of /opt/mailman/mm/error.log failed: No such file or directory > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or > directory > error: stat of /opt/mailman/mm/smtp.log failed: No such file or directory > root@zarathustra: > > What am I doing wrong please? Here's a logrotate script I use: ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` A couple of caveats. The first line of the postrotate script may be wrapped. `sudo ... true` is all one line. That line could also be ``` /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true ``` I.e., it either has to run as the mailman user or specify the --run-as-root option. Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't in /opt/mailman/mm/var/ those paths need adjusting. Finally, there may be an issue with `mailman reopen` in the postrotate scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: mailman web spamming uwsgi error log.

by Mark Sapiro

On 6/28/21 2:02 PM, Sarah H wrote: > I'm having an issue with the mailman web logs (/opt/mailman/web/logs/uwsgi-error.log) spamming the below: > > 20:53:44 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/django_q/cluster.py", line 436, in worker > res = f(*task["args"], **task["kwargs"]) > File "/opt/mailman/venv/lib64/python3.6/site-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month > mlist = MailingList.objects.get(name=mlist_name) > File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv/lib64/python3.6/site-packages/django/db/models/query.py", line 417, in get > self.model._meta.object_name > hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. ... > I do not have a list named "MailingList". hyperkitty.models.mailinglist.MailingList.DoesNotExist is the name of the exception. MailingList refers to the hyperkitty.models.mailinglist.MailingList class. It is not the name of a list. The actual code is ``` def _rebuild_mailinglist_cache_for_month(mlist_name, year, month): try: mlist = MailingList.objects.get(name=mlist_name) except MailingList.DoesNotExist: log.warning('MailingList with name %s does not exist', mlist_name) return mlist.cached_values["participants_count_for_month"].rebuild(year, month) ``` Thus, there should be a warning level log message MailingList with name xxx does not exist Identifying the list name. This will be in Django's log which is probably not /opt/mailman/web/logs/uwsgi-error.log, but may be /opt/mailman/web/logs/mailmansuitelog. It is defined in settings(_local).py as the value of LOGGING['handlers']['file']['filename'] I'm not sure how this issue comes about. I suspect it comes from a task that was created before some list was deleted and the task is being continuously retried because it fails. What does your Django admin `qinfo` command show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Message of migrated list showing "unsubscribe@%(host_name)s" in footer

by Mark Sapiro

On 10/8/23 16:03, alex(a)presland.net wrote: > > We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. > > ===== > LISTNAME mailing-list -- LISTNAME@DOMAIN > To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s > ===== > > 1) I don't know why %(host_name)s hasn't been automagically substituted > 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface The `mailman import21` process creates templates for existing 2.1 regular and digest headers and footers in Mailman 3's var/templates/lists/LIST_ID/LC/ directory. LIST_ID is the list's id like listname.example.com and LC is the language code for the list's preferred language. These have names like list:member:regular:header.txt, list:member:digest:header.txt, list:member:regular:footer.txt and list:member:digest.footer.txt. These are based on the mailman 2.1 lists regular and digest headers and footers with replacements translated to the appropriate Mailman 3 equivalents. However, there are various reasons why some replacements can't be translated, and these are left as is. in your case you need to edit those files and change %(host_name)s to $(domain}, or, since the default mailman/templates/en/list\:member\:generic\:footer.txt is ``` _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ``` just deleting the var/templates/lists/LIST_ID/en/list:member:regular:footer.txt file will probably do what you want. Note that templates defined in Postorius are handled differently, and if a template is currently undefined in Postorius, starting to define it in Postorius starts with an empty template instead of the current file system template. See https://gitlab.com/mailman/postorius/-/issues/366 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/18/19 11:29 AM, Manos Pitsidianakis wrote: > Hello, > > I've been getting "Cannot connect to SMTP server localhost on port 25" > from runner "out" in mailman.log over some mails stuck in shunt queue, > postfix logs show nothing when this happens, tcpdump on lo interface > port 25 shows nothing. The log shows up when I start mailman, and then > it seems not to show up again. That log message is only written once. It won't be written again unless the out runner is restarted or there is a successful delivery followed by another socket.error. > I can do 'telnet localhost 25' just fine, including as mailman user. I > can send and receive mail on my mail server. I tried making a test list > and sent/received messages fine. Is only one list affected, and is it all messages from this list or only some? > smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object > at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on > repeat, where the email address is one of the addresses of the shunted > mails. Do some deliveries of the problem message succeed? I.e., in the normal case without failure, there will be one "IndividualDelivery to: <email(a)address.tld>" message for each recipient in the recipients list. In the shunted message case, the msgdata object in the shunted pickle contains the recipients. Are there "IndividualDelivery to: <email(a)address.tld>" entries for some but not all recipients. Is the last of these an invalid local address? (Postfix can return a 421 status and drop the connection if there are too many invalid local recipients, although I don't know if this would apply in the VERP case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Search results for query "sapiro"