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

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 7:44 PM, Alan So wrote: > I just notice that if I send an email to a list with a Cc header broken into multiple lines and the pair of double quotes are put in different lines, the email addresses afterwards will be wrongly rewritten. > > For example, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> tl;dr It is not valid to fold a header inside of a quotes string. First of all, the above is invalid. Presumably the address is intended to be "ABC DEF (XYZ)" <name(a)example.com> RFC 5322, sec 2.2.3 says in part: "The general rule is that wherever this specification allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP." and the definitions in sec 3.4 say in part: address = mailbox / group mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr display-name = phrase In this case, the quoted-string "ABC DEF (XYZ)" is a phrase which is the display-name and the only places where comments or folding white space are allowed is immediately preceding the "<" or following the ">" surrounding the addr-spec. Folding in the middle of the quoted string is not allowed. Were there no quotes, e.g. ABC DEF (XYZ) <name(a)example.com> Then ABC DEF is a phrase and (XYZ) is a comment and folding between DEF and (XYZ) would be allowed > It will become the following after going through the mailing list: > > CC: XYZ <"ABC DEF"@mail.server.name> Which is clearly wrong, but GIGO. > It seems that Outlook often split the To/Cc header into multiple lines and they often add double quotes to the full name of the users. Is the rewriting of Cc header handled by Mailman's code or another Python class? I haven't looked at the code to see exactly what's responsible here. I do note that adding double quotes around a display name is not only allowed, but is required if the display name contains "specials". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Thu, Dec 15, 2022 at 5:00 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > (sorry: I sent this yesterday afternoon, but from a unsuscribed mail > account) > > El 14/12/22 a las 19:04, Odhiambo Washington escribió: > > > On Wed, Dec 14, 2022 at 8:33 PM Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > > > >> 1. The post-update script runs everything required. For the avoidance of > >>> doubt, here it is: > >>> <CUT> > >>> #!/bin/bash > >>> > >>> set -e > >>> > >>> BINDIR="/opt/mailman/mm/bin" > >>> CONFDIR="/opt/mailman/mm" > >>> SETTINGS="settings" > >>> DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" > >>> STATIC_DIR="$CONFDIR/static" > >>> DEBUG="False" > >>> > >>> set -x > >>> > >>> if [ "$DEBUG" == "False" ]; then > >>> mkdir -p "$STATIC_DIR" || : > >>> "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput > >> --verbosity 0 > >>> "$DJANGO_CONTROL_SCRIPT" compress > >> Odhiambo, I had problems in the compress process in the last updates. I > >> would make sure the process is running ok. I had to disable the off line > >> compression for this matter. > >> > > @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> that sounds a bit > > non-standard, but care to explain what additional arguments you passed to > > django-admin compress? > > I had to set compression off in the update to 3.3.7 because I was > reproducing the same error as when I updated to 3.3.6. My guess is the > problem you have now is about the same problem and you cannot see > because you ran it in a script. > > I reported that in > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… In my case I do not get any errors so I think this is unrelated. I just seem to have a problem with the CSS files when accessing the archives. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Digest Formatting

by Mark Sapiro

On 11/7/20 9:08 AM, Stephen J. Turnbull wrote: > > I thought there was a way to trigger immediate distribution of a > digest immediately, but I guess I'm remembering that from Mailman 2. > Neither the Postorius management interface nor the core documentation > suggests there's such a trigger in Mailman 3. There is nothing in the web UI or REST, but the `mailman digests` command can send accumulated digests for one or more named lists or all lists unconditionally or only if the list's digest_send_periodic is set to True. see `mailkman digests --help` for details. > > 2) I have customized list:member:digest:header, but am not seeing > > the custom text where I thought it should be. The documentation > > seems to imply that both list:member:digest:header and > > list:member:digest:footer surround each message in the digest > > Which documentation do you mean? As far as I know (Mark will have > authoritative information if I'm wrong), the digest header and footer > appear at the top and bottom of the *whole* digest message (ie, once > each per digest), not surrounding or in the bodies of the component > messages. Steve is correct. The layout is as follows The masthead from the list:member:digest:masthead template. The digest header if any from the list:member:digest:header template. The table of contents. The individual messages. The digest footer from the list:member:digest:footer template. For the MIME digest, these are all separate MIME parts and the individual messages are message/rfc822 parts within a multipart/digest part. For the plain text digest, the digest is one text/plain part containing the above formatted par RFC 1153 And in another post, mailman(a)manygoodideas.com wrote: > I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks. This already exists, it is list:member:digest:footer. Your confusion seems to be because you think the list:member:digest:header template and list:member:digest:footer template are prepended/appended to each individual message in the digest which would not make sense and is not the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Templates

by David Krantz

On Sat, Sep 23, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) > you are using? No, that would have been strange to me; the table in the database was up to date. But now I tried that, I got no effect this time but I probably could set up a better test. I also had another problem [solved]: I get the error message "Multiple rows were found for one_or_none" when I try TemplateManager.get(name, context) for the list. There is only one matching row in the templates table so something is fishy with the ORM. This occured when I changed to the previous uri value. As the database does not have any duplicates in the templates table I suspect either a broken join or that the cache retains the old value. The traceback looks like this in the mailman shell: >>> tm.get('list:member:regular:footer', 'test.example.com') Traceback (most recent call last): File "<console>", line 1, in <module> File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/template.py", line 98, in get contents = cache_mgr.get(actual_uri) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/cache.py", line 125, in get CacheEntry.key == key).one_or_none() File ".../venv-3.5/lib/python3.5/site-packages/SQLAlchemy-1.2.0b2-py3.5-linux-x86_64.egg/sqlalchemy/orm/query.py", line 2814, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Workaround: Delete cached files in .../var/cache and run delete from file_cache in postgresql. Then that works again. The culprit was that the file got cached twice so there is a bug in the cache function. I used the ITemplateManager-util in the shell to cause the problem. >> 2. the $user_delivered_to and $user_email do not expand for some >> reason. Known problem? > > > These require that the list delivery be personalized. See > <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. > That explains things. Thank you! Now I got two footers, first one without personalisation and one personalised. Interesting. best regards // David

8 years, 1 month

[MM3-users] Re: Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.

by Abhilash Raj

On Tue, Apr 9, 2019, at 2:34 PM, roger.hislop(a)is.co.za wrote: > Hi all -- really need some help. I'm tech literate, but definitely not > a sysadmin or dev. > > I'm following the tutorial at "Olay's Farmland" at > https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > which seems to be a clone of the same content here > https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ The right place to get help regarding these guides would be the author of the posts, which AFAIK, have no affiliation with Mailman Core Team. On a (very) quick glance, it seems fine. > Easy enough to get most of the way ... set up EC2 instance, configure > SES and add DNS settings with DKIM etc. Set up Postfix, test it. All > working groovy. > > I run through the how to all the way through setting up the containers > and firing it up. This is where things start to get funky. > > Once the docker-compose is run, I run "curl > http://172.19.199.3:8000/postorius/lists/" to test. First time it said > it couldn't connect to database. So I nuked and restarted from scratch. > Second time it said the same thing... was reading around the place and > tried again, and then reran that curl and it worked -- gave me html > from a page. But the VM started running slowly --taking forever to > follow keypresses. > > Eventually became unresponsive. So I rebooted the machine via AWS > console, and docker ps showed only the postgres db running. > docker-compose ps shows > Name Command State > Ports > ------------------------------------------------------------------------------------------ > docker-mailman_database_1 docker-entrypoint.sh postgres Up > 5432/tcp > mailman-core docker-entrypoint.sh maste ... Exit 255 > 8001/tcp, 8024/tcp > mailman-web docker-entrypoint.sh uwsgi ... Exit 255 > 8000/tcp, 8080/tcp > > So rebuilt the container -- same thing. It looks and feels like its > running out of memory. > > I used the compose file from > https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4… (with appropriate edits). How much memory do yo have in your VM? Have you tried using a bigger VM? thanks Abhilash

6 years, 6 months

[MM3-users] Shorted Subjects in Mailman

by Stephen J. Turnbull

Stephan Krinetzki writes: > We have been experiencing the following problem lately: When a user > sends a mail with an unusually long subject to a mailing list, this > subject is shortened. Is this being observed by all subscribers? Especially subscribers with various different mail clients? Do you observe this when you look at the "original message"? (Different clients describe this function in different ways, but most mail clients allow you to look at all of the header and body text exactly as sent, with no formatting). > Here are the two examples: > > Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on > lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) > > Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos > Anti-Virus on" (57 characters long) By design, Mailman does not truncate the subject, it folds it to multiple lines to conform to Internet mail standards which state that lines should be no longer than 78 characters. So, including adding the "edv-support" tag, a stock Mailman installation should be changing: Subject: [SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" (all one line) to (two lines, split after "on" with the space starting the second line[1]: Subject: [edv-support] [SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" A mail client that conforms to Internet mail standards might either display it exactly that way, or it might unfold it to a single line, or it might unfold it, then refold it to match the user's display width. Of course if you look at the original text and there is no second line, that's a Mailman bug. > Is there any way to work around this? If Mailman is folding the subject as described above, you'd have to patch the code, and maintain the patch across upgrades. I think the patch might be a little tricky because the code that does this is in the Python distribution, not in Mailman itself, if I remember correctly. Alteratively, get people to use clients that properly handle Internet mail. Asking people to change their mail clients rarely goes over well though. Regards, Steve Footnotes: [1] The mail standards permit splitting header lines only on whitespace under certain conditions, not at hyphens and other punctuation as normal in English text.

3 years, 3 months

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

by Onyeibo Oku

On Sat, 29 Oct 2022 18:21:06 +0900 "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > > After series of SELinux file context labeling, setting the nis > > boolean, and a few custom policies, it resolved. Thank you for the > > responses (and your patience). > > Perhaps you could post these to our wiki (https://wiki.list.org) if > you don't consider them sensitive? > No problem. Although I suspect some of the Custom SELinux policies may be unnecessary, assuming I missed certain files/folders that require specific labels. I tried my best using the following pages: 1. https://www.systutorials.com/docs/linux/man/8-mailman_queue_selinux/ 2. https://linux.die.net/man/8/mailman_selinux > > 1. Will there be a conflict of resource (ports, threads, etc) > > running another instance [of uwsgi]? > > There can be. That's your problem, you need to configure each > application to use non-conflicting ports and locations (URL paths, if > the applications share externally-visible domains and ports). They > can also conflict over internal resources such as file locks and I/O > channels, but that depends on the specific applications. There are no > conflicts among Mailman suite applications if configured as we > recommend, but to know what conflicts might arise you need to explain > what other apps will be running, and how you plan to configure them. > I am not sure I understand what you mean by apps. Is that Django apps (./manage.py startapp app)? Do you mean a Django Project instead (./manage.py startproject app)? What I have here is an active website project (live) done on Django framework. It runs from a different virtual environment (venv). hence: mailman --> /opt/mailman/venv website --> /srv/website/venv (has a running uwsgi instance) > > In whichcase, it doesn't hurt to follow the doc to its logical > > conclusion? > > I don't understand what you mean by logical conclusion. > That is to follow the guide to the end of the page (disregarding the possibility of conflicts). This guide here: https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… --Onyeibo > _______________________________________________ > 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/

3 years

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 11:33 AM, Mark Sapiro wrote: > On 10/29/20 5:23 AM, Brian Carpenter wrote: >> I have a list owner who had his subscription policy set to confirm. >> Apparently that was too hard for his list members to handle so he >> changed it to moderate only. If someone sent a subscription request that >> needed to be confirm, did not respond to it, and then tried subscribing >> again after the member policy changed to moderate, their 2nd >> subscription attempt still shows up in the confirmation queue. Is that >> normal behavior. My understanding is it is. Please let me know if I am >> wrong here. > > Are you certain that the request waiting confirmation is the second one > and not the first? Good point and I am not sure. I will try to note that if this pops up again. > > >> The real mystery here is when someone tried subscribing again >> (listname-subscribe@listdomain) hours after the subscription policy was >> changed to moderate and they still showed up in the confirm queue. How >> is that possible? I tested the list with two of my addresses and both >> showed up in the moderation queue as expected. As far as I can tell from >> the mailman logs, this was the person's first attempt at subscribing. > > I suspect it was not the first attempt and that the subscription waiting > confirmation was requested when the policy was confirm. The confirmation moderation notice had the date-time stamp that came a few hours AFTER the subscription policy was changed. Also I only saw one confirmation request sent out via Postfix' mail.log. I saw no other for this subscriber. Same thing with the smtp.log. I cannot duplicate this behavior when I try to subscribe. My subscription attempts went straight to moderation. > > The real question is if a user has a subscription waiting confirmation > and the policy is changed to moderate, is a second request rejected > because of the request waiting confirmation. If so, I think this is a > bug which should be fixed. > Do you think this is a bug with Mailman core or my system? -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 19:36, Jan Eden wrote: > On 2022-11-27 08:01, Mark Sapiro wrote: > > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > > contents) are readable and writeable by mailman:mailman: > > > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > > > I fail to see where haystack tries (and fails) to create the directory. > > > FWIW, deleting threads is not a problem. > > > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > > add that user to the `mailman` group. > > That's what baffles me – uwsgi is run as the mailman user: > > mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini I tried setting permissions on /opt/mailman/fulltext_index to 777 temporarily, but the issue remained (as expected). It occurs in the Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > if self.use_file_storage and not os.path.exists(self.path): os.makedirs(self.path) where self.path is referenced, which is defined in line 110 (as part of the __init__ function): > def __init__(self, connection_alias, **connection_options): > super().__init__(connection_alias, **connection_options) > self.setup_complete = False > self.use_file_storage = True > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > self.path = connection_options.get("PATH") Unfortunately, I cannot see where the PATH key for connection_options is defined. - Jan

2 years, 11 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Stephen J. Turnbull

Daniel Armengod writes: > Hello Christoph, > > > If we setup such a system, can we assume that it will silently operate > > without causing much administration work most of the time (like my > > nginx server)? Or is maintaining a Mailman 3 server a significant burden? > As with all things, it is easy once you've mastered it, and easy for > someone who /has/ mastered it to say it's easy :P A Mailman 3 server isn't hard to manage. It's the rest of the system that provides most of the challenges ;-) (including the challenges in configuring Mailman!) You can get pretty close to a turnkey system by using one of the Mailman containers Abhilash provides, but then you need to run Docker, and that's probably going to increase the spec of the hardware you need. Mailman 2 is much more self-contained than Mailman 3. You still need an MTA and a webserver that provides CGI, but that's all. > > The only problem is that our list runs on Mailman 2. We would like to > > move to Mailman 3 > Why? I'll echo this. We don't need to know (unless there's a specific technical challenge to Mailman 2 that you hope Mailman 3 can resolve, and then we can tell you whether Mailman 3 has it, will have it soon, or won't have it soon if ever), and don't really care (happy to help and all that). But you need to ask yourself that question because it's rarely a good idea to fix what ain't broke. And Mailman 3 is sure to become more robust, easier to install, and easier to migrate Mailman 2 lists over time. Don't do it until you forsee a near- future *need* to migrate, is my advice. If you're worried about Python 2's "end of life," especially about lack of security maintenance going forward, I wouldn't worry about that. Python 2.7 is a very robust, resilient, and secure in its internal operation. It's very unlikely that a Python-2-specific bug in a Mailman installation is how an attacker gets in. It's not going to need much maintenance. As a whole, Daniel's advice is excellent and worth studying. Steve

5 years, 8 months

[MM3-users] Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

Putting this back on the list. On 5/19/21 9:46 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> ... >> Have you set >> ``` >> [mailman] >> sender_headers: ... >> ``` >> in mailman.cfg?, and if so, to what? > > We have not changed it: > > [mailman] sender_headers: from from_ reply-to sender > > According to the smtp.log, there was an envelope sender ("MAIL FROM:.."), which matched the From header. In the example I'm looking at right now, the sender was not a member of the list, but the Accept these non-members box in the list settings has a regexp that matches the sender's domain. In another example from this morning, to a different list, the envelope sender and From header match, and is a member of the list. > > I don't see any obvious reason or configuration setting that would make either address invalid. First of all, the discard has nothing to do with whether the sender has any connection to the list. It only says the message had no sender at all. Assuming the message had a From: with a syntactically valid email address, this discard should not occur. Also, if the envelope (MAIL FROM:) was a syntactically valid email address, this discard should not occur. The address is validated by mailman/email/validate.py by first splitting it into `local_part`, `@`, `[domain_parts]` where domain_parts are the `between dots` parts of the domain and then validating the local_part and domain with regexps defined per > # What other characters should be allowed? > _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) > # Strictly speaking, both ^ and | are allowed and others are allowed in quoted > # local parts, but this can open the door to certain web exploits so we don't > # allow them. > _valid_domain = re.compile('[-a-z0-9]', re.IGNORECASE) > # These are the only characters allowed in domain parts. Does the From: local part or the MAIL FROM: contain any characters not in the [-0-9a-z!#$%&'*+./=?@_`{}~] class? -- 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] MM3 Postfix FROM header issue

by eboltz＠lhtservices.com

Installed MM3 on Debian 11, followed the steps from the MM3 website. I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. When I check the /var/log/mail.log without the sender_canonical_maps setting enabled, then the initial email sender is either rejected because 'Recipient address rejected: User unknown in virtual alias table' or '550-From header sender domain not verified (example.com) 550-On your sending > Verified senders page 550 verify the sender domain or email to be allowed to send' I have smtp_sasl_passwd_maps disabled, since I'm trying a different SMTP relay Here is my main.cf setup # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 2 on # fresh installs. compatibility_level = 2 # Mailman related settings #owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains #relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_domains # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level=may #smtp_tls_CApath=/etc/postfix/o365_smtp_cert.pem smtp_tls_security_level=may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = localhost alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain relayhost = [mail.smtp2go.com]:587 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 sender_canonical_maps = regexp:/etc/postfix/sender_canonical smtp_use_tls = yes smtp_always_send_ehlo = yes unknown_local_recipient_reject_code = 550 always_add_missing_headers = yes #smtp_sasl_auth_enable = yes #smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd smtp_sasl_security_options = noanonymous header_size_limit = 409600 default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 header_checks = regexp:/etc/postfix/header_checks mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128

1 year, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Thu, 2021-02-25 at 13:24 -0800, Mark Sapiro wrote: On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. Hi Mark, Thanks for being patient with me. I'm still baffled but might have found the problem. I've done the above, to no avail. If I look at the queries being sent to mysql, I see stuff like this: 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP 174 Query SET sql_mode='STRICT_TRANS_TABLES' 174 Query COMMIT 174 Query SET AUTOCOMMIT = 0 174 Query SET AUTOCOMMIT = 1 174 Query SET AUTOCOMMIT = 0 I note that there is nothing about the charset, so something's clearly wonky. As previously stated, /etc/mailman3/mailman-web.py has the right thing: 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, but that latter is having no effect. I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset (but does have init_command), but I _think_ that's only about the package management system. So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py (which obviously has the right thing), but what about the .pyc file? # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc Binary file /usr/share/mailman3-web/settings_local.pyc matches # grep -i charset /usr/share/mailman3-web/settings_local.pyc # It ain't in the .pyc file. Am I overly optimistic that that might the be problem? If so, I'd be grateful if someone'd tell the newbie how to recreate that file without trashing something. Cheers, David

4 years, 8 months

[MM3-users] Re: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 10:35 PM, Abhilash Raj wrote: > > > On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > > The issue has confirmed by other users: > > > > https://github.com/maxking/docker-mailman/issues/382 > > The issue seems to happen because the static files that are present at > the default staticfile locations aren't valid anymore and aren't > removed automatically on upgrades. > > You can run: > > sudo rm -rf /opt/mailman/web/static > > To remove them manually and then it should be re-created properly on > the next start. I'll try to work on a fix for this in some automated > fashion. Seems like I wasn't using the right options like Mark pointed out above. --clear flag will automatically remove the old files. I have created a PR[1] to fix it and will try to get it out with a new release soon. [1]: https://github.com/maxking/docker-mailman/pull/384 > > > > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > > > >>> COMPRESS_OFFLINE = True > > > >>> COMPRESS_ENABLED = True > > > >> > > > > > > > > These two are commented out. > > > > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > > going on. > > > > > > -- > > > 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/ > > > > > _______________________________________________ > > 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) -- thanks, Abhilash Raj (maxking)

5 years, 4 months

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

by Onyeibo Oku

On Wed, 12 Oct 2022 17:52:47 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: Thanks Eggert and Sapiro. > > As Eggert suggests, see > https://docs.mailman3.org/en/latest/install/virtualenv.html and > follow that. I already started out on the above route. Its an adaptation because I am running Fedora. I had no problem with system-wide installations via dnf package management. However, some parts of the documentation does not add up. > 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. > I will come to this eventually (assuming that does not break things later). I aim to get it all working with regular pip packages first. I have installed mailman core already. Fedora expects mailman files to reside at /usr/lib/mailman. It appears to ship with a mailman unix user. I adapted to those system defaults. Now I observe that "su - mailman" gives me the proper prompt but .bashrc doesn't kick in. I still have to manually change to the virtual environment despite setting the automatic change in .bashrc. However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". Is this normal? Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which should correspond to "/usr/lib/mailman/mm/var/*" on my instance. However, I don't see any instructions on how to get the "/mm" folder and the associated sub-folders. I just have "/usr/lib/mailman" I am lost "pip list" within the venv environment confirms that I have "mailman 3.3.5". What am I missing? Regards Onyeibo

3 years

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Mark Sapiro

On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: > I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. Are you saying that a 'reply' , not 'reply-all' will reply to the From: only and ignore Reply-To:? If so, the email clients that are doing that are badly behaved. I can't say they are non-compliant as RFC 5322 <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: The originator fields also provide the information required when replying to a message. When the "Reply-To:" field is present, it indicates the address(es) to which the author of the message suggests that replies be sent. I.e., Reply-To: is only a 'suggestion', but well behaved clients will follow it. > When they use Reply All, the email is addressed to both the From: and Reply-To:. Reply All should reply to the Reply-To:, To: and Cc: addresses and to From: if there is no Reply-To:. Whether Reply All should include From: if there is a Reply-To is not well defined. > Reading through previous threads here, I've tried a number of things: > > 1) DMARC mitigation action is "Replace From: with list address" > 2) For Alter Messages - Set "Reply goes to list" > > The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! If Alter Messages -> Reply goes to list is set to Reply goes to list, Reply-To: will include the list posting address. What are the clients that ignore this? Complaints should go to the providers of those. Tf DMARC mitigation action is "Replace From: with list address", that will happen to messages to which DMARC mitigation action applies. If you want it to apply to all messages, set DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

--------------------------------------------------------------------------- First issue:Postfix v3.5.8 on RHEL 8. The below is from journalctl -xe: --------------------------------------------------------------------------- Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or directory Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or directory I manually created the var_dir: /opt/mailman3/mm/var directory specified in the mailman.cfg file. How do I find out how to populate the postfix_domains.db files, and the postfix_lmtp.db file? --------------------------------------------------------------------------- Second issue: Postgresql authentication. PostgreSQL v10.23. --------------------------------------------------------------------------- I have this in the active mailman3.cfg file, where xxxxxxxxxx is the same complex password in the mailman3 config file: url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 Same password when I created the mailman3 and mailman3web users: create role mailman3 with encrypted password 'xxxxxxxxxx '; create role mailman3web with encrypted password 'xxxxxxxxxx '; psycopg2.OperationalError: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: Ident authentication failed for user "mailman3" --------------------------------------------------------------------------- Contents of the "live" mailman.cfg file, from "mailman info" --------------------------------------------------------------------------- (venv) [mailman3@someserver ~]$ cat -n /opt/mailman3/var/etc/mailman.cfg 1 # /opt/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 # This address is the "site owner" address. Certain messages which must be 8 # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # bounce from a list owner), will be sent to this address. It should point to 10 # a human. 11 site_owner: user(a)example.com 12 13 [database] 14 class: mailman.database.postgresql.PostgreSQLDatabase 15 ##### url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # ---------------------------------------------------------------------------------- 17 # Changed: Fri Jun 28 11:56:02 EDT 2024 18 url: postgresql://mailman3:xxxxxxxx@localhost/mailman3/mailman3 19 # Changed: Fri Jun 28 11:56:02 EDT 2024 20 # ---------------------------------------------------------------------------------- 21 22 [archiver.prototype] 23 enable: yes 24 25 # For the HyperKitty archiver. 26 [archiver.hyperkitty] 27 class: mailman_hyperkitty.Archiver 28 enable: yes 29 configuration: /opt/mailman3/mailman-hyperkitty.cfg 30 31 [shell] 32 history_file: $var_dir/history.py 33 34 [mta] 35 incoming: mailman.mta.postfix.LMTP 36 outgoing: mailman.mta.deliver.deliver 37 lmtp_host: 127.0.0.1 38 lmtp_port: 8024 39 smtp_host: localhost 40 smtp_port: 25 41 configuration: python:mailman.config.postfix 42 verp_confirmations: yes 43 verp_personalized_deliveries: yes 44 verp_delivery_interval: 1 Suggestions appreciated for how to fix the postfix_domains files, and the postgres authentication isssue. ------------- Keith

1 year, 4 months

[MM3-users] Re: anomalous behavior

by Mark Sapiro

On 10/5/24 04:14, donato(a)molino.it wrote: > Hi, > I installed mailman-full on debian 12. How? Did you follow https://docs.mailman3.org/en/latest/install/virtualenv.html or did you install the Debian packages. If the latter, please see https://wiki.list.org/x/12812344 > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > I have three MLs: > 1) example(a)example.com > 2) test(a)example.com > 3) hello(a)example.com > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > The configurations are identical for all 3: > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > I also enabled all debugging in mailman.cfg. > But everything is fine What's in the MTA log? Does list 1 have any non-digest members with delivery enabled `mailman members --regular --nomail enabled example(a)example.com` In addition to the above in smtp.log, I would expect to see entries similar to the following for your post to this list. ``` Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 seconds Oct 05 11:15:02 2024 (3390806) <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 seconds Oct 05 15:22:57 2024 (3390806) <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes ``` (the delay between 11:15:02 and 15:22:57 above is the time between arrival and held message approval) Do you see things like that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

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

by Stephen J. Turnbull

Onyeibo Oku writes: > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. As Mark already wrote, "adapting" to Fedora is a bad idea. It makes it harder to read our documentation, which as you note is imperfect. Also, it interferes with Fedora's own package management. You should not be installing anything but Fedora packages into /usr and /var (among others). > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? Yes. Exec summary: Different startup files are read depending on whether the "login" and "interactive" flags are set, and the bin/activate script is not a normal script, invoking it is very finicky. I don't know exactly what's going on with the automatic invocation of the venv, but I suspect it's related to that. A quick workaround for the difference between "su mailman" and "su - mailman" would be to link .bash_profile -> .bashrc, or source one from the other. See bash docs for details. > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" That's undoubtedly related to "adapting" to Fedora practice. Where pip packaged files ended up depends on where you put your venv. My recommendation is to delete everything you've done to this point and start over from the beginning, following our instructions to the letter. This has two benefits: (1) you don't need to continuously translate from Mailman instructions to Fedora practice, and (2) in case our instructions are inaccurate or poorly adapted to the Fedora environment, it's *much* easier for us to advise you on what to do. Steve

3 years

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 14:31, Mark Sapiro wrote: > On 10/17/20 10:39 AM, Torge Riedel wrote: >> The message is being held because: >> >> Header "Yes" matched a header rule >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> I think this is wrong, it should read 'Header "x-spam" matched a header >> rule'. Cause the header rule is configured for header "x-spam" and >> pattern "Yes". > > The message is defined as > > 'Header "{}" matched a header rule' > > where {} is replaced with the value of the matching header. I agree it > would be better if it were something like > > 'Header value "{}" matched a header rule for {}:' > > with {}s replaced with the header value and name. That would make it in > your case > > 'Header value "Yes" matched a header rule for x-spam:' > >> I haven't found a bug report for this yet on gitlab. If someone of the >> developers confirm this is wrong, I will file a bug on gitlab for it. > > Please do file a bug. It won't be fixed until after the upcoming 3.3.2 > final release because we not making i18n changes between the candidate > and final releases. Also, if you don't like my suggestion, feel free to > suggest something else. > FWIW, I suggest: Header "{name}": rule matched value "{value}" Name tends to be short and must be simple ASCII. Value can be very long and encoded, so it may wrap. Name will be short and recognizable. Plus the name provides the context for the value - and name:value is the way the header appears in the e-mail. So I think name before value obeys the UI principle of least surprise. I might also add the rule number or config filename:line, as in Header "{name}": rule in {file}:{n} matched value "{value}" This would be helpful when backtracking from a rejected message to the cause. A sample expansion might be: Header "X-Spam": rule in foo.conf:83 matched value "yes"

5 years

[MM3-users] Dump/restore users (with passwords) via API Update

by Conrad Holmberg

Hello: Just an update and review on a previous thread and some progress. I'm trying to write a Python script to do the following: - Dump all the members from a email list within mailman instance A. This includes the display name, email, password hash, and all the preferences. The output is a json file. - Then we read this json file and create the user, membership to the email list, and the preferences into mailman instance B. The problem is that we are trying to insert the members with the password hash and NOT a new plain text password. A simple json dump example: { "password":"$6$rounds=656000$QhEAT7XCQ9tyUmJV$cj2xv3GKd8UXdSSasMZdqe0NjUL4T751nBEkdubog55jzIY1iZ5AQ4aRVeJIi1jnS1CKHHJn6nVnW.Hz91Xvk.", "list_fqdn": "helpme(a)confused.com", "display_name": "Bob Nobody", "email": "nobody(a)nowhere.com", "preferences": { "receive_list_copy": false, "hide_address": false, "preferred_language": "en", "delivery_mode": "regular", "receive_own_postings": true, "acknowledge_posts": false, "delivery_status": "enabled" } } The code for this within the mailman client API is pretty straight forward. However, the method for create_member will not work for our situation because the argument requires the password to be in plain text to be encrypted later. The rest of the tasks (subscribing, preferences) can be done with the mailman client with this single exception. Now my question is irf someone can send a single piece of code example or where to look to accomplish this. I see two options: Using the mainman core. I believe the modified code would be something like this: user_manager = getUtility(IUserManager) #with transaction(): new_user = user_manager.create_user( 'nobody(a)where.com', 'Bob Nobody') new_user.password = config.password_context.encrypt('abc123') #replace with hash new_user.password = '$6$rounds=656000$tS8sTX' So the password is set with the hash instead of the encryption method. Original code: new_user.password = config.password_context.encrypt('abc123') The other possible method is through django. However, I'm not really sure where to being on this on as I've been looking over the django-mailman3 and this is the only example I can find in test_delete_account.py: def setUp(self): self.mm_user = Mock() self.mm_user.user_id = "dummy" self.mailman_client.get_user.side_effect = lambda e: self.mm_user self.user = User.objects.create_user( 'testuser', 'test(a)example.com', 'testPass', first_name="firstname", last_name="lastname", ) self.client.login(username='testuser', password='testPass') Again, it appears that the password is encrypted somewhere else before encrypted. Any help on this is greatly appreciated. Thanks Conrad

7 years, 1 month

[MM3-users] Re: [NON-INTERNAL] Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

I tried with a new post and still, not showing the messages from July 25th in the Archive. There must be a way to force the archiving of the messages from July 25th. List metrics Created at March 25, 2016, 11:15 a.m. Last post at July 25, 2025, 12:01 p.m. Digest last sent at July 25, 2025, 12:01 p.m. Volume 135 ________________________________ From: Stephen J. Turnbull <steve(a)turnbull.jp> Sent: Monday, July 28, 2025 12:15 PM To: Willie Castillo <Willie.Castillo(a)caemilusa.com> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. willie.castillo(a)caemilusa.com writes: > Looks like "hyperkitty" stopped archiving right after the CERT for > the mailman3 website expired, How can I make the missing archives > visible on the website? I see there "*pck" files in > the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The > list archive does not show that last posting [of 25 July 2025. It's been a while since I've looked closely at this, but if I'm wrong nothing disastrous will happen, you'll just have to wait a little longer. The hyperkitty/spool directory is a staging area for the messages to be archived. As usual "spool" implies "work to be done", and HyperKitty (specifically the mailman_hyperkitty IArchiver implementation) considers all .pck files in the spool to be tasks in the queue. The assumption is that most sites will (a) rarely have trouble and (b) will be archiving frequently, so there is no polling done. Rather, when a message is scheduled to be archived, the archiver wakes up and archives everything in that directory. So the messages should be added to the archive the next time a message arrives. Note that this is not list-specific: if there's a pending message for list A and a message for list B arrives, the archiver will process A and then B. The easiest way to trigger this is to send a test message. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://urldefense.us/v3/__https://www.siriusopensource.com/__;!!E8b8mVbrrf… Software systems consulting in Europe, North America, and Japan

3 months, 1 week

[MM3-users] Re: Disable user registration

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > jens.guenther(a)posteo.de writes: > >> Same question here :-) > > This is not a simple question. Mailman is built from the ground up on > the assumption that users sign up. Making sign-up easy and powerful > is the raison d'etre of Mailman. > > One obvious approach is to add "^.$" to each list's ban list > (eventually that should be configurable as a list style, so "easy" to > make domainwide or sitewide), but that doesn't stop people from > creating users via Postorius. One way to address that would be to > clean out users with no subscriptions once a week or so. > > I guess you could go into the templates and remove the > accounts/signup/ links everywhere if "denial by obscurity" is enough, > or into urls.py and send that URL to a "Get out of here you hacker!" > view. Since these interventions are global, though, so the > desideratum of "no site admin intervention" is right out. Users are > site-global. Modifying urls.py to match `/accounts/signup` and redirect to a static page that says “Signups are disabled” or just event a 404 page is probably easiest to do. diff --git a/example_project/urls.py b/example_project/urls.py index 9c854989..3187756e 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -23,16 +23,22 @@ This file is the main URL config for a Django website including HyperKitty. from django.conf import settings from django.conf.urls import include, url from django.contrib import admin +from django.http import Http404 from django.urls import path, reverse_lazy from django.views.generic import RedirectView +def not_found(request): + raise Http404("Signups are disabled on this site.") + + urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('hk_root'))), url(r'^hyperkitty/', include('hyperkitty.urls')), # url(r'^postorius/', include('postorius.urls')), url(r'', include('django_mailman3.urls')), + url(r'^accounts/signup', not_found), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), This did the job for me locally and will present the user with a 404 page saying the “Signups are disabled on this site”. Note it is important to put the new pattern before the “^accounts/“ pattern since the URLs are matched in the order they are defined. -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Archive import fails: "IndexError: list index out of range"

by Johannes Rohr

I am now importing the archives of my old mailman2 installation. Unfortunately, with some of the larger and older lists, import fails halfway through, with an exception, the last message of which is IndexError: list index out of range Below is an example. This means that the last few years are missing from the archive in several lists. Are there any suggestions what I could do to still get them importet? Thanks! Johannes File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '@localhost>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 387, in handle importer.from_mbox(mbfile, report_name) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 212, in from_mbox progress_marker.tick(unquote(message.get("message-id", 'n/a'))) File "/usr/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range

2 years, 9 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > You're the "it's 2019, let's use SMTP UTF8 everywhere" guy, right? No, I'm not that guy. I've not said anything like that, nor have I knowingly configured Postfix to use that. I've looked up how to do it now that you mention it, and found the smtputf8_enable parameter[1]. I have not used it, but it turns out that it is enabled by default. I can turn it off and see if that makes any difference in the future. Testing with telnet, Postfix indeed announced "250 SMTPUTF8" on EHLO. > If you're right about the umlaut being the trigger, the first thing I'd look at is a feature-negotiation problem in the MTA delivering to Mailman. I'm pretty sure our LMTP does not offer the SMTP UTF8 feature. In that case the problem should go away with disabling SMTPUTF8, I suppose? > I would guess this is in the shunt queue. If there's only one file there, you can just delete it. There was a whole bunch of files in that directory. I've taken a look several of them, and as they were all spam, I've taken the liberty to delete them all (this list is so low volume that I know all the senders personally anyway). However, even after restarting mailman, the 500 error persists when visiting the held messages page in postorius. I've also looked into all the other queue directories, they were all empty. > Assuming you're right about your name being the trigger, U+FFFD REPLACEMENT CHARACTER is not in your name. I confess that I haven't visited the held messages page for a very long time (because I didn't have a reason to; I received no notifications of held messages). Only after I received the notification that my errorneous message was being held, I visited it, and I was faced with the 500 error. If Mailman failed to notify me of held messages previously, they might have been in hold status already and one of them might be the cause. Marvin [1]: http://www.postfix.org/postconf.5.html#smtputf8_enable PS: Sorry for the missing link [1] from the last mail. Here it is: https://gitlab.com/mailman/hyperkitty/issues/201 -- Blog: https://mg.guelker.eu

5 years, 10 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by brian＠emwd.com

> > Everything else works fine. Postfix is receiving and > > delivery mail to Mailman3. List members are receiving the posts. I can access the list on > > Hyperkitty just no archived messages. > What URL do you use to access HyperKitty. I use http://mailman3-lists.com/mailman3/hyperkitty/. However I changed the base-url from localhost to mailman3-lists.com and saw the same error except the URL reflected mailman3-lists.com instead of localhost. > The problem URL above, > http://localhost/mailman3/hyperkitty/api/mailman/archive is based on the > base_url setting in mailman-hyperkitty.cfg which in your case is > http://localhost/mailman3/hyperkitty/, byt the web server listening on > localhost:80 is returning the Service Unavailable. It probably doesn't > like the IP or name 'localhost'. I have this in the apache2.conf file: ServerName localhost I can access the apache default page when using the following: curl http://localhost.com > Set base_url in mailman-hyperkitty.cfg to use an acceptable host name > instead of localhost or adjust your apache config to accept localhost. Isn't ServerName enough? This error also appears in the apache log file when new posts are sent to the list: [Thu Apr 11 19:55:38.755750 2019] [:error] [pid 21370:tid 139988922513152] (32)Broken pipe: [client ::1:49574] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.769245 2019] [:error] [pid 21370:tid 139989049186048] (32)Broken pipe: [client ::1:49576] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.777583 2019] [:error] [pid 21370:tid 139988914120448] (32)Broken pipe: [client ::1:49578] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.787681 2019] [:error] [pid 21370:tid 139988905727744] (32)Broken pipe: [client ::1:49580] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.798273 2019] [:error] [pid 21369:tid 139989082756864] (32)Broken pipe: [client ::1:49582] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.807790 2019] [:error] [pid 21370:tid 139988897335040] (32)Broken pipe: [client ::1:49584] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.818123 2019] [:error] [pid 21369:tid 139989074364160] (32)Broken pipe: [client ::1:49586] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.827737 2019] [:error] [pid 21370:tid 139988888942336] (32)Broken pipe: [client ::1:49588] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.837612 2019] [:error] [pid 21370:tid 139988880549632] (32)Broken pipe: [client ::1:49590] sending data to httpd-UDS:0 failed [Thu Apr 11 19:55:38.848250 2019] [:error] [pid 21370:tid 139988872156928] (32)Broken pipe: [client ::1:49592] sending data to httpd-UDS:0 failed Brian

6 years, 6 months

[MM3-users] Re: Another interesting error...

by Darren Smith

OK chalk another one up to a python newbie... commit() was the magic sauce that we needed. The error 500 is no longer happening on that mailing list. We have three different lists so far that have gotten into this state, and we are going to work on the other two to make sure that this all works. FYI if this is fixed somehow in a later release (later than 3.1.0) we are working on migrating to the latest mailman code. -Darren On Mon, Apr 23, 2018 at 4:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 02:59 PM, Darren Smith wrote: > > Well, using the mailman shell we were able to find the request that was > > causing the problem - it was apparently a spam message that had some > > chinese characters in it. > > > I am trying to duplicate this issue in a test environment. I can create > a message with an invalid RFC 2047 encoded subject, i.e., > > Subject: =?gb2312?Q?=ff=fe=de=21=a2?= > > and send it to a list where it gets held, but I don't get a 500 in > postorius and I see the held message with a raw (not decoded) header. > > I think there were some recent changes that affect this. I'll look some > more. > > > > We used the shell to delete the held request... > > > > And postorius is still giving me an error 500. > > > > If I'm not mistaken the held messages are kept in .pck files - do you > know > > if when postorius asks for held messages through the API, does mailman go > > to the database or to the .pck? I would actually suspect the latter, or > > removing the request should have fixed the problem. > > > They were held in .pck files in Mailman 2.1, but not in Mailman 3. They > should just be in the database and deleting them via mailman shell > should delete them as long as you quit the shell or commit(). > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Abhilash Raj

On Wed, Apr 17, 2019, at 8:18 AM, Mark Sapiro wrote: > On 4/17/19 8:10 AM, Abhilash Raj wrote: > > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: > >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: > >>> > >>> Which version of Hyperkitty are you using? > >>> > >>> Did you upgrade the version of Hyperkitty when you migrated to the > >>> new host? > >> > >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple > >> releases), so it's hyperkitty 1.1.4. > >> > >> I didn't upgrade anything with the move. > > > > I am not sure where does Debian packaged version store it's fulltext index, but > > I am assuming the move somehow makes Hyperkitty not be able to read the > > index. > > > I think this is a known incompatibility between the Python 2.7 and > Python 3 versions of Whoosh. I *think* 1.1.x releases were based on Python 2.7, so that part looks right to me. > > From the tracebacks, the current HyperKitty is running under Python 2.7. > If the prior server was running HyperKitty with Python 3, that would > explain this. Given that 1.1.x supports only 2.7 and Ubuntu doesn't have 1.2 release, it is unlikely Python 3 was used. > > > Can you try removing and re-building the entire index? I don't know again > > the right command for Django there, but the hyperkitty command you want > > to run is called `rebuild_index`. For source package, something like: > > > > $ python manage.py rebuild_index > > > > Do note that this will take a lot of time if you have a big archive. > > > If this is the incompatibility, rebuilding the index will fix it. > > -- > 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)

6 years, 6 months

[MM3-users] Re: Google auth issue redirect_uri_mismatch

by Ugnius S

Thank You for the showing good road. Resolved! For Apache2 setup should look: ProxyPassMatch ^/static/ ! ProxyPass / http://127.0.0.1:8002/ ProxyPassReverse / http://127.0.0.1:8002/ ProxyPreserveHost On Kind regards Ugnius 2019-09-09, pr, 03:29 Abhilash Raj <maxking(a)asynchronous.in> rašė: > > > On Sun, Sep 8, 2019, at 2:12 PM, Ugnius S wrote: > > Hi. > > New question about configuration, maybe somebody has experience and know > > what I should change it. I have tried to implement Google authorisation. > > I have created Google credentials keys and successfully added using > Django > > admin page. > > I use UWSGI proxy for apache setup like "ProxyPass / > http://127.0.0.1:8002", > > UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects > to > > internal) What happens when I try Google auth... > > If I set Authorised redirect URIs: > > http://lists.example.com/accounts/google/login/callback/ , Google gives > me > > error 400 Error: redirect_uri_mismatch and requests for: > > http://127.0.0.1:8002/accounts/google/login/callback/ > > If I set that requested address to Google, then Google authorises > me, > > but and after authorisation redirects to > > http://127.0.0.1:8002/accounts/google....../.... (very long line) Of > > course this internal address does not open, but... > > If I just manually replace part of address just: > http://127.0.0.1:8002 > > replace to https://lists.example.com/.../...(long line) this makes me > get > > in as authorised user to the page. > > How to make django to send external request to Google? Because > > Google should not point back to internal address... This seems simple, > but > > I do not find what I should change in the configuration: Apache or Django > > or uwsgi.ini I hope anybody of You have experience and made it to run. > > You need to set this in nginx under your location directive, where you > setup your proxy_pass or uwsgi_pass > > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > Something similar should exist for Apache. > > > > > Kind regards > > Ugnius > > _______________________________________________ > > 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) >

6 years, 1 month

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Correction. Not 22.04. I'm trying 24.04. Am 2024-04-25 13:35, schrieb Thomas Stein: > Howdy! > > I'm trying to migrate an aged mailman3 installation from ubuntu 20.04 > to ubuntu 22.04. Fresh install of mailman3-web gives me: > > Creating config file /etc/dbconfig-common/mailman3-web.conf with new > version > creating database mailman3web.db: success. > verifying database mailman3web.db exists: success. > > Creating config file /etc/mailman3/mailman-web.py with new version > /usr/lib/python3/dist-packages/django_q/conf.py:174: UserWarning: Retry > and timeout are misconfigured. Set retry larger than t > imeout,failure to do so will cause the tasks to be retriggered before > completion.See https://django-q2.readthedocs.io/en/maste > r/configure.html#retry for details. > warn( > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > mailman3-web > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) > > I've already seen this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > ...but that does not get me anywhere. > > Could someone please push me in the right direction? > > cheers! t. > _______________________________________________ > 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 himbeere(a)meine-oma.de

1 year, 6 months

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 10:29 AM, Dmitry Makovey wrote: > On 09/27/2017 10:20 AM, Abhilash Raj wrote: > > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >>>> I've come across mailman-cli docs: > >>>> > >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >>>> > > > > This is basically one of our GSoC projects which hasn't yet been merged > > with MailmanClient. It uses the REST API to to provide a command line > > client for Mailman, while there hasn't been any in-compatible changes in > > API since this project was finished, I am not sure about the current > > status of it. > > > >>>> yet I cannot figure out what's the official source for the installation. > > > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > > and it doesn't have a CLI, the Github project you linked to says right > > on the top that it is not official project (Thanks for that Rajeev!). > > I did see that, thus I was asking the question here. > > > Also, I would say not to use this client to remotely access Mailman, the > > REST API is not meant to be exposed over internet (unless you have a VPN > > or other sort of setup to securely access the box remotely). > > > > in my case - I need to use REST API since we're deploying with docker > and pieces that need to integrate with mailman commands now live in a > different container (and very likely on a different machine). I do need > to be able to execute commands remotely - I can handle securing of that > connection, but it is not an option for me to run "fat" docker > containers thus the only interconnect is via sockets (either UNIX or > TCP). The CLI project is basically a Shell+CLI based on MailmanClient (python library for Mailman API) and Mailman Core's REST API. So, if I understand correctly, this would run commands over REST API like you want. -- Abhilash Raj maxking(a)asynchronous.in

8 years, 1 month

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. I tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

4 years, 8 months

[MM3-users] Re: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On 04.01.19 10:44, Abhijith PA via Mailman-users wrote: > Hi. Thomas > > On Friday 04 January 2019 02:10 PM, Thomas Stein wrote: >> On 04.01.19 05:15, Stephen J. Turnbull wrote: >>> Thomas Stein writes: >>> >>> > Thanks for your answer. So the the file in queue/shunt contains >>> > information too? I will have a look. >>> >>> The file in queue/shunt is the message plus some Mailman metadata, as >>> a Python pickle. You can find out what is in it using "bin/mailman.py >>> qfile", but probably the log and traceback will tell you (or us) >>> everything needed to fix the problem. >>> >>> If it's a Mailman bug (somewhat unlikely), we send you a patch and you >>> use "bin/mailman.py unshunt" to reinject the message into the mail >>> system via Mailman. If it's a nonconforming mail message (somewhat >>> more likely -- typically this happens when you have raw UTF-8 or other >>> 8-bit characters in the message header), then the easiest thing to do >>> is to edit a saved copy of the message and resend from your mail >>> client. (It's theoretically possible to edit the pickle and use >>> "unshunt", but Mailman currently does not provide that feature.) >> >> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >> i missed something else but after adjusting the permissions of that template everything worked as expected. > > > Can you explain little bit more about this template, path and its > permission ? Sure. I should start with mentioning the mailing list in question was imported with "mailman import21". After that i had: root@shinymail:~# ls -l /var/lib/mailman3/templates/lists/hoppla.domain.de/en/ total 8 -rw-rw---- 1 list list 106 Dec 26 18:48 list_member_digest_footer.txt -rw-rw---- 1 list list 110 Dec 26 18:48 list_member_regular_footer.txt root@shinymail:~# These txt files where owned by root:root. After changing it to list:list the problem disappeared. cheers t. > --a > _______________________________________________ > 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/ >

6 years, 10 months

[MM3-users] Re: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > It seems Microsoft Azure uses SAML2 authentication. When you say > "(what software, what requirements, what ID-related attributes are > available)" -- they just Nobody ever stops at "just". ;-) > want them to authenticate to the mailman listserve using > AZURE. What attributes besides username would have to be passed to > Mailman? The only attribute *needed for authentication* is username. But users are unlikely to be satisfied, and the straightforward implementation that I'm using has a number of implications that happen to work for my client, but I'm pretty sure would not be satisfactory in some other environments. 1. Users in my environment expect their profiles (display name, time zone) to be populated. (I haven't figured out how to do the latter, but it's a company with overseas offices, "that's the server's time zone" is acceptable.) Lack of first name, last name was considered a showstopper, though. In your environment there may be other attributes you'd like to add, but I think in stock Mailman 3 those (plus email, see point #2) those are all the attributes you would like to populate from the ID provider. 2. Owners and moderaters *need* their emails in the profile to be linked to their existing lists migrated from an existing Mailman 2 site (and maybe to future lists they admin, I haven't checked in detail). But confirming an email address is an annoyance you'd probably like to avoid. 3. The REMOTE_USER approach we use authenticates on every request, before the login screen is invoked. This means that superusers known to the network can't have a separate account; you need to give their personal users superuser privilege. This doesn't matter in my environment; the lists are used mostly for customer service, the admins with superuser normally don't interact with lists, so this actually increases accountability. (I don't think there's a "sudo" or "drop privileges" feature in Django.) This wouldn't be desirable in my university environment, as many of the superusers are faculty members who teach classes and supervise lists for their classes. So, yeah, all you *need* is the username, but I'm willing to bet you will be askeed to deal with some of those other issues. And again, the only SAML Service Provider I know how to configure is Shibboleth. Steve

2 years, 4 months

[MM3-users] Re: update_index

by Darren Smith

OK - next issue...here's the warning that I'm receiving when I run that: /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date received a naive datetime (2018-04-03 07:51:25) while time zone support is active. RuntimeWarning) I'm not sure that anything else occurred. The indexing took 2 seconds, and there have been tens of thousands of emails imported since the last index. Thoughts? -Darren On Tue, Apr 3, 2018 at 10:55 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Holy cow I think that's exactly what the problem is. I will give that a > try and let you know what happens! > > On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/03/2018 09:02 AM, Darren Smith wrote: >> > Hello, >> > >> > If I'm reading the docs correctly, when we run manage.py update_index, >> it >> > should be an incremental index of new emails that have been added since >> the >> > last time update_index was run - can anyone confirm that this is the >> > expected behavior? Or is there another command line option that I am >> > missing? >> >> >> There are two ways to run update_index. >> >> Hyperkitty's update_index is incremental and is run by >> >> manage.py runjob update_index >> >> Running >> >> manage.py update_index >> >> runs haystack's update_index which with no options does a full update. Run >> >> manage.py update_index --help >> >> to see the options. The incremental 'manage.py runjob update_index' >> should be run every minute by 'manage.py runjobs minutely' assuming cron >> is running the periodic Django jobs, so running either update_index job >> manually shouldn't be necessary >> >> >> ... >> > So...can anyone help with how to get the update_index to do only emails >> > added since the last time the update_index was run? >> >> >> manage.py runjob update_index >> >> -- >> 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/ >> > >

7 years, 7 months

[MM3-users] Re: Emergency Moderation

by Allan Hansen

> On May 24, 2020, at 11:34 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/24/20 10:59 AM, Allan Hansen wrote: >> In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. >> I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. > > >> My own current top-of-the-list issues: >> >> A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? I can only speak for my own application of MM3: Desiring consistency between the lists, I don’t want to turn all the moderators into owners who can change list settings. Many of my moderators keep asking me to see the list of members and to subscribe and remove members. I end up servicing those requests. So... a. Moderators should be able to unsubscribe and subscribe members. b. Moderators should be able to set the member’s moderation status. c. Moderators should not be able to see/modify any other member settings. > > >> A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Awesome!!!! Thank you, Allan > > -- > 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, 5 months

[MM3-users] Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 21:19, Abhilash Raj wrote: > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >> >> I restarted de server and the error changed. Now the log >> shows "KeyError: 'subscription_mode'": >> >> Did you also restart Mailman Core after the upgrade? >> >> Yes, indeed: I stopped mailman core and all the processes related. >> Did the upgrades. Started all again. Find the errors in the web user >> interface. Stopped all again. Looked for errors in the log. Restarted >> the complete server. Found the second error that this second mail is >> about to. It happens when, in the main page that shows all the lists >> you click to see one of them. It seems to me that it has been >> database structure changes in django that the upgrade is not aware... >> but it's a very long shot from my side. > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > a derived atrribute and not stored in Database. Mailman's API should be > returning this attribute for each Member, but for some reason it seems > to me like it isn't doing that even though do have Mailman 3.3.3 running > like you said. > If you have Curl installed, can you send me the output of: > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 This is the output you asked for (it's the same you can see when you try to interact with one list): /usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> No log entry has been produced... TIA. > It should ideally return an output that looks something like shown > here[1]. You > can put the username/password of Core's API server in the above command. > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Abhilash >> I'm using sqlite as django database and mysql for mailman. >> >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >> Server Error: >> /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'subscription_mode' During handling of the above exception, >> another exception occurred: Traceback (most recent call >> last): File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner response = get_response(request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response response = >> self.process_exception_by_middleware(e, request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response response = >> wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view return self.dispatch(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch return super(MailingListView, >> self).dispatch(request, *args, **kwargs) File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch return handler(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >> line 295, in get member.subscription_mode == File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute >> 'subscription_mode' *********************** some info about >> the installed versions via pip list: pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 pip list | grep postorius >> postorius 1.3.4 On 6/2/21 11:12, >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I've just upgrade mailman 3 installation following Mr. >> Sapiro advice: did a pip install --upgrade >> django-mailman3 hyperkitty mailman mailmanclient >> mailman-hyperkitty postorius I did a "python3 manage.py >> migrate" after, too. And all seemed to run well. All the >> lists showed in postorius via web, but when I try to >> accesss into one of them the browser shows an error. In >> the log you can see: *-*-*-*-*-*-* Traceback (most recent >> call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'get_requests_count' .. (And after all the traceback >> lines) AttributeError: 'MailingList' object has no >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >> seem to be distributing messeages well.. but I cannot >> acces via web administration (django/postorius) Can >> anyone point me in the right direction to solve this, >> please? _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send >> an email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users >> mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an >> email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users mailing >> list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >> mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>

4 years, 8 months

[MM3-users] Re: Removing a mail addresses and users

by Abhijith PA

Hi Mark, On 11/06/20 1:16 am, Mark Sapiro wrote: > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) In my case these user signups were just to test postorious. These mail accounts didn't subscribed to anything. >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > Thanks for the link, let me try that out. --abhijith

5 years, 4 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by kelly.close＠lrewater.com

I'm adding to this thread because I'm running into the 403 HyperKitty failure (Access is forbidden) and adding my public ip address to the MAILMAN_ARCHIVER_FROM variable did not do the trick. I'm at a loss as to what might be going on so I'm hoping someone is willing to put fresh eyes on this. All other aspects of this new are site working. It's worth noting that I set up this new install and then restored database backups of mailman3 and mailman3web from my previous install, and also copied over the /var/lib/mailman3 folders (but I left behind the contents of the cache folder). I can see in the apache access log that the attempts are coming from the public IP, and it shows the archive key I'm using also: 54.71.5.180 - - [20/Jun/2020:09:51:01 -0600] "POST /mailman3/hyperkitty/api/mailman/archive?key=<mykey> HTTP/1.1" 403 4151 "-" "python-requests/2.18.4" Here's my ARCHIVER_FROM variable setting: MAILMAN_ARCHIVER_FROM = ('127.0.0.1','::1','54.71.5.180') The apache error log has "broken pipe" messages which Mark said in are just the normal outcome of the failure and not a clue. The mailman.log had both 403 (Access is forbidden) and 503 (Service Unavailable) errors, but the 403 errors come first and I think the 503 is just the result of not having access = here's what the 403 error looks like, right after the successful message posting: Jun 20 09:50:59 2020 (29587) ACCEPT: <20200620155058.1324.27893@mailman3> Jun 20 09:51:00 2020 (29591) HyperKitty failure on https://udfcd-lists.org/mailman3/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1></body></html> (403) I verified (like a thousand times) that: MAILMAN_ARCHIVER_KEY (with quotes, in mailman-web.py) = api_key (without quotes, in mailman-hyperkitty.cfg) And for fun, here's my base_url. base_url: https://udfcd-lists.org/mailman3/hyperkitty/ I've tried it with http instead of https, and also and with the original //localhost/. With it set to localhost I get an ssl.CertificateError stating that localhost does not match any of the certified domains, which I think is because certbot sets you up with Virtual Hosts when you install the certificates so I need to have the base_url set to my actual domain and use the ARCHIVER_FROM variable to allow the IP address - I think I have all that set up right but still...forbidden. I've run out of things to check - any thoughts out there? Thanks! ~Kelly

5 years, 4 months

[MM3-users] UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, I've accidentally sent from an unregisted address to one of my lists. Mailman correctly held the message back for moderation, but when I go to the page for held messages in postorios, I receive a 500 error. I've included an except from the log below. To me, it looks as if it errors on processing my last name (which has a non-ascii character in it). This is Postorius 1.1.2 on Ubuntu 18.04 LTS from the repos. I've searched on the tracker for the problem and found one ticket[1], but it has something with logging so I suppose this is a different problem. Ideas? And how do I discard the message without access to the held messages page? Python version is 3.6.8. Log excerpt: Dec 09 13:21:04 2019 (3090) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128) Dec 09 13:21:04 2019 (3090) 127.0.0.1 - - "GET /3.0/lists/tsc-devel(a)lists.secretchronicles.org/held?count=10&page=1 HTTP/1.1" 500 59 -- Blog: https://mg.guelker.eu

5 years, 10 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

Dear Mr. Turnbull, dear blackout69, thank you very much for your answers. Below this text you will find a brief documentation how I finally managed to install mailman3 and mailman3web packages under Debian 11 with a remote PostGreSQL server v10.22. Maybe there is a more elegant way to install both packages correctly, but AFAIK any solution will be only a workaround for the main problem, that the DBA's password is usually unknown during the whole installation process if you use a remote database server that is run by another staff team. Best regards, Markus ------------ 8< ------------ Mailman3 installation ===================== 1. Installation mailman3 2. Installation mailman3web 3. Integration in boot sequence 1. Installation mailman3 ------------------------ Once the remote database server has been set up with databases mailman3 and mailman3web and with a database user mailman3 that has access to both databases, create database mailman3; create database mailman3web; create user mailman3 with encrypted password 'streng_geheim'; grant all privileges on database mailman3 to mailman3; grant all privileges on database mailman3web to mailman3; the package mailman3 can be installed: # apt install mailman3 To avoid the DBA password prompt that ususally cannot be answered if the database server is run by another team, the installation tool dbconfig-common should be omitted: * Configure database for mailman3 with dbconfig-common? No The mailman3 package will be installed without errors. The configuration of the database connection can be done in file /etc/mailman3/mailman.cfg: ... class: mailman.database.postgresql.PostgreSQLDatabase ... url: postgres://mailman3:<secret>@<host>:<port>/mailman3 At this point the required tables have not yet been created in the database. Therefore, the mailman3 package should be configured again: # dpkg-reconfigure mailman3 Because the database mailman3 already exists on the database server, it does not need to be recreated using dbconfig-common: * Reinstall database for mailman3? No * Add the HyperKitty configuration to mailman.cfg? No Also moving the HyperKitty configuration to /etc/mailman3/mailman.cfg is not necessary at this time. After dpkg-reconfigure has finished, all necessary tables do now exist in the database mailman3: mailman3=> \dt List of relations Schema | Name | Type | Owner --------+--------------------+-------+---------- public | _request | table | mailman3 public | acceptablealias | table | mailman3 public | address | table | mailman3 public | alembic_version | table | mailman3 ... An initial start of the service mailman3 shows no errors: # systemctl start mailman3 # systemctl status mailman3 ● mailman3.service - mailman3 server. Loaded: loaded (/lib/system/system/mailman3.service; enabled; vendor default: enabled) Active: active (running) since Thu 2022-11-03 10:10:29 CET; 11min ago. ... 2. Installing mailman3-web -------------------------- Once the mailman3 package is installed, package mailman3-web can be installed: # apt install mailman3-web This time you should not do the installation process without the help of the installation tool dbconfig-common: * Configure database for mailman3 with dbconfig-common? Yes * Database type to be used by mailman3-web: pgsql * Host name of the PostgreSQL database server for mailman3-web: new host * Host running the PostgreSQL server for mailman3-web: <remote host> * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> Even if the DBA password prompt cannot be answered: Create configuration file /etc/dbconfig-common/mailman3-web.conf with new version Password for user postgres: ?????? the dbconfig-common tool should be used again: * Next step for database installation: retry * Configure database for mailman3-web with dbconfig-common? Yes * Connection method for PostgreSQL database of mailman3-web: TCP/IP * Host name of the PostgreSQL database server for mailman3-web: <remote host> * Port number for the PostgreSQL service: 5432 * Method for authenticating the PostgreSQL administrator: password * Method for authenticating PostgreSQL user: password * PostgreSQL database name for mailman3-web: mailman3web * PostgreSQL username for mailman3-web: mailman3 * PostgreSQL application password for mailman3-web: <secret> * Password confirmation: <secret> * Name of the database's administrative user: postgres * Password of your database's administrative user: sldjkfhskldfjhyxlökcjy The prompt for the DBA password cannot be answered correctly again, therefore "ignore" should now be the best choice for the further course of the installation process: * Next step for database installation: ignore * Password of your database's administrative user: sldjkfhskldfjhyxlkcylö An error does occur now because the database user mailman3 can not be created: ... Password for user postgres: unable to connect to postgresql server. error encountered creating user: psql: error: fe_sendauth: no password supplied ... But this error doesn't matter, because the database user mailman3 does already exist and the installation process of the package mailman3web will nevertheless be finished completely. A look into file /etc/mailman3/mailman-web.py shows that dbconfig-common has entered the database connection to the database server correctly, too: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman3web', 'USER': 'mailman3', 'PASSWORD': '<secret>', 'HOST': '<remote host>', 'PORT': '', <--- missing? 'OPTIONS': { }, } } Also all required tables have been created in the database mailman3web during the installation process: mailman3web=> \dt List of relations Schema | Name | Type | Owner --------+-----------------------------------+-------+---------- public | account_emailaddress | table | mailman3 public | account_emailconfirmation | table | mailman3 public | auth_group | table | mailman3 public | auth_group_permissions | table | mailman3 public | auth_permission | table | mailman3 ... The initial start of the service mailman3-web shows no errors: # systemctl start mailman3-web # systemctl status mailman3-web ● mailman3-web.service - Mailman3-web uWSGI service. Loaded: loaded (/lib/system/system/mailman3-web.service; enabled; vendor default: enabled). Active: active (running) since Thu 2022-11-03 10:42:30 CET; 11min ago ... 3. Intergration in boot sequence -------------------------------- Finally, the two services mailman3 and mailman3-web can be included in the boot sequence: # systemctl enable mailman3 Synchronize the state of mailman3.service with the SysV service script with /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3 # systemctl enable mailman3-web Synchronize the status of mailman3-web.service with the SysV service script using /lib/systemd/systemd-sysv-install. Runs: /lib/systemd/systemd-sysv-install enable mailman3-web ------------ >8 ------------ On 01.11.22 08:10, Stephen J. Turnbull wrote: > blackout69 writes: > > > For mailman3 > > sudo dpkg-reconfigure mailman3 > > > > For mailman3-web > > sudo dpkg-reconfigure mailman3-web > > I guess those will work too as long as the users and databases have > been created. But they'll still fail at the first step without that > (and they might fail anyway if checking for the existence of those > users and databases involves logging in to the database as the admin > user). > > _______________________________________________ > 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/ -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

3 years

[MM3-users] Re: Rejection based on total message size including attachments

by Mark Sapiro

On 09/19/2018 03:34 PM, leith(a)khimaira.com wrote: > As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. > > Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Is this a Mailman 3 question or a Mailman 2.1 question? If Mailman 3, the architecture is quite different. This would be done with a rule, not a handler, but based on details in your question, I think you are asking about Mailman 2.1. In that case, the appropriate list is really mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>, but since you're here, the basic info on custom handlers for MM 2.1 is at <https://wiki.list.org/x/4030615>. There is an example called MyHandler.py linked from that page. It won't do what you want but can be used as a starting point. Also, look at Mailman/Handlers/Hold.py, in particular the code following the "# Is the message too big?" for how to determine the message size. That handler will compare the size to the list's max_message_size and hold the post if it's too big. You probably want to compare the size to a fixed value or a size defined in mm_cfg.py and either reject or discard the message. If you put your handler between Moderate and Hold, it's probably safe to reject the message because it is from a member or an address in accept_these_nonmembers. Rejecting post from arbitrary non-members is a bad idea because of spam backscatter. If you need more help, please join mailman-users(a)python.org and post to that list. In any case, this could be generally useful enough that I will probably add it to the stuff at <https://www.msapiro.net/scripts/>. -- 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: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

Yeah I'll set up some advanced debugging in Postfix on the relays to see whats' coming in and out. Will take time though 'cause we have a TON of messaging going through that smtpproxy out to the 'net so it'll take a bit for me to dissect the message logs. Give me a bit since it's EOD for me now. Thomas On 12/6/23 15:44, Mark Sapiro wrote: > On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: >> See, that's the oddness. There appears to be SOME weird mail loop >> here where $ORIGIN (MS365/Exchange) hands it once, then there's >> back-and-forth between SMTPPROXY and Mailman. IT's really odd how it >> behaves, and I have no explanation for it. >> >> Right now I'm away from the office where this happens, but when I'm >> back there I'll grab logs from both sides. >> >> >> Thomas >> >> On 12/5/23 17:54, Mark Sapiro wrote: >>> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>>> We use a multi-hop SMTP system to go from the inside of our network >>>> out to the Internet at the domain test.lists.example.com. >>>> >>>> The setup is this way for ingress: >>>> >>>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>>> Connector) -> Mailman for delivery to listserv > > > Presumably the EXTERNAL to MS365 SMTP transaction includes > > MAIL FROM: <user(a)example.com> > RCPT TO: <invalid(a)test.lists.example.com> > > It seems that somewhere in the path to Mailman this is getting changed to > > MAIL FROM: <invalid(a)test.lists.example.com> > > so the outbound DSN is sent to invalid(a)test.lists.example.com instead > of user(a)example.com. The question is which one of the MTAs in the path > is doing this and why. > > But even more mysterious is the fact that the DSN from Mailman should > be sent with > > MAIL FROM: <> > > so when it's undeliverable, no further DSN is sent. >

1 year, 10 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Abhilash Raj

On 9/8/21 3:39 PM, Patrick Brückner wrote: > Hi everyone, > > one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. > > What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. > > The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. > > Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. > > According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. > > Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? You are probably on an old version of Mailman which didn't expose the values in API and also Postorius didn't expose it in UI. You can install a new version manually by downloading new debs from Debian unstable repos (I don't know if Ubuntu just copies the ones from Debian or has their own packaging, I think it is former) that have newer built debs. On your version, you probably would be able to set the accept_these_nonmembers using the command line using ``` mailman withlist -l test(a)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 test(a)example.com mailing list >>> m.accept_these_nonmembers ['*.example.com'] >>> m.accept_these_nonmembers = [r'*.example.com'] >>> commit() >>> quit() ``` -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello guys, This is what I've got on ../var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db What should I do in order to let mailman install the DB files? Thanks El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > 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, 3 months

[MM3-users] Re: logrotate

by Christian

Thank you! Would I run your script weekly in cron or ? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, May 2, 2023 4:37 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: logrotate 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/me > ssage/ > 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 _______________________________________________ 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/ JTUKYJDD5Y5JIAVK3OOFNVCK4CVDGK6O/ This message sent to csa(a)web-analysts.net

2 years, 6 months

[MM3-users] Re: getting all registered users and their lists

by Mark Sapiro

On 1/27/22 00:06, IOhannes m zmoelnig wrote: > On 1/26/22 17:19, Mark Sapiro wrote: >> On 1/26/22 00:16, IOhannes m zmoelnig wrote: > >>> is there a scriptable way to get all users that have registered in my >>> mailman3 (3.2.1) instance and which lists they are subscribed to (if >>> any)? >> >> It's in Postorius >= 1.3.6 > > i'm not entirely sure how this relates to the above (working) snippet. > > is it, that with postorious>=1.3.6 i would be able to perform that task > from the webinterface, rather than having to resort to 'mailman shell'? Not really. In Postorius 1.3.6 there is a `Users` view that will display users and their create date and it is ordered by create date. Then each user's entry has a `Manage` button which goes to a page which among other things, lists their subsubscriptions. So, you could find the users of interest via this interface, but unless you developed a screen scraping script, it would be a multi-step manual process. > in any case, this might be related: > before i received your email with the 'mailman shell' snippet, i scraped > some bits of my django knowledge and visited > <https://lists.example.com/admin> (the django admin interface), and > noticed the list of users there. > so i scraped that page for users (assuming that this was the list of > registered users). > then i get myself a list of all subscribers in my instance, using a > crude `mailman lists | grep "@" | while read l; do mailman members > "${l}"; done | sort -u`. > finally i calculated the difference between the two sets. > > interestingly the results are quite different from the ones i got from > your script: both sets contain users that are not in the other set. > how come? My script deals with Mailman users who may or may not be Django users. They won't be if they never signed up on the web UI. On the other hand, anyone can go to the web UI and sign up and become a Django user even if they never join any list and become a Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Fwd: Incoming command emails (i.e. listname-leave) routed to list itself

by Stephen J. Turnbull

This was my bad. For about 20 years now, I myself never used mail commands except subscribe and my Mailman 3 users have *always* used the web interface. And as you might guess, the exim4 config was developed by tweaking a Mailman 2 config until it worked for me. Thank you for diagnosing and documenting a more configuration, Abhilash! Steve Abhilash Raj writes: > Hi Mark, > > Excerpts from Mark Lindsay's message of April 20, 2017 5:37 pm: > > <snip> > > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > > potato-leave(a)lists.mydomain.org email: > > > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > > succeeded] > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > > H=localhost [127.0.0.1] C="250 Ok" > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.o > > rg > > > >> `? > >> > > > > I think this is actually an exim4 problem, so if the solution is to just > > switch to postfix, then I will definitely do that. But I'm just asking in > > case someone had a similar issue with exim4 and was able to work through > > it. > > > > > Yes, I had the exact same problem very recently and was able to fix it. The > updated documentation[1] should fix your problem. The basic gist of the > problem > is that the exim configuration on the older documentation is missing a > critical > part. > > Exim4 by default strips off any prefixes/suffixes when delivering mail to > the > mailman, which causes mailman to post all the messages to mailing list > instead > of processing them as commands. > > `rcpt_include_affixes = true` > > Adding the above line to the transport fixes that problem. > > [1]: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mt > a.html#exim4-configuration > > thanks, > Abhilash >

8 years, 6 months

[MM3-users] Memory usage

by Adi Kriegisch

Dear all, I've been using mailman2 for quite some time and I am considering upgrading to mailman3. In a test setup I noticed that mailman3 with just a basic setup (Debian with mailman3 package and sqlite as backend using exim4) uses over 700MB RAM (RSS): | USER VSZ RSS COMMAND | list 73072 54568 /usr/bin/python3 /usr/lib/mailman3/bin/master | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 | list 73100 54572 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1 | list 73100 54560 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=command:0:1 | list 73100 54600 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=in:0:1 | list 146832 54700 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=lmtp:0:1 | list 73100 54808 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=nntp:0:1 | list 73100 54652 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=out:0:1 | list 73100 54504 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=pipeline:0:1 | list 150516 58228 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=rest:0:1 | list 73100 54508 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=retry:0:1 | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=virgin:0:1 | list 73100 54608 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=digest:0:1 This is with only one test list configured that just has one member. Compared to a mailman2 setup with many lists with up to 300 members that only uses around 70MB RAM: | USER VSZ RSS COMMAND | list 63724 1396 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -q start | list 62896 10660 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s | list 61156 1792 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s | list 58148 1808 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s | list 73116 23316 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s | list 55464 1672 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s | list 65840 11868 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s | list 62036 10840 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s | list 58716 5712 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s This is without hyperkitty or a management interface, just mailman3 core that uses 10 times as much ram as mailman2. Did I do something wrong here? Is there probably a bug in my python environment? Are there any config options that I should set to avoid this huge memory footprint? I found one thread[1] on this mailing list where a user asked a question similar to mine with comparable numbers. best regards, Adi Kriegisch [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…

7 years, 1 month

[MM3-users] Re: The doubled entries issue

by Lars Bjørndal

[Abhilash] > On Sat, 11 Nov 2023, at 10:15 PM, Stephen J. Turnbull wrote: > > Lars Bjørndal writes: > > > > > > raise ComponentLookupError(interface, name) > > > zope.interface.interfaces.ComponentLookupError: > > > (<InterfaceClass mailman.interfaces.listmanager.IListManager>, '') > > > > That says that "python scriptname.py" need the IListManager interface > > but can't find it. You didn't provide enough information to explain > > why that might be, so I'm not going to guess. > > This is mostly because of trying to run script with `python scriptname.py` > but since it doesn’t initialize the mailman’s zope system. > > What you probably want to do is run the script using `mailman shell —run` > command, which will ensure that it runs the script after initializing the > zope components (and other mailman config and things are initialized too). Thank you. The script I try to run, is found here: https://gitlab.com/mailman/mailman/-/issues/657 I named the script fix-doubled-entries.py. When I try `mailman shell --run ./fix-doubled-entries.py` I get: Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/commands/cli_withlist.py", line 282, in shell r = call_name(dotted_name, *run_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) ^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/importlib/__init__.py", line 121, in import_module raise TypeError(msg.format(name)) TypeError: the 'package' argument is required to perform a relative import for './fix-doubled-entries' How should I invoke the script? Thanks, Lars

1 year, 11 months

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Mark Sapiro

On 09/30/2018 11:42 PM, Thomas G wrote: > Hi, > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > install in Mailman3.2. > > I didn't found how migrate the archives. >>From : HyperKitty - Version: 1.1.1 - Python2.7 > To : HyperKitty - Version: 1.2.1 - Python3.5 As Abhilash said, you shouldn't need to migrate anything but the search index. > I exported a mbox from hyperkitty (web interface) and tried to re-import > it, without result. > """""""""""""""""""""""""""""""""""""""" > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > listedetests(a)hatlab.fr You can't import a gzipped mbox. You have to gunzip it. > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index is not updated for this list. It will not be > updated by the 'minutely' incremental update job. To update the index > for this list, run the 'manage.py update_index_one_list > listedetests(a)hatlab.fr' command. > """""""""""""""""""""""""""""""""""""" > The database stay empty (and web interface): > """""""""""""""""""""""""""""""""""""" > mailmandbnameprod=# select * from hyperkitty_email; > id | message_id | message_id_hash | subject | content | date | timezone > | in_reply_to | archived_date | thread_depth | thread_order | > mailinglist_id | parent_id | sender_id | thread_id | sender_name > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > (0 rows) > """""""""""""""""""""""""""""""""""""" > > Any idea to do this importation ? Why is the database empty? It should be as it was with the prior HyperKitty. Also, it doesn't seem to be the issue here, but if you don't specify a --since option to hyperkitty_import, it won't import any messages older than the most recent message in the existing archive. i.e., if there are any messages in the existing archive, the default for --since is the date of the most recent such message. -- 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: Moderate mails from owner

by Mark Sapiro

On 4/30/19 1:04 AM, Henrik Rasmussen wrote: > @Mark: I am really sorry for the delayed responses, but this is a very low frequency list. I have subscribed to the list using a non-Microsoft address to see the outcome. > > The mails does indeed contain 'X-Mailman' headers. > > X-Mailman-Rule-Hits:nonmember-moderation > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation It looks like the message hit the nonmember-moderation rule and was accepted. This can happen in a few ways: First we determine the senders. Assuming the config is default, these are the addresses in From:, the envelope sender, and addresses in Reply-To: and Sender: if any. The only address I can see in the message headers that hasn't been altered by Mailman is the From: and maybe Reply-To: which you have munged to [LISTNAME](a)senderdep.example.com. Anyway that unmunged address and possibly others from the original incoming message will be users of the list with role nonmember. Now each of those (possibly only the one) nonmember(s) is checked for a moderation action. Since the message does not appear to have been held or processed through rules beyond nonmember-moderation, we presumably found a moderation action of accept. This can happen in a few ways., If this list was originally imported from Mailman 2.1 by the 'mailman import21' command, there may be a legacy accept_these_nonmembers attribute for the list. If so, and if a nonmember sender address matches an address or pattern in the list's accept_these_nonmembers, the message will be accepted. Otherwise if the moderation_action for a nonmember sender address is accept the message will be accepted. You need to check the list's accept_these_nonmembers attribute and the non-member address's moderation action. If you have recent Postorius, you can see nonmembers and their options from the 'users' -> Non-members view. In any case, you can do something like mailman shell -l list.example.com Welcome to the GNU Mailman shell The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers returns a possibly empty list Then for the sender addresses >>> memb = m.nonmembers.get_member('sender address') >>> memb.moderation_action This may return <Action.accept: 3> in which case you may want >>> memb.moderation_action = m.default_nonmember_action -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Abhilash Raj

On Wed, Nov 25, 2020, at 9:24 AM, Mark Sapiro wrote: > On 11/24/20 7:22 PM, Abhilash Raj wrote: > > > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). > > > It's more complicated than that. Sometimes the fragment name is the > heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor > #3.3.3 work at all as these are #id2 and #id1 respectively. Currently > the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is > #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs > under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but > when a Command line section is added under 3.3.3, that will probably get > the command-line id. > > Thus, the note "Permalink to this headline" es misleading at best > because it isn't very permanent fo an evolving document. Yeah, I was thinking about internal references, `:ref:` which accepts heading names, but anchors aren't added you are right. > > > > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. > > > I too think this is correct. I suppose it might be worth doing for > NEWS.rst in particular since Sphinx doesn't seem to like fragments like > n.n.n. Another way to deal with this would be to always use code names. > It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. > `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` Yep, I created news-3.3.3 for 3.3.3 and we can keep the convention going. I tested it out and it worked for me. https://gitlab.com/mailman/mailman/-/merge_requests/736 > -- > 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)

4 years, 11 months

[MM3-users] Re: Message IDs

by Mark Sapiro

On 10/15/21 3:19 AM, Philip Colmer wrote: > > I'm not sure that the message ID identifies the author, does it? No, but it identifies the message, and while Mailman has made some cosmetic modifications to the headers, it is still the same message. > I've just done a quick test of sending myself an email and then replying to it. > > The original email has a message ID of > CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com > > In the reply, the following headers are present: > > References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > In-Reply-To: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > Message-ID: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> > > Would it be reasonable for Mailman 3 to use "References:" to keep the > original Message ID and then add a new Message ID? No, because the message from the list is not a reply to the incoming message. It is the incoming message. > I think that what Mailman 3 is doing is similar to forwarding the > email. If I forward an email, again the headers change: If you want Mailman to 'forward' the message, set DMARC mitigation action to wrap the message. >> The IETF has addressed the issue of non-identical but equivalent >> messages with the Resent-Message-ID field (and in general the whole >> suite of Resent-* fields. > > Mailman doesn't appear to be adding that header. Would that be an > acceptable solution instead of the one I suggested above? Mailman doesn't add the header, but even if it did, I doubt it would solve the problem with Gmail. > I appreciate your view that Google is broken. I'm just trying to find > an acceptable solution to the end-user perception of "I've sent an > email to the list but I haven't received a copy back". That is going > to be a big issue/headache for us. It's a long standing PITA with Google. See <https://wiki.list.org/x/4030680>. Your Gmail users can partially mitigate this by setting their Acknowledge posts option to Yes. Note also that Mailman core communicates with archivers to determine what goes in the Archived-At: header and this value is usually based on the Message-ID:. Changing the Message-ID: could possibly render that value incorrect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: hyperkitty failed to create a thread

by tlhackque

On 11-Feb-19 13:01, Abhilash Raj wrote: > On Mon, Feb 11, 2019, at 9:55 AM, Marvin Gülker wrote: >> Hi, >> >> Am 11. Februar 2019 um 19:47 Uhr +0200 schrieb Danil Smirnov: >>> What could be a reason of HyperKitty failing to create a thread from >>> chained emails? >>> >>> For example, see "RECENTLY ACTIVE DISCUSSIONS" on page >>> https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ >>> >>> "Openvpn and Network mapping" discussion displayed as five threads instead >>> of only one... >> This looks exactly like the problem I have been experiencing, see >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> >> >>> Any ideas how to improve HyperKitty ability to detect threaded >>> messages? >> Sadly, no. Let's hope the problem gets resolved. > Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages. > > It would help us recreate the problem if you could attach a raw messages in the issue. I am > assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit > any sensitive information. > > I haven't looked at the threading code in HK since a long time, but my impression is that it > looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous > email that it received. > > In some cases, the order of the incoming messages can cause this to break, like when the > reply comes in first and the original messages comes in later. I am not sure exactly what is > happening here, but looking at the raw messages should help us reproduce and possibly > fix the issue. > I believe that for threading to work more or less reliably, the thing to do is to look at the 'References' header. That should give you the thread in order, and allow any message received out of sequence to be put in the proper location in your display. 'References' should be a superset of Reply-To (which is at most 1 Message-ID), so you only need Reply-To if there is no References - or to handle a client that doesn't obey the RFCs. See https://tools.ietf.org/html/rfc5537#page-15 & https://tools.ietf.org/html/rfc5322#section-3.6.4

6 years, 8 months

[MM3-users] Re: Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

These mails keep looping for days in the out queue and are never shunted. Looks to me as a serious bug. Is there anything that can be done for this? Note that the 29 other mailinglists are working fine. Best Regards, Eric On Saturday, January 9, 2021, 03:52:40 PM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: In my mailclient it looks like the LF's have been removed. I'll attach the log extracts to make them better readable. Best Regards, Eric On Saturday, January 9, 2021, 02:17:18 PM GMT+1, Eric Broens <ebroens(a)yahoo.com> wrote: ----- Forwarded Message ----- From: Eric Broens via Mailman-users <mailman-users(a)mailman3.org>To: Mailman Users <mailman-users(a)mailman3.org>Sent: Saturday, January 9, 2021, 02:14:42 PM GMT+1Subject: [MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail. The mailman3 error log show that there is a connection failure to port 25. A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail. Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail. Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either. For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue? Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric _______________________________________________ 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/ _______________________________________________ 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/

4 years, 9 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:00 AM, Seth Seeger wrote: > > I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: > > Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose > process(mlist, msg, msgdata, start_chain) > File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process > link.function(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), > File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ > self.set_payload(_text, _charset) > File "/usr/lib/python3.8/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 > > There are two owners listed, one of them is also listed as the moderator. This is redundant. Having the same user as both owner and moderator only results in possible duplicate notifications. There is no reason to have an owner also be a moderator. > "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Please do send me the shunted .pck. what is going on is this is an English language list which has character set `ascii` and the notice for some reason has non-ascii, possbbly the Subject: or the user's display name has non-ascii. But possibly the message itself is defective. In any case, I'd like to get the shunted message to see if there's something we should fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Problems with SPOOFED_UNAUTH

by M.Ede

Hello everyone, I use mailman together with mailcow and have configured my mailing list as follows: - Anonymous list: Yes - DMARC mitigation action: Replace From: with list address - DMARC Mitigate unconditionally: Yes My problem is that my emails are not being accepted by mailcow (rspamd) with the error SPOOFED_UNAUTH (50.00) In the out-queue of mailman the headers look like this: [QUOTE] Authentication-Results: <my.mailserv.er>; dkim=none; spf=pass (<my.mailserv.er>: domain of sender(a)t-online.de designates 194.25.134.81 as permitted sender) smtp.mailfrom=sender(a)t-online.de; dmarc=pass (policy=none) header.from=t-online.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.<list.domain>; s=dkim; t=1757400255; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=zmDaIaGeCj1IT8TuP4aJmXRbfyNHV3LqjIfHveVMS0M=; b=Im4F/mpchty4CJvvcW4ZqxMl0BRNnybjcmkPboUSuodopd7nOXaesj3w6kgIwZkLHn1uHY FOiSSjyfZ8Zu0/w4l4Du5uoij2qDCEYHvGFhEugFizE9HJ71i7x0SzoEVSZ9uve6sqnWaE X8+GqtCE+vf0TLLeKhXKHJaBdltbMSqO+QT0BOlbmOdvmUCy6MIqysocTod9io5/+CQOgd SSvsSdDq00CG1IBUsg0Tm2rSf/L2bpGD3bl7QEBKS2id7NeLFM/Zme/3mkHo0N/u7m47xy XSLS9R0C3Kg/YxHY8ctPt7Yas6fwYfzGAOXRvVJz1eeXSrl8B5vWfzJ8+WrE5Q== ARC-Authentication-Results: i=1; <my.mailserv.er>; dkim=none; spf=pass (<my.mailserv.er>: domain of sender(a)t-online.de designates 194.25.134.81 as permitted sender) smtp.mailfrom=sender(a)t-online.de; dmarc=pass (policy=none) header.from=t-online.de ARC-Seal: i=1; s=dkim; d=lists.<list.domain>; t=1757400255; a=rsa-sha256; cv=none; b=yrD6cRE7c/L/v8D76U5Ohn57/MJ7/VsObkzQdAHbFny5DbyEO8pZvM0VCVYA5hUGXqoqoU nnKpEW6/CqvNIZmsS9hKzQQEdO5yIzNnyYjARcW5w5MpAlkMjmH3dQ68mLIS9SUyXUsoXj m1zAeYmdTjZWQOiYanaNJLRuxCWSFQHOpAljZe/lZt+4llNNA01YqirqGBRe6uMaJoebe6 2ubsHTr6VlfTrBrdFqLLSWyRBls+e0JwOd2jGahaQ6/ZIf4l1dOqdaUHSq31RjEDAiofmK IGeKC97iu3r9LiFsjICyi+/yedMGbwSeyyFMzz+cAV7wM84eWfSx2S2kPP1c9Q== [END QUOTE] When the email arrives at rspamd for verification, the DKIM header is added, but there is also the entry: arc=reject ("signature check failed: fail, {[1] = sig:lists.list.domain:reject}"): [QUOTE] DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.list.domain; s=dkim; t=1757413251; h=from:reply-to:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:content-language:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post; bh=jH/b69qzW7O+s5h3yE2MxKTwFLElX7b39ILc9yHGhkc=; b=AApU4mb2iuN9u1lYTrIKIcPnB4jzXDX+8vC+2/WwHC8JvCukiR2Std5k3E10cuAyYFhPVk zn6AWY+s6c6HKslDn0RiO3i9QYRLAY5MESxvj0tKO1dKDMz+A8RdcOf4kdO4hDr0DQBf7v yQLLnLjgK8QpZdW8MrlfxcQpQ9XrlyP2GX+ntFh5vDl7frNPXQfnBMoo+l0DIs6SWQuaFX ikrOiISYKugL8TmWXnGohXiAM84W/JT0lvP/Lmt3NjxlyNsAWpHQz736LphydY4r5/JjHI of99pRcbTvEmkZogthHFaXMOG2sDGxGwlIc3+oIUHoXqyY+VLsBQs8FzjR+eaw== Authentication-Results: <my.mailserv.er>; arc=reject ("signature check failed: fail, {[1] = sig:lists.list.domain:reject}") ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.list.domain; s=dkim; t=1757413249; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=QSqNoTMweT1jo6F77TLHa+Nh7a0n/g9qDOsUTT8KpQ4=; b=rDgMC26uNsyTPgmddqQOiUsJh25KUa69TeMJfekVn5sFOnvhQdoa9LCogRMMKzJomA0wu6 CCdi6jGJpjtJdzB7PQ8UhQbeFiOUy9JNswFxQ+Qk1GXBxgN892C6KL/DiB/VW1j1nL0xOk Tc0BNC1zH1/MG2hB332t6u/rjWO+PtxIznAdcCP29AhO39RWWY/J0c/CHCOoqFYKCEf1ZH J4Wqeu9ANF44cPwopuJzJioWts6JKRvAM5TjnInZ+HaSv5QmuHvdI0fWvh272O3vGfvEPc iG1QsJS9XWpzkymRjYWo6h1c4/eY7eZd4FEzSR/TtW6Ud9b04A5lUmPpEvTxlQ== ARC-Authentication-Results: i=1; <my.mailserv.er>; dkim=none; dmarc=pass (policy=none) header.from=t-online.de; spf=pass (<my.mailserv.er>: domain of sender(a)t-online.de designates 194.25.134.20 as permitted sender) smtp.mailfrom=sender(a)t-online.de [END QUOTE] What am I still doing wrong? Can you help me, which setting is still missing? What informations are you still missing? Thanks for your help, Matthias

1 month, 3 weeks

[MM3-users] Re: DMARC Mitigation Wrap

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > > MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. > > The From address of this message has been replaced with the list > address, while the From name has 'via list' appended. Please be > careful when using 'via list' addresses later for new emails, as they > will be sent to the whole list.\r\n -------------------------- > ----------------------------------------------------------------------\r\n > From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> > Subject: [Testlist] wrap with divider and BLANKLINE > > Which coding option am I missing? I have searched for one online. I assume you are entering your text in Postorius in the DMARC wrapped message text box. There are a number of things going on here. Postorius is wrapping and filling the text and stripping trailing whitespace. If you want more whitespace, I suggest following your text with one or more empty lines and a single dot as in The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list. ------------------------------------------------------------------- . In the above, the blank lines before and after the line of dashes will be preserved as will the final dot which should be unobtrusive enough. More importantly, the rendering of the received message is up to your mail client. Your's apparently begins the wrapped message immediately after the wrapper's text, but many will not do that. Unless you actually view the received message in every mail client used by your user's, you won't know what they actually see. -- 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

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 11/2/21 20:15, Mark Sapiro wrote: > > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > I contributed in january to translate to spanish all the items > > > left in > > > Mailman Core, Django-mailman, HyperKitty and Postorius via > > > Weblate. I > > > thought they will be used in the next upgrade, but I cannot see > > > any > > > improvement and there are many words untranslated. > > > > The Spanish translations for Mailman core and HyperKitty are > > currently > > completely up to date with weblate. django-mailman3 differs in one > > string that was translated on Feb 10 and hasn't yet been merged. > > Postorius also differs in a few places from the Feb 10 version that > > hasn't yet been merged. > > Ok. Thanks for checking it. I put my little contribution in Weblate > and I like that it could be used by anyone. Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-) > I tried to run this using the same command as I did for the > "collectstatic" (that solved all my previous problems for the > upgrade) > and "migrate" runs but it shows me an error: > > su -m mailman3 -c "python3 manage.py compilemessages" > CommandError: This script should be run from the Django Git checkout > or your project or app tree, or with the settings module specified. I got this very same error, and was also confused, as manage.py runs at the project level, not application level. > I'm lost. Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-) Confused-with-translations-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 8 months

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > About 500 list. Not sure how to check size of the archives. > > On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> >> >> On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> >> wrote: >> >>> Any suggestion on how to migrate mailing list and archirve with >>> diffirent server and domain. For the mailing list from >>> sample.domain1.example.com to sample.domain2.example.com >>> >>> Old Mailing list >>> Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) >>> [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] >>> Domain Domain1.example.com >>> >>> New Mailing list >>> Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) >>> [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] >>> Domain domain2.example.com >> >> >> >> How many lists? How big are the archives? >> >> Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, >> it seems like it's not a trivial exercise. >> >> However, I am wondering about the consequences of: >> 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then >> re-importing >> 2. editing settings.py and webserver config to reflect the DOMAIN2 >> 3. reconfiguring your MTA to handle list mails using the DOMAIN2 >> >> I am imagining a virtualenv type of installation. >> > The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… . -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

[MM3-users] Re: Can you use @list to include members in accept these non-members in v3?

by Lieuallen, Thomas Otis

Danil, That looks awesome, as do several other features and fixes. It doesn’t look like 3.3.10 is released yet, though. Any ideas on when that might happen? Thank you for directing me there. Tom Lieuallen From: Danil Smirnov via Mailman-users <mailman-users(a)mailman3.org> Date: Thursday, September 5, 2024 at 3:45 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Can you use @list to include members in accept these non-members in v3? [This email originated from outside of OSU. Use caution with links and attachments.] Hi Tom, This feature has been added recently in version 3.3.10, see "New Features" in the changelog: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…<https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/docs/NEWS.rst> Sincerely, Danil Smirnov Mailman3.com On Thu, Sep 5, 2024 at 12:22 AM Lieuallen, Thomas Otis < Tom.Lieuallen(a)oregonstate.edu> wrote: > No answers yet on this, so I’m not hopeful that MM3 supports this > feature. I guess I’ll start on a script to update the list of allowed > senders. > > Thank you > > Tom Lieuallen > > From: Lieuallen, Thomas Otis <Tom.Lieuallen(a)oregonstate.edu> > Date: Thursday, August 29, 2024 at 2:35 PM > To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> > Subject: Can you use @list to include members in accept these non-members > in v3? > In Mailman v2, one could use @listname in ‘accept_these_nonmembers’: > > A line consisting of the @ character followed by a list name specifies > another Mailman list in this installation, all of whose member addresses > will be accepted for this list. > > I don’t see this option listed in version 3. Is it no longer > supported/allowed? Is there another option? > > We often send email to lists of lists and have loved that @listname option > to help us deliver email to 20+ lists without needing to approve the emails > each time or reconfigure all the lists when another sender needs to be > added. > > Thank you > > Tom Lieuallen > Oregon State University > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> > Archived at: > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to danil(a)smirnov.la > _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

1 year, 1 month

[MM3-users] Re: New year releases!

by Jeff

I finally got around to doing this upgrade. I followed the instructions at: https://docs.mailman3.org/en/latest/upgrade-3.2.html Everything seemed to go fine but, mailman3 failed to start because “_BindParamClause” could not be found in sqlalchemy.sql.expression. It looks like alembic-1.6.2 is not completely compatible with SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in alembic-1.6.2, but should Mailman start requiring a newer version of alembic? > On Jan 4, 2023, at 4:59 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > All the releases are published to PyPI and you can find links to all the PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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 mm3(a)steele.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/vnd.microsoft.icon Name: favicon.ico Replaced multipart/alternative part with first alternative.

2 years, 7 months

[MM3-users] Re: Weird behavior with Outlook and any MM3 List

by Thomas Ward

Ye it gets a little tricky when we have custom thread IDs being added. I could do some postprocessing on a reply and see what the "In-Reply-To" header says if I can figure out how to fetch the previous message subject line for the custom need for my workplace with a thread/post ID in the subject line. I'm going to experiment with alternative brackets and see if it still does it. While also opening a support ticket with Microsoft to give me a chance to rage at them. I'll report back if I find a solution/alternative. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, November 1, 2023 2:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Weird behavior with Outlook and any MM3 List On 11/1/23 09:42, Thomas Ward via Mailman-users wrote: > I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). > > When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. > > While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. > > Has anyone observed this behavior before? If so, have you found any workarounds? This is a Microsoft/Outlook issue. As you note at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… this is just the way Outlook displays the message subject. I know of now way around this, but I don't use Microsoft MUAs. Does Outlook also strip the prefix from replies? This probably wouldn't matter for replies to the list as the list will add it back, but might be an issue for other direct recipients. Presumably, Outlook is looking at the [] around the prefix. You might try either dropping the brackets or using something else such as _My-List_ instead of [MyList]. -- 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 teward(a)thomas-ward.net

2 years

[MM3-users] Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

Hello everyone, I am starting a new thread on this so that the issues I encountered do not get mixed up with the other discussions. Over the weekend I upgraded an MM3 installation to the latest versions of the components. I started off by creating a new venv, installing and then migrating the configurations and the scripts. In the end, I ended up with MM3 Core ==3.3.7, postorius==1.3.7, HyperKitty==1.3.6, django==4.1.3. 1. SQLAlchemy - At the stage where one runs 'mailman info', I encountered the first error: : sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:postgres This is solved by a change in mailman.cfg so that the URI starts with postgresql:// instead of postgres://. SQLAlchemy used to accept both but has removed support for the postgres name. <https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013> 2. Django==4.x At the point of running the post-update processes, particularly the "migrate" bit, I got the following error: : ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py) I understand this is a consequence of the django.conf.urls.url() having been deprecated starting version 3 and has been removed in version 4 of Django. https://docs.djangoproject.com/en/4.1/releases/4.0/#features-removed-in-4-0 The upgrade process seems to have brought in the newer version of Django because now I have 4.1.3 up from 3.x If anyone wants, I found an elaborate explanation at https://bobbyhadz.com/blog/python-importerror-cannot-import-name-url-from-d… . My Google-fu found suggestions that in urls.py, I should import re_path and use it, or alias it for url for the migrate to work. The solution I used was to alias url to re_path, but I am considering just doing away with url altogether. Not sure which is the better option between using re_path or path. So here is the patch I have used: (venv) mailman@lists:~/mm$ diff -u urls.py.bak urls.py --- urls.py.bak 2022-12-03 12:20:28.028090659 +0300 +++ urls.py 2022-12-03 12:36:20.298875624 +0300 @@ -17,7 +17,8 @@ # Postorius. If not, see <http://www.gnu.org/licenses/>. -from django.conf.urls import include, url +from django.conf.urls import include +from django.urls import re_path as url from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView 3. The last issue that I encountered is one I kind of solved, but completely don't understand the consequences of the solution I applied: /opt/mailman/mm/bin/django-admin migrate <CUT> System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount </CUT> Here again, Google-fu came to the rescue. I added the following line to settings_local.py and the warnings were suppressed. DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' I need to understand how this affects everything and how this is likely to impact the functionality of MM3. What is the proper solution for this? And should it be django.db.models.BigAutoField or django.db.models.AutoField? Which is which? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

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

by Stephen J. Turnbull

Onyeibo Oku writes: > I am not sure I understand what you mean by apps. Is that Django apps > (./manage.py startapp app)? Do you mean a Django Project instead > (./manage.py startproject app)? An app for my purpose is everything configured via the settings.py used by the Django application created in a wsgi.py file. I guess you would think of them as projects. > What I have here is an active website project (live) done on Django > framework. It runs from a different virtual environment (venv). > > hence: > mailman --> /opt/mailman/venv > website --> /srv/website/venv (has a running uwsgi instance) The venvs isolate the Python code used by each app from the other. But the apps can still have conflicts over ports (this is mentioned in the Django docs), filesystem objects, and other resources. For example, a lot of applications use the /static/ location as a place to keep content that is supplied by your project and doesn't change. This is problematic if two different apps each wants to install a default.css, but they're different. One of the apps is going to look funny. Only the person who configures the apps can guess whether this kind of conflict will arise. Neither Mailman nor Django itself tries to protect you from such conflicts (I don't see how they could, in fact). > > > In whichcase, it doesn't hurt to follow the doc to its logical > > > conclusion? > > > > I don't understand what you mean by logical conclusion. > > > > That is to follow the guide to the end of the page (disregarding > the possibility of conflicts). No, you can't disregard the possibility of conflicts. My understanding from what you've posted so far is that you have an app "website" that is already implemented and running. Most likely that app has configured resources (specifically ports and website locations in particular /static/) that are likely to conflict. You need to manage those conflicts, most likely by changing the ports used by Mailman, Postorius, and Hyperkitty and by mapping a different location such as /mailman/static/ to the /var directory that actually contains the static files managed by "manage.py collectstatic". There may be other possible conflicts, but I can't help you with those because they depend on your website code. Steve

3 years

[MM3-users] Re: Email verification

by Abhilash Raj

On Sun, Feb 9, 2020, at 9:38 AM, Allan Hansen wrote: > Thank you, Abhilash. > Yes. People are getting these messages. I just got a message from one who had the issue. I asked her to try to sign in again and then she got the verification message. > > It’s just that some have issues, and I’d like to be able to help. Can you check your MTA logs to see if those confirmation emails were indeed sent out? It would help figure out of the email was never sent out or whether they didn't receive it. > Yours, > > Allan Hansen > hansen(a)rc.org > > > >> On Feb 9, 2020, at 9:12 , Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> >> >> On Sun, Feb 9, 2020, at 8:05 AM, Allan Hansen wrote: >>> Some members cannot get past the email verification when they create >>> their accounts. >>> They insist that they have looked in their spam folders. Their email >>> addresses they entered are correct - the are able to log into their >>> accounts with the right email address. But they get the message saying >>> that a confirmation message was sent and if they don’s see it to >>> contact us. >> >> Is your Django configured to send out emails? >> >> https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… >> >> >>> >>> 1. Who is ‘us’? My members are asking... >>> 2. How do I help them? >>> >>> I tried subscribing them to a bogus list with pre-verified email, but >>> that did not work, so both they and I are stuck. >>> Tried finding help in archive, but did not see anything. >>> >>> Yours, >>> >>> Allan Hansen >>> hansen(a)rc.org >>> >>> >>> >>> >>> _______________________________________________ >>> 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) >> _______________________________________________ >> 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, 8 months

[MM3-users] Managing mailman3 via curl (using bash-scripts or perl-scripts)

by Christian Schneider

Hello Mark, hello Stephen, sorry for bothering again...but the amount of documentation is overwhelming... Some info about my setup: I run mailman3 in an virtual environment with postgresql-Server (all in recent versions) - operating system Ubuntu 24.04-LTS. My aim is to provide one high-level script for the daily task of list creation. - list creation via command-line script with two/three parameters like: ./create-list --listname myfirst.list(a)lists.example.org --admin-email admin-user(a)example.org [--admin-name "Peter Rabbit"] The create-list script itself should be a bash- or perl-script (I am not very familiar with python - SORRY ;-) ) I would like the scripts to trigger some curl-calls on the mailman server (from outside the mailman shell and even from outside the virtual environment) Reading the RestAPI documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… several questions arise: 1) Can I succeed with this plan? (Are curl-calls sufficient? Is it possible from outside the virtual environment?) 2) Is this a viable curl-call to create a user?: curl -X POST -u 'admin-user:<password>' -H "Content-Type: application/json" -d '{ "email": "peter.rabbit(a)example.org", "display_name": "Peter Rabbit", "password": "secret" }' http://localhost:8001/3.1/users 3) and in a second step can I assign this user to a list as owner with a curl-call like this?: curl -X POST -u 'admin-user:<password>' -H "Content-Type: application/json" -d '{ "list_id": "newsletter.lists.example.org", "subscriber": "peter.rabbit(a)example.org", "role": "owner" }' http://localhost:8001/3.1/members 4) What about the commits that are used while operating in mailman shell? (Do I have to trigger commits while operating via curl-calls? And how can I trigger commits via curl?) 5) In the unlikely event that I change from the dark side to the good side i.e. "python programming" ;-) is there a "to-the-point" reference for IListManager, IUserManager etc. giving available functions (with parameters) in a kind of list way? (the example kind of documentation referenced above is good, but where can I find a list of all functions?) 6) I think the starting point for managing lists with python is here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… right? 7) Going the python way will require to enter the virtual environment, right? (otherwise the libraries, environment variables etc. are not available...I think) Thank you for some guidance here... :-) Kind regards Chris

1 month

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 17:54, Mark wrote: > > Thank you Mark. It's so close. After wrangling your solution a bit it's > working a treat on my test server (wrangled solution below) . > > When I add it to the production server (same OS, MM installation, etc) > I'm getting a "Bad gateway" error page and the log reports ... > > ... > raise self.model.DoesNotExist( > django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist. That error will occur when settings.py contains SITE_ID = 0 and the host in the http request is not one of the hosts in the django_site table in the database or in Sites in the Django admin web UI. Is that possibly the case here? In any case, if the change to /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py that you report below is the only thing that changed from a working installation, I don't see how that can affect this. Is there a complete traceback preceding the log snippet you report. If so, what is it? > I cannot for the life of me get my head around that. I suspect it's > something to do with what you said -- "whatever is proxying to Django > setting the appropriate HTTP_HOST header." -- which I don't understand. This is in the configuration of the web server. It should be configured to pass the host of the incoming request to the proxy target in the HTTP_HOST header. In nginx this is `proxy_set_header Host $host;`. In apache it is `ProxyPreserveHost On`, but again the change to user_adapter shouldn't affect this. > Any additional advice gratefully received. > > > ================================== > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > ================================== > COMMENT OUT THESE 2 LINES... > > # def is_open_for_signup(self, req): > # return False > > REPLACE WITH THE FOLLOWING... > > def is_open_for_signup(self, req): > if req.META['HTTP_HOST'] == 'lists.mydomain.com': I had if req.META.HTTP_HOST == 'lists.mydomain.com': which as you discovered is wrong. What you have is correct. > return False > else: > return True And here I had return super().is_open_for_signup(self, req) which should return the is_open_for_signup result from allauth.account.adapter.DefaultAccountAdapter but since that result is an unconditional True, what you have is OK too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark for your response. But I am having a final query over this issue. Out of the two hyperkitty records I observed in the database, I am confused which record do I need to remove directly from the database? Because I doubt still there is one more list with the same style i.e. with two hyperkitty records. Please advise. On Mon, Jul 27, 2020 at 4:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > > Thank you Mark. > > > > What you have said is right.. > > > > I found a list with two "hyperkitty" records in the listarchiver in the > > database. I had removed the list and recreated it and now I found it is > > working fine. The recreated list is having only one record. > > > OK, but that's not a reasonable way to fix this in general. You can just > remove the `extra` record using a direct database query which is > probably the least disruptive way to fix this. > > > > After searching the links you provided I found there is just a work > around > > but not the precaution to be taken for not getting the duplicate record. > > > > Can you say what might be the reason for this duplication? If I need to > > provide any details, please let me know. > > > As noted in the threads I referenced, we don't know the cause. Yours is > the first report of this issue with the `hyperkitty` archiver. In all > the other reports, the duplicate archiver has been `mhonarc`. > > If it happens again and you know the exact sequence of events that led > to it, i.e. what was done with the list between the last time it worked > and when it stopped working, that might give us clues, but currently we > are at a total loss to understand how this happens. > > -- > 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: Restore/export existing Mailman lists + hyperkitty archives on a new server

by alexs＠ecoscentric.com

Mark Sapiro wrote: ... > I thing just dumping and loading the databases and copying mailman.cfg > and the Django settings should do it. Are the domains the same on the > new server? If not there may be issues with that. I'd need to see the > exception and traceback to say more. I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: # mailman-web showmigrations account [X] 0001_initial [X] 0002_email_max_length admin [X] 0001_initial [X] 0002_logentry_remove_auto_add [X] 0003_logentry_add_action_flag_choices auth [X] 0001_initial [X] 0002_alter_permission_name_max_length [X] 0003_alter_user_email_max_length [X] 0004_alter_user_username_opts [X] 0005_alter_user_last_login_null [X] 0006_require_contenttypes_0002 [X] 0007_alter_validators_add_error_messages [X] 0008_alter_user_username_max_length [X] 0009_alter_user_last_name_max_length [X] 0010_alter_group_name_max_length [X] 0011_update_proxy_permissions [X] 0012_alter_user_first_name_max_length contenttypes [X] 0001_initial [X] 0002_remove_content_type_name ... # mailman-web migrate --plan Planned operations: contenttypes.0001_initial Create model ContentType Alter unique_together for contenttype (1 constraint(s)) auth.0001_initial Create model Permission Create model Group Create model User account.0001_initial Create model EmailAddress Create model EmailConfirmation account.0002_email_max_length Alter field email on emailaddress admin.0001_initial Create model LogEntry admin.0002_logentry_remove_auto_add Alter field action_time on logentry admin.0003_logentry_add_action_flag_choices Alter field action_flag on logentry contenttypes.0002_remove_content_type_name Change Meta options on contenttype Alter field name on contenttype Raw Python operation Remove field name from contenttype ... But the migrate fails at the first operation: # mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying contenttypes.0001_initial...Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 82, in _execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 315, in _query db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 239, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") ... Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. So how can I upgrade my existing mailman3-web database?

2 years, 1 month

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Fri, Aug 2, 2024 at 5:51 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/08/01 10:09, Roland Giesler via Mailman-users wrote: > > > > I needed to put these files at these locations: > > > > transport_maps = > > hash:/etc/mailman3/data/postfix_lmtp > > local_recipient_maps = > > hash:/etc/mailman3/data/postfix_lmtp > > relay_domains = > > hash:/etc/mailman3/data/postfix_domains > > > > However, since I'm using power-mailinabox, Postfix is configured to > > use sqlite already and has these lines by default: > > > > virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf > > virtual_mailbox_maps=sqlite:/etc/postfix/virtual-mailbox-maps.cf > > virtual_alias_maps=sqlite:/etc/postfix/virtual-alias-maps.cf > > local_recipient_maps=$virtual_mailbox_maps > > > > So I have only added this line to postfix's main.cf: > > > > # Add postfix_domains path so mailman can add domains to it for lists > > relay_domains=hash://etc/mailman3/data/postfix_domains > > > > The local_recipient_maps are set by power-mailinabox already, so I'm > > ignoring what mailman creates. > > > It seems that this is a mistake. If I don't let postfix read the > local_recipient_maps that mailman3 created, the incoming emails are not > sent to the other host. So I have a conflict with the > local_recipient_maps that postfix has (created by Power-mailinabox) and > those created by mailman3. > > I'm hoping that if I specify local_recipient_maps more than once and > then both sources will be considered. Would that work? > > If not, then I'm pretty much stumped, unless I go for the database > option that has not been merged yet. Even if I do that, I would need to > make sure that mailman3 doesn't remove the other entries in the database > which, judging by what I've seen, seems to be the case. > > Any ideas? > Quoting the official documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta ``` If your current main.cf contains settings for these items, including the default setting for local_recipient_maps, you should add the Mailman setting to the existing setting rather than replacing it. ``` Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: > >Hi Mark, > > > >Actually all this stuff happens inside the container after it's started > >and > >initialized without errors. I didn't amend the image anyhow. > > > >Also I have the configuration based on docker-compose.yaml provided in > >the > >repository which works just fine for mailman-web image. > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > >fails > >with 500 error... > > > >Now answering your questions: > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > >what > >> is set for Q_CLUSTER? > >> > > > >I've checked settings.py inside the container and I haven't found any > >of > >the mentioned configurations there. > > > >Does the manage.py that's being run here point to the right > >settings.py? > >> > > > >No clue. > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > >configured image? > > > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > Because I am a dum dum ;-) > > Will work on removing those crons and stuff. Would be nice if you > opened an issue on Github so that I don't forget. Should now be fixed in the latest image. > > >Danil > > > > > > > >> -- > >> 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/ > >> > >_______________________________________________ > >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/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- thanks, Abhilash Raj (maxking)

6 years, 8 months

[MM3-users] Re: Sendgrid experiences

by Andrew Hodgson

Hi. Thanks for the recommendation on the Google Workspace. How did you set this up in terms of the domain, since I don’t want to use Google Workspace as the main email provider for this domain. Also did you have to set anything special in Mailman? Thanks. Andrew. From: Stephen Daniel <swd(a)pobox.com> Sent: Thursday, May 11, 2023 2:57 PM To: Andrew Hodgson <andrew(a)hodgson.io> Cc: Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp>; mailman-users(a)mailman3.org Subject: Re: [MM3-users] Re: Sendgrid experiences I would definitely look for alternatives to SendGrid. I tried using them and had a very poor rate of people actually getting my emails, even when I temporarily upgraded to an expensive plan with a dedicated IP address. I'm currently hosting mailman in Google Cloud and relaying outbound mail through a Google Workspace account. It's working OK. The workspace account costs me $6/month for basically unlimited mail relay. On Thu, May 11, 2023 at 9:50 AM Andrew Hodgson <andrew(a)hodgson.io<mailto:andrew@hodgson.io>> wrote: Stephen J Turnbull wrote: >2023-05-10 03:49 に Andrew Hodgson wrote: >> Sendgrid is maintaining the Message-Id header which is good for >> archiving. It is re-writing the Return-Path header though which means >> that bounce handling in Mailman won't work, but I think all the >> services do this in some way so I am happy to live with that for the >> moment. >How does it rewrite the Return-Path? Returned mail is not something that such a service would be able to handle properly (although they can help with apparently returned spam). If mail is legitmately sent and returned as undeliverable, only the author or their agent will know how to handle it. So such >services should provide some way to find out about returned mail. An example: Return-Path: bounces+[Sendgrid GUID]-andrew=hodgson.io(a)em6096.lists.hodgsonfamily.org<mailto:hodgson.io@em6096.lists.hodgsonfamily.org> Sendgrid provide information about bounces but crucially that bounce isn't forwarded back to the original return-path sender (i.e, Mailman). A few people have pointed out they can provide list hosting at a cheaper cost than Sendgrid so I'm looking for alternatives again. Andrew. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@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 swd(a)pobox.com<mailto:swd@pobox.com>

2 years, 5 months

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Guillermo Hernandez (Oldno7)

El 21/4/23 a las 10:37, Odhiambo Washington escribió: > > > On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: > > I'm having troubles with Django and cannot access to web admin. > > I need to unhold a message while figures out what is happening. > > Searching the mailman cli help commands didn't help me. > > Anyone who knows how to unhold a message, please? > > > TBH, I find it a lot easier to fix the web UI than mess with the > python shell :-) > > While you wait for @Mark Sapiro <mailto:mark@msapiro.net> to save you, > you can be reading the following: > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Thanks: it seems the place to do it (I didn't find it) I'm fighting the web UI problem. It seems that something in wsgi has changed and is no more compatible with my version of things. Error log from apache shows: mod_wsgi (pid=30632): Failed to exec Python script file '/usr/local/mailman3/wsgi.py'. mod_wsgi (pid=30632): Exception occurred processing WSGI script '/usr/local/mailman3/wsgi.py'. Traceback (most recent call last): File "/usr/local/mailman3/wsgi.py", line 34, in <module> from django.core.wsgi import get_wsgi_application File "/usr/local/lib/python3.9/site-packages/django/core/wsgi.py", line 2, in <module> from django.core.handlers.wsgi import WSGIHandler File "/usr/local/lib/python3.9/site-packages/django/core/handlers/wsgi.py", line 3, in <module> from django.conf import settings File "/usr/local/lib/python3.9/site-packages/django/conf/__init__.py", line 19, in <module> from django.utils.deprecation import RemovedInDjango50Warning, RemovedInDjango51Warning File "/usr/local/lib/python3.9/site-packages/django/utils/deprecation.py", line 4, in <module> from asgiref.sync import iscoroutinefunction, markcoroutinefunction, sync_to_async ImportError: cannot import name 'iscoroutinefunction' from 'asgiref.sync' (/usr/local/lib/python3.9/site-packages/asgiref/sync.py) Yesterday all were running without problems, today is another day X) > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 6 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 12:15 AM, Peter Münster wrote: > > It seems, that mailman bounces the bounces, so that the list-owner never > sees them: > > --8<---------------cut here---------------start------------->8--- > postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] > postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] > postfix/cleanup[11841]: 879D6F12E8: message-id=<> > postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) > postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) > postfix/qmgr[10092]: 879D6F12E8: removed > --8<---------------cut here---------------end--------------->8--- There are a few things going on here. It appears that out04.smtpout.orange.fr has bounced a list post from the <test(a)my-domain.org> list and and sent a DSN back to Mailman at <test-bounces(a)my-domain.org>. It is this DSN that has no Message-ID:. Mailman's LMTP runner rejects such messages. The underlying issue is the orange.fr domain is sending DSNs without a Message-ID: header. > What could I do please, to get the bounces? I would like to use VERP to > identify wrong addresses... If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] section of your config), this log message > postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) would contain to=<test-bounces+user=example.com(a)my-domain.org> and you could identify the bouncing address (user(a)example.com in this case) that way. Beyond that, there are still other issues, the biggest of which is currently, Mailman is not processing bounces other than storing them in the database. See <https://gitlab.com/mailman/mailman/issues/343>. Also, the LMTP runner requires a Message-ID: at least in part because that is part of the algorithm for creating a unique ID for archiving. Given that messages to a -bounces address are handled differently and not archived, it would be possible to not require a Message-ID: for those messages, but arguing against that, if a recipient MTA can't create a DSN that has a Message-ID:, would you trust what else it does? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: moving individual list to different domain

by Johannes Rohr

Dear Mark, thanks as always for your very thorough explanation. I guess, it is simply not practical then... Cheers, Johannes Am 21.03.23 um 19:11 schrieb Mark Sapiro: > On 3/21/23 06:21, Johannes Rohr wrote: >> Dear all, >> >> on mailman2 it was possible to move a list to a different domain >> within the same mailman instance. >> >> I have found no information on how the same can be accomplished on >> mailman3. >> >> Is this possible at all? > > > In mailman 2.1, a list was identified by its name only without the > domain and those names had to be globally unique. A site could be > configured to support multiple virtual hosts and a list had a > host_name attribute which could be changed if desired to assign the > list to a different virtual host, but there couldn't be two lists with > the same name even if they had different host names. > > Mailman 3 is different. In order to remove the restriction that list > names (without the domain) had to be globally unique, in MM 3 the > domain is part of the list name. I.e., we can now have > list(a)example.com and list(a)example.net as two distinct lists in the > same installation. > > Suppose we want to rename list(a)example.com to list(a)example.net. This > becomes involved in Mailman 3 because it affects not only Mailman > core, but also mail delivery and archiving. Furthermore, the list with > fqdn_listname list(a)example.com has the list_id list.example.com. If we > change the fqdn_listname to list(a)example.net, the list_id should > remain list.example.com per RFC 2919 Sec. 4. > <https://www.rfc-editor.org/rfc/rfc2919>. We can just change the > list's mail_host attribute via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or via a database query, but this leads to confusion. I.e., a URL like > https://example.com/mailman3/lists/list.example.com/ will still work > but https://example.com/mailman3/lists/list@example.com/. > > To avoid this, we could also change the list_id, but we can't do that > via REST as it's a read-only property, and changing the list_id says > this is really a new list, not the same list with a new name. > > Also, none of this addresses archiving. >

2 years, 7 months

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

by Mohsen Masoudfar

Thank you Mark! [EXTERNAL EMAIL] On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? >> Sorry, It was my misunderstanding. DMARC mitigation is functioning well for newly created lists, even with Gmail addresses. >> I am suspicious that Gmail might be rejecting or bouncing emails from the list due to the reputation of those lists. >> It's worth noting that I am not the owner of the lists, but admin the Mailman3 infrastructure. My objective is to determine if our suspicious is accurate, whether Gmail is rejecting emails because of the bad reputation. We have asked Google, but no response so far. >> I am interested to know more about the reasons behind these bounces, they are all handled by Postfix and deleted. > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. >> Is there a way to send them to a mailbox? Or prevent them from being deleted, so that I can look into the message body? -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

> It just occurred to me what the issue is. It is almost certainly that > there is a /usr/share/mailman3-web/settings_local.pyc that is as new or > newer than the /usr/share/mailman3-web/settings_local.py symlink even > though it is older than the target /etc/mailman3/mailman-web.py. > > Just remove that .pyc, and that should fix it. > > But I still wonder what python version this is since current Mailman > requires python >= 3.6 Hi Mark, $ ls -lR /usr/share/mailman3-web/ /usr/share/mailman3-web/: total 52 -rwxr-xr-x 1 root root 242 May 23 2017 manage.py -rw-r--r-- 1 root root 14835 Apr 12 2018 settings.py -rw-r--r-- 1 root root 8157 Nov 25 20:02 settings.pyc lrwxrwxrwx 1 root root 28 Apr 12 2018 settings_local.py -> /etc/mailman3/mailman-web.py -rw-r--r-- 1 root root 5752 Mar 15 2018 settings_local.py.sample -rw-r----- 1 root root 2359 Dec 7 16:11 settings_local.pyc-210302 -rw-r--r-- 1 root root 1314 May 23 2017 urls.py -rw-r--r-- 1 root root 798 Dec 7 16:11 urls.pyc -rw-r--r-- 1 root root 1173 May 23 2017 wsgi.py and $ ls -l /etc/mailman3/mailman-web.py -rw-r----- 1 root www-data 5876 Mar 1 21:13 /etc/mailman3/mailman-web.py Moving settings_local.pyc (as above) seems not to have had any effect at all. I'm not on the latest mailman, unfortunately. I use the bundled packages on Ubuntu 18.04, which are mailman3 3.1.1-9 mailman3-doc 3.1.1-9 mailman3-full 3.1.1-9 mailman3-web 0+20170523-14 From the mailman-web logs, it looks like it's using python2. I did a wee experiment and copied /etc/mailman3/mailman-web.py to /usr/share/mailman3-web/settings_local.py (rather than the symlink) and life got totally strange. Suddenly I'm seeing this in /var/log/mailman3/web/mailman-web.log: hyperkitty.lib.utils Failed to update the fulltext index: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? and I can no longer connect to the web site. All the postgres is commented out in /etc/mailman3/mailman-web.py (and thus settings_local.py ...) Put the symlink back, and it works again. (But still without the emojis working, of course.) Postgres is what's in settings.py, but I assume that should be overriden by what's in settings_local.py. Baffling. I don't really know what to do next, but I'll keep looking. Cheers, David

4 years, 8 months

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

by Mark Sapiro

On 5/13/21 11:28 AM, Ruth Ivimey-Cook wrote: > 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. Yes, I overlooked some aspects of virtualenv. Actually, the Python in the virtualenv is mostly symlinks to the Python it was built with, so whether it continues to work after a Python upgrade depends on what the symlinks are and how the Python upgrade installs. > 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.] I haven't tested any of this, but I suspect if Python is for example, /usr/bin/python3.6 and /usr/lib/python3.6 the upgrade removes those and installs /usr/bin/python3.8 and /usr/lib/python3.8, that you could just create symlinks from /usr/bin/python3.6 and /usr/lib/python3.6 to /usr/bin/python3.8 and /usr/lib/python3.8 respectively and it would work. On the other hand, if the symlinks in the venv are to things like /usr/bin/python3 and /usr/lib/python3 which used to point to 3.6 versions and after upgrade point to 3.8 versions, it should just work. As far as installing Python3.8 on Ubuntu 18.04 goes, the machine I'm typing this on is Ubuntu 18.04 and has 6 different Python3 versions mark@msapiro:~$ /usr/bin/python3.5 --version Python 3.5.2 mark@msapiro:~$ /usr/bin/python3.6 --version Python 3.6.9 mark@msapiro:~$ /usr/local/bin/python3.6 --version Python 3.6.12 mark@msapiro:~$ /usr/local/bin/python3.7 --version Python 3.7.9 mark@msapiro:~$ /usr/local/bin/python3.8 --version Python 3.8.7 mark@msapiro:~$ /usr/local/bin/python3.9 --version Python 3.9.1 and /usr/bin/python3 is a symlink to /usr/bin/python3.6 and /usr/local/bin/python3 is a symlink to /usr/local/bin/python3.9, so take your pick... -- 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: New release candidates for Postorius and Hyperkitty

by Abhilash Raj

+cc: mailman-usersmailman3.org for more visibility. On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote: > Hi, > > Is there a recommended method for upgrading an existing, running, server > from Python 3.6 to 3.8, especially in such a way as to enable downgrade > if something breaks? It depends on how did you install Mailman. If you installed using virtualenv, you can create another virtualenv and install new versions, that use the same configuration and switch between new and old versions, > > [When I upgraded a server distribution without enough preparation, it > broke mailman3 because I lost python3.6, and getting it working again > needed a lot of work to reinstall it without zapping needed state.] > > Regards > > Ruth > > > On 16/01/2021 20:38, Abhilash Raj wrote: > > Hey Everyone, > > > > Happy new year to everyone! > > > > I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! > > > > These include both new features and bug fixes. Complete change log for each components: > > > > Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > > > Since these are pre-releases, you can install them using: > > > > $ pip install --pre --upgrade postorius hyperkitty > > > > Or you can also specify the exact versions: > > > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > > > Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. > > > > If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. > > > > [1]: https://docs.mailman3.org/en/latest/translation.html > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Mark Sapiro

On 7/12/18 7:34 AM, Marvin Gülker wrote: > Hi, > > I've just upgraded to Mailman 3.2.0 (finally everything Python 3 now, > thanks!) and it appears to work. However, there's a repeating error > message in mailman-suite's logfile for Hyperkitty that looks like this: > > ERROR 2018-07-12 14:28:33,895 2742 hyperkitty.lib.utils Failed to update the fulltext index: ord() expected a character, but string of length 0 found > Traceback (most recent call last): > File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/lib/utils.py", line 179, in run_with_lock > fn(*args, **kwargs) > File "/home/mailman/env3/lib/python3.5/site-packages/hyperkitty/search_indexes.py", line 115, in update_index > update_cmd.update_backend("hyperkitty", "default") > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 276, in update_backend > last_max_pk=max_pk) > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 178, in update > self.setup() > File "/home/mailman/env3/lib/python3.5/site-packages/haystack/backends/whoosh_backend.py", line 126, in setup > self.index = self.storage.open_index(schema=self.schema) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/filestore.py", line 176, in open_index > return indexclass(self, schema=schema, indexname=indexname) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 421, in __init__ > TOC.read(self.storage, self.indexname, schema=self._schema) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 632, in read > check_size("int", _INT_SIZE) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/index.py", line 626, in check_size > sz = stream.read_varint() > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/filedb/structfile.py", line 191, in read_varint > return read_varint(self.read) > File "/home/mailman/env3/lib/python3.5/site-packages/whoosh/util/varints.py", line 102, in read_varint > b = ord(readfn(1)) > TypeError: ord() expected a character, but string of length 0 found > > The error repeats every minute, so I suppose it comes from the minutely > cronjob. This cronjob looks like this: This is due the the change from Python 2.7 to Python 3. The existing search index is not compatible with Python 3 whoosh. I fixed this by deleting all the files in the index directory which is defined as PATH in HAYSTACK_CONNECTIONS in your settings and running 'django_admin update_index', but just running 'django_admin rebuild_index' should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 9:29 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > >> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: >> >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ >> TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ >> TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> >> The proxy pass config is >> <IfModule mod_proxy_uwsgi.c> >> ProxyPass /mailman3/favicon.ico ! >> ProxyPass /mailman3/static ! >> Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" >> ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" >> ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" >> ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" >> ProxyPass "/django" "http://127.0.0.1:8000/django" >> ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" >> ProxyPass "/archives" "http://127.0.0.1:8000/archives" >> </IfModule> > > There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. Also, replace, /django with /admin. > You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Do, either one of those listed above and `/admin` work for you? -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

Third Party Config files on FreeBSD are to be found under /usr.local/etc. For instance apache, cups, rsync are to be found under /usr/local/etc/apache24, /usr/local/etc/cups, and /usr/local/etc/rsync respectively, but that is a problem for anyone who wants to port Mailman 3 to FreeBSD. I guess one option would be to set mailman3-flags="--config-file=/usr/local/etc/mailman/mailman.cfg" in /etc/rc.conf or somesuch... On Sun, Aug 13, 2017 at 7:23 PM, John Poltorak <karotlopj(a)gmail.com> wrote: > I'm making progress, albeit slowly. Any progress I make I will post on the > FreeBSD forums... > > https://forums.freebsd.org/threads/61050/ > > On Sun, Aug 13, 2017 at 7:14 PM, Barry Warsaw <barry(a)list.org> wrote: > >> Thanks for the reference John, >> >> > On Aug 13, 2017, at 06:52, John Poltorak <karotlopj(a)gmail.com> wrote: >> > >> > Regarding location of mailman.cfg...FreeBSD adopt a strict directory >> > hierachy >> > >> > https://www.freebsd.org/cgi/man.cgi?hier(7) >> > >> > Anything installed outside the base OS belongs in /usr/local >> >> I looked over that page. Does this mean that even if you were to install >> Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want >> mailman.cfg in /usr/local/etc instead of /etc? That would differ from most >> Linux distributions where package manager installed packages would have >> their configuration files in /etc, and where “third party” packages would >> have them in /usr/local/etc. >> >> > I guess that issue is something for the FreeBSD porters of Mailman3… >> >> I think so. I think for now I don’t want to support >> /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion >> if there are some more generic use cases. OTOH, the internal function that >> calculates the search paths could be refactored to make it easy for >> distributions to carry small deltas to add that as a search path (it really >> wouldn’t be that hard to do now, but it’s a little icky). Of course, you >> can’t add a configuration file to find a configuration file. :) >> >> Cheers, >> -Barry >> >> >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >> >

8 years, 2 months

[MM3-users] Re: External MTA incoming mail: configuration

by Mark Sapiro

On 7/30/24 11:18, Roland Giesler via Mailman-users wrote: > > Now, lists.fast.za.net is the mailman server. The docs say that mailman > passes these on to the MTA. However, the MTA (postfix) on > box2.gtahardware.co.za has the following setting in it main.cf: The docs are badly worded. "but also will be passed to the MTA to identify the Mailman host." means passed manually in the MTA's configuration. > virtual_transport=lmtp:[127.0.0.1]:10025 You should not be using virtual_transport. You should be using transport_maps. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > If I reply to a signup confirmation email for example, the mail is > received and processed by box2.gtahardware.co.za, and it is not passed > on to the mailman server. It appears you have a situation where the MX for the Mailman domains is not the Mailman server. You need to configure the MTA on box2.gtahardware.co.za to relay Mailman's mail to the mailman server. You can to this by configuring that MTA to use transport_maps, etc as if it were the Mailman server. In order to get Mailman's generated files on the other server, you need to create a process to do that. When Mailman makes changes by adding or deleting lists or when it is started, it updates the postfix_lmtp and postfix_domains files and calls a command (normally postmap) to update the corresponding .db files. The command can be set by setting `postmap_command` in the `[postfix]` section in mailman.cfg. You can set this to a process which accepts a file name argument and then runs postmap on the file and rsyncs the file and it's .db to the other server. > So what is meant by "but also will be passed to the MTA to identify the > Mailman host" in the docs? As I said, that's badly worded it means 'passed manually to the MTA's config'. > If I change the config of the MTA (postfix) to be > "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming > mail will be forwarded, but how does postfix know that only the mailman > emails should be forwarded and not all the other mail that the server at > box2.gtahardware.co.za receives? Using transport_maps you can forward only list mail. -- 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

[MM3-users] How to process emails with Mailman3?

by Stephen J. Turnbull

Kyle Lahnakoski writes: > I am setting up an email list for my local community (just myself > right now). Being a nerd, I am using Amazon SES to send and > receive emails. Outgoing SES is full of unpleasant surprises. In particular, they restrict use of certain headers (DKIM-Signature is the most important one from Mailman's point of view) and commandeer Message-ID (which means archivers and explicit addressees see a different Message-ID from the one subscribers see). > I have mailman installed on ec2 (using "pip install mailman") and > it is working well enough to send an email to the list with > > /opt/mailman/venv/bin/mailman inject -f <somefile>all(a)mymaillist.org > > SES is putting incoming mail into an S3 bucket, one file per > email. Using a small python program, I use the above command to > send them to the list. It's not obvious to me how to make this work for administrative traffic. As Mark says, it needs to find its way into the 'command' queue ('-q command'), but you may also need to specify what the command is (ie, the extension such as '-join' or '-confirm') using added metadata (the '-m' option, see 'mailman inject -h'). I don't know offhand what the format of that would be, though. (I mention that because 'mailman inject -h' specifies that the target argument is a LISTSPEC, either the List-ID or the posting address, which would not include the extension that tells Mailman what to do with the message. Just putting it in the command queue is probably enough, though.) As far as I know, SES does no filtering incoming. If that's true, you would make life a lot easier by installing an MTA and having it relay incoming mail to Mailman as usual, rather than queuing the mail in an S3 bucket (saving the cost of the bucket). If I'm wrong, you have to trade off the benefit of filtering vs. simplicity in your operations. Alternatively, using the 'LMTP' class from 'smtplib' your Python script is almost a one-liner. You get the intended recipient from 'Delivered-To' (if it exists, if not life is considerably more complex), the sender from 'Sender' or 'From', and just pass that on to the LMTP object's send method to send to localhost:8024 (assuming the default port). Steve

7 months, 3 weeks

[MM3-users] Re: HyperKitty and duplicate emails across maillists

by Abhilash Raj

On Mon, Sep 16, 2019, at 9:31 AM, Stephen J. Turnbull wrote: > Derek Lambert writes: > > > For new messages does mailman generate unique message IDs for each > > recipient? > > Mailman in principle doesn't generate message IDs at all. That's the > job of originating clients or their MTAs. > > Mailman is what is called an "intermediary": it may do useful > transformations on a message (such as adding RFC 2369 header fields > and the List-Id field, as well as headers, footers, and subject > decorations, removing banned media types, and even changing the format > of text parts (such as removing HTML parts from multipart/alternative > messages, or translating HTML to plain text by formatting with a > browser such as Lynx), but in some sense the content of the message > remains faithful to the author's intent. In such cases, the message > is considered to be the same for the purposes of assigning Message-Id, > so Mailman doesn't touch it. > > In the case that Mailman receives a message that has no Message-Id, it > may be a good idea to generate one. (I don't think this is > implemented. It has its problems as well as its benefits.) > Otherwise, no, Mailman leaves the existing Message-Id alone. > > > E.x. if multiple lists (children) are members of another list > > (parent), will the children lists all be able to archive the same > > message sent by parent? > > Yes. I'm not sure whether the message body is stored multiple times > or only once[1], but the primary key for archived message is > effectively the list id plus the message-id. It is stored separately for each list and Hyperkitty enforces unique combination(like Steve mentioned :-) of list_id and message_id. So, you can't have two message with same id in the same list but in separate lists, they should be fine. > > Steve > > Footnotes: > [1] Probably multiple times, once for each list that has archiving > turned on. Ensuring that any relevant decorations (headers, footers, > Subject tags) are consistent would require pretty fragile analysis of > the messages and complicated storage and indicies. > _______________________________________________ > 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)

6 years, 1 month

[MM3-users] Re: error when starting the mailman executable from the venv

by Christian Stalberg

Thanks for the quick response Brian. No I did not try what you suggest. I rebooted the entire server and that fixed it. What can I do to prevent this from happening again? -----Original Message----- From: Brian Carpenter <brian_carpenter(a)emwd.com> Sent: Wednesday, February 10, 2021 5:52 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: error when starting the mailman executable from the venv Have you tried using the following as root? #systemctl restart mailman On 2/10/21 8:39 AM, Christian Stalberg via Mailman-users wrote: > I tried to access a 'held' message and got the 'Mailman REST API not > available. Please start Mailman core.' error message. When I went to > start the mailman executable from the venv I get this > > #~mailman/mm/venv/bin/mailman start > Starting Mailman's master runner > Generating MTA alias maps > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.3.2', 'console_scripts', 'mailman')() > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", line 829, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", line 782, in main > rv = self.invoke(ctx) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke > return super().invoke(ctx) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", line 1259, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", line 1066, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", line 610, in invoke > return callback(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func > return f(get_current_context(), *args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/commands/cli_contr ol.py", line 131, in start > os.execl(*execl_args) > File "/usr/lib/python3.7/os.py", line 539, in execl > execv(file, args) > TypeError: expected str, bytes or os.PathLike object, not NoneType > > > Please advise. Thank you. > ~Christian > _______________________________________________ > 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/ -- Brian Carpenter Harmonylists.com Emwd.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/

4 years, 8 months

[MM3-users] Re: mailman import21 passwords

by Mark Sapiro

On 9/16/24 18:18, Sam Darwin via Mailman-users wrote: > >> inherently not secure > > The passwords were good enough for mailman2. If a mailman2 instance has been in production for 20 years and users aren't complaining about security, maybe it's not a show stopper There are regular complaints dating back at least to <https://bugs.launchpad.net/mailman/+bug/265179> about passwords mailed in the clear. > The point is to make the upgrade seamless. That means... being able to say that everyone gets to keep their user account and password. To be able to easily tell the users "Your account is still the same. Just log in. Change your password when you like." But is it "the same"? What about an import of two lists with members which are the same person, but with possibly separate email addresses and/or passwords? Do we really want to create multiple Django users, or let the user create one Django user with multiple addresses? > In the current context, passwords are associated with django accounts rather than mailman-core accounts. So this is about creating django users. > >> creating a django user is "expensive". "poor performance" > > I didn't follow what that means. What is expensive? What is poor performance? I pointed to <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> which discusses the performance issue as a reason for dropping the import of MM 2.1 passwords. > Creating new django accounts en masse would be a one-time operation. It doesn't matter if it's slow, or expensive, since it only happens once. While probably not typical, mail.python.org currently has (still) 209 MM 2.1 lists with 40261 unique member addresses. Creating 40261 Django users, even just one time would probably be painful. > And it would be optional. With the --django-accounts flag. Or another separate script. Then you can tell users "Your account is the same as before. A transparent upgrade. Just log in". I really don't understand why telling the user that she has an account and she can just log in with one of the N MM 2.1 passwords she had on the N MM 2.1 lists or get a reset email if she doesn't know or remember the password(s) is any easier for the user than telling her to go to ... and sign up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

Thanks for some clarification. I cleared out 2800 held messages via Python shell "mailman -l" option and it took about 28 hours. Anything done via Mailman shell is a connection from Mailman core to the database, correct? Although I can't replicate that many messages via Postorius/DJango, I do see similar slowness there as well at a message per minute or more of processing. I recreated the above Mailman shell clean up via Docker container running MariaDB and noticed similar processing time for discarding held messages. That leads me to conclude that the issue isn't network related or specific to AWS RDS. I'm open to testing and switching over to Postgres if that is the straightforward solution. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022 10:23 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages Caballero, Danny (Dan) writes: > I don't understand. We have a single database configured for > everything. I don't recall reading anything in the set-up > documentation about using more than 1 database for Mailman3. I was trying to help localize the database request to one of the three major components: core, Postorius, HyperKitty. If you use the two- database scheme documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… knowing that database would at least identify whether the slowness is associated with core or with the web apps. The excruciating details: Conceptually, there are three separate databases: the one used by Mailman core to manage everything but authentication and archives, the one used by Django to manage authentication for HyperKitty and Postorius, and the one used by HyperKitty to manage archives. They don't share tables, and there are no name collisions for the tables so it doesn't really matter how the backend handles them. The two database configuration is not really a recommendation. I suppose the practice derives from an abundance of caution, as there are concepts like "User" that must be implemented in somewhat different ways across components (core doesn't authenticate users, while Postorius's primary function is authentication of users). I myself would worry that there might be name collisions among tables, which would cause mayhem, but that's probably excessive.

2 years, 11 months

[MM3-users] Re: Message Sent to A Re-Created List Results In Error

by matthew＠alberti.us

Mojo, Thanks for the link. I finally got it sorted out. I probably need to write all this somewhere else. I have a combination of local, virtual, alias, and Mailman3 mail transport/routing, all on one server. Virtual, alias, and Mailman3 all use the same domain. Mailman also has an additional domain. It seemed like no matter what I did, the virtual mail would not work and mailman would, or the virtual mail would work but the domain that is both virtual and mailman wouldn't work with mailman. The problem was the (well documented) behavior when defining "virtual_transport" (for dovecot lmtp) and "virtual_mailbox_domains" (for virtual domains and Mailman domains). When "virtual_transport" is defined, the "transport_maps" option is basically ignored, which causes Mailman to not work (assuming Mailman is setup with virtual domains, not alias or relay). When I took out "virtual_transport", then virtual mail via dovecot stopped working. To fix it, I ended up creating an additional mysql lookup for the virtual mail (they use dovecot lmtp for delivery). I put this lookup in the "transport_maps", and things seem to work. Now Postfix will check with both the virtual mailbox database and Mailman's lmtp regex list, and know the correct transport (dovecot-lmtp and mailman-core lmtp) respectively. So after all that, I have to circle back around and see if there is still an issue with using aliased or virtual addresses as a Mailman owner or subscriber. I'm guessing probably not, since now the correct transport method for each is now defined to Postfix. Thanks for reading. - Matt Alberti -----Original Message----- From: Morris Jones <mojo(a)whiteoaks.com> Sent: Tuesday, December 15, 2020 1:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml#unusual-postfix-configuration I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously. I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/ma ilman-zimbra-integration.rst See if that helps ... Best regards, Mojo On 12/14/20 9:38 PM, matthew(a)alberti.us wrote: > I checked all over the mailman core logs and couldn't find a problem. > But then I noticed that the 550 error was coming from dovecot-lmtp. > I should rename this thread because the actual problem seems to be > unrelated to re-created lists. > > It seems like the actual problem seems to occur in the following > situation: > > * Using Postfix > * Using Dovecot > * /etc/postfix/virtual includes addresses with same domain as mailman > lists. > * An e-mail address subscribed to a mailman list is in the > /etc/postfix/virtual file as an alias (possibly also if destination > address for an alias). > * (Possibly related) E-mail address is also one of the list owners. > > In that environment, Postfix seems to check only 'virtual_transport' > list, which in my case is dovecot-lmtp, and when it doesn't find the > mailman listname@domain entry in there, it sends a 550 user unknown. > It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp. > > When I remove that one address (that is in /etc/postfix/virtual) from > the list of subscribers, I'm able to post again. Interestingly enough, > when I put it back in as a subscriber. I'm still able to post. So it > seems unsubscribing and re-subscribing that address fixed it, or > adding an additional list owner and deleting it fixed it, or some > combination of those. > > I know this might be shaping up to be a very unlikely scenario. But > basically the account is mine, an admin, doing testing before/after a > deployment.. I'll try to create a few test procedures to document the > method to reproduce the problem, and also hopefully fix it. If I can > do that, I'll open another thread. This could also be a postfix config > error of some kind, which is definitely possible if not likely. > > Thanks for reading. > > - Matt Alberti > > > > -----Original Message----- > From: Abhilash Raj <maxking(a)asynchronous.in> > Sent: Monday, December 14, 2020 11:42 PM > To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> > Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In > Error > > > > On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us > <mailto:matthew@alberti.us> wrote: >> I created a list in the Postorius interface, used it, and then >> deleted it. A week or so later, I re-created the list, and things >> were fine thru the creation and subscription process. But when I sent >> a message to the list, a >> "550 user unknown" error was sent back. > > Can you share more error details from the Mailman logs? If 550 error > response was sent, there must be some internal error traceback in the logs. > >> >> >> I tried to determine if this is a known issue by searching the issues >> in Gitlab; but didn't find anything. But wanted to ask if this was a >> known issue or not? > > I personally don't remember seeing such an issue, but Mark or others > might know. > >> >> >> >> Thanks. >> >> >> >> - Matt Alberti >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> To >> unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> To unsubscribe send an email to > mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > _______________________________________________ > 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/ > -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.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/

4 years, 10 months

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

On 4/26/21 2:00 AM, Andrew Hodgson wrote: > > Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: > > [2021-04-26 08:53:12 +0000] [28181] [ERROR] Error handling request > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request > for item in respiter: > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox > msg = email.as_message() > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message > msg["Message-ID"] = "<%s>" % self.message_id > File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ > self._headers.append(self.policy.header_store_parse(name, val)) > File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse > raise ValueError("Header values may not contain linefeed " > ValueError: Header values may not contain linefeed or carriage return characters Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. I think if you replace the ``` msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py with ``` msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. Please try it and report. > I do still have the original mbox files for the imported lists which were on Mailman 2.1. The other thing is when downloading these mbox files I noticed they aren't the raw messages as we had in Mailman 2.1 but modified with headers stripped and email addresses modified. Is there any way to get the raw mbox back as in the option we had in Mailman 2.1? Not from HyperKitty. It doesn't store the raw messages anywhere, but if you enable the prototype archiver for a list, the raw messages will be stored in maildir format in var/archives/prototype/list(a)example.com/ for each enabled list. Messages imported with hyperkitty_import won't be there, but all posts to the list, at least since enabling the prototype archiver, will be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: How to fix lists with characters errors?

by Helio Loureiro

Hi, Thanks a lot! Nice catch. It was indeed loading as latin-1. Not sure why, but that's a matter to discuss on the Ubuntu mailing list. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 24 Mar 2024 at 01:07, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/23/24 11:56, Helio Loureiro wrote: > > Hi, > > it is python 3.10. Problem is... some mailing lists were created long > ago, > > with python2 something. Most probably 2.5. And the tables on mysql were > > set to latin1. > > > This has nothing to do with the data or the charsets/collation in the > database. The issue is the locale setting in your python is causing > stdout output from the `mailman members` command to be encoded as > `latin1` and at least some user's display name contains a `\u0142` (i.e. > `ł` character. > > > > That I know. Question now is how to fix this. Any suggestion? What is > > the table? I probably can run some script for these specific lists that > > have the failure, import data as latim-1, and update back to the table as > > utf-8. > > That's not the issue. The issue is the Python in your venv has > sys.stdout.encoding set to latin1, probably for locale reasons. You ca > apply this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -17,6 +17,7 @@ > > """The 'members' subcommand.""" > > +import sys > import click > > from mailman.core.i18n import _ > @@ -30,6 +31,9 @@ from zope.component import getUtility > from zope.interface import implementer > > > +sys.stdout.reconfigure(encoding='utf-8') > + > + > def display_members(ctx, mlist, role, regular, digest, > nomail, outfp, email_only, count_only): > # Which type of digest recipients should we display? > ``` > to mailman/commands/cli_members.py to fix the issue. > > -- > 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 helio(a)loureiro.eng.br >

1 year, 7 months

[MM3-users] Re: External Mail-Server?

by Abhilash Raj

On 9/12/21 12:21 AM, Florian Schulze wrote: > Hi! > > But LMTP is the "Local" Mail Transfer Protocol. I only have access to > IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming? For incoming, you'd have to have a local MTA that can receive emails over SMTP and deliver it to Mailman over LMTP. Mailman also accepts emails over HTTP API, but you'd have to have a separate application listening for incoming mails and sending it to Mailman with appropriate parameters. Mailman by itself doesn't have a way to listen for incoming emails or fetch emails from a remote mailbox. > > Regards, > Florian Schulze > > > On 11 Sep 2021, at 21:21, Jörg Michael Schulz via Mailman-users wrote: > >> Hi, >> >> yes, this should be possible. >> >> See the parameters in your mailman.cfg: >> >> [mta] >> # The class defining the interface to the incoming mail transport agent. >> incoming: mailman.mta.exim4.LMTP >> #incoming: mailman.mta.postfix.LMTP >> >> # The callable implementing delivery to the outgoing mail transport >> agent. >> # This must accept three arguments, the mailing list, the message, and >> the >> # message metadata dictionary. >> outgoing: mailman.mta.deliver.deliver >> >> smtp_host: mail.yourfavoritedomain.de >> smtp_port: 25 >> smtp_user: >> smtp_pass: >> >> Am 11.09.21 um 19:53 schrieb Florian Schulze: >>> Hi! >>> >>> Is it possible to use an external Mail-Server? Does mailman3 support >>> that directly, or would I have to setup a local MTA which somehow >>> fetches incoming mails from the external inbox and uses the external >>> Mail-Server for delivery? >>> >>> Does anyone do that and have example configurations? >>> >>> Regards, >>> Florian Schulze >>> _______________________________________________ >>> 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/ >> >> >> _______________________________________________ >> 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/ > _______________________________________________ > 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)

4 years, 1 month

[MM3-users] Request Entity Too Large

by Christian Stalberg

Now mail sent to mm3 for distribution is not going out, for two different lists. The mailman.log shows this error: Oct 17 21:50:00 2021 (491) ACCEPT: <030601d7c3a0$ee342f20$ca9c8d60$(a)somedomain.com> Oct 17 21:50:04 2021 (488) HyperKitty failure on https://somedomain.net/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> (413) Oct 17 21:50:04 2021 (488) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Oct 17 21:50:04 2021 (488) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Please advise. TY. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, October 16, 2021 11:21 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen > and in the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- 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/

4 years

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Stephen J. Turnbull

Mark Sapiro writes: > > On Thu, Jan 25, 2024 at 4:43 PM Wikinaut <mail(a)tgries.de> wrote: > > > >> I recently found the "pipx" wrapper very useful and wanted to > >> ask you if this could be facilitate the fresh installation of > >> the mailman3-suite. Has anyone in the list already experiences > >> installing mailman and mailmanweg through "pipx"? > pipx apparently does create virtual environments. See > https://pipx.pypa.io/stable/comparisons/ > > The thing there that concerns me is "pipx replaces a subset of > pip's functionality; it lets you install cli applications but NOT > libraries that you import in your code." > > What does this say about the multiple dependencies that we install. I'm pretty sure it will install dependencies. I think (everything I say below is based on reading the README.md from pipx's pypa.io repo, so caveat installer) that the complexity that will arise is that (for example) a naive approach like $ pipx install mailman $ pipx install mailmanweb $ pipx install postorius $ pipx install hyperkitty will create 4 separate venvs with 3 copies of mailmanclient, 3 copies of django-mailman3, and two copies of Django. Besides the space waste, there's also the small problem that mailmanweb won't have copies of postorius and hyperkitty in its venv. :-þ pipx has an "inject" command that allows adding other packages to a venv, but I think this means that pipx has no great advantage over the standard way of installing mailman into a venv. pipx also installs stuff into the user's $HOME, specifically into ~/.local/share/pipx/venvs which I think will be kind of annoying if you need to dig into package resources. (I expect that you will still install configs into /etc/mailman3 and various data into /var/lib/mailman3/var or /opt/mailman3 or whatever without a problem.) This would only be an issue for heavy-duty customizers. This can probably be customized. One of the big advantages pipx touts is "look ma, no sudo". That's not really an advantage for system daemons, though. So bottom line is you can do it, but you'll need to study up on pipx arcana, because Mailman is a bunch of daemon it buys you very little, and the result won't look like any Mailman installation you've seen described on mailman-users or StackExchange. Steve

1 year, 9 months

[MM3-users] Re: list of subscribers

by Simon Hanna

On 02/04/2018 08:37 PM, Peter Münster wrote: > On Sun, Feb 04 2018, Simon Hanna wrote: > >> You should be able to use mailmanclient to get a list of subscribers with >> names. > It seems, that mailmanclient does not know about the real name (the > first name and the last name in Django). But this seems to work: > > from django.contrib.auth.models import User > user = User.objects.get(email='address(a)of.user') > print(user.first_name) > print(user.last_name) > > So, I'll try to make some loop over a list with email addresses, that I > can get on the web interface. These are names that are saved in Postorius' (django) database and have nothing to do with mailman. Furthermore you will only find them if people have logins for the frontend. They don't have to. Also these names are optional. They aren't populated during signup and people have to provide them afterwards themselves. >> Names are optional though, if people signup without them you won't be able to >> get them. > My usage of mailman is perhaps a bit special: users can't sign up, only > the site owner signs up manually with create_user(email=, first_name=...) > Then the site owner creates the mailing lists and uses mass subscription > (for example all members of a basketball team). At one moment, the list > of subscribers should be verified by all members, just to be sure, that > nobody got forgotten. > > >> Currently there is no option to require names. I'll open an issue in >> postorius about showing the name in the member list if there is one >> associated. > Thanks. It would be nice, to see the first_name and the last_name of the > django-auth user object. > > >> IIRC one person(postorius account) can also signup at different lists using >> different names (regardless of address). > You mean the "display_name" of mailmanclient here? I won't use it. > For my usage, I prefer a clear association of email, first name and > last name in one account, no need for "display_name" here. Displaying the names stored in django probably won't happen. Matching the names in django with the members in lists would require lots of code where people can just supply their name when they signup for a list. Also you might want to be known by name on one list and not on others...

7 years, 8 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Stephen J. Turnbull

Abhilash Raj writes: > I don't have any strong opinions on treating all disabled options as just > disabled for the user. Good. > Would List admins be interested in knowing more details about that > or should it be the same for them? I feel they might be interested > in such details. Brian mentioned that Affinity actually details > explicit value of the delivery_status, so maybe it is useful for > them? I think they definitely are interested in the disabled by bounce case. If you get one complaint, sort the page by en-/dis-abled status, and the whole first page is "disabled by bounce", I bet you react strongly. :-) The distinction between disabled by admin and disabled by user is pretty small -- I suppose most "disabled by admin" are either cranky or technically innocent user requests. > > This is probably a good idea, but in a situation where we know the > > problem is excessive bouncing we should caution [...]. > Yeah, a link to an FAQ entry in documentation perhaps? Maybe that would be enough. I'll think about it. > I am thinking that most addresses disabled due to bounces would > really either be spam subscriptions or abandoned/invalid email > addresses that once were working. Normally, yes, but situations like DMARC April 2014 and upgrade from old Mailman 3 do happen. I think we should focus on the situations that cause users and admins pain. > > Surely we can help them go directly there? > > I guess yes, but that brings up the whole discussion about how does > Core know about the URLs. I was afraid of that. Users will complain if they have to go from login to user page to list page to options (I don't think it's that bad, though), but they will be able to get themselves re-enabled. Making it a more friendly experience can wait if the solution isn't obvious. > Although, we can add "Goto your list subscriptions to re-enable" your > subscription. This sounds good. > Maybe even a new email command that allows re-enabling > subscription without logging into P? I don't like that much, as to be useful it would have to bypass authentication or require plain-text credentials, and even the latter would be beyond many users. Bypassing auth would allow annoying attacks where you enable all of a person's post-only addresses for mail delivery.

4 years, 8 months

[MM3-users] Re: Managing mailman3 via curl (using bash-scripts or perl-scripts)

by Christian Schneider

Hello, thank you very much to everyone who took part in this discussion! I got a very interesting insight! @Jeremy: The ansible approach is fabulous! My team plans to go the ansible way for various automation and configuration tasks! So this is a good perspective for the future! And with your link to the ansible file I am prepared for the change to come... :-) Also the remark on using the venv installed binaries, libraries etc. from outside is very helpful. @Stephen: Thank you for your warning! I will keep it in mind while doing such kind of operations from outside the environment. (I am familiar with the shell and shell variables like PATH, LIBRARY_PATH etc...so I hope I can get along... :-)) Your comments on my curl-command are right and this is due to my "anonymization"-effort: > > Is this a viable curl-call to create a user?: > > curl -X POST -u 'admin-user:<password>' -H "Content-Type: application/json" -d '{ > > "email": "peter.rabbit(a)example.org", > > "display_name": "Peter Rabbit", > > "password": "secret" > > }' http://localhost:8001/3.1/users > > > > The "admin-user" in this command is the "restadmin" user, not the > list-owner. I think in the 'create-list' command you meant the > --admin-user to be the list owner. > Also, the "password" attribute is not very useful in Mailman 3. The > only authorized user of the REST API is the restadmin user. There is > no provision for access by other users. To authenticate other users, I should have used the alias "restadmin" and the password "restadmin-password" for the "-u"-parameter to be more precise...so the curl-call should look like this: curl -X POST -u 'restadmin:restadmin-password' -H "Content-Type: application/json" -d '{ "email": "peter.rabbit(a)example.org", "display_name": "Peter Rabbit", "password": "secret" }' http://localhost:8001/3.1/users And for describing the call of my high-level script I should have used: ./create-list --listname myfirst.list(a)lists.example.org --owner-email peter.rabbit(a)example.org [--owner-name "Peter Rabbit"] Using python...I think your suggestion: > However, in production, you would most likely use "mailman shell -r script". is the recommended way according to the docs here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… Once again: Thank you very much to everyone for this enlightening and helpful discussion! Kind regards Chris

1 month

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Michael Heseltine

Hi Mark, I was confused by the wording of that segment and ended up using another file as template for the settings.py. I have now copied the Gitlab settings.py to my installation, just changed the "DEBUG = True" to "DEBUG = False", and nothing else. But that did not change anything, I still get the following error message when running "/opt/mailman/mm/bin/mailman-post-update" in the venv: > ~# /opt/mailman/mm/bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line > utility.execute() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute > django.setup() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/__init__.py", line 24, in setup > apps.populate(settings.INSTALLED_APPS) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/apps/registry.py", line 114, in populate > app_config.import_models() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/apps/config.py", line 301, in import_models > self.models_module = import_module(models_module_name) > File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1014, in _gcd_import > File "<frozen importlib._bootstrap>", line 991, in _find_and_load > File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 671, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 848, in exec_module > File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/models.py", line 1, in <module> > from compressor.conf import CompressorConf # noqa > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/conf.py", line 9, in <module> > class CompressorConf(AppConf): > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/appconf/base.py", line 73, in __new__ > new_class._configure() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/appconf/base.py", line 102, in _configure > value = callback(value) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/conf.py", line 115, in configure_url > if not value.endswith('/'): > AttributeError: 'NoneType' object has no attribute 'endswith' Do I need to repeat any steps in between the creation of the settings.py file and the running of "/opt/mailman/mm/bin/mailman-post-update"? Cheers, Michael.

3 years, 10 months

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mark Sapiro

On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? In what log is that message? Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. > > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Getting rid of held messages from the command line

by Aymeric Mansoux

Hello, We're currently running some of Mailman software, as available via pip, namely: - mailman 3.1.1 (pip3) - postorius 1.1.2 (pip2) - hyperkitty 1.1.4 (pip2) - mailmanclient 3.1.1 (pip3) So far so good, however, for some reasons, a couple of our lists have started to accumulate held messages that cannot be manipulated via the REST API. Regardless if we use the web interface or mailmanclient, it ends up with: Mar 14 10:58:32 2018 (24287) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.5/dist-packages/falcon/api.py", line 244, in __call__ responder(req, resp, **params) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource resource = super()._make_resource(request_id) File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource results = requests.get_request(request_id) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request result.data_hash, expunge=False) File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm value = json.loads(keyvalue.value) File "/usr/lib/python3.5/json/__init__.py", line 319, in loads return _default_decoder.decode(s) File "/usr/lib/python3.5/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode obj, end = self.scan_once(s, idx) json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) Mar 14 10:58:32 2018 (24287) 127.0.0.1 - - "GET /3.1/lists/xx(a)xx.xx/held HTTP/1.1" 500 59 Is there a way to manipulate/see/remove these mails differently? Right now this prevent moderation of any held messages (note: some lists do not suffer from this and the held panel or mailmanclient works perfectly fine). Thanks!

7 years, 7 months

[MM3-users] Re: How to remove a nonmember from a list

by Abhilash Raj

On Thu, Apr 9, 2020, at 1:57 PM, skenny(a)scss.tcd.ie wrote: > Abhilash Raj wrote: > > > Could be, I am not sure which operation is it stuck at. Can you check logs to see > > where is it breaking? > > Sure. I'm doing all this under Docker; below is what I see in > /opt/mailman-web-data/logs/mailmanweb.log when I try to delete a > nonmember via the web interface. Thediagnostics appear 30 seconds > after I click on 'delete': It looks like you are looking at the Mailman-web logs. From the looks of it, the client side is basically timing out after 30 seconds. Same seems to be true for the script you wrote (which is calling the REST API underneath using mailmanclient), which is trying to fetch the list of non-members. Can you also look at the server side of the logs? It should be available at /opt/mailman/core/var/logs/mailman.log if you are using the standard docker-compose file from the repository. Abhilash > > ERROR 2020-04-09 20:35:51,482 19 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 672, in urlopen > chunked=chunked, > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without > response > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/requests/adapters.py", line > 449, in send > timeout=timeout > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 720, in urlopen > method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] > File "/usr/lib/python3.6/site-packages/urllib3/util/retry.py", line > 400, in increment > raise six.reraise(type(error), error, _stacktrace) > File "/usr/lib/python3.6/site-packages/urllib3/packages/six.py", line > 734, in reraise > raise value.with_traceback(tb) > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 672, in urlopen > chunked=chunked, > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > urllib3.exceptions.ProtocolError: ('Connection aborted.', > RemoteDisconnected('Remote end closed connection without response',)) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 96, in call > headers=headers) > File "/usr/lib/python3.6/site-packages/requests/api.py", line 60, in > request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3.6/site-packages/requests/sessions.py", line > 533, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3.6/site-packages/requests/sessions.py", line > 646, in send > r = adapter.send(request, **kwargs) > File "/usr/lib/python3.6/site-packages/requests/adapters.py", line > 498, in send > raise ConnectionError(err, request=request) > requests.exceptions.ConnectionError: ('Connection aborted.', > RemoteDisconnected('Remote end closed connection without response',)) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File > "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", > line 21, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", > line 38, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line > 943, in remove_role > roster = getattr(the_list, '{}s'.format(role)) > File > "/usr/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 86, in nonmembers > response, content = self._connection.call(url, data) > File > "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 119, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not > connect to Mailman API > ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie > ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie > > The file /opt/mailman-web-data/logs/uwsgi.log contains just one line: > > [pid: 19|app: 0|req: 82/96] 172.19.199.5 () {46 vars in 1233 bytes} > [Thu Apr 9 20:35:20 2020] GET > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie => generated 5583 bytes in 31411 msecs (HTTP/1.0 503) 5 headers in 180 bytes (1 switches on core 0) > > > > > Can you try doing the same with the REST API, just to verify if it > is the Core which > > has the issue or it is the web frontend. > > Using the REST API, I can successfully remove a named nonmember from > the list. But I see the same pause-then-fail behaviour when I try to > simply list all the nonmembers. My snippet of code can happily > produce a listing of the members, but it gets stuck trying to list > nonmembers, and then 30 seconds later it crashes out with exactly the > same error messages as when I tried to delete a user in the web > interface (see above). My piece of code appears below (II invoke it > like this: > docker exec -it mailman-core bash -c 'python3 > /opt/mailman/local/probe.py scss-sysadmins(a)lists.scss.tcd.ie'). > > from mailmanclient import Client > from mailmanclient import MailingList > import sys > > my_list = str(sys.argv[1]) > client = Client('http://172.19.199.2:8001/3.0', 'restadmin', 'restpass') > this_list = client.get_list(my_list) > > print("\n\nMembers:\n-------------------------------------------------") > for i in this_list.members: > print(i) > > print("\nNonmembers:\n-------------------------------------------------") > for i in this_list.nonmembers: > print(i) > > Thanks again > Stephen > _______________________________________________ > 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, 6 months

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

by Franklin Weng

Hi, It looks like to have some clues now. Mark Sapiro <mark(a)msapiro.net> 於 2019年10月30日週三 13:07 寫道： > On 10/29/19 8:21 PM, Franklin Weng wrote: > > Yes, it is checked. > > Have you checked Mailman's logs - Mailman's var/logs/mailman.log in > particular? > I found some hyperkitty URL error: The default settings of base_url in mailman-hyperkitty.cfg is defined as base_url: http://localhost/mailman/hyperkitty/ In the mailman.log there are messages like: Oct 30 13:53:43 2019 (14259) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF// DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p> I changed it to base_url: https://localhost/mailman3/hyperkitty/ then the log became File "/usr/lib/python3/dist-packages/requests /adapters.py", line 514, in send raise SSLError(e, request=request) requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /mailman3/hyperkitty/api/mailman/archive?key=xxx (Caused by SSLError(SSLCertVerification Error("hostname 'localhost' doesn't match ' lists.slat.org'"))) which makes sense because the SSL certificate applied from Letsencrypt is for lists.slat.org. If I use base_url: https://lists.slat.org/mailman3/hyperkitty/ The log became Oct 30 15:25:50 2019 (6256) HyperKitty failure on https://lists.slat.org/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1> </body></html> (401) In my mailman-web.py: MAILMAN_ARCHIVER_KEY = 'my-key,same as in mailman-hyperkitty.cfg' MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') Not sure what to change here. > Do messages received from the list have an Archived-At: header? > Yes, but it's empty List-Id: 測試論壇 <slat-list.lists.slat.org> Archived-At: <> List-Archive: <> List-Help: <mailto:slat-list-request@lists.slat.org?subject=help> List-Post: <mailto:slat-list@lists.slat.org> List-Subscribe: <mailto:slat-list-join@lists.slat.org> List-Unsubscribe: <mailto:slat-list-leave@lists.slat.org> > > What's in /etc/mailman3/mailman-hyperkitty.cfg? In particular does the > [general] setting base_url define a URL that accesses hyperkitty It seems to be the question… and > does the [general] setting api_key match the MAILMAN_ARCHIVER_KEY > setting in /etc/mailman3/mailman-web.py, but note that the > MAILMAN_ARCHIVER_KEY setting is quotes because it is a Python string > assignment and the api_key setting is not quoted > Yes, it's single quoted. Thanks for all your help! Franklin

6 years

[MM3-users] Re: Mailman issues after re-boot

by paulrubin37＠gmail.com

Ok, I edited request.txt for -lock and -in8 and got: (venv) mailman@mail:~> mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.8.10 (default, May 05 2021, 15:36:36) [GCC] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:xxxxx@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@mail:~> That got me: mail:/opt # systemctl start mailman3 mail:/opt # systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2023-09-29 15:36:13 EDT; 4s ago Process: 20268 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 20271 (python3) Tasks: 15 (limit: 4622) CPU: 16.548s CGroup: /system.slice/mailman3.service ├─20271 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg ├─20277 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─20278 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─20279 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─20280 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─20281 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 ├─20282 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─20283 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─20284 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─20285 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─20286 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─20287 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 ├─20288 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 ├─20289 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 └─20306 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg gatenews Sep 29 15:36:11 mail systemd[1]: Starting GNU Mailing List Manager... Sep 29 15:36:12 mail mailman[20268]: Starting Mailman's master runner Sep 29 15:36:12 mail mailman[20268]: Generating MTA alias maps Sep 29 15:36:12 mail systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Sep 29 15:36:13 mail systemd[1]: Started GNU Mailing List Manager. YEAH! progress. When I tried to use mailman-web I get this error: django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE Which config file is this and what do I need to add?

2 years, 1 month

[MM3-users] Re: Main daemon process sticks around after forking

by Jérôme Charaoui

Mark Sapiro wrote: > On 8/6/25 18:17, Mark Sapiro wrote: > > On 8/6/25 09:03, Jérôme Charaoui wrote: > > I'm running a (rather large) mailman3 instance on Debian 13 (trixie) > > using the distribution packages. > > To manage the mailman3 daemon, the package installs this systemd > > service unit: > > https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ > > It has been working fine until recently: after a reboot, we noticed > > the mailman3 unit consistently failing to start due to a timeout error. > > I figured out that the timeout was related to the service unit type > > (Type=forking) and the fact that the main/parent process was forking > > subprocesses (and running normally), writing a PID file, but it wasn't > > exiting, so systemd identifies this as an error and aborts the service. > > The master is not supposed to exit. It continues to run and monitor the > > child runner processes and will under some circumstances restart a > > runner that dies. > > Further, our recommended systemd configuration is at > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman... > and includes Type=forking and this is the first I've heard of an issue > with that. I ended up figuring out the problem by myself: I needed to create a list, and via the web interface it would return a 502 error after a small delay. On the command-line, the "create" operation was hanging forever, never completing. I used strace to check out what the process was doing and saw it was in a loop attempting to get a lock on "/var/lib/mailman3/locks/mta". There were a number of files in that locks directory that also seemed stale, so I stopped the mailman3 daemons, removed all the lock files manually, and started them again. That fixed both creating a new list and the fact that the startup process was not exiting as systemd was expecting. [0] It seems to me like this all might be caused by some code path that will retry forever to get a lock without ever timing out or logging some error. Furthermore, I suspect the stale lock file themselves could have been a side-effect of the extremely frequent OOMs we were suffering from before disabling HYPERKITTY_MBOX_EXPORT, due to scrapers continuously hitting /export/ endpoints. [1] [2] [0] https://gitlab.torproject.org/tpo/tpa/team/-/issues/42255 [1] https://gitlab.torproject.org/tpo/tpa/team/-/issues/41957 [2] https://gitlab.com/mailman/hyperkitty/-/issues/385

2 months, 3 weeks

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://gitlab.com/mailman/mailman/-/issues/417> fixed by <https://gitlab.com/mailman/mailman/-/merge_requests/329> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/bin/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 >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in Mailman's mailman.log? -- 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] Upgrade

by Darren Smith

Hello all, I'm working on upgrading our mailman3 instance. The current running instance is 3.1.0, and I am attempting to move to 3.2.0a1. Partially because La Villa Strangiato is a better song than Between the Wheels, but mostly because we want some of the bug fixes, and we are nailing down our upgrade process for the future. Initially after updating when I ran the "mailman info" command, I got this: Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 7, in <module> from mailman.bin.mailman import main File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 19, in <module> import click ModuleNotFoundError: No module named 'click' So I went and installed click - easy enough to do. But then I get this error: "Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 696, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 621, in make_context self.parse_args(ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1018, in parse_args rest = Command.parse_args(self, ctx, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 880, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 1404, in handle_parse_result self.callback, ctx, self, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 78, in invoke_param_callback return callback(ctx, param, value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/bin/mailman.py", line 93, in initialize_config initialize(value) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 219, in initialize initialize_2(propagate_logs=propagate_logs) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/core/initialize.py", line 178, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/factory.py", line 54, in create database.initialize() File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/base.py", line 107, in initialize url, isolation_level='READ UNCOMMITTED', pool_pre_ping=True) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/__init__.py", line 387, in create_engine return strategy.create(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 160, in create engineclass.__name__)) TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), using configuration PGDialect_psycopg2/QueuePool/Engine. Please check that the keyword arguments are appropriate for this combination of components." Anyone able to point me where to go to look for a solution for this? We're running postgresql as the database, and psycopg2 has been installed. Thoughts? -Darren

7 years, 6 months

[MM3-users] Re: Trying to configure a list (hosted)

by Abhilash Raj

On Sat, Aug 31, 2019, at 6:25 PM, paul(a)arenson.org wrote: > I guess my message wasn't clear? > > Let me try again. > > I have not made any list settings or sent mails because I do not want > my archive filled with a lot of test mails. > > I am simply trying to understand > > a) why there are supposed to be two ways to sign up--one where you just > get the messages by email and one where you are able to interact with > the archives and send from the web interface. > > Example, as seen here---> > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… Web UI is only of the ways you can configure subscriptions to the MailingList. A user can purely interact through email to subscribe to a MailingList, a possible 3rd way to sign up a MailingList. This is by design for the flexibility of choosing the interface users are comfortable with. > > 1) I was told that Subscription / Unsubscription lets you truly register Login and Sign-Up to the Web UI only lets you manage your subscription through the Web UI, Post through the Web UI. You can interact with Mailman purely through email commands too, without having to ever look at the Web UI. Send an email to <listname>-requests@<domain> with subject "help". > > and that just below that > > 2) "You can also subscribe without creating an account" lLets you just > receive emails but not interact with the archives.post from the web. > > CONFUSION > > --> Aside from the confusing use of "subscribe/subscription for both, > when I tried testing both options, BOTH sets of emails ended up in my > members list. > > If there is a guide (I was told it is not ready), it would help, but anyway: > > 3) Can anyone help me understand the problem above? > > 4) Will it go away if I enter my settings? Will my users (this who > truly register with a password) be able to get the archives and post > from the interface? This isn't configurable right now, so you can't disable email commands or subscribing without signing up. > > The next post is about the other issue: > _______________________________________________ > 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)

6 years, 2 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

If I run >>> for mlist in getUtility(IListManager): ... print(mlist) ... <mailing list "testlist1(a)chapelwoodhoadev.org" at 0x7f83f593fba8> I get only one list. Permissions? Where are the other lists? On Sun, Nov 10, 2024 at 11:52 AM Stephen Daniel <swd(a)pobox.com> wrote: > OK. Ran the script. No errors while running it, but when I look at the > users through Postorius GUI, they still show as 'Disabled by Bounces' > > ?? > > On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > >> Thanks all! I will use these pronto. >> >> On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >>> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >>> > >>> >> Mistakes were made, and for while every single outbound email bounced. >>> >> I've fixed the mistakes, but now in my largest and most active email >>> list, >>> >> every single user's delivery status is "Disabled by Bounces". >>> >> >>> >> Is there a way to bulk fix this? Or do I have to go into each user, >>> one at >>> >> a time, and fix them? >>> > >>> > Please see this thread: >>> > >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> >>> The script in that post does all lists. For a single list see >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> but note that the command line >>> ``` >>> $ shell -l list(a)example.com >>> ``` >>> should be >>> ``` >>> $ mailman shell -l list(a)example.com >>> ``` >>> >>> -- >>> 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 swd(a)pobox.com >>> >>

11 months, 3 weeks

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Abhilash, ср, 27 февр. 2019 г. в 22:21, Abhilash Raj <maxking(a)asynchronous.in>: > So, what errors are you looking at in uwsgi*.log? > There are tons of errors like this: Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds Do you see any successful requests in mailman core's mailman.log? > Nope, just 'runner started.' entries. Danil > > > With my best regards, > Danil > > > пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: > > Hi Abhilash, > > Thank you for the quick resolution, but I'm still unable t start the > container: > https://github.com/maxking/docker-mailman/issues/309 > > DB migrations are failing. > > Danil > > вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: > > Hi Abhilash, > > Thank you for the explanation, I've created a report: > https://github.com/maxking/docker-mailman/issues/307 > > Danil > > > > сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: > > On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: > > Hi, > > > > I'm interesting in Mailman3 deployment with archiving feature completely > > disabled. > > > > I've tried to deploy Core + Postorius using this docker-compose > > template: > > > https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… > > > > Unfortunately Postorius version came with this template is quite > outdated: > > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image > I > > see version 1.2.3. > > > > I've also checked image maxking/postorius:rolling but it seems > > irrelevant/broken (container exits with error). > > > > Are there newer Postorius docker image I can use? > > No, but if you could report the failure and error that you, maybe the > Maintainer can help > fix that issue you have? > > P.S. I maintain those images. The Postorius image is kind of neglected > since there are > fewer people using it, but I'd be happy to fix any error that you see. > > Package ugprades are merely a version number bump in Dockerfile :) > > -- > thanks, > Abhilash Raj (maxking) > > > -- > thanks, > Abhilash Raj (maxking) > > >

6 years, 8 months

[MM3-users] Re: Docker or virtualenv?

by Tim Cutts

Sent from my iPhone > On 31 Dec 2022, at 13:22, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > Tim Cutts writes: > >> Has anyone considered whether it’s feasible to turn it into a bunch >> of Lambda functions with a serverless database behind it? > > ... you just did. I'm not sure if "patches welcome" is appropriate > for what looks to me to be a pretty radical idea, but someone could > give it a try. :-) > > I don't think anybody in Mailman core has thought about it though. I > don't really see the advantage for most sites. Cost and simplifying security updates, principally. The more I think about it the more I suspect it would be too radical a re-write, and it would probably simpler to use Amazon’s SES to send the mail rather than a traditional MTA. People have done simple newsletter type lists this way (https://blog.marcolancini.it/2020/blog-serverless-mailing-list/) and they’re very cheap to run because there’s no permanently running infrastructure, and for smaller sites almost certain to sit within the free tier. Nowhere near as sophisticated in capabilities as Mailman, but easier to keep secure, since most of the underlying dependencies are gone. No operating system to patch, no database upgrades. > Hosts, especially VMs, > are cheap, and unless you're running the lists for a major university > or the like, lowest tier hosts will do. > That was true until MM3. I had to double the size of VM I use when I went from MM2 to MM3. It’s still not huge, but you can’t easily run MM3 on a free tier VM on AWS any more, it needs too much RAM. I found 2GB is probably the practical minimum. > As for "serverless databases", that depends on whether Django and > SQLAlchemy support them. Mailman has a lot of code invested in those > ORMs. Which is why I thought it would actually require a fairly drastic re-write, although of course AWS does offer Pg and MySQL relational databases as a service. That increases the cost again compared to running the DB yourself inside the same VM, but at the benefit of not needing to patch and upgrade the database any more. SQLAlchemy can work with DynamoDB but I’m sure that would have behaviours somewhat different from Postgres or MySQL, and would need some work. I’m just musing here really. Regards, Tim (PS for full disclosure - I work for AWS, but these comments are in my personal capacity) > Steve

2 years, 10 months

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Andrew Hodder

Oh, the SITE_ID was definitely corrected before this, it doesn't show it anywhere else in Hyperkitty, hence why I'm assuming it's connected to the theme itself being all messed up. Nor does it display on every page or every time. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Thu, Oct 26, 2017 at 5:51 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote: > > I have an odd one, my Hyperkitty is functionally working fine (archived > > several lists without issue, can login/out), however I must have done > > something wrong during it's setup as it's layout is completely broken > > (and > > it keeps throwing Example.com up in the top-left corner). > > You need to change SITE_ID in your Django's configuration to point to > your domain name you want to be show there. Default is set to > `example.com` which corresponds to SITE_ID=1 in the Django's > configuraiton. > > How to find the SITE_ID of your domain? > > This is rather no-so-nice right now, you will basically have to go to > the admin console (/admin/) and login as admin. Then you visit > `/admin/django_mailman3/maildomain/` and you should see your domain > there. Clicking on it will how your it's id in URL bar, like > /admin/django_mailman3/maildomain/2 or something. > > I understand this is rather difficult thing to do, there is an issue > open to make this information visible in the UI. Ideally, SITE_ID is > sequential, so if you have only one domain, it is most probably 2. > > > > > > > See attached. > > > > I'd run into a similar issue with Postorious when I first set it up, but > > I > > can't recall what fixed it. Any ideas to what needs correcting? Thanks. > > > > > > > > Sincerely, > > > > Andrew Hodder > > Systems Administrator > > Support Operations, Afilias > > E-mail: drew(a)afilias.info > > Phone: +1 416.673.4164 > > Fax: +1 416.646.1541 > > _______________________________________________ > > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

[MM3-users] Re: [Mailman-Developers] Mailman Core 3.3.1rc1 release

by Brian Carpenter

On 4/10/20 3:31 AM, Abhilash Raj wrote: > Hey Everyone, > > I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. > > This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). > > Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. > > It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. > > There has also been a whole lot of bug fixes. A full list of changes can be found at: > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 > > The release is available via PyPI: > > https://pypi.org/project/mailman/3.3.1rc1/ > > To install this release via pip, you can run: > > $ pip install --upgrade --pre mailman > > Note the `--pre` flag because this is a pre-release. > > If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. > > If there aren't any major breaking changes reported, the final release will be identical to this one. > Well this is exciting and timely. I plan on upgrading Mailman core on my development server today to 3.3.1rc1 so we can start implementing the new REST API elements into Affinity. I will keep you posted via Gitlab if we run into any issues. Thanks! -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 6 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:58 PM, David Newman wrote: > > On 1/14/22 6:35 PM, Mark Sapiro wrote: >> >> The place for feature requests for Mailman core (which this is) is >> https://gitlab.com/mailman/mailman/-/issues, however, this is not >> straightforward as Mailman core doesn't know if you even have >> Postorius or some other web management UI installed or what the URL to >> access it might be. Thus it's not just a simple matter of editing >> templates. It would also require a configuration setting for the base >> URL for the web admin UI and changes in logic to provide an >> appropriate replacement depending on whether or not the base URL was >> configured. > > Understood, thanks. Although this distinction is very important for > server admins, it's likely not meaningful for many list owners and > moderators. For them, MM2.1 sent an email saying "go here" and > MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. > > There is some pending template in use by default, just not one with a > URL included. All the templates have defaults and the defaults don't have URLs because these are unknown to core. > Is this something better handled in the venv and/or Web installation > docs? Or should I file a feature request for core, or Postorious or > someplace else? I think a feature request for core is appropriate. I'm only saying implementing this is a non-trivial change. What I do on sites I admin is put custom versions of all these domain:admin:notice:new-list.txt list:admin:action:post.txt list:admin:action:subscribe.txt list:admin:action:unsubscribe.txt list:admin:notice:pending.txt list:member:digest:footer.txt list:member:digest:masthead.txt list:member:regular:footer.txt list:user:action:invite.txt list:user:action:subscribe.txt list:user:action:unsubscribe.txt list:user:notice:post.txt list:user:notice:probe.txt list:user:notice:welcome.txt in /opt/mailman/mm/var/templates/site/en and at mail.python.org which also has German language lists, in /opt/mailman/mm/var/templates/site/de. That could be documented, but it would be preferable to be able to document just a base web management URL and then put a replacement such as $web_ui in the default templates and replace that with a URL if configured or some generic text otherwise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: toward improving correctness when running on single core system ...

by Odhiambo Washington

I have been following this thread with curiosity. Is there any current Linux OS that recommends a single core hardware with 500MB RAM for a production server? I could whip up a VM with such specs on my laptop using VirtualBox or VMware, but what's the OS? And is it for promotion environment? I don't understand what this thread is trying to prove in the 21st century. I'm sorry to say it's just a waste of time. Perhaps you should try another system for a mailing list. On Tue, 20 Jun 2023, 22:18 Ruth Ivimey-Cook, <ruth(a)ivimey.org> wrote: > One of the simpler ways of experimenting with mailman on a restricted > system is using an SBC - something like a Raspberry Pi 2 or 3, or a > Beaglebone, or similar. Both have limited memory and CPU, and are > relatively slow systems. I would avoid a Pi 4 because it's too powerful > in this context! > > Logging errors always changes the behaviour, but you can do much by > noting things to internal variables and then after the event printing > those (e.g. set a variable to count the number of times a try-lock > operation found the lock held), and perhaps then doing the logging to a > memory filesystem (Linux: tmpfs) which will have much lower latency. > Normally a linux /tmp is using tmpfs. > > A multicore system will have different behaviour to a single core, but > the kernel will almost always be preemptive (force timeslice). So one > option might be to experiment with a fast-tick (e.g. 1000Hz or higher) > kernel such that the timeslices are shorter. (It used to be the case > Linux ran on 100Hz - I know most kernels are now "tick-less", meaning > there is no persistent timer interrupt marking time, but there will be a > unit of timeslice). > > A final option: if the problem is (as it appears to be) one of > starvation, then perhaps the system is better run (on that hardware) > with fewer worker processes. That is, cut the 13 workers down to e.g. 8. > That said, starvation is something that can normally be designed out of > systems though I know far to little about the architecture here to say > if that is the case here. > > HTH, > > Ruth > > > On 19/06/2023 18:51, Stephen Daniel wrote: > > I'm currently running the entire mailman3 stack, including postgres and > > postfix, plus my production web server, all on a GCP e2-small instance. > > e2-small is two virtual CPUs running on a single physical core, > restricted > > to consuming at most 50% of the CPU cycles on that core. The system has > 2 > > GB of memory, 10GB of disk space. > > > > The entire stack runs well, albeit slowly, on this configuration, for > which > > I pay about $13/month. The entire stack is shut down every night so I > can > > take a snapshot while the applications are down. Once the snapshot is > > complete, the stack is restarted. I have no startup issues in this > > configuration. > > > > It is hard to imagine a more limited pool of resources, yet everything > > works. > > > > On Mon, Jun 19, 2023 at 12:38 PM Nelson Strother < > > justfixit(a)marilynstrother.com> wrote: > > > >> [My apologies for the mangled formatting of the diffs in [2] and [3] > >> above. at least as shown on the web view of this list. Will happily > >> repost or resend by direct email if anyone expresses interest.] > >> > >> > Presumably there's also a chance for the runner to detect and log > the > >> expired lock before it dies. > >> > >> This may require some cleverness, as the delays introduced by recording > >> a log message e.g. "I'm the nntp runner holding the lock, and it has not > >> expired yet." are likely to change the results of the lock competition, > >> maybe even allowing all runner processes to continue as intended. It is > >> unclear to me whether a process would ever have an opportunity to record > >> a log message e.g. "I'm the nntp runner holding the lock which has > >> expired, but I am not dead yet." before it dies. If such an opportunity > >> exists, it should extend the lock's lifetime via e.g > >> Lock.refresh(timedelta(seconds=10)). > >> > >> As I attempted to summarize at the end of [3] above, each time I tried > >> shorter sleep intervals (1, 10, 15 seconds) within > >> .../flufl/lock/_lockfile.py the original problem remains, namely one or > >> more locks are broken and runner processes die. > >> > >> On 6/19/23 03:00, Stephen J. Turnbull wrote: > >>> > The best "performance" I have yet obtained on this single core > >>> > system is [by] [3] [which waits 20s before trying to obtain the > >>> > lock]. > >>> > >>> Is 20s necessary? There are a lot of runners, you may be able to cut > >>> the startup time by 2-3 minutes if you can cut that to 5s or less. > >>> That would still be 100x longer than the naive #cores * seconds > >>> estimate, but perhaps significant. > >> _______________________________________________ > >> 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 swd(a)pobox.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 ruth(a)ivimey.org > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > _______________________________________________ > 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 odhiambo(a)gmail.com >

2 years, 4 months

[MM3-users] Re: MTA setup

by Arte Chambers

I'm not sure how to check mailmans shunt queue. I'm not seeing any errors in mailman logs There are several .pck files in Mailman's var/archives/hyperkitty/spool/ I can send email from the server using mail utilities as long as the "from email address" contains the server's domain name. I also notice that in this MM3-Users list the "from" email shows senders(a)emailaddress.com VIA mailman3.org. I'm wondering if I've missed something that would allow my server to behave this way. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Sun, Nov 17, 2024 at 11:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/24 19:32, Arte Chambers via Mailman-users wrote: > > > > Mailman is successfully sending invite emails however user messages sent > to > > the list are not being sent to subscribers. Also in Hyperkitty none of my > > test messages to the list are showing up in the archive. > > > Are there messages in Mailman's shunt queue? Check for errors in > mailman.log. Are there messages for hyperkitty queued in Mailman's > var/archives/hyperkitty/spool/ directory? > > > I am using Postfix with an SMTP relay hosted at Brevo.com (formally > > sendinblue). Brevo's logs show the message getting rejected > > > > > > Log from brevo.com (SMPT Relay) > > Sent on 17-11-2024 21:49:16 > >>From listmember(a)gmail.com > > To listmember(a)gmail.com > > Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= > > BJ7Q(a)mail.gmail.com> > > > > 17-11-2024 21:49:16 > > Sending has been rejected because the sender you used > listmember(a)gmail.com > > is not valid. Validate your sender or authenticate your domain > > > This appears to be something you need to do for the MTA at > smtp-relay.sendinblue.com, or possibly something more is needed in > /etc/postfix/sasl_passwd. > > > #SMPT Relay Brevo > > relayhost = [smtp-relay.sendinblue.com]:587 > > smtp_sasl_auth_enable = yes > > smtp_sasl_security_options = noanonymous > > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd > > > -- > 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 paul.m.robey(a)gmail.com >

10 months, 1 week

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Mihai Moldovan

* On 4/16/25 01:04, Sam Darwin via Mailman-users wrote: > "Virtualenv Installation, recommended for Production" > > It's recommended for production. > > I've followed that method. If someone does this, they may never encounter > or bump into any files from the "distro packaging (specifically in Debian > and Ubuntu)" . True, and that's fine. :) > Which means they're missing out on this particular idea about the mailman > wrapper. The script is small enough it can be described in the docs. > > Let's try a grep inside mailman-suite-docs: > > grep -r -i wrapper * > > no relevant results. They are small scripts, but describing them in the documentation is problematic because they depend on user names and file system locations, which in turn are distro- or even system-dependent. (Just as an example, some distros use www-data as the web service user, which is needed for the hyperkitty and postorius integrations, while other distros use wwwrun and even others just plain www or something else entirely.) Providing such wrappers as part of venv or the upstream repository is hence not possible. This said, nobody prevents you from creating such wrappers for use with your venv installation tailored to your system either, just make sure that you write them up correctly. :) Also, as is often the way, the documentation could probably be also improved. For instance, the migration documentation says: > This, and in general all, mailman commands should be run as the Mailman > user and not as root. Running some of these commands as root can create > files owned by root that can’t be read by the Mailman user. But it doesn't explicitly tell you how to do this. Naturally, as a system administrator installing, maintaining and migrating mailman instances, you should probably know how to run a command as a specific user. su -s /bin/sh -c "mailman ..." $LIST_USER and su -s /bin/sh -c "$PYTHON_BINARY $PATH_TO_MANAGE_PY ..." $WWW_USER is probably what you want to execute commands either as the mailing list or as the web user, with all these variables being pseudo-variables that you want to fill in/hardcode to fit your system correctly. Putting that in the documentation and especially educating users to not use them in a copy-and-paste manner is difficult, though. Try that and you'll probably have an influx of requests along the lines of "I don't have a variable called $LIST_USER, the command fails to execute!" Mihai

6 months, 2 weeks

[MM3-users] Migrating to Mailman3

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > I am about to migrate from mailma2 on CentOS to mailman3 on > Ubuntu. Are there any special gotchas of which I need to be aware? > TIA. * The Ubuntu packages are old, and not well-supported by Ubuntu or the Mailman project. Mailman 3 is not a hyperactive project, but we are making steady progress and many new Mailman 3 users have issues or requests for enhancement for 2-, 3-year-old packages that have been fixed or implemented in the most recent releases. For these reasons, we strongly recommend installing from source or from PyPI in a virtual environment: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… (Installing from source is not hard, but it's more work than using pre-built packages. Source is required for beta testers and developers, but not recommended for most production environments.) * If your preferred RDBMS is in the MySQL family: 1. Make sure the Mailman database(s) have the utf8mb4 charset option set. Otherwise all emoji and some Asian characters will cause your database to throw errors (I think this is mostly an issue for HyperKitty and maybe a few users who put them in their display names in Postorius and Mailman core). This is not needed for PostgreSQL or SQLite3. 2. You may want to increase the timeout for startup (I think this is in the systemd units for mailman and mailmanweb). The issue is that the mysqld doesn't exit until the journal has been flushed to the main database (or something like that), and this may take many seconds. This is not an issue for SQLite3 (it's a library) or PostgreSQL (it uses dbus to notify systemd that it's ready). * The migration scripts for list database and web databases are quite good, but not 100%. * The user model is completely different. Ordinary subscribers will probably be happy or won't notice, but there are some traps for administration roles. The most important is that some list owners will give the owner password to moderators so they can do work like use mass subscribe, but put them on the moderator list attribute so they get the moderation notices. These moderators will lose the "owner" capabilities like mass subscribe. * If you're looking at a multinode installation with Mailman core, Postorius and HyperKitty distributed across several hosts or containers, configuration can be finicky. I don't recommend it unless you're familiar with such distributed operations. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 4 days

[MM3-users] Re: no mails to list members

by Abhijith PA

Thomas On Friday 04 January 2019 03:25 PM, Thomas Stein wrote: > On 04.01.19 10:44, Abhijith PA via Mailman-users wrote: >> Hi. Thomas >> >> On Friday 04 January 2019 02:10 PM, Thomas Stein wrote: >>> On 04.01.19 05:15, Stephen J. Turnbull wrote: >>>> Thomas Stein writes: >>>> >>>> > Thanks for your answer. So the the file in queue/shunt contains >>>> > information too? I will have a look. >>>> >>>> The file in queue/shunt is the message plus some Mailman metadata, as >>>> a Python pickle. You can find out what is in it using "bin/mailman.py >>>> qfile", but probably the log and traceback will tell you (or us) >>>> everything needed to fix the problem. >>>> >>>> If it's a Mailman bug (somewhat unlikely), we send you a patch and you >>>> use "bin/mailman.py unshunt" to reinject the message into the mail >>>> system via Mailman. If it's a nonconforming mail message (somewhat >>>> more likely -- typically this happens when you have raw UTF-8 or other >>>> 8-bit characters in the message header), then the easiest thing to do >>>> is to edit a saved copy of the message and resend from your mail >>>> client. (It's theoretically possible to edit the pickle and use >>>> "unshunt", but Mailman currently does not provide that feature.) >>> >>> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >>> i missed something else but after adjusting the permissions of that template everything worked as expected. >> >> >> Can you explain little bit more about this template, path and its >> permission ? > > Sure. I should start with mentioning the mailing list in question was imported with "mailman import21". After that i had: > > root@shinymail:~# ls -l /var/lib/mailman3/templates/lists/hoppla.domain.de/en/ > total 8 > -rw-rw---- 1 list list 106 Dec 26 18:48 list_member_digest_footer.txt > -rw-rw---- 1 list list 110 Dec 26 18:48 list_member_regular_footer.txt > root@shinymail:~# > > These txt files where owned by root:root. After changing it to list:list the problem disappeared. Thanks for sharing. My instance had same issue. With your investigation I was able to fix the same in mine. Thanks a lot. --a

6 years, 10 months

[MM3-users] Re: Emergency Moderation

by Allan Hansen

> On May 25, 2020, at 23:18 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Allan Hansen writes: > >> Not sure what is the difference between ‘emergency moderation’ and >> ‘Hold for moderation.’ It appears redundant. > > It is redundant. But conceptually, "emergency moderation" is a flag > set on the list, for situations where a flamewar (or spam via spoofed > users) is getting out of hand. "Hold for moderation" is set on > individual users. Of course the latter can be used to implement the > former, but from the moderator's point of view they're used in rather > different situations. Makes sense now. I have all users set to default list moderation, so setting the list to ‘Hold for moderation’ for me is the same. But yes, individual users have other options, then emergency moderation is stronger. > >> Desiring consistency between the lists, I don’t want to turn all >> the moderators into owners who can change list settings. > > Reasonable. This is why Mailman restricts the operations moderators > can perform in the first place. I appreciate that. > >> Many of my moderators keep asking me to see the list of members and >> to subscribe and remove members. I end up servicing those >> requests. So... >> >> a. Moderators should be able to unsubscribe and subscribe members. > > Reasonable, but traditionally (ie, in Mailman 2) they can't, and this > might be inappropriate for some lists. So for backward compatiblity, > we probably need to make this a list owner option (or maybe domain > owner, but if a list owner wants it I don't see why they shouldn't > have it, and denying it creates some perverse incentive to give list > owner credentials or permissions to moderators). I’m willing to do the work now, but would rather it be done by moderators, as these list maintenance things (listing, sub/unsub) seem to be moderator level activities. > > I could see defaulting it on eventually, though. Correct. It could be a domain default, overridden by list owner. > >> b. Moderators should be able to set the member’s moderation status. >> c. Moderators should not be able to see/modify any other member >> settings. > > Not sure if there are other settings "somebody" might want to give to > moderators, but we should remember you definitely don't want > moderators to have them, and make them owner options. Excellent! Thank you, Steve and Mark! Allan

5 years, 5 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

That worked. Now on https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically it says "Pay attention to the config file output above and make sure that you see /etc/mailman3/mailman.cfg there. If the config path is different, you should make sure to create a new config file at /etc/mailman3/mailman.cfg and re-run the command." Well...mailman info yields GNU Mailman 3.3.5 (Tom Sawyer) Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: /opt/mailman/mm/mailman.cfg db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Should I create a new config file at /etc/mailman3/mailman.cfg ? Lastly, when I ran this command it says "loaded failed failed" (venv) mailman@lists:/opt/mailman/mm$ systemctl list-units | grep -i mailman gunicorn.service loaded active running GNU Mailman web interfaces ● mailman.service loaded failed failed GNU Mailing List Manager Please advise. Thank you. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 10:33 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly > (stale_lock). Try using --force mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically -- 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/ LV5WTFTNRZ455KPDESRQHFV67SJ5VOFH/ This message sent to csa(a)web-analysts.net

8 months, 3 weeks

[MM3-users] Re: New problem on new installation of Mailman

by Abhilash Raj

On Tue, Jun 9, 2020, at 9:50 AM, Brian Carpenter wrote: > I am just about done with installing Mailman 3 on a new Debian 10 > server and when I go to run ./mailman-post-update, I am running into > the following error: > > ./mailman-post-update > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 10, in <module> > sys.exit(execute_from_command_line()) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line > utility.execute() > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute > django.setup() > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/__init__.py", > line 24, in setup > apps.populate(settings.INSTALLED_APPS) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/registry.py", line 91, in populate > app_config = AppConfig.create(entry) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/config.py", line 90, in create > module = import_module(entry) > File "/usr/lib/python3.7/importlib/__init__.py", line 127, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import > File "<frozen importlib._bootstrap>", line 983, in _find_and_load > File "<frozen importlib._bootstrap>", line 967, in > _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 677, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 728, in > exec_module > File "<frozen importlib._bootstrap>", line 219, in > _call_with_frames_removed > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/__init__.py", line 11, in <module> > from haystack.utils import loading > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/utils/__init__.py", line 9, in <module> > from django.utils import six > ImportError: cannot import name 'six' from 'django.utils' > (/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/__init__.py) > > I assume it has something to do with Haystack. > > Suggestions for a fix? Downgrade to Django 2.2.x release with something like: $ pip install ‘Django<3.0’ We aren’t compatible with Django 3.0 due to haystack yet. You can also install the latest beta of django-haystsack but that is beta so YMMV: $ pip install -U —pre django-haystack And then restart. > Thanks, > Brian > _______________________________________________ > 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: [ERROR] Error handling request List archivers

by Mark Sapiro

On 7/23/20 12:39 AM, Shashikanth Komandoor wrote: > Thank you Mark for guiding me to the benefit of putting the list and so I > have added the list. > > Along with the [archiver.hyperkitty], [mta] and [database], few lines of my > mailman.cfg look like below: > > > > [webservice] > workers = 4 > timeout = 900 > > The above block of webservice is added yesterday for testing or trail as I > am getting the above issue. > > And there is no line that is calling *gunicorn* in my mailman.cfg. As I tried to explain to you in an off-list reply: You can't configure Mailman's REST gunicorn workers directly in the [webservice] section of mailman.cfg. The only thing you can configure there is: configuration: /path/to/gunicorn.cfg That file, which is separate from your web server gunicorn.cfg, is where you put things like [gunicorn] timeout = 900 It also will not work to put a gunicorn section in mailman.cfg. It must be in a separate file pointed to by webservice.configuration. Increasing the number of workers won't help this issue. > Apart from that I tried to locate and see the content of the gunicorn.cfg > file as below : > > *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg > [gunicorn] > # All the options that can be put here are available at > # http://docs.gunicorn.org/en/stable/settings.html#settings > > # No of seconds to wait before killing the worker processes. > graceful_timeout = 30 > > Please confirm the time I have to change is *graceful_timeout *in > *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I > have never used or never known about this *gunicorn* but still running the > service in production. First, the file you reference above is the default gunicorn configuration for the REST server. You don't want to edit this file because your changes will be overridden in an upgrade. You want to create your own gunicorn.cfg file and point to it by adding configuration: /path/to/your/gunicorn.cfg to the webservice section in your mailman.cfg. Your gonicorn.cfg does not need to contain the graceful_timeout = 30 setting as that is a gonicorn default, and that is not what you need to increase. What you need is [gunicorn] timeout = 900 (actually 900 seconds is probably way overkill. 90 seconds would probably be enough.) -- 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: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini This fishy, why do you have both uwsgi and "python manage.py runserver" running? You only need one of those, since they both do the exact same thing. Please remove whatever is running the "python manage.py runserver" part and only use uwsgi. On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: > Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. > May mailman processes are next: > > 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 > 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini > 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg > 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 > 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 > 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 > 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 > 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 > 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 > 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 > 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 > 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 > 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 > 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 > 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 > > Looks like there are no double. Nothing more is running. > > 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >> __ >> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>> >>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>> $ sudo pip3 install mailman >>> $ sudo pip3 install postorius >>> $ sudo pip3 install hyperkitty >>> $ sudo pip3 install mailman-hyperkitty >>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >> >> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >> >>> >>> >>> >>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> >>>> >>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>> > Hi. All the project installation is under the same user / path and >>>> > it works. Archiving working as well, (just one remark: no matter what >>>> > to set in postorius, hyperkitty shows list as public) >>>> > I have found work around - it is possible to change list as private in >>>> > "admin" page. >>>> > I started to get issues with runjobs after I have created couple of >>>> > new lists with "no archive" option. >>>> >>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>> >>>> > >>>> > If as owner user from project home I run: >>>> > >>>> > django-admin mailman_sync >>>> > >>>> > Traceback (most recent call last): >>>> > File >>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>> > line 84, in _execute >>>> > return self.cursor.execute(sql, params) >>>> > File >>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>> > line 383, in execute >>>> > return Database.Cursor.execute(self, query, params) >>>> > sqlite3.OperationalError: attempt to write a readonly database >>>> > >>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>> > "django-admin runjob new_lists_from_mailman" >>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>> > END TRACEBACK >>>> > >>>> > I did not find information how to fix this. It was worked without errors >>>> > before. >>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>> > to work. >>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>> > again. >>>> > I did not check other jobs, but I think what is related to database, >>>> > will get errors. >>>> > Seems mailman locking the database. It is not a file permissions issue. >>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>> > >>>> > if to rename /project_directory/var/data/mailman.db to something, >>>> > mailman creates database file size 0, django-admin runjobs start >>>> > working, but of course postorius stops working. I did it for testing. >>>> > I have returned this database file back, postorius started to work >>>> > again, but django-admin runjobs does not work, error: "database read >>>> > only". >>>> > Please help me how to fix this issue. >>>> > _______________________________________________ >>>> > 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) >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/24/22 15:06, Mark Sapiro wrote: > On 1/18/22 06:24, Stephan Krinetzki wrote: >> Hello, >> >> We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is >> installed in a venv and deployed using Apache and uwsgi. This works >> quite well so far, only withheld messages cause us a problem: If we >> try to approve them via Postorius, the message is delivered to the >> list immediately, but the success message in Postorius takes a long >> time - on average the process hangs for three minutes until the >> message is no longer displayed. We have already adjusted the timeout >> in gunicorn.cfg, but this does not improve the situation. Are there >> any tips on how we can speed up the REST API? Or is it even a >> configuration error? > > > There are two steps in handling the POST for a held message. The first > step is accepting, rejecting or discarding the message. This is > happening immediately. > > The second step is handling the poster's moderation action based on the > choice from the Set member moderation dropdown in the view of the held > message. This is processed by the code at > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…>. > If no selection has been made, the default value POSTed for > moderation_choice is `no-action` and that code is skipped. If it is one > of the choices `Hold for moderation`, `Reject (with notification)`, > `Discard (no notification)`, `Accept immediately (bypass other rules)` > or `Default processing` that is processed. So presumably a selection has > been made and processing is stuck on getting the member or setting the > member's moderation action. > > Possibly the logs of your database manager will have information. > Some additional info. By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If you are using gunicorn as a wsgi server, that is separate from the gunicorn serving the REST API and its config doesn't affect the REST API. The relevant config is mailman/config/gunicorn.cfg?. Also, I doubt the issue is with the REST API per se, but rather it is in Mailman core's processing of the particular endpoint and if that is slow, it is most likely some kind of database 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, 9 months

[MM3-users] Re: unrequested unsubscription

by Mike Wertheim

Thanks. Here are the log lines that correspond to the emails to the "-leave" address in /var/log/mailman3/smtp.log... Jun 14 10:10:29 2023 (199628) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jun 14 10:10:29 2023 (199628) Peer: ('127.0.0.1', 35610) Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) handling connection Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'LHLO mydomain.com ' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'MAIL FROM:< someone-i-know(a)gmail.com>' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) sender: someone-i-know(a)gmail.com Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'RCPT TO:< mylist-leave(a)mydomain.com>' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) recip: mylist-leave(a)mydomain.com Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'DATA' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'QUIT' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) connection lost The IP address is 127.0.0.1. Would that imply that the messages were really sent from the localhost, or could that mean that the real sender IP address just wasn't captured for some reason? On Wed, Jun 14, 2023 at 8:29 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/14/23 19:40, Mike Wertheim wrote: > > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > > > A few of the list members are reporting that they received Email Address > > Unsubscription Confirmation emails, but claim that they never requested > to > > be unsubscribed. (All are Gmail users. but they might be coincidental, > > since most list members are Gmail users.) > > > > Has anyone seen this behavior before? Any ideas on what might be > happening? > > > Yes. This is someone sending an email `leave` or `unsubscribe` command > for the user in question. This may be malicious, i.e. someone doesn't > like a user's posts and tries to unsubscribe them, or it may be just > spam of some sort. > > the user should just ignore the email. Beyond that, there's not much you > can do unless you can identify from mail logs the source of the requests. > > -- > 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 mike.wertheim(a)gmail.com >

2 years, 4 months

[MM3-users] Re: Improve logging?

by Odhiambo Washington

On Tue, Jan 31, 2023 at 7:42 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/31/23 00:40, Odhiambo Washington wrote: > > Some entries in the log files can be very scary, while in actual sense > they > > are harmless. > > Such inconsequential, but scary entiess can mess up the well-being of a > > SysAdmin. > > I humbly request for the logs related to posts by non-members to a MM3 > list > > to be improved a little bit :-) > > Here is the example in mailman.log: > > > > <cut> > > Jan 31 10:03:54 2023 (92481) DISCARD: < > > 2a1c588a6ccd47abbf57ee5fc61c9946(a)phellineconsultancy.co.ke>; ['The > message > > is not from a list member'] > > [31/Jan/2023:10:04:48 +0300] "GET > > /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f HTTP/1.1" 200 253 "-" "GNU > > Mailman REST client v3.3.5" > > [31/Jan/2023:10:04:48 +0300] "GET > > /3.1/users/1bad08f703fe4bc0a829f4bdce10fc8f/addresses HTTP/1.1" 200 473 > "-" > > "GNU Mailman REST client v3.3.5" > > Jan 31 10:18:09 2023 (92343) deque: do_confirm_verify > > Traceback (most recent call last): > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/workflow.py", > > line 69, in __next__ > > return step() > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/app/subscriptions.py", > > line 476, in _step_send_confirmation > > raise StopIteration > > StopIteration > > </cut> > > > > Is there a possibility to change the logging engine to just *fold* the > last > > 7 lines into "The message is not from a list member. It was discarded", > or > > something close? > > No. > > This entry > > Jan 31 10:03:54 2023 (92481) DISCARD: > <2a1c588a6ccd47abbf57ee5fc61c9946(a)phellineconsultancy.co.ke>; ['The > message is not from a list member'] > > is a single entry about a discarded message. > > The next two are logging requests via the REST API that have nothing to > do with the discard and are logged by a different module. > > The last entry with a traceback is yet another separate event. That one > could probably be suppressed because raising StopIteration is a normal > occurrence in workflow processing. > I was thiinking that they were all related. The scary part though is the line that starts with ' Traceback'. It's what I'd love to not-see unless there is a serious problem. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: MM2 to MM3 on debian 10

by Gelpi Andrea

Il 27/04/20 18:59, Mark Sapiro ha scritto: > On 4/27/20 8:26 AM, Gelpi Andrea wrote: >> Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 >> mailing lists. I know that not all can work. >> >> In my old lists I have email and regular expressions in >> reject_these_nonmembers and discard_these_nonmembers >> >> After importing the list all these email are in non member list. >> >> All these email have Delivery status enabled. > > > Delivery status is not relevant for non-members and only has to do with > receiving list posts in any case. > > What version of Mailman core is this? There have been changes in > `mailman import21` that may affect this, but an address in > `reject_these_nonmembers` should be imported as a non-member with a > moderation action of `reject` and similarly for `discard`. > > Note that regexps in *_these_nonmembers should be imported into the MM 3 > legacy *_these_nonmembers attributes. Some older versions of import21 > also imported non-regexp addresses here, but that was wrong. > Mailman V 3.2.1 Python V 3.7.3 Postorius V 1.3.2 Hiperkitty V 1.2.2 Yes reject_these_nonmembers has a moderation action of 'reject' and the some for discard. > >> Does this mean that all of them will receive any message sent to the list? >> The moderation rule is correct, but if I understood correct Delivery >> status should be disabled. > > > Delivery status is irrelevant for non-members. Only members are > candidates for delivery. > Ok, but will non-members receive the list posts or only members will? > >> For migration I followed this link >> https://docs.mailman3.org/en/latest/migration.html >> >> To migrate archives it states to run >> >> python manage.py hyperkitty ... >> >> I cant' find a manage.py on debian 10 > > > manage.py is a Django generic term for the Django admin command. You > probably want something called django-admin or similar. > Yes in debain 10 exists django-admin. Now I need to understand how to use it. It asks me to load a configuration. > >> A search shows the only /usr/share/mailman3-web/manage.py exists. >> >> Is there any documentation specific for debian? > > That would be up to Debian. > -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 6 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Abhilash Raj

On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: > > On 10/21/20 5:39 PM, Mark Sapiro wrote: > > On 10/21/20 12:14 PM, Brian Carpenter wrote: > >> > >> Well I can't dictate that to my list owners and there is no confirm > >> token sent with the moderation notice. Why include this option in > >> Postorius when it can't be properly handled? > > > > Postorius is still a work in progress. The unsubscription policies are > > in core and are exposed in Postorius. Certainly the ability to moderate > > an unsubscription should be in Postorius, but it isn't yet. We are an > > all volunteer project and there aren't that many of us, and perhaps I'm > > overreacting, but the tone of some of your recent posts seems a bit > > demanding. > > I apologize. I didn't think I was coming across demanding but I am > somewhat exasperated at some of these issues. I have a list owner who is > now going to get a moderated request notice everyday that he can't do > anything about it. > > But my question still remains: why is this option in Postorius when it > can't be handled properly? Surely the option can be easily removed, right? I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. > > Is the ability to list (via the pending moderation notices tab) and > handle (as in the List owner can decide a moderation response) an > unsubscribe moderation request there in Mailman core so that I can > properly address it via Affinity? Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > -- > > Brian Carpenter > Harmonylists.com > Emwd.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/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 03:04, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > afaiu, this snippet allows me to purge outdated pending subscriptions. > > modifying it slightly, also allows me to just list the pending > subscriptions along with their tokens and print them out. That is correct. > is it still possible to just use these tokens to confirm the pending > subscription (even though it is long overdue)? Yes. > while investigating this a bit, i also noticed that it seems that with > mailman3 the only option to confirm a pending subscription is via email > ("leaving the subject intact") - at least that is the only option that > is listed in the confirmation mail. > > now i would like to massage this into what i think is a bit more > user-friendly. > first of all: most email confirmation systems allow me to either "reply > by email" or "click this link". > is there a way to do this for mailman3? that is: is there a (hidden) URL > that would accept the token in order to confirm a subscription? See https://gitlab.com/mailman/mailman/-/issues/901 You can add something like ``` Alternatively, you can confirm by going to the URL https://$domain/mailman3/lists/$list_id/confirm/?token=$token ``` to the list:user:action:subscribe template. Note that `$domain` may not be appropriate here because it is the email domain which may not be the web domain. > also: the confirmation mail says that the subject must be kept intact. > however, i noticed that the actual "From" address of the confirmation > mail already contains the token. The current template https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… doesn't say that. > would it be enough if people just sent an email to this special > email-address (that contains the token), regardless of the subject? Yes. > i'm thinking of sending a rather personalized email that has a more > attractive subject than "confirm flkdsajfsalkjflsajfsoisjdl". The current mail has Subject: Your confirmation is needed to join the <fqdn_listname> mailing list > finally: what else is required to approve the confirmation? will the > sender's email-address be taken into account? (e.g. if they subscribed > "foo+mylist(a)example.com" but send the confirmation-reply from > "foo(a)example.com", will that still work? Yes. Only the token is required. -- 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

[MM3-users] Re: Archive Policy not reflecting in Hyperkitty

by Abhilash Raj

On Fri, May 3, 2019, at 8:38 AM, Nathan Dixon wrote: > So the issue I am seeing is that when I set a lists archive policy to > prviate, it isn't reflecting that in Hyperkitty. > > I am running the docker installation of Mailman, postorius and hyperkitty. > So I go into the docker instance of mailman-core and run this: > > python3 manage.py shell from hyperkitty.models.mailinglist import > MailingList MailingList.objects.all().values_list('name', 'archive_policy') > > And all my lists are showing '2', regardless of how I set the mailing list > archive policy. > > This might be a duplicate of > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Am I missing something in my install? Or is this a bug? It can take upto an hour for this change to reflect in Hyperkitty. Did you wait for that long? This happens because Hyperkitty stores it's own data, and queries Mailman Core periodically to fetch updates every hour. In future, we might be able to do this in more realtime fashion by using an event based pub/sub model. But, we are not there yet. > > Many thanks for your attention, > > -- > > *Nathan Dixon* MEng > Senior Software Architect > m: +44 (0)7402 690311 > > t: +44 (0)20 81231252 > e: nathan.dixon(a)evadon.com > w: www.evadon.com > > This e-mail and any attachments are confidential and may be protected by > legal, professional or other privilege. If you are not the intended > recipient you should not store it, copy it, re-transmit it, use it or > disclose its contents, but should return it to the sender immediately and > delete your copy from your system. The views expressed are those of the > sender and not necessarily those of Evadon. Please note that whilst we scan > all e-mails for viruses we cannot guarantee that any e-mail is virus-free. > Please be advised that we expressly reserve the right to monitor email > content for the purposes of ensuring compliance with legal requirements and > company policies and your sending to, or receiving from, us of any email > constitutes your agreement to these terms. > > > Evadon Dynamics Limited, registered in England No. 09494097. Registered > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, > S1 2BJ > _______________________________________________ > 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)

6 years, 6 months

[MM3-users] Imported Digest Settings

by Brian Carpenter

I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported: > For the last three REDACTED digests I have been getting unusual and > unreadable characters? See example below. > >> Begin forwarded message: >> >> *From: *REDACTED >> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >> *Date: *February 13, 2021 at 12:30:24 AM PST >> *To: *REDACTED@REDACTED >> *Reply-To: *REDACTED@REDACTED >> >> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ >> [��X��ܚX�H �XH [XZ[ �[� H Y\��Y�H �] �X�X� ܂�� H� [ � ‚] [�\�\]Y\� >> [�ܙ‚�[�H �[� �XX� H \��ۈ X[�Y�[�� H \� ] �] [�[#<^_NSEDR_^#<ۙ\� >> [�ܙ‚�� [� �\ Z[�� X\�H Y ] [�\� �X�X� [�H �� ] \� [ܙH � X�Y�X [� �N� >> �۝ [� � و S� Y�\� �� ^I�� X�΂� K� �N� [� \� � [\ � >> �� ] >> \�B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB�Y\��Y�N�B� >> ] N� �K L� �X��HL ��N�� L ��N� �� ] \� �� ] >> \�]\�X˘��O��X�X� � � S�H �N� [� \� � [\ • Έ �� [�Y[ �� [�Y[ >> ]ܙ[��K�Y O��Έ � S� H �[\ ] ^Y\�� [� \�] [ۘ[ �] �ܚˈ� [� >> [�ܙς�Y\��Y�KRQ � Q� >> � >> KM�� M� N Q �P��PL �P �] \�]\�X˘��O��۝ [� U \ N� ][ \ \� �[ \�] >> ]�N‚X��[� \�OP\ KSXZ[ M ь P�KL�L�KM ��KP�KM��̌#<^_NSEDR_^#<͌ >> L �Y\� H [�� YX�� H \� Y �[[^H [� � X� \� [�� Y] [�� Y�ܙH H Y� >> \� [� ] �Y[\� �\� Y [� �� \�H ��\ ] H ] [ � H �\� ۙH و \� � Y [� ˈ [ >> [�� ]�\�] [�� H �]�H YK �\� [� ]�Y X[ \ \�� [� �\�[ [�� X� [ۜˈ H >> �\�[ [�� X� [ۋ �H �\� �\� H [�� [\ ܝ [� [� �[ XX� H \� � H ۸�&] [�� >> H �]�H [ و \� � Y [� � H �[YH X] \�X[ ˈ ] �\� H ]X� [ܙH >> \�#<^_NSEDR_^#<ۘ[ ^�Y \ ��X� �܈ XX� � Y [� � H ��Y� \� �� ] H [� >> ܚ] [� � Y� H �]�H YH H \�� Y [� ]�[� ] � �� Y\� >> [�H ]�H � �H � � ۛ�� Y� ] \�JK ��\� �܈ �^[ۙ ] � [�� ] \��[� >> ��H ^H T ۙB� ۈ �X�L So the questions I have are: 1. Why does the formatting of digests change for some members when coming from MM2 to MM3? 2. What proble does the above example reveal? 3. What is the best approach to mitigate these issues? What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: re-injecting emails that were not archived

by Mark Sapiro

On 6/25/23 11:47 AM, Ken Alker wrote: > > I noticed when I came onto the project last week that there were 140 > messages stuck in the "shunt" queue for the two lists hosted by this > server (I have no idea why and the old logs were not available and I > don't recall the results of "mailman qfile", assuming that had shed some > light on the reason why they were shunted). In any event, I unshunted > these messages and they flowed out to the subscriber's email addresses > successfully. What I was not expecting is that the system did not > inject any of these emails into the archive. AFAICT, the messages are > no longer anywhere on the system (but I could be mistaken). Here are my > questions: > > 1) Why would these emails not have been injected into the archive? The message may have been shunted from by the `out` runner, in which case unshunting would only cause them to be processed again by the 'out' runner. Archiving is a separate queue and process. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/archi… for an overview of the message handling process. The bottom line here is if a message was shunted by the 'out' runner only, it should have been archived at the original post time. Were these messages already archived? If not, depending on list settings there may be HyperKitty archiving iossues in which case they may by queued in Mailman's var/archives/hyperkitty/spool/. directory, but if they are, there would be errors in mailman.log from regular attempts to process them. Also they may be found in var/archives/prototype/<list>/new/ directory. > 2) Is there some way for me to re-inject these messages into the two > lists? The only place I (THINK I) have them is in my own personal IMAP > box since I'm a subscriber to the lists. You can inject them into the archive queue with `mailman inject`. See `mailman inject --help`. Before doing this, be sure it's necessary, i.e. they're not already archived, although HyperKitty won't accept a message whose Message-ID: is already in the archive. > 3) Can this be done without the emails being re-delivered to subscribers? As long as you inject them into the `archive` queue queue only, they won't be resent to the list members. -- 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: List mails blocked from GMX - web.de > Spamfolder

by Jens Günther

+1 Already asked both providers why some mails are 1. going to spam 2. going to a black hole 3. are bouncing. After some writing forth and back, they said pretty much nothing. One thing I clearly found with United Internet is that they will bounce mails, when they are hold for moderation and are only acknowledged after 5-7 days. Then their mail server says ... blabla not corresponding to our policy. For that the support says, that the mail header is wrong/corrupt, which it isn't, but they don't listen (or have no clue what they are talking about / others configured). If you find any solution, please advice here and those 2 examples, thanks. I also registered an account with web.de and tried to find out, what led to the SPAM-folder, unfortunately their header looks like this: X-Spam-Flag: YES UI-InboundReport: junk:10;M01:P0:jgPEANxMfXA=;cj0ZvmLEFaDIs770zHpx99rAJcDCbA 1Y3gNPC5fXQ38fRvWtQZrCuXffBLv+zr7BhZUXmCP5/0gT5HLRRVgHo8DH5v4UYCoLF7BO3sN ZUGVdpDVHe6enTE1YRDQ6choFKxR9D7DsaJzQtwytB/RcKeju85tXl9mnazTlGn8/s5JuN+Yq uv+UmyOykpSy0m8f/LMjfvbVlDszxG0pL9Epk/JE0mrCgV2YuSaU879+YBGcM0SgO/nJNBhIe rJ8KhdN8vFbgwQx02PN4BjwRziPuQVEagiSpoIWhoP6zOT3tQGI+Zm/bKiUcgxdv24VqcoHSN ZzPR7KYZTNbRJEdpIbCoY+FfRVi1psvfx8+4jr+3ev5f2YdaFlme40n7KTzRVNo04h4BN5m4s CfEobF0CsJpxWc2mtcztohmatA1yiCs+Ei6WGW2mxDxHjYV0ksx9eu6BDZDpG84zVa9VBP/5w 0zQshIfVBefL7kksMBFFaAG30p/F8SUNYCDxDXWv3mKx4ALTRWtgaaCA/dfzOUY0h42KZljhZ KaOz2m0AbJAySiiEks9X+IGiTv27zbvhHGu5+SP6xEa79DZ/+OSMBqI1rKShCwQvqG3qMU71c 15ULsComyU4QTR7GzuqVGh5lgRftZOhld9CpcIXcIF4COk6nXRTPgAW9PFeN0t+WJAbDNIlbn C888yLIdj+gpyHkQkgT4PaFSB2tI3J23N1G9qxXxcTN+SJMfZP6x6GFNvR/V06C8w5ZPb5erV yPeOCoSRN8mv802vn8PmEaFMtRsHEYF3Vv/5zDf/VaF6DqgPLow/i1nSiENNRxrd2uAFkK6UQ 1i/v/5swrF3n7miAbZUA/Scu2NgWCjk8+MEI4AkjXWt9PAA0TQR+Tp1j4vRb7fR6zw7tKsYx7 xFv8CjQcDbCW/9GNjeZfpgULIrSIKIcke4Dklr8r5p7L1A9O4ohMDs4xb3iVN17iVoa2kQ7xz tMVIOgDS6L9dzCoS5tUSOdUdd6xzeJPlOTAB6wxv2IRAxPCMdBvdLQjimp+DTdeIDqgYfCMqA Bv8/MeoWjQLsS0sWo34StLj8iVSWWwMEjmXe1XCPN5dhmjQ5FZhgcuYCoKc4tY0Yq+QSQ8m1L HEazh7D4nj2zABI2+3WNgKuKFJRFY/9haJNrw7380Mhs86IHDkyfKv3DW+MUEsKLNgjtToR14 sGA6pzZXIjtnGssp5QiqUBcl0UT0PE3IYUyT4utqY5ltdNcr0nLbdxozqhjlkxkuDoY9fZXWU PoGqzs/ZzT6+1E2nDHgDYU+s9EU6zElM83FPW2apHrq/Fi//uBipfxKCJmWyVIxRd32pcuaRH 6EtYwKEw9FOLvLS7fsXqhQPyzxTnjaUh2ldnndv2btaoqvSceCv5W511S97n72V4t4i804kkR PJ+4RdwsNn+Hmb5j+kIQMt4f/4KWVPxP1yz8bzr7KvfuptMpi/cwxH7uHuJw1aBc1rsV3oDcu 6JHfpVRdqqZjdldtV3teWxhunu1ivroAbMKOh36ZNGO/n8rwPo/UZCS4Np68WFJAXakuOfa4D blkAOFLBT2hTwXIFtRL5fwEuCm556qY7S6RQ9elDco4V4kud/iy8XJ2G2YRFFcWxCwt9q13NZ 0OWmgKU+8u/Qz4DcI4THInnR/eXoPsBKCrFKtjZ0GWJ+0NPkz4ZWuPfgD98YYRVtoszQ5Qa9l IYEOd4QYl44lCAaL7IbYDExja1/xDQ0EwvBTDOQuIqYjokdQWD+z7zaN9A5oYZOnoQgkpOG0I r0zyMzWlbCjLuU6S2erSEyXN8qwdNVE3Q48S4b8o4s9mQPUK5ZsvfEXFdub0zDRLFy9JJfrom IyLKgv2nPKxgKKgIrM+VTOcK4aMUk0aNVifsldpLH/P+FvbT3l2gzTvhFKUs+ZRWSxScOLxDH 5Rzfmou+5JA8sGB+rNvuCVguInKGHylO4+fRFjW8HZ0XZiVxMlSbW8FTwGF7Eo0dTMlCedHIK LOHACSJu+S0VdyeJumaXHGyBV7dWYGoFTVW5Oyf4pg1rh6TEAWXye98U7hSyHgQhMaiIrixkg OTqz4N9s2RpRD4dKrUI7emlHwxemMuok0wgxoyXaSFaTRhfidy5yQXv5exKrO2ANrSSuaRQm9 FIuymlYXT5VSCB9TbaIAIGg3KHXet5TO1qhgaSU8PUi/CKjIl/UYnohq5uQkxxw9s4ACNcD+1 CC13NEoQxr+32LbqQ2cMiPQNAyNBRIgFMm5MqCBFlvrggi+2AHPAX7dhfNjxxvLj/q6CG2ENr /bl/RR4M2XRdxMvMXvthvS6FPBBcPOBMG5tXDmziZYUagg08D+gNHnYYjVTr3F0DOHRHeKKsv 5T8a2G5duY+/ZdpwHC9CM0NWLZqUnjpfaRvA7gHxrmmy2EExjmJD1TJaaktPdDCH4iPWMjdCs 5utOPCFKJ3pm7gOUQQ1g1B7JaenOm3mmqQD70KJXhXiLWk6fKCRH2QZz2SWoG9T1FE6rPFDxc 9meYarhF+v3TzheuUha/KB2xozZC3uWTglm9SaENuSm1S3vAVyc21vl/qx+Ul73iCaHdNpu48 OYgDRlO5s1eQAZ5IQGnPDd9IoIlLxOTI7Lv3LXKC9BZXQOBlp5slPLbFfmDlDDK5YeorOrw6a nRJ0MCrjgfIaQAl15f9WTG6P5bSy/gik5ZaCMeuBnukIufVC7EQRAOdLX/GEmTF3TEqv9gWdS KnOEBC4GuT3mynDLkGXqQGv2iBAMCa6R4ESAtVe8AsQSswKbuCE7G26n1MbdvkxSTuYbGoRo6 8NAqmDxYK6qoMmlkw0O+KZlNIL2d+/tBSIEE9Dm/QXf84Dq6pZjknNVaJNTfTwGwwh4jW53I/ WxBZwZ2NKXdgfkS2xQEOIv1Q26mVPq3EMFR+6t85wJ2WGFJCHIlNsEmGhQHQQP6x7Wr5kmKi3 sIy9jFmowKe6zn2ObYTRitg0crol0OIIo1MtwSSCyrfZ+mtb7lOIOj66JvVcIY66LLxNW1CEx t9Eoy7qS58aSvLg+fkqxG4654vh88+iM5reY9XxAmjsmj+WC4wayd4yfnG0bTkGw4188nszB4 PRaVfMLeSN4l3/VOZUyRTnGi2XORg/HHVhF1RVSNiRbrkyjhFit+Lrn6G2zyCxpS7Iewghgbg T8hyUkzhQVA2VLwWXp3b6lckjbjDQpmCCR3NdfS7Rbu+667Md+UQo3Z7LkwrrTfeoZmzoGNxS pUtp68FJ86iH5DePxvDiTsmrMBqXPtDDRxFFRJN/SpqaKdSCH/UyX/AFn0SFXrx7SeEGEIwBx iSDXKvNnQ2BZ0rR5QAFExx50GrwNQDHYklA7sD3EnEsaRUqDmPT6PVXUs2ukP1Vvai6CCk7fi 6qkAnez0f3cmi6cJjs54NCECVbWBi9SlgQoruZPmJzJHdahK3sgxQJ2bk67Bt9+nNq/lVNMuL JrGyJYnHW5ERYh4iKW9wkolThyxaUwswl/ptN67XssLrKLkAfOgvYOsXjkT8VMYnymI9brosk ajSJQCbUCrzNq5HVI/jSc2eU7LyS8dqKUfKGJ8Ov1QGULZ9V/YAV02W163jG2hUnSQiXy62ZC OFD3F1sy8D1UwjhR/LEmX9t8Srj38NDDAi+HexMIF+Wvi+IVRf5ggSpnzZ6XbIGo380aNWqGS CmSZgzrrb/Jm5fB6Na7pzbzwz+NSSoBqg7usgje8mQv1TTusDqZh6+5JGEChvTPs72O+8oO0X Xrz1WTU83D13xCP9YLmKcWF350fgRwngRnz7WCkIKQ1dtBIjs3N0DxvCSV2OC3w1+JgBhKTBd 6k7uNIc5bYk/qplcKsHISmBcjnpfdQah3toJKY2YUC0wWpqayscf28kMEz4Nojw7Z5wwryvrA MQmO2I+rkU1T7R8cqPxO6tncoyr4XwQhQaDbTJsSdm5I/R1DB+blOY6p5Nnt8hAlX4vLthNk0 LxvyrFKQDcplcoamrtQ1MCTbYm2dhTDF7t4dktEIerI7UeDGbQsmQrTzZurQrlMYZtLClPqZj opfgdwXr4p//8Bf+aZ7Jq7nLO+7N9t2YWexopctICqHS1KoOAzclfjWe8sy17maKJVEbRC94N vbWpOQKn17NnOW3gsweM70aNGcQOg8wAzQmC/l+fg1qH6OrTzGsC8dzRXPqZgX77y7gh6spk1 wRa8RYniweSF4HaVPR2+zvpvJwNptwwI8d4GgH2LKclgQvKeGRW8bvRPdnHgpRgu4hs2g+jbS xov8FfQNu5BTGyXIth67NU9EDT3r9cbeH3N28DX83ewVTw9dn6DrpTc4JubNc01CUjT5mm/eM uaISF/Jxm/ShSj+ZXdvdbU7T5ZOvU4n/8vG3amGzkuHgtEBo87yjM5Ttebneg1VYKAxw9Vr2l NUjAA2ZWo7wvWmblYPgJQDaBpCf//+J55GliqYE3odoHAajsxg++PixiRXPjc4Pg1aZ/ipjmn KuQ3VIRPDW8KMUBJu8cC/s61+Uk89pFiGHi8I9Yjhn+ggO3kQcCbRHfy0F6siG8TKNhZBa5ew 8TJQLMai/DziVFbbl0VZddqcbnVHW2ICPXVumPlJl1j7/k2nfJk+rvWcmxUMN+UDXwsa6LHUU M+JkXGgxBFURfmGxuBJxLE= Asking the support, they couldn't tell me anything. I just asked again from within the account. Am 19.07.23 um 14:31 schrieb itservice--- via Mailman-users: > How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net > I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. > unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. > > At web.de they go to the SPAM folder. > _______________________________________________ > 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 jens.guenther(a)posteo.de

2 years, 3 months

[MM3-users] moving list from mm3 -> mm3

by Jens Günther

Hey there, I'm still trying to figure out, how to move a bunch of lists from one mm3-instance to another. If somebody has a working solution, I would be really glad to hear from it. I came across this thread, but I don't think it tackles my question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (or maybe I missed the right parts) We have equal setups and versions: - maxxking docker install 0.4.5 - Core 3.3.8 - API 3.1 - Postorius 1.3.8 ## Config So I found the possibility to get the config of a list via REST-API: curl -u restadmin:restpass localhost:8001/3.1/lists/$short.$domain/config | jq > short.domain This is a nice collection of the configuration of a certain list. Does anybody know how I would get this data back to the newly created list in the second working mm3-instance? Shouldn't it be possible via POST command? I thought of something like: curl -u restadmin:restpass -d @short.domain -H "Content-Type: application/json" localhost:8001/3.1/lists/&short.&domain/config But it returns {"title": "405 Method Not Allowed"} and I don't know where to look in the docs, since it shows almost always a way through mailman shell. Here I found something about POST: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but how would it work exactly? ## Members, moderators, owners To export all members I normally run within mm-core-container as user mailman the following command: mailman members &short.&domain > &short.txt To fill them back in, it can be done in Postorius (or is there a way through API?). What I would love to know is how to get out Owners of the corresponding lists and reimport them in the new one (which will be the same at the end :-D but different instance). ## registered users This part is somehow tricky, since I have no clue how to do it. Some of the mailinglist-admins don't want to bother their list-owners again with registering newly on the other system. Is there a way to export all users (I think I found them in the DB in the table auth_users, somehow in combination with account_emailaddress) and get them over to the new instance (actually I just need part of them, but that's another question that I might solve lateron on my own). Maybe the answer is already here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)? Thank you in advance, I hope it's not too much or too nooby :-) Jens.

1 year, 10 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Stephen J. Turnbull

Abhilash Raj writes: > The is definitely a bug, caused due to the fact that "Delivery Status" field > only has two options, "Enabled" and "Disabled". Internally, this field can > have 4 values, "enabled", "by_user" (maps to "Disabled" in Postorius), > "by_admin" (means disabled by admin) and "by_bounces" (means > disabled due to bounces). So, when the value of the field is among > the last two options, it appears as "unset" with no options selected, > which unfortunately is also how it looks by default since all options > are "unset" from start. > > The "fix" for this issue would be simply adding a new choice to the > delivery_status field with a caveat that it is only a Readonly option to I don't see why most users would care (there will always be somebody who cares "just because", of course). For those who don't care, I expect it will be confusing. I think it's better just to treat all of the disabled settings as just "disabled" in the UI for members. > We could also go a step further and show it on the List's info page > when their delivery is disabled due to excessive bounce and allow > the them to re-enable it themselves without admin intervention. This is probably a good idea, but in a situation where we know the problem is excessive bouncing we should caution them that there is almost certainly a probably with delivery *to their specific address* and that Mailman and the admins *can do nothing about that*, so if that isn't fixed they'll just get disabled again. I suppose it would be good to add that frequently these are due to occasional problems like disk full that "management" at their site normally takes care of, so there's little if any harm to just reenabling. > to the list's info page, but I guess that is the first place you'd go to > debug when you get an email that your delivery was disabled? Surely we can help them go directly there? > https://gitlab.com/mailman/postorius/-/issues/470 > > I don't know if there are any downsides to letting users re-enable > their delivery on their own. I don't see any myself. Maybe if the list is planning a surprise party for them? ;-) There is a specific downside, which is that if you only allow them to reenable if they disabled it themselves, you have to show them the other cases.

4 years, 8 months

[MM3-users] Re: Python is updated

by Duane Raymond

Hi Lars, I did the same thing this weekend (upgraded mailman to latest and python from 3.7 to 3.11) as part of a process to do some work I've promised Mark :-) Here are my notes (to I can repeat it next time). I'm on Debian 10. My mailman install is based on Brian Carpenters install notes: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 0) IF UPGRADING: copy /static folder, /venv folder and base config files to new backup folder (e.g. config_bak) 1) Install desired python e.g 3.11 (from source if necessary) and be sure to include: apt install libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev 2) IF UPGRADING: Stop the mailman related services: systemctl stop mailman qcluster gunicorn 3) Create local venv at: python3.11 -m venv /opt/mailman/mm/venv (backup old one first to backup folder) 4) Set ownership of venv folder and subfolders/files: chown -R mailman.mailman venv 5) Switch to owner: su mailman 6) Activate venv: source /opt/mailman/mm/venv/bin/activate 7) Check pip uses the intended python version: pip -V 8) Upgrade PIP if necessary: pip install --upgrade pip 9) Install mailman3 basics: pip install --upgrade mailman hyperkitty postorius 10) Install additional if missing: pip install --upgrade django-mailman3 mailmanclient mailman-hyperkitty 11) Install DB connector: pip install pylibmc psycopg2 python3-psycopg2 python3-pil python3-psycopg2 whoosh python3-whoosh python3-httplib2 12) Update /opt/mailman/mm/urls.py with desired paths (django) 13) IF UPGRADING RUN: bin/django-admin migrate PLUS: bin/mailman-post-update (or individually below) bin/django-admin collectstatic --clear --noinput --verbosity 0 bin/django-admin compress bin/django-admin compilemessages 13) Exit venv environment: deactivate and Exit mailman user: exit 14) Start mailman: systemctl start mailman (check status: systemctl status mailman.service) 15) Start qrunner: systemctl start qcluster (check status: systemctl status qcluster.service) 16) Start gunicorn: systemctl start gunicorn (check status: systemctl status gunicorn.service) Note: 1. /django-admin is the same as /mailman-web in some installation notes. 2. The bin/mailman-post-update script Brian used does everything except the "migrate" step 3. I don't know if all the pip psycopg2/whoosh modules are needed - I didn't take the chance. 4. My system now uses django 4.1.8 so I didn't need to worry about the psycopg2-binary install (I don't think I did - it seems to all work) 5. The 3.8 release notes contain a breaking change with the postgresql connection command. I changed that before upgrading. (assuming you are using postgresql!) 6. What I haven't covered here is checking the autostart, service settings and crons are working as that is in the documentation and may already/still be running on your server. Hope that helps :-) Cheers, Duane

2 years, 6 months

[MM3-users] Re: Archive Policy not reflecting in Hyperkitty

by Nathan Dixon

I'm not sure if it's also related, but within the mailman-web and mailman-core docker containers, crontab -e only shows these entries: # do daily/weekly/monthly maintenance # min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly And all of those folders are empty. I'm not sure where the synchronisation task for Hyperkitty should actually being run from? Thank you On Tue, 7 May 2019 at 10:20, Nathan Dixon <nathan.dixon(a)evadon.com> wrote: > The change to the archiving policy aren't reflected in Hyperkitty after > many days for all the lists. > > The only error that I am seeing in the /web/mailmanweb.log is: > INFO 2019-05-02 14:16:55,062 38 hyperkitty.tasks AsyncTask task "<function > unlock_and_call at 0x7f5d8851f048>" with args "(<function > update_from_mailman at 0x7f5d88544a60>, 'task:status:%s:%s', '<list > address>')" and kwargs "{}" finished with errors. > > I'm not sure if that could be related? (I have changed the actual list > address to <list address> for security reasons) > > Thank you > > On Sat, 4 May 2019 at 16:24, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Fri, May 3, 2019, at 8:38 AM, Nathan Dixon wrote: >> > So the issue I am seeing is that when I set a lists archive policy to >> > prviate, it isn't reflecting that in Hyperkitty. >> > >> > I am running the docker installation of Mailman, postorius and >> hyperkitty. >> > So I go into the docker instance of mailman-core and run this: >> > >> > python3 manage.py shell from hyperkitty.models.mailinglist import >> > MailingList MailingList.objects.all().values_list('name', >> 'archive_policy') >> > >> > And all my lists are showing '2', regardless of how I set the mailing >> list >> > archive policy. >> > >> > This might be a duplicate of >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> > >> > Am I missing something in my install? Or is this a bug? >> >> It can take upto an hour for this change to reflect in Hyperkitty. Did >> you wait >> for that long? >> >> This happens because Hyperkitty stores it's own data, and queries Mailman >> Core periodically to fetch updates every hour. In future, we might be >> able to >> do this in more realtime fashion by using an event based pub/sub model. >> But, >> we are not there yet. >> >> >> > >> > Many thanks for your attention, >> > >> > -- >> > >> > *Nathan Dixon* MEng >> > Senior Software Architect >> > m: +44 (0)7402 690311 >> > >> > t: +44 (0)20 81231252 >> > e: nathan.dixon(a)evadon.com >> > w: www.evadon.com >> > >> > This e-mail and any attachments are confidential and may be protected by >> > legal, professional or other privilege. If you are not the intended >> > recipient you should not store it, copy it, re-transmit it, use it or >> > disclose its contents, but should return it to the sender immediately >> and >> > delete your copy from your system. The views expressed are those of the >> > sender and not necessarily those of Evadon. Please note that whilst we >> scan >> > all e-mails for viruses we cannot guarantee that any e-mail is >> virus-free. >> > Please be advised that we expressly reserve the right to monitor email >> > content for the purposes of ensuring compliance with legal requirements >> and >> > company policies and your sending to, or receiving from, us of any email >> > constitutes your agreement to these terms. >> > >> > >> > Evadon Dynamics Limited, registered in England No. 09494097. Registered >> > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, >> Sheffield, >> > S1 2BJ >> > _______________________________________________ >> > 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) >> _______________________________________________ >> 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/ >> > > > -- > > *Nathan Dixon* MEng > Senior Software Architect > m: +44 (0)7402 690311 > > t: +44 (0)20 81231252 > e: nathan.dixon(a)evadon.com > w: www.evadon.com > > This e-mail and any attachments are confidential and may be protected by > legal, professional or other privilege. If you are not the intended > recipient you should not store it, copy it, re-transmit it, use it or > disclose its contents, but should return it to the sender immediately and > delete your copy from your system. The views expressed are those of the > sender and not necessarily those of Evadon. Please note that whilst we scan > all e-mails for viruses we cannot guarantee that any e-mail is virus-free. > Please be advised that we expressly reserve the right to monitor email > content for the purposes of ensuring compliance with legal requirements and > company policies and your sending to, or receiving from, us of any email > constitutes your agreement to these terms. > > > Evadon Dynamics Limited, registered in England No. 09494097. Registered > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, > S1 2BJ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 5 months

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by Mark Sapiro

On 2/8/23 08:34, C. Souza wrote: > I'm trying to manage 2 held messages in a specific list and I'm getting > this error below when I click on /held_messages. It never happened before. ... > ==> mailmanweb.log <== > ERROR 2023-02-08 16:01:30,149 1516 django.request Internal Server Error: > /mailman3/lists/mylist.domain.com/held_messages > Traceback (most recent call last): ... > File > "/opt/mailman/venv/lib64/python3.6/site-packages/django/utils/dateparse.py", > line 107, in parse_datetime > match = datetime_re.match(value) > TypeError: expected string or bytes-like object I'm not certain, but it looks like one of the held messages has a bad or possibly missing Date: header. Working around this is tricky. You can do the following in mailman shell. ``` $ mailman shell -l list(a)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 >>> requests = IListRequests(m) >>> msgstor = getUtility(IMessageStore) >>> for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if data['_request_type'] == 'held_message': ... print(f'request ID = {request.id}Message-ID = {key}\n ' ... f'message = {msgstor.get_message_by_id(key)}') ... This will print for each held message output like request ID = nnn Message-ID = <the message id> message = the message content You can then handle these messages with >>> from mailman.app.moderator import handle_message >>> handle_message(m, nnn, action) where nnn is the request ID and action is either Action.discard to discard the message or Action.accept to accept it. And finally >>> commit() ``` If you decide you want to edit the message content before accepting it, you could find the message in the file system. One of the headers in the displayed message is something like Message-ID-Hash: IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL the message is saved as a python pickle in the file system in Mailman's var/messages/ directory. This has subdirectories of the first two characters of the Message-ID-Hash value and those have subdirectories of the second two characters of the Message-ID-Hash value, so if the above were the actual Message-ID-Hash the pickle would be at var/messages/IW/L2/IWL2EUW3FT7IIUA3QYTZEX4W4JBZ26HL. You would need to pickle the new message content and save that over the existing file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: SECRET_KEY is not defined. Aborting.

by Steven Jones

This is the part from the file as below, root@debian-mailman-001:/opt/mailman/docker-mailman# vi docker-compose.yaml ======= 8><---- mailman-web: image: maxking/mailman-web:0.2 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - HYPERKITTY_API_KEY=blah-blah-hyper - SECRET_KEY=blah-blah-secret - SERVE_FROM_DOMAIN=lists.xxxxxxxx networks: mailman: ipv4_address: 172.19.199.3 8><===== regards Steven ________________________________ From: Abhilash Raj <maxking(a)asynchronous.in> Sent: Wednesday, 26 June 2019 12:58 PM To: Mailman users Subject: [MM3-users] Re: SECRET_KEY is not defined. Aborting. On Tue, Jun 25, 2019, at 5:56 PM, Steven Jones wrote: > 8><--- > root@debian-mailman-001:/opt/mailman/docker-mailman# docker run > maxking/mailman-web:0.2 > SECRET_KEY is not defined. Aborting. > root@debian-mailman-001:/opt/mailman/docker-mailman# > 8><--- > > > I keep getting this, I have attempted to set a SECRET_KEY in > > > /opt/mailman/web/settings_local.py > > > and, > > > docker-compose.yaml Did you set it under mailman-web -> environment? That is where you need to set that value. > > > No joy, can you tell me how I set this variable? or where I get it > from? is it pre-generated somewhere? your documentation just does not > explain this that I can find, despite even a lot of time googling. It is not autogenerate, you neeed to generate a random value and put it there manually. > > > PS I have assumed the hyprekitty key is something I set myself, just > like a manual password sort of thing, again there is no explanation I > can find that explains how to do this properly either. > > > Can this documentation be improved please. > > > To get anywhere at all I finally found this, > > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fxiaoxing.… > > > So I have core running OK I think, > > > ====== > > root@debian-mailman-001:/opt/mailman/docker-mailman# docker ps > CONTAINER ID IMAGE COMMAND > CREATED STATUS PORTS NAMES > 99f434ef3664 maxking/mailman-core:0.2 "docker-entrypoint.s…" > 2 hours ago Up About an hour 8001/tcp, 8024/tcp > mailman-core > 4c0e165d3a90 postgres:9.6-alpine "docker-entrypoint.s…" > 2 hours ago Up About an hour 5432/tcp > dockermailman_database_1 > root@debian-mailman-001:/opt/mailman/docker-mailman# > ====== > > > > > regards > > Steven > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 4 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Abhilash Raj

On Wed, Sep 29, 2021, at 9:50 AM, Odhiambo Washington wrote: > 1. Confirmation emails to Users has wrong domain name (example.com!) > <https://docs.mailman3.org/en/latest/faq.html#id1> > <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> > > This happens when your reverse (SSL) proxy isn’t setting up the correct > headers when proxying requests. Fix this by setting the right > proxy_set_header directives: > > # For Nginx. > location / { > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Forwarded-Host $host; > proxy_pass http://localhost:8000/; > } > > Appropriate headers for different web servers needs to be set if something > other the > > > > How is this supposed to be mitigated in Apache when using WSGI? It seems like Apache has this `ProxyPassReverse` thing, which should do the same job: https://www.nginx.com/resources/wiki/start/topics/examples/likeapache/ I haven't tried it myself, but it might help! > > My config: > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > user=mailman group=mailman > WSGIPythonHome "/usr/local" > WSGIProcessGroup hyperkitty > > <VirtualHost *:443> > ServerName lists.doma.ain > ServerAdmin odhiambo(a)gmail.com > > SSLEngine on > SSLCipherSuite > ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL > SSLCertificateFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem" > SSLCertificateKeyFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem" > SSLCertificateChainFile > "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem" > > CustomLog /var/log/mm3-lists-access.log combined > ErrorLog /var/log/mm3-lists-error.log > LogLevel info > > Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman/static > > > <Directory "/usr/local/mailman/static"> > Order Allow,Deny > Require all granted > Allow from all > </Directory> > > WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py > process-group=hyperkitty > > <Directory "/usr/local/mailman/"> > <Files wsgi.py> > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > > </VirtualHost> > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' :-) > _______________________________________________ > 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)

4 years, 1 month

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:24 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > > > /usr/local/include/sass > > > > > > > > That is the only thing found that is in the base system. > > > > > > And that's the one you want. What is it's mode? > > > > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > This sounds like a result of you running `pip3 install sass`, probably > with sudo > which failed mid-way due to the exception you posted above. > Closer to the truth! It failed. I was running this from within the virtualenv. > Which OS are you using? FreeBSD. > On debian/ubuntu, you can install: > > sudo apt install sassc > Do I need to install sassc in the base OS or in the virtualenv? > I am not exactly sure how it got removed during your upgrade > to the new version of Mailman since it shouldn't affect your system > packages. > The funny part is my MM3 used to run. Mark took so much hand-holding for me to get it running. Then one day I used the update process and things got hosed. The happy part is that I had not put any production lists on MM3 as I hadn't developed the confidence of managing it. Did you install Mailman initially using system packages or instructions > provided at [1]? > > [1]: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… No. I relied on https://wiki.list.org/DOC/Mailman%203%20installation%20experience. This is way back! Your new link is recent, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 5 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Odhiambo Washington

On Tue, Dec 20, 2022 at 9:50 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Tue, Dec 20, 2022 at 3:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/17/22 23:22, Odhiambo Washington wrote: >> > >> > I have dropped the DB, recreated, ... >> >> When you created the DB did you specify `CHARACTER SET utf8mb4`, e.g. >> >> CREATE DATABASE mailmansuite CHARACTER SET utf8mb4 >> > > Yes. That is what I do at the minimum for my databases unless specific > instructions exist against it. > So it seems like I have done everything that is commonly expected, but the > import still fails on several messages. > It turns out that all this time I was barking up the wrong tree! I was having all my modifications in /etc/mailman3/*. When I did run 'mailman info', the information that came out is that mailman was actually reading /opt/mailman/mm/mailman.cfg I then just moved all the files I had put in /etc/mailman3/ to /opt/mailman/mm/. There is a WARNING on https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install which says one must create the config file as /etc/mailman3/mailman.cfg How to force mailman to read that file is something I haven't understood, but turns out to be what has taken me days trying to get things right. Ultimately, when I did the import, there was only one email from the archives that failed to be imported - which I honestly don't mind, but maybe there is a solution for this "'utf-8' codec can't encode character '\udcae' in position 331: surrogates not allowed" ?? (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin hyperkitty_import -l kictanet(a)lists.kictanet.or.ke /usr/local/mailman2/archives/private/kictanet.mbox/kictanet.mbox Importing from mbox file /usr/local/mailman2/archives/private/kictanet.mbox/kictanet.mbox to kictanet(a)lists.kictanet.or.ke 21%*Failed adding message <1260802782.6596.1350003565(a)webmail.messagingengine.com <1260802782.6596.1350003565(a)webmail.messagingengine.com>>: 'utf-8' codec can't encode character '\udcae' in position 331: surrogates not allowed* Computing thread structure Synchronizing properties with Mailman 915 emails left to refresh, checked 0 767 emails left to refresh, checked 0 Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list kictanet(a)lists.kictanet.or.ke'. (venv) [mailman@gw ~/mm]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Which documentation to follow for installation

by Ruben Ibanez

Hi Abhilash, Thanks for your reply. The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? Of course, I'm not asking for .rpm, .deb, etc... because I understand that's quite complex, but I tried it following all available guides, including the Contributor's Guide, and it seems impossible to get it running at the first time (or just to get it running) without getting crazy or fixing lots of unexpected errors during installation. Have you tried to deploy Mailman 3.x strictly following the documentation? By the way, many thanks for your hard work! Cheers, RI From: "Abhilash Raj" <maxking(a)asynchronous.in> To: ribanez(a)sciops.esa.int Cc: mailman-users(a)mailman3.org Sent: Saturday, August 19, 2017 8:55:20 AM Subject: Re: [MM3-users] Which documentation to follow for installation On Fri, 18 Aug 2017 09:40:37 -0000 ribanez(a)sciops.esa.int wrote: > Hi everyone, > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > look for documentation. I found two different sites: > > https://mailman.readthedocs.io/en/latest/ > http://docs.mailman3.org/en/latest/ Both of the above are actually latest documentation, docs.mailman3.org should be the one to look for installations guidelines for the entire Mailman 3.x Suite, mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles the mail. http://docs.mailman3.org/en/latest/prodsetup.html This should be the best place to start, be sure to look at the Pre-Installation Guide if you are new to the Python ecosystem. > > Do you know which one should be followed? Both at the same time? I find it > quite unclear... and this installation will be for an operational environment. > > Also, there are some (official?...) docker images, but all images are for > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. It is meant for Mailman 3.X series and is maintained by me. It currently includes the latest releases for all the Mailman's sub-projects, also Mailman 3.1. Hope that helps! -- thanks, Abhilash Raj This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email.

8 years, 2 months

[MM3-users] problem with postorius initial setup

by John Covici

Hi. I am trying to setup postorius, but I have run into a problem. I am using the example project, except I am using postgresql instead of sqlite3. I ran python manage.py migrate which was successful. On running the development server I get: Exception in thread django-main-thread: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 20, in import_string return getattr(module, class_name) AttributeError: module 'postorius.middleware' has no attribute 'APICountingMiddleware' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/django/core/servers/basehttp.py", line 45, in get_internal_wsgi_application return import_string(app_path) File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 17, in import_string module = import_module(module_path) File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1014, in _gcd_import File "<frozen importlib._bootstrap>", line 991, in _find_and_load File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 671, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 783, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/home/covici/mailman_django/example_project/wsgi.py", line 17, in <module> application = get_wsgi_application() File "/usr/lib/python3.8/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application return WSGIHandler() File "/usr/lib/python3.8/site-packages/django/core/handlers/wsgi.py", line 127, in __init__ self.load_middleware() File "/usr/lib/python3.8/site-packages/django/core/handlers/base.py", line 40, in load_middleware middleware = import_string(middleware_path) File "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", line 22, in import_string raise ImportError('Module "%s" does not define a "%s" attribute/class' % ( ImportError: Module "postorius.middleware" does not define a "APICountingMiddleware" attribute/class The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3.8/site-packages/django/utils/autoreload.py", line 53, in wrapper fn(*args, **kwargs) File "/usr/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 138, in inner_run handler = self.get_handler(*args, **options) File "/usr/lib/python3.8/site-packages/django/contrib/staticfiles/management/commands/runserver.py", line 27, in get_handler handler = super().get_handler(*args, **options) File "/usr/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 65, in get_handler return get_internal_wsgi_application() File "/usr/lib/python3.8/site-packages/django/core/servers/basehttp.py", line 47, in get_internal_wsgi_application raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: WSGI application 'wsgi.application' could not be loaded; Error importing module. Thanks in advance for any suggestions. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 7 months

[MM3-users] Re: Process on migrating mailman

by Mark Labeste

Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else should remain the same. Stop both Mailman's processes: ``` systemctl stop mailman3 systemctl stop mailmanweb ``` Assuming that Mailman core and Mailman web were using the same DB (named mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file: ``` mysqldump mailman3 > mailman3-DOMAIN1.sql sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql mysql mailman3 < mailman3-DOMAIN2.sql ``` Run the migrations as documented in https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… Restart the processes ``` systemctl start mailman3 systemctl start mailmanweb ``` Of course, check your logs for anything strange and fix it :) PS: Could you please try and not top-post? Put your replies below the ones you receive. On Tue, Jan 23, 2024 at 3:28 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > Once you dump and replace DOMAIN1 with DOMAIN2, everything else should > remain the same. > > PS: Could you please try and not top-post? Put your replies below the ones > you receive. > > > On Tue, Jan 23, 2024 at 9:57 AM Mark Labeste <marqueejen13(a)gmail.com> > wrote: > >> Just like to confirm when doing this dumping process. Nothing will change >> on the current mailing list? >> > > > [snip] > > Once you dump and replace DOMAIN1 with DOMAIN2 globally, everything else > should remain the same. > > Stop both Mailman's processes: > > ``` > systemctl stop mailman3 > systemctl stop mailmanweb > ``` > > Assuming that Mailman core and Mailman web were using the same DB (named > mailman3), dump the DB and replace DOMAIN1 with DOMAIN2 in the sump file: > > ``` > mysqldump mailman3 > mailman3-DOMAIN1.sql > sed "s/DOMAIN1/DOMAIN2/g" mailman3-DOMAIN1.sql > mailman3-DOMAIN2.sql > mysql mailman3 < mailman3-DOMAIN2.sql > ``` > > Run the migrations as documented in > https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… > > Restart the processes > ``` > systemctl start mailman3 > systemctl start mailmanweb > ``` > > Of course, check your logs for anything strange and fix it :) > > > PS: Could you please try and not top-post? Put your replies below the ones > you receive. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > mysqldump seems not working. it says command not found. -- Regards, mARK

1 year, 9 months

[MM3-users] Re: how to administrate mailman3 in CLI ?

by testeur

Sorry. I didn't see in the good place. when i see parameters here : https://URL/mailman3/postorius/accounts/per-subscription-preferences/ the options or the specific language chosen (not for the ui) for the list is finally changing when i use the code used before... i should use shell with mailman user. ok i note it. I ve seen this link about python script to manage mailman3 by shell : https://fog.ccsf.edu/~msapiro/scripts/ (thx you) Regards, On 23/09/2023 17:33, Mark Sapiro wrote: > On 9/23/23 07:40, testeur via Mailman-users wrote: >> >> |# mailman shell -l testlist(a)domain.tld | > > It looks like you are running `mailman shell` as `root`. You should > always run mailman commands including starting mailman as the Mailman > user, never as root. Running thing as root can create things that > later can't be read by the mailman user. > >> ||>>> from mailman.interfaces.action import Action >>> for mbr in >> m.members.members: mbr.moderation_action = Action.defer |||commit()| >> >> |||>>> from mailman.interfaces.action import Action |||||||>>> >> english = getUtility(ILanguageManager).get('en')| >>> for mbr in >> m.members.members: || mbr.preferences.acknowledge_posts = False >> mbr.preferences.delivery_mode = DeliveryMode.regular >> mbr.preferences.delivery_status = DeliveryStatus.enabled >> mbr.preferences.hide_address = False >> mbr.preferences.preferred_language = english >> mbr.preferences.receive_list_copy = False >> mbr.preferences.receive_own_postings = True|commit()|| > > > I'm not sure what the above actually says. The interaction should look > like > ``` > >>> from mailman.interfaces.action import Action > >>> english = getUtility(ILanguageManager).get('en') > >>> for mbr in m.members.members: > ... mbr.preferences.acknowledge_posts = False > ... mbr.preferences.delivery_mode = DeliveryMode.regular > ... mbr.preferences.delivery_status = DeliveryStatus.enabled > ... mbr.preferences.hide_address = False > ... mbr.preferences.preferred_language = english > ... mbr.preferences.receive_list_copy = False > ... mbr.preferences.receive_own_postings = True > ... > >>> commit() > ``` > Actually, importing Action is not necessary as it is among the things > defined by default in `mailman shell` in interactive mode. > >> Before the shell command, the web interface was with an other >> language (i tested with italian one) and other options preferences, >> but after the shell command, after a web interface refresh, it >> doesn't change. > > > The above shell interaction sets the preferred_language for all list > members to english. This has nothing to do with the language for the > web UI. This is set by Django. See > <https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#how-django-d…>. > >

2 years, 1 month

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mohsen Masoudfar

Thanks you so much Mark, I appreciate your help! Yes, I did: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: newlistserv.aaas.org lmtp_port: 8024 smtp_host: newlistserv.aaas.org smtp_port: 25 configuration: python:mailman.config.postfix # postconf recipient_delimiter recipient_delimiter = + # postconf owner_request_special owner_request_special = no in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp transport_maps = hash:/opt/mailman/var/data/postfix_lmtp virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. I restarted the whole stack and added a new list. In postfix logs I see: Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_vmap.db: No such file or directory I touched the /opt/mailman/var/data/postfix_vmap, but it did not help neither. In addition, I found out this : On my old mailman2 I have a setting in postfix main.cf: alias_maps = dbm:/usr/local/mailman/data/aliases the file /usr/local/mailman/data/aliases says in its first line: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE This makes a lot of sense to me. The point is I am missing any similar settings on postfix on mailman3. Maybe local_recipient_maps do that, but as I mentioned the DB file is older than the text file. The result is that the list (which is actually a postfix user) is unknown to postfix completely. Now what is missing here? It appears that postorius can talk to postfix to send welcome messages out, but Postfix is not aware about the User that Postorius has created and exists in SQLite DB. So rejects any email addressed to that one. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, April 15, 2020 10:09 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Recipient address rejected: User unknown in local recipient table [EXTERNAL EMAIL] On 4/15/20 3:47 PM, Mohsen Masoudfar wrote: > I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . > Or probably this is related to a postfix setting? Have you configured Mailman core and Postfix per <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…>? -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 6 months

[MM3-users] Re: External MTA incoming mail: configuration

by Mark Sapiro

I see this reply is now moot as you have now configured list mail to go directly to the Mailman server, but ... On 8/5/24 03:44, Roland Giesler via Mailman-users wrote: > > In the logs of the MTA I see this however: warning: do not list domain > fast.za.net in BOTH virtual_mailbox_domains and relay_domains > > Mailman creates these entries, but postfix doesn't like it. I don't see > any mail delivered to the mailman yet. Is this the problem? Probably not. It is telling you that mail to the fast.za.net domain cannot both be delivered to local mailboxes (virtual_mailbox_domains) and relayed to foreign hosts (relay_domains) > In the MTA postfix main.cf: > > relay_domains = hash:/etc/mailman3/data/postfix_domains > > cat /etc/mailman3/data/postfix_domains > ... > > and also > > local_recipient_maps=$virtual_mailbox_maps, > hash:/etc/mailman3/data/postfix_lmtp > > cat /etc/mailman3/data/postfix_lmtp > ... How about transport_maps = hash:/etc/mailman3/data/postfix_lmtp > > Then there's: > virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf > > cat /etc/postfix/virtual-mailbox-domains.cf > dbpath=/home/user-data/mail/users.sqlite > query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM > aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE > source LIKE '%%@%s' > > When I run that query in sqlite3, it returns no records, so I'm not sure > how this is supposed to work. %s to me means that first argument, so is > this used in python and then %s is the argument sent to this query? See https://www.postfix.org/sqlite_table.5.html `%%` is replaced with `%` which is a SQL wildcard matching anything and `%s` is replaced by the key postfix is looking for, i.e. the domain that it is asking about. So, that query becomes SELECT 1 FROM users WHERE email LIKE '%(a)fast.za.net' UNION SELECT 1 FROM aliases WHERE source LIKE '%(a)fast.za.net' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%(a)fast.za.net' I.e, it returns true if any user or alias or auto_alias has an address ending in '@fast.za.net' and if that's true the mail to any '@fast.za.net' address including list mail will be stored locally. If you really have local users on box2.gtahardware.co.za with addresses '@fast.za.net' and you want to relay list mail to lists '@fast.za.net', you need to see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by matthew＠alberti.us

Steve, Thanks for the response. I put " HYPERKITTY_ALLOW_WEB_POSTING = False " in and that has worked as intended. Sorry I wasn't more clear in my previous e-mail. I was trying to say that Django-recaptcha might be a good way to gate the signups, but it looked like mailman code would have to be changed to work with djangi-recaptcha. But it seems not effective enough to be worth pursuing. For now, maybe disabling posting via hyperkitty will be enough. Any SPAM sent in from other sources will be subject to scanning. - Matt Alberti -----Original Message----- From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Thursday, August 26, 2021 1:36 PM To: matthew(a)alberti.us Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Unwanted E-mail to Maillists Submitted via Postorius Interface matthew(a)alberti.us writes: > I’ve seen a recent uptick in SPAM messages making it into > mailing lists. Looking at the raw, it seems that the e-mails are > being submitted thru the Postorius/Hyperkitty “Start a New Thread” > interface. Is there a way to turn that off? I think this is HyperKitty only. Postorius doesn't know anything about posting or distributing posts. You can disable web posting by setting HYPERKITTY_ALLOW_WEB_POSTING = False (as above, no quotation marks etc) in settings.py. I don't know much about HyperKitty, so I'm not sure where that file lives in your installation. > Part of the problem is that our anti-spam system RSPAMD trusts the > mailman-web IP… so it doesn’t scan things originating from > there.. %G 笘ケ%@ You know your organizational constraints, but it's a bad idea to trust any web-facing application that can send email to be responsible about it. :-( > Another uestion: Is there a way to implement captcha, or is > there a recommended gate that can be put in the signup process? Here's the most recent technical discussion I can find. Archived-At: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message /RSZLMKPASCTKFY63RKGPGNCVVPAB5C4M/> However, it turns out that bots are almost as good at solving captchas as humans, and they can retry a lot faster. Captchas are also really horrible from an accessibility perspective. > Apparently bots are finding a way thru the signup process, and then > sending messages to the list via the Postorius web interface. There > seems to be a Django plugin for it; but it appears the Mailman code > would have to be adjusted to implement it. I don't think so, because Mailman (that is, HyperKitty and Postorius) delegate authentication to Django. Why do you think Mailman code needs to be adjusted? Steve

4 years, 2 months

[MM3-users] Re: Mailman 3 installation documentation

by Terri Oda

Hurrah! I'm very excited about these updates. :) On October 6, 2019 8:17:15 p.m. PDT, Abhilash Raj <maxking(a)asynchronous.in> wrote: >Hi All, > >I have been trying to work on revamping the documentation site we have >at https://docs.mailman3.org. It is on https:// but I am not sure why >the http->https redirect doesn't work in Readthedocs. I have set it to >"serve always from https". > >Anyway, it might not look too different right now, but there are some >small re-organizations. I have been learning some new ReST and Sphinx >tricks and been trying to cross-reference and link various sections and >settings. The docs site shows up Mailman's logo now (I didn't even know >we could do that ;-). > >There is a place[1] for all supported Django settings that Postorius >and Hyperkitty have. I am also planning to add some common Django >settings that often people have to lookup and is not fun for people >from non-python backgrounds. Hopefully, it will make lives easier for >administrators. > >I have reverted my own stupid decision to use "sudo pip3 install" in >the docs to instead use virtualenv. The installation docs are going to >grow to be more comprehensive. > >I am also working on mailman-web project[3], which should simply >installation process for all the web components using a single project >and provide better guidance on Django's settings file management and >howto run manage.py commands. > >I have added a `mailman-web` command, which, for those of you familiar >with internal details of Django, is going to be our custom manage.py >script. It sets up settings correctly and would hopefully reduce the >pain of using `django-admin` and/or finding out the right path for >`manage.py` script. It is still not ready for prime time, but it is >usable. Early adopters can play with it if they like! > > >I would really appreciate if people who have tried to manually install >Mailman 3 in the past would share their experiences about what they >think could be documented better. You can reply here or open an >issue[2]. > >The user documentation are going to follow, hopefully soon :) > > >[1]: >https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… >[2]: https://gitlab.com/mailman/mailman-suite-doc/issues >[3]: https://gitlab.com/mailman/mailman-web > >-- > thanks, > Abhilash Raj (maxking) >_______________________________________________ >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/

6 years

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/26/20 3:15 AM, Odhiambo Washington wrote: > There is still some confusion on my part about the directives in the file > so allow me to seek some clarifications. > > The following are the contents of a file I have created and placed in my > Apache Includes/ directory. > I was hoping that with it, I can now access http://lists.my.server/mm3 and > get the UI. > > <CUT> > > # Global section > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > WSGIRestrictSignal Off > > <VirtualHost *:80> > ServerName lists.my.server > ServerAdmin odhiambo(a)gmail.com > > # (I'm not sure that WSGIRestrictSignal Off is required, but it was in the > # provided example so I kept it. I also made changes to WSGIDaemonProcess > # based on my own mod_wsgi experience elsewhere.) > > ErrorLog /var/log/myserver-error.log > LogLevel debug > > # This goes in the VirtualHost block for the domain. > > # Mailman 3 stuff > Alias /static "/var/spool/mailman-web/static" *<----- Where is this > directory supposed to be and what/who creates it and with what permissions?* It is created/updated by the mailman-post-update script based on CONFDIR and STATIC_DIR. > <Directory "/var/spool/mailman-web/static"> With the settings in the sample, the above should be <Directory "/opt/mailman/mm/static"> and the alias Alias /static "/opt/mailman/mm/static" Clearly <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> doesn't match some other files. I'll review abd update that. > Require all granted > </Directory> > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > <Directory "/opt/mailman/mm/"> > <Files wsgi.py> > Order deny,allow > Allow from all > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > </VirtualHost> > > </CUT-HERE> > > I end up with an "Internal server error" and from the error log I see: > ... > [Sun Jul 26 12:04:44.093265 2020] [wsgi:error] [pid 6444] [remote > 197.232.81.246:53383] ModuleNotFoundError: No module named 'settings' Django is trying to import your settings.py file and can't find it. Is it at /opt/mailman/mm/settings.py and also local settings at /opt/mailman/mm/settings_local.py? -- 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: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, Well... not that good. Now it is mailman3-web that doesn't work. mailman@new-machine ~ (v3.3.9)> source venv/bin/activate.fish (venv) mailman@new-machine ~ (v3.3.9)> mailman-web Type 'mailman-web help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate optimizemigration runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check System check identified no issues (0 silenced). (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 158, in get_app_config return self.app_configs[app_label] KeyError: 'migrate' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in handle app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in <listcomp> app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 165, in get_app_config raise LookupError(message) LookupError: No installed app with label 'migrate'. Any idea why migrate isn't working and saying it is installed? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sat, 16 Dec 2023 at 07:51, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Helio Loureiro writes: > > > And now it is starting without errors. I guess that was it. > > Thank you for the success report! We love to hear it. > > Please do continue to watch for strange behavior and feel free to > report here if you have futher problems. > > Steve > > _______________________________________________ > 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 helio(a)loureiro.eng.br >

1 year, 10 months

[MM3-users] Re: docker mailman-core mailman3 image not responding on port 8024

by Abhilash Raj

> On Aug 17, 2021, at 11:37 AM, bob B <bader(a)cchmc.org> wrote: > > I restarted the containers so the new/current ips are > > > core "IPAddress": "172.25.0.3", > web "IPAddress": "172.25.0.4", > > > > Here is the content of that file > > ************************** > > docker exec -it mailman-core /bin/bash > bash-5.0# cat /etc/mailman.cfg > # This file is autogenerated at container startup. <snip> > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 172.25.0.3 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg Looking at your [mta] configs, it seems like incoming configs are correct, but outgoing configs aren’t. You have the Mailman Core binding to 172.25.0.3, which is the IP address allocated to it from Docker and it should be accepting connections on 172.25.0.3:8024. The outgoing config will use the hard coded IP configs in the 0.3.11 release of the container images, but you can fix that by setting SMTP_HOST: 172.25.0.1 in both mailman-core and mailman-web container configurations in docker-compose.yaml file under “environment”. I am assuming that Postfix is listening on all interfaces (0.0.0.0, which is usually the case that I have seen, but something still that perhaps should be verified). > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > # mailman-core hostname or IP from the Postfix server > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > # Postfix server's hostname or IP from mailman-core > smtp_host: ########## > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: ########## > bash-5.0# This part is probably the one causing trouble, probably coming from what you added to mailman-extra.cfg. This overrides the configs above (which is right for incoming emails) ones. Mailman is binding to 127.0.0.1 inside the container, and that loopback interface isn’t accessible from anywhere outside the container itself, so you won’t be able to talk to it. It needs to listen either on 0.0.0.0 (all interfaces) or (at least, one of the) public IPs assigned to the container. The fix is that you just want to delete the entire [mta] section of mailman-extra.cfg and restart the container. Do also setup the SMTP_HOST environment to fix that outbound email issue. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: Mailman 3 database restore unexpected behavior

by Tibor Molnar

Hi Odhiambo, I have looked at the tables, and member and user tables have same fields but I'm not sure if that is the source of issue. In my experience is whenever I restore the databases the bounce message hits all users. Followed through the mailman logs also and all I can see is everyone is getting unsubscribed from all lists. However all members are still stay part of every list. Before restored the databases I have dropped them all the time. On 28/03/2023 13:36, Odhiambo Washington wrote: Have you looked at the tables and actually seen the duplicates? SELECT COUNT... Again, restoring a database usually should drop the table before restoring. On Tue, Mar 28, 2023, 14:00 Tibor Molnar <tibor.molnar(a)waltoninstitute.ie<mailto:tibor.molnar@waltoninstitute.ie>> wrote: Mailman3 built from source using virtual environment. Version: GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg Issue: I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed? Bounces message: name(a)email.com<mailto:name@email.com> unsubscribed from [listname] mailing list due to bounces Only restoring two files: mailman3 and mailman3web Did anyone come acroos this behavior ? It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. I may do something wrong during the restoring process. Please advise me. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@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 odhiambo(a)gmail.com<mailto:odhiambo@gmail.com> -- [Walton icon] Tibor Molnar [website icon] <https://waltoninstitute.ie/> [linkedin icon] <https://www.linkedin.com/in/tibor-molnar-564293106> [twitter icon] <https://twitter.com/username> [facebook icon] <https://www.facebook.com/username> System Administrator tibor.molnar(a)waltoninstitute.ie<mailto:name.name@waltoninstitute.ie> | +353 (0)51 30 6145 Walton Institute, South East Technological University, West Campus, Carriganore, Waterford, Ireland, X91 P20H [walton logo]<https://waltoninstitute.ie/> [setu logo] <https://www.setu.ie/> [DORA logo] <https://sfdora.org/read/> ________________________________ This email is subject to the following disclaimer(s) available at SETU Disclaimer.<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> Tá an ríomhphost seo faoi réir an tséanta/na séanta seo leanas atá le fáil ag SETU Séanad<https://www.wit.ie/about_wit/documents_and_policies/email-disclaimer> [SETU]<https://www.setu.ie>

2 years, 7 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Stephen J. Turnbull

gordon(a)dickens.com writes: > I am now running Python3.11 [using] the "apt autoremove" command > which I did use during the OS upgrade. This is not a problem, but you do have to upgrade your venv as well. > Why doesn't mailman3 work with Python3.11? It works fine with Python 3.11. The problem is that the point of a venv is to freeze everything -- including the Python binary -- "in place". However, because (a) Python is extremely stable across minor releases and (b) it is important to keep up with bug fixes, especially security fixes, in Python, the venv usually symlinks to the /usr/bin/python3.x binary (which is usually a symlink to a 3.x.y executable). If /usr/bin/python3.9 disappears, that will, of course, leave your Python 3.9 venv with a bunch of dangling symlinks and nothing in the venv will work. > Does this mean that I will need to rebuild mailman3's venv > everytime that python is upgraded? No. /path/to/new-python3.y -m venv --upgrade /path/to/venv should upgrade the venv to use Python 3.y, without changing any of the installed package sources. I believe it also recompiles all the source.py to __pycache__/source.cpython-3y.pyc files for you, but that is merely a minor time saving for the next time you start Mailman since Python will automatically recompile when you change versions. If you have upgraded the /usr/bin/python3 in place (apparently you did) you can simplify the above to python3 -m venv --upgrade /path/to/venv and venv will figure out the right symlink for you. Caveat, I have never tried this, I just don't uninstall the old Python installations because as a developer I need to test Mailman against them. But that's what "python3 -m venv --help" tells me. :-) If you don't trust my untested suggestions (and why should you? ;-), you can try PYTHONPATH=/path/to/venv/site-packages python3 -m pip freeze and if that looks sane (ie, a list of Mailman and Django related packages and their versions), you can redirect it into requirements.txt. Then if necessary you can blow away the original venv and start new with the upgraded Python 3 and exactly the same package versions you had before with python3 -m pip install -r requirements.txt You can also avoid the venv upgrade entirely by using python3 -m venv --copies /path/to/venv to build the venv in the first place, which as I understand it will copy the whole Python installation into the venv. But then you lose the benefit of Python bug fixes from your distro and of course the space saving of symlinks. Steve

2 years

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 1:30 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > On Thu, Dec 20, 2018, at 10:25 AM, brian(a)emwd.com wrote: > > > I am using Exim as the MTA. I followed the instructions located at: > > > > > > https://github.com/maxking/docker-mailman > > > > > > In particular the "Setting up your MTA" > > > > > > Are you saying I need to do something with Django because your > > > documentation at github makes no reference to that? Where would I find > > > the settings.py file? I used your image to install Mailman3. FYI I am > > > referencing the "# To be added to Django's settings.py" instructions at > > > > > The documentation at Github does makes reference to it. It might not be > > in the most visible manner, which I have opened an issue to fix[1] > > > > > To configure the mailman-web container to send emails, see these > > > configuration settings. > > The documentation also mentions about the Django configuration file, > > settings_local.py (which is imported by settings.py at runtime). [3]. > > > > I have opened another issue to make that clear as well. [2] > > > > You can add all your Django related settings in `/opt/mailman/web/settings_local.py` > > if you using the images and docker-compose.yaml file from the above mentioned > > repo. > > > > > > [1]: https://github.com/maxking/docker-mailman/issues/277 > > [2]: https://github.com/maxking/docker-mailman/issues/278 > > [3]: https://github.com/maxking/docker-mailman#configuration > > > > > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > > > _______________________________________________ > > > 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/ > > > > > I am glad this is going to result in getting more clearer documentation. > > I have added the following to /opt/mailman/web/settings_local.py > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = <username> > EMAIL_HOST_PASSWORD = <password> > > The question I have is where does the username and password come from? It is for your MTA authentication. If you are using Exim, which is configured to not authenticate users from trusted hosts, you can skip them both. It is useful when you are using some SMTP service like Amazon SES, Gmail etc. -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: deployment recommendation(?)

by Andrew Hodgson

noc(a)iem.at wrote: ># Debian packages >this is what I would normally pick, but: my past experience with mailman3 in Debian was... rather suboptimal. >(my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). Yep, I think a lot of people on this list have tried these packages and have got burnt. That is mor likely due to our own shortcomings rather than anything the package maintainers have done, but my impression is that most people on this list have gone either virtualenv or Docker due to the support that others have with these methods. For various reasons I now have to use Ubuntu, and when I migrated to Ubuntu 22.04 I wanted to go from Docker to use these packages, only to find that the packages were missing from Ubuntu due to the fact that Ubuntu shipped a newer Python version and that didn't work with the older version of Mailman in those packages. Since then I did an upgrade to Ubuntu 24.04 and briefly looked at the packages but my existing install was already on 3.3.9 so continued with the venv method. ># Docker packages >this is of course the simplest from a deployment perspective, but then i'm a bit worried about the security perspective. >in my perception, docker deployments tend to get installed and then forgotten, and while the host OS keeps getting updates, the docker images are just left as is. so they tend to get stale. The Docker containers are well maintained by Maxking (Abhilash Raj) who is also the core Mailman maintainer. If you look at the images on Dockerhub they do get regular updates. I would say that your update strategy would need to take Docker image updates into account. I used these images for a while, I moved from Docker because I run software on the same machine as my small Mailman instance which takes over the Docker management, and I wanted Mailman to be installed alongside that. ># virtualenv >this is the deployment method recommended in the docs. >however, it doesn't say why this method is any better than the others. >also, the website says that it was last updated in 2019, so: is this recommendation still relevant? This is the method I use now and seems to be the most universally supported on this list. I've explained why I went this method earlier on in this post. The installation docs for virtualenv installation were very recently updated. Upgrading the distro (Python major version upgrade) does require a venv rebuild, but general updates throughout the year seem absolutely fine. All the persistent data is stored outside the venv of course. Thanks. Andrew.

1 year, 3 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 06/17/2016 12:16 PM, Bill wrote: > Hi, > > I'm looking for some information on Mailman3 administration. I've found > that it's not yet packaged by any of the common Linux distros - Debian, > Ubuntu, Mint, RedHat, Centos, Fedora, Suse, Arch etc so I have some > concerns about the amount of upkeep that running Mailman3 will entail. > > I know that Mailman2 is available as a package on the above distros, but > we would really like to take advantage of the kludge-free, virtual > domains feature on Mailman3. > > I've been asked by a local non-profit provider to assist them in moving > their 200+ mailing lists from an outdated Sympa list server to > Debian8/Postfix/Mailman. One of their chief concerns is the amount of > extra administration, over and above normal list administration, that > Mailman3 will require in the form of manual updates and maintenance. > > We are in the evaluation and design stage right now, but could use any > pertinent advice about supportive distros, available packages, the > amount of extra administration involved or perhaps, in a worst case > scenario, alternate list managers supporting a virtual domains feature > similar to Mailman3. > > Thanks for your help, > > Bill McGrath > President, Vancouver Linux Users Group > https://vanlug.bc.ca I've copied this post and set Reply-To: to the Mailman 3 users list <mailman-users(a)mailman3.org>. Please join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> before replying there. That said, we are working on packaging for a more turn-key installation, but we aren't there yet. I've installed a couple of instances including the one at lists.mailman3.org, and it does require extra work. Some of the work in my case is because I want to run all the Mailman pieces from the heads of their branches rather than what's in PyPI, but even without that, installation is significantly more work than installing a distro's package. I will be writing up my experiences, but that's not done yet either. I will say that once you have Mailman 3 installed and running, updating (which I do frequently, but which doesn't need to be done unless you want specific updates/fixes) is pretty easy. As far as alternatives are concerned There is an up to date Mailman 2.1 branch with better virtual domain support at <https://code.launchpad.net/~msapiro/mailman/vhost>, but I think in the long run, you'd be better off with Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 4 months

[MM3-users] Office365 posts shunted (authres.core.SyntaxError)

by Stephen J. Turnbull

Bryan Loniewski writes: > I've been dealing with another issue (and why I upgraded to the > latest code) when posting messages to my test list from our schools > Office365 infrastructure (OWA). The post gets shunted; mailman.log > has the following error: Bottom line: the reported Authentication-Results (A-R) field has nonconforming syntax. The problem is that the RFC defines a syntax where the authentication service ID is the first thing in the field, and only one is allowed. In the quoted field it occurs twice. There are more syntax errors, but that's the one Mailman flagged. As far as I know the only part of Mailman that uses A-R is the ARC module. Just disable it and be happy, I think. Like DKIM, DMARC, and friends, this is really an MTA function. If possible you should get your MTA to do the work. BTW, I'm not sure this is an Office365 problem. It appears that the A-R field was constructed on lists-test.rutgers.edu, which doesn't look like Office365. Is it possible that the Office365 system didn't provide one, and this A-R field was added by Mailman itself? (Don't overthink this: if so, it's our problem and I'll be looking at it. But if you know offhand it will point me in the right direction.) Excruciating detail follows, in part as notes to me. ;-) In the following, the in-reply-to quoting is omitted and the field is folded for clarity. authentication-results: # field name lists-test.rutgers.edu; # authenticator ID dkim=none (message not signed) # DKIM result info header.d=none; # DKIM property (no DKIM signature field) lists-test.rutgers.edu; # #### nonconforming (not "; key=value") dmarc=none # DMARC result info action=none # #### syntax OK, undefined property header.from=oit.rutgers.edu # DMARC property (field to check) ; # #### nonconforming (nothing to separate) So it looks like whoever wrote the code doesn't understand RFC 7601 at all. A-R starts with a string naming the authentication authority (here lists-test.rutgers.edu) and an optional number naming the version of A-R being used. These are followed either by a semicolon and the word "none", or by a sequence of results blocks. Each block consists of a semicolon followed by a sequence of key=value pairs. This funny phrase "a semicolon followed by a sequence of key=value pairs" is probably easier to understand if I say "the semicolons separate results blocks from the authenticator ID and from each other" (they are not block terminators). RFC 7601 is quite pessimistic about nonconforming A-R, and repeatedly advises they be ignored or even deleted, although completely broken syntax is not mentioned. Steve

5 years, 1 month

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/23/21 12:43 AM, Marco Marinello wrote: > Dear Mark, > > I upgraded the pypi packages as you suggested but the problem remains the same. > Tried also installing from git heads but always get > > ==> /opt/hyperkitty_django/hyperkitty.log <== > ERROR 2021-10-23 09:42:42,523 30765 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > > ==> /var/log/mailman/mailman.log <== > Oct 23 07:42:42 2021 (30888) HyperKitty failure on http://127.0.0.1:8080/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key must be > sent over the Authorization HTTP header. > </p></body></html> (401) Those messages look correct for HyperKitty 1.3.5, if mailman-hyperkitty is not sending the key as expected. The particular condition causing those messages is there is no "Authorization" header in the headers of the request from mailman-hyperkitty and there is also no "key" parameter in the request as there would have been with mailman-hyperkitty 1.1.0 This would seem to say that both HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 are doing the right thing, but somehow the request headers are not getting through in the http request from mailman-hyperkitty to HyperKitty. What is your setting for base_url in mailman-hyperkitty.cfg? Is there some redirect or other situation going on in serving the request to HyperKitty that could cause headers to get lost? > For information, how does your release cycle work? I prefer installing from a source rather than pypi. Is the master normally stable? When a packages lands on pypi? We are a small, all volunteer project and we don't have a fixed release schedule. We make releases when we feel enough change has been accumulated to warrant on or when there is a serious issue to fix. The heads of the gitlab branches are generally usable. There was actually a situation briefly where the mailman-hyperkitty changes for this issue were merged before the HyperKitty changes. See https://gitlab.com/mailman/hyperkitty/-/merge_requests/354#note_693162778 but situations like this are rare. The servers at lists.mailman3.org and mail.python.org run the heads of the gitlab branches (I update them regularly) so you can generally be confident that they work. > I'll stick on 1.3.4 / 1.1.0 for the moment. There are several changes in HyperKitty 1.3.5. See https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Missing Base64 encoding from control message reply

by Stephen J. Turnbull

Jana Berger writes: > You can see the same or similar result by opening the EML I > quoted. Does the list support attachments? Then I will attach the > file directly. No, I just misjudged the length of the email -- without the header it's way too short to generate that much mojibake. I'll take your word for it now. > I have multiple control messages, all received By whom? Through what other systems have they passed? Is this happening with any other domain than USERDOMAIN.NET? The remote MTA in the message you included earlier seems to be something called Nemesis, and Google suggests it may be a German homebrew MTA. That's another candidate for causing this issue. > from my instance which all contain the "Content-Transfer-Encoding: > base64" marker, their contents is plain text (Content-Type: > text/plain; charset="utf-8"), but they are still encoded using > base64. Yes. The question remains, where is it happening and why. As mentioned earlier, Mark tried to reproduce on one of his systems, but did not get the body in UTF-8/base64. It came out us-ascii/7bit, which is what we expect. Given Mark's experiments and the "all English" configuration you report, it seems unlikely to be from our distribution of Mailman. One possibility is that Mailman or Python is getting confused by something in your whole system configuration (not limited to Mailman). Where did you get Mailman? Did you install a OS distribution package, from PyPI, or from source? How about Python 3? I wonder if some MTA is using SMTPUTF8 and to make life "easier" for themselves they convert everything to UTF-8, but gets confused about whether base64 encoding is done or not. > Global "Preferred language" is "English (USA)", which is not > overridden by the list in question. I have not changed the default > encoding. Is there a surefire way to detect this? > My mailman.cfg has no section pertaining to encoding, and all > related files also do not mention encoding. Then everything is configured for UTF-8 except for English, which is US-ASCII. The only way to change the site default language or any charset is in mailman.cfg (or in the code). If you have a distro package of Mailman, you could check in site-packages/mailman/config/schema.cfg to see the settings for default_language (should be en) and immediately after [language.master] (charset should be us-ascii). I think that changing language.master.charset to utf-8 is probably very tempting for distros so that people can safely put emojis and smartquotes in their template messages in English. Steve

2 years, 1 month

[MM3-users] Re: Detectors and Bounces

by summersan＠nclack.k12.or.us

Okay, I've tried updating that `Notify owner on bounce increment: No` setting to `Notify owner on bounce increment: Yes` on a different, testing mailing list. When I tried subscribing two example users to the list, disabled the email account of one of the example, and tried sending an email to the testing mailing list, I got the following type of email (edited): Subject: example_user_2(a)local.domain's bounce score incremented on example_list Body: example_user_2(a)local.domain's bounce score on example_list(a)lists.local.domain has been incremented. The triggering DSN if available is attached. ---------- Forwarded message ---------- From: Mail Delivery System <MAILER-DAEMON(a)mailman_server.local.domain> To: example_list-bounces+example_user_2=local.domain(a)lists.local.domain Cc: Bcc: Date: Fri, 5 Aug 2022 14:13:42 -0700 (PDT) Subject: Undelivered Mail Returned to Sender This is the mail system at host mailman_server.local.domain. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <example_user_2(a)local.domain>: host aspmx.l.google.com[173.194.202.27] said: 550-5.2.1 The email account that you tried to reach is disabled. Learn more at 550 5.2.1 https://support.google.com/mail/?p=DisabledUser k26-20020a63561aexample_listexample_listb0041296bc96b6si3982888pgb.268 - gsmtp (in reply to RCPT TO command) Also, when I checked the `/opt/mailman/mm/var/queue/bounces/` directory, I saw a new file there related to this test bounce. When I checked the directory a little while later, the file was no longer available. This makes it seem like things are processing, but now I see the extended > 70 %CPU thing happening again with the related `mailman` `python3` command via `top`. Here's an example of `strace` output from that high CPU time: poll([{fd=21, events=POLLIN|POLLERR}], 1, -1) = 1 ([{fd=21, revents=POLLIN}]) recvfrom(21, "\27\3\3\0R", 5, 0, NULL, NULL) = 5 recvfrom(21, "%u\340\0\337W\375I1\204P\363\237\272\253\22\16\220\260Z\207\267>\350\0\217\24\333Em\345\253"..., 82, 0, NULL, NULL) = 82 sendto(21, "\27\3\3\0\334\24a\334F\16\223\207\317Zp3\25Md\275\237\302\323m\263K\346\353\223W(1"..., 225, MSG_NOSIGNAL, NULL, 0) = 225 But now, a few minutes later, the %CPU is down to something more expected < 10 %CPU. When I check `strace` again, here is some example output: lseek(22, 0, SEEK_CUR) = 0 read(22, "\200\5\225\25o\0\0\0\0\0\0\214\25mailman.email.messa"..., 4096) = 4096 read(22, "ChtmRrvIKnCG61VyFUDF+Rg9QFohd5og"..., 20480) = 20480 read(22, "gin-bottom:=\r\n10.0pt;=0D=0A\tmarg"..., 4096) = 3872 close(22) = 0 openat(AT_FDCWD, "/opt/mailman/mm/var/messages/BQ/SK/BQSK2L2B6GAF7W6MXGLTTGDUUXU5WHKT", O_RDONLY|O_CLOEXEC) = 22 fstat(22, {st_mode=S_IFREG|0660, st_size=28485, ...}) = 0 ioctl(22, TCGETS, 0x7ffcb2617920) = -1 ENOTTY (Inappropriate ioctl for device) I don't know if this info helps, but I wonder if things are working as expected at this point?

3 years, 2 months

[MM3-users] Re: Weird startup problem after upgrade

by Odhiambo Washington

On Fri, Dec 2, 2022 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/2/22 08:21, Odhiambo Washington wrote: > > I am facing an odd situation in which MM3 doesn't start successfully on > > reboot, but I can start it manually. > > This is a venv install. > > This started after I did an upgrade (pip install --upgrade mailman > > postorius hyperkitty mailman-hyperkitty) followed by the requisite > > collectstatic|compress|compilemessages|migrate > > post-update commands. > > > Was the venv activated when you ran pip? > Yes. > > You should also include django-mailman3 and mailmanclient in the > packages to be upgraded although they are dependencies and "should" > upgrade anyway. > I did not include them in the list of packages to be upgraded because I did not explicitly install them when I installed my server. In BC's HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> which is what my MM3 server is based, they were never part of the modules (app?) installed explicitly. > Also, at least one person has noted that --force-reinstall was required > to get all dependencies upgraded > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > I can try this as well and report back. > > Secondly, it appears that the upgrade did NOT change the versions for the > > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > > the latest. > > > What does `pip freeze` in the venv show for versions? > Here is the listing: https://pastebin.ubuntu.com/p/tMGDxjKwJ8/ > > > Thanks in advance for any insights into what could be causing this. > > > How do you start it manually? `mailman start` or `systemctl start > mailman3`? systemctl start mailman3 > What's the content of /etc/systemd/system/mailman3.service? > root@lists:/home/wash# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysql.service postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman ExecStart=/opt/mailman/mm/bin/mailman start ExecReload=/opt/mailman/mm/bin/mailman restart ExecStop=/opt/mailman/mm/bin/mailman stop [Install] WantedBy=multi-user.target A special note that before I did this upgrade, the startup wasn't an issue. I can actually go back to where I was, because I have complete backup of my venv before the update, but it would be great to figure out why things are the way they are now. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

2nd follow-up. Apologies for spamming this list. I went wandering through the code as suggested by the traceback. I discovered that thee "as_boolean" routine is expecting a string argument but getting a boolean argument. So, If I send the booleans as strings, with values "true" or "false", all is well. This is not what the API documentation suggests I should do. Can someone either fix the documentation or the code? Thanks -- Stephen On Tue, Jan 18, 2022 at 1:44 PM Stephen Daniel <swd(a)pobox.com> wrote: > Followup note: The failed post is associated with this message in > mailman.log: > > 2022-01-18 13:01:49 [FALCON] [ERROR] POST /3.1/members => Traceback (most > recent call last): > File "falcon/app.py", line 361, in falcon.app.App.__call__ > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/members.py", > line 302, in on_post > arguments = validator(request) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/validator.py", > line 227, in __call__ > values[key] = self._converters[key](value) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/lazr/config/_config.py", > line 762, in as_boolean > value = value.lower() > AttributeError: 'bool' object has no attribute 'lower' > > > Possible bug in code? > > On Tue, Jan 18, 2022 at 1:22 PM Stephen Daniel <swd(a)pobox.com> wrote: > >> Mailman3 experts -- >> >> I am trying to subscribe a user to a mailing list via the REST API. >> This works: >> >> Posting to url http://localhost:8001/3.1/members >> POST payload: >> { >> "list_id": "<LISTID>", >> "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", >> } >> RESULT post of "http://localhost:8001/3.1/members" succeeds with code 202 >> >> >> This works does *not *work >> >> Posting to url http://localhost:8001/3.1/members >> POST payload: >> { >> "list_id": "<LISTID>", >> "subscriber": "d13b0bbb29844eb9af4b38dad7bb3707", >> "pre_approved": true >> } >> RESULT post of "http://localhost:8001/3.1/members" fails with code 500 >> >> >> Any suggestions? As best I can tell, inclusion of *any* boolean types >> in my JSON causes the error code 500. FWIW I am generating the JSON using >> go language's JSON package. >> >> I noticed in the API doc that the boolean values are represented as >> 'True' rather than 'true'. So I tried converting all instances of 'true' >> to 'True' in my encoded json. That produced an http 400 error, as it >> probably should. >> >> Thanks! >> >> -- Stephen >> >

3 years, 9 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:42 AM, Mark Sapiro wrote: > On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: >> Mark, >> >> Here is my postconf -n >> >> alias_database = hash:/etc/aliases >> alias_maps = hash:/etc/aliases >> always_add_missing_headers = yes >> append_dot_mydomain = no >> biff = no >> compatibility_level = 2 >> default_destination_concurrency_limit = 15 >> default_destination_recipient_limit = 30 >> header_checks = regexp:/etc/postfix/header_checks >> header_size_limit = 409600 >> inet_interfaces = all >> inet_protocols = ipv4 >> local_recipient_maps = proxy:unix:passwd.byname $alias_maps >> hash:/var/lib/mailman3/data/postfix_lmtp >> mailbox_size_limit = 0 >> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >> myhostname = lists.example.com >> mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 >> myorigin = /etc/mailname >> readme_directory = no >> recipient_delimiter = + >> relay_domains = hash:/var/lib/mailman3/data/postfix_domains >> relayhost = [mail.smtp2go.com]:587 >> smtp_always_send_ehlo = yes >> smtp_sasl_security_options = noanonymous >> smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem >> smtp_tls_security_level = may >> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache >> smtp_use_tls = yes >> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) >> smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated >> defer_unauth_destination >> smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem >> smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key >> smtpd_tls_security_level = may >> transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp >> unknown_local_recipient_reject_code = 550 >> virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap > > > It looks like you are now following > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > > >> What would I have to do to ensure that MM3 and postfix (same new >> server) use the newly created lists.example.org domain, which only >> exists within Postfix when setting up the Postorius domain and lists? >> I want to have it so that whatever the list name is, for example >> 'Staff(a)lists.example.org' will route through Postfix correctly. > > > Have you set an alias_domain for the lists.example.org domain? > > What are the contents of /var/lib/mailman3/data/postfix_vmap and > /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to > anonymize the domains in these, please only change the tld so we can see > the actual subdomains. However, it looks like you don't need to follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> as lists.example.org is not a virtual_alias_domain. You just need to add lists.example.org to mydestination, assuming lists.example.org and lists.example.com are actually different domains, and follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Putting mailman3 server behind a netscaler

by Lieuallen, Thomas Otis

I’m obviously new to MM3, so overwhelmed by all the various pieces. In rereading some documentation and playing with the admin interface, I see that one can specify a web host. I made that change, but it didn’t seem to make any difference. I’m very tempted to scrap my installation and start over again. I had also removed the example.com site, which I thought I saw in passing one shouldn’t do. If I start over, I should be able to have hostname, email domain, and web site all be distinct? Thank you Tom Lieuallen From: Lieuallen, Thomas Otis <Tom.Lieuallen(a)oregonstate.edu> Date: Tuesday, November 28, 2023 at 13:14 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Putting mailman3 server behind a netscaler (I sent this a week ago, but apparently it got lost, trying to resend.) We’ve been using MM2 for eons and are working on a migration to MM3. So, bear with me as I’m still coming up to speed. I’m running MM 3.3.8 and Postorious 1.3.8. Our mailing lists include members within our organization as well as a number outside. We don’t want to expose our MM3 server directly to the open internet, so wish to hide the web portion behind our netscaler and our regular pool of web servers. Those web servers will proxy MM3 web pages on over to our MM3 machine to handle. This seems to work. Email will meander in via MX and mail relay servers. I found and followed directions in this email regarding changing URL paths: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> So, say our MM3 server is: mm3.fqdn I am trying to publish and use urls like https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…><http://www.fqdn/mailman3-admin>, https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fqdn%2…><http://www.fqdn/mailman3/lists>. Again, that works for me. However, MM3 still has its concept of what URLs should be. I hoped I could fix that by way of templates, but I’m not sure there’s a template for everything. I added some templates, but have not replaced all. I was wondering and hoping that some central change could fix any default templates en-mass. Most recently, I changed the mailman admin email yesterday and the confirmation email directed me to mm3.fqdn/…/confirm-email/…. I looked at the stock templates and nothing there had that wording. I just looked at postorious docs and nothing jumps out at me there. 1. Have I gone down a bad rabbit hole? 2. Is there a way to change the advertised web server address? 3. Should I just continue rolling out my own templates and hope and assume that will take care of this issue? Thank you Tom Lieuallen Oregon State University _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

1 year, 11 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Apollinaris Schöll

> On Nov 21, 2020, at 8:51 AM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 11/21/20 10:39 AM, Stephen J. Turnbull wrote: > > This particular client did bring up some Yahoo issues a week ago which I looked into it. The conclusion was Yahoo is deferring a small percentage of outbound mail for a small period of time due to mail volume. Overall we have great successful deliveries to Yahoo addresses on our Affinity server. So I am simply surprised at his communication sent to this list. Yahoo delivery always improves when mail volume becomes more consistent. That week we have moved over a moderate amount of lists that had a few dozen Yahoo members. That caused our SenderScore.org <http://senderscore.org/> rep score to drop from 98 to 96 (which is still a very high reputation). It's back up to 98 (pats myself on the back) because the new outgoing mail volume has become more consistent. Eventually we will fill up the server and will bring up a new server to add new lists to. This approach has worked well for all of our servers for years. So conclusion: broken DKIM signatures are not playing a part with his issues at all. At least from the evidence I have seen. > Also a client of harmony lists and assume to have have same server settings. I hear some Yahoo users have 100% email in spam. But no bounce related to yahoo. Maybe 10% of Yahoo users have problems. After marking them as not spam all users have reported that it is fixed and Yahoo doesn’t mark emails as spam. Yahoo spam detection obviously is a very personalized thing. Gmail overall is much better where < 1% of users see emails in spam. A good resource is here to understand what can be done. https://www.whitelist.guide/yahoo/ Unfortunately it’s not possible to debug such problems without having access to each subscribers email account. Subscribers without technical knowledge are very vague in their reports and do not always understand instructions how to fix it. My suspicion is that some users like to use the “report spam” buttons way too much and then end up with a extremely sensitive individual spam scoring. > > > -- > Brian Carpenter > Harmonylists.com <http://harmonylists.com/> > Emwd.com <http://emwd.com/> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 11 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 2:27 PM, Ken Alker wrote: > --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> The 404s are addresses im HyperKitty's sender table for whih there is no >> corresponding Mailman user. There are multiple possible reasons for this. > > And that is OK, right? Sure. It only means that there are messages in the archive that are From: addresses that aren't currently Mailman users. >> If the behavior has stopped it's probably because the periodic Django >> jobs are not being run - this is bad. > > I see this in the logs from just after midnight: > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > Followed by a huge amount of HTML (strange). This is all from one post. The first is normal it just says that Mailman's var/public_suffix_list.dat doesn't exist, but it should be retrieved from https://publicsuffix.org/list/public_suffix_list.dat and then saved at var/public_suffix_list.dat so it doesn't need to be retrieved from the web again until the saved copy is older that the configured dmarc.cache_lifetime (default = 7 days, so that message) after which time the message will be 'Cached copy of public suffix list is out of date' The second is acceptance of the post. The third is a failure in archiving the message. Th HTML should contain an error message with a traceback which should help determine the problem. > Is there a way to kick it into re-running whatever it does at midnight > so I can test this again after putting the public suffix list back? I > assume I can just execute "mailman-web runjobs daily", but will this > mess things up, or is it OK to run it mid-day without stopping anything > first? Midnight is a coincidence in this case. the above are all due to the post with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> The cached var/public_suffix_list.dat should now be there with a timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) > Is the last (third) log line excerpt simply a result of the first, or do > I have something else messed up? The third is not because of the first. It is because of some issue with archiving that post. -- 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: digest summary heavily cluttered with hrml code

by Mohsen Masoudfar

Hi Mark, Thanks again for your help! Yes, I meant "Today's Topic". I checked the link you sent, but could not see the solution to the issue. You mentioned: " They are in order of priority, list based, address based and global" Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings are empty, even though I set them and saved. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 14, 2020 12:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: digest summary heavily cluttered with hrml code [EXTERNAL EMAIL] On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years

[MM3-users] translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 13/2/21 20:00, Mark Sapiro wrote: > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One would > need to create Spanish translations of all the templates in > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> > and submit a merge request to add them to a mailman/templates/es/ directory. I downladed the templates and I'm beginning the translation process, but I have a question. What language map has to be used? In my S.O. it's ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before having to do a remapping of the files after... It comes to my attention that three files have 0 bytes. -rw-r--r-- 1 Oldno7 wheel 382 14 feb. 00:22 domain:admin:notice:new-list.txt -rw-r--r-- 1 Oldno7 wheel 886 15 feb. 11:28 help.txt -rw-r--r-- 1 Oldno7 wheel 289 14 feb. 00:22 list:admin:action:post.txt -rw-r--r-- 1 Oldno7 wheel 120 14 feb. 00:22 list:admin:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 122 14 feb. 00:22 list:admin:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 133 14 feb. 00:22 list:admin:notice:disable.txt -rw-r--r-- 1 Oldno7 wheel 71 14 feb. 00:22 list:admin:notice:removal.txt -rw-r--r-- 1 Oldno7 wheel 59 14 feb. 00:22 list:admin:notice:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 257 14 feb. 00:22 list:admin:notice:unrecognized.txt -rw-r--r-- 1 Oldno7 wheel 45 14 feb. 00:22 list:admin:notice:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:digest:header.txt -rw-r--r-- 1 Oldno7 wheel 337 14 feb. 00:22 list:member:digest:masthead.txt -rw-r--r-- 1 Oldno7 wheel 154 14 feb. 00:22 list:member:generic:footer.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:regular:header.txt -rw-r--r-- 1 Oldno7 wheel 562 14 feb. 00:22 list:user:action:invite.txt -rw-r--r-- 1 Oldno7 wheel 753 14 feb. 00:22 list:user:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 739 14 feb. 00:22 list:user:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:user:notice:goodbye.txt -rw-r--r-- 1 Oldno7 wheel 281 14 feb. 00:22 list:user:notice:hold.txt -rw-r--r-- 1 Oldno7 wheel 439 14 feb. 00:22 list:user:notice:no-more-today.txt -rw-r--r-- 1 Oldno7 wheel 98 14 feb. 00:22 list:user:notice:post.txt -rw-r--r-- 1 Oldno7 wheel 568 14 feb. 00:22 list:user:notice:probe.txt -rw-r--r-- 1 Oldno7 wheel 273 14 feb. 00:22 list:user:notice:refuse.txt -rw-r--r-- 1 Oldno7 wheel 151 14 feb. 00:22 list:user:notice:rejected.txt -rw-r--r-- 1 Oldno7 wheel 353 14 feb. 00:22 list:user:notice:warning.txt -rw-r--r-- 1 Oldno7 wheel 532 14 feb. 00:22 list:user:notice:welcome.txt TIA.

4 years, 8 months

[MM3-users] Does anyone have a working DKIM/ARC configuration?

by Stephen J. Turnbull

Philip Colmer writes: > However, in sending test messages to a mailbox hosted by Microsoft, > I'm seeing a header like this: We need *all* the relevant fields (all the DKIM signatures, all the ARC-* fields from both your server and Microsoft, and the From field, and if possible all the trace fields like Received) to figure out what's going on. The ARC-A-R header from Microsoft is complex, but here's what I guess is going on: ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 1.2.3.4) smtp.rcpttodomain=destination.org SPF is OK. rcpttodomain is not relevant. smtp.mailfrom=mmserver.org; dmarc=bestguesspass action=none header.from=mmserver.org; I assume IP 1.2.3.4 reverse DNS to mmserver.org, so DMARC passes at this point (I'm assuming that the From: address is an @mmserver.org address, as the header.from parameter indicates). This is a spurious pass; it only works because you happened to send From: somebox(a)mmserver.org. Any other author domain will fail DMARC. dkim=test (signature was verified) header.d=mmserver.org; This is mmserver.org's DKIM signature, presumably added after passing through Mailman, which passes. dkim=fail (signature did not verify) header.d=sender.org; This is sender.org's DKIM signature, and it is expected to fail unless Mailman is configured in pure pass-through mode where it does not touch the body or any of the signed header fields. sender.org's DKIM signature may as well not be there for a conforming MTA (I assume Microsoft's does in this, I don't see any advantage to them in breaking DKIM). arc=fail (47) I have no idea what went wrong, since you don't provide mmserver's ARC-* fields. This is saying that Microsoft couldn't validate something in the ARC-* fields provided by mmserver.org, or perhaps that Mailman failed to validate something at mmserver.org. > Manually sending an email from the server to the same external > email address does give me an email with a valid DKIM header: The ARC-A-R field above appears to show the expected failure of the "pre-Mailman" DKIM signature and the expected success of the "post-Mailman DKIM signature. DKIM does not appear to be a problem. > Hence the question: does anyone have Mailman 3 + Postfix working > successfully with DKIM and ARC? DKIM is all over the place, working fine. Mailman ARC was tested, and passed, during the ARC development process at the IETF. I don't know offhand if anybody is using that combination now. If you own the MTA, we recommend doing ARC there if supported by the MTA (I think Postfix does). I'm glad to see Microsoft supporting it! Steve

4 years, 1 month

[MM3-users] Re: Default values for new lists

by Abhilash Raj

On Thu, Jan 4, 2018, at 3:00 AM, Sten Aus wrote: > Also, I would like to change archive (hyperkitty) default sort order > (for Name), because I think it is weird where I cannot see lists I am > participating in (even if I am logged in) in "most popular" view. Can it > be achived somehow? > > > And I think it's weird too that I see all lists in archive view (even if > they are private) even when I am not subscribed to them. Only thing > keeping me away from that list is that I cannot see archives and error > message is displayed. > > > Although I cannot imagine how many of list users log in to mailman panel > and then try to access archives, mostly it is done by accessing direct > link. But I don't need to display all archives (almost 3000) lists to > every logged in user, if they are member of only one or two. I am not 100% sure about it, but I don't think it can be configured right now. You can open an issue in Gitlab[1], I think it would be something useful to have. [1]: https://gitlab.com/mailman/hyperkitty/issues > > On 04/01/2018 11:47, Sten Aus wrote: > > Hi > > > > I haven't found out where I could choose or edit default list values > > (when creating new list). > > > > For example I would like that all new lists would be with *private > > archive* (and change this when it is needed). > > This is great that I can choose not to advertise list in Index (which > > I can choose from list creation interface) but I would like to choose > > other options too. > > Right now only solution is to create list and then choose Archiving > > and then select "private archives". > > > > Another thing is that I would like to choose default subscription > > policy to "Moderate". > > > > If anyone has encountered this problem, let me know! Default settings are termed as "styles" in Mailman Core, and these can be used to create a default configuration for a list. However, these aren't easily configurable right now. There are few default styles that do exist today (annoucement, for example), but I am not sure if they are exposed in the UI. We had one of our GSoC student work on this and there is a merge request pending somewhere that improves the "Styles" in Mailman Core. However, it isn't a part of Core yet. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 9 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Mark, RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. I ran mailman aliases and the first try got can't read main.cf. I granted read-only access to other on the file, the next mailman aliases command ran without errors, but I don't know if it did anything or not, e.g. nothing in postfix_domains or the lmtp files. How can I verify that "mailman aliases" worked? Thanks, ---------- Keith On Wed, Jul 3, 2024 at 2:52 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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 keith1christian(a)gmail.com

1 year, 3 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Shashikanth Komandoor

Thank you Mark for your response. I understood that gunicorn is a front end that is used like web server like nginx. But I don't think I am using it instead I am using the httpd to redirect requests to postorius. And I am starting the mailman-suite with the command "python manage.py runserver 0.0.0.0:8000 --insecure &". Hope this does not use gunicorn (which of course I don't know what it is until now). Please correct me if any point I am mentioning is wrong. So, in this case, do you think configuring gunicorn as below would work: *calling gunicorn.cfg in mailman.cfg as below * *[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* *and content of gunicorn.cfg as below* *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.* *workers = 4graceful_timeout = 90* Also what is the difference between timeout and graceful_timeout ? Please help me if I can increase the management better. Any guide is also helpful for me. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 4:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:21 AM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Never mind please I am sending to you only instead of group as I am > > sending you the production content along with the mail. > > > See my other reply. > > > > I have configured the workers count as 4 and timeout as 900 in > > mailman.cfg under [webservice]. This is FYI. > > You can't configure Mailman's REST gunicorn workers directly in the > [webservice] section of mailman.cfg. The only thing you can configure > there is: > > configuration: /path/to/gunicorn.cfg > > That file, which is separate from your web server gunicorn.cfg, is where > you put things like > > [gunicorn] > timeout = 900 > > It also will not work to put a gunicorn section in mailman.cfg. It must > be in a separate file pointed to by webservice.configuration. > > Increasing the number of workers won't help this issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 3 months

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

by Thomas Ward

On 10/23/23 22:57, Abhilash Raj wrote: > On 10/23/23 20:37, Thomas Ward via Mailman-users wrote: >> I want to add a custom handler that implements customized thread IDs >> in the system. I already have the DB logic worked out, but the >> documentation for plugins is NOT clear on how to define a handler in >> a plugin, nor does the example plugin in the documentation on Gitlab >> have any custom handlers. >> >> I'm looking to add a custom handler so that the private pipeline for >> threaded-subject-list can use thread-subject (the custom handler) >> instead of subject-prefix (builtin). > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/plugins/testin… > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… > > > These are two places you can find docs for an example plugin that > ships with Mailman's code. Adding a new "component", like a Handler, > works very similar to the "rules" in the example shown above. Yeah these're helpful, but the problem I was running into was file naming schema - I was not aware it's always PLUGIN/COMPONENT/COMPONENT.py in the naming, which it was not entirely clear about. It makes sense now that I look back, but it never hurts to get clarification. > > You will probably need a directory tree like: > ``` > example/ > __init__.py > hooks.py > handlers/ > __init__.py > handlers.py > ``` > > Installing the handler is same as per shown in docs using below (do > note that the above example is the name of the package that is > importable): > > > <snip> > > Finally, you can verify that your handler was loaded properly using > something along the lines of: > > ``` > $ mailman shell > 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. > > >>> for each in config.handlers: > ... print(each) > ... > <snip> The only other thing that was missing is how to set up the proper code for a Handler implementation/class, which I used an existing mailman3 core plugin as an example to just run with for testing purposes. There are notes in the example plugin on Gitlab and the documentation that "other components will be added as examples eventually" but that was well over a year ago, so we'll see how that ages. Thanks for the assist! Thomas

2 years

[MM3-users] Re: Missing Base64 encoding from control message reply

by Jana Berger

On 24.09.2023 16:52, Mark Sapiro wrote: > On 9/24/23 07:20, Stephen J. Turnbull wrote: >> >> The only thing I can think of at the moment that might move the >> discussion forward is if Mark knows how to run his test in your Docker >> environment to see if it also produces >> Content-Type: text/plain; charset="US-ASCII" >> Content-Transfer-Encoding: 7bit > > Assuming there is not something like > ``` > [language.en] > charset: utf-8 > ``` > in your mailman.cfg overriding the default us-ascii charset for > English, if you send a message From: yourself to > list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation > is needed to join the list(a)example.com mailing list (replacing list > and example.com with the actual list and domain), you should receive a > response like (some headers removed) > ``` > Subject: The results of your email commands > From: list-bounces(a)example.com > To: mark(a)example.com > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Message-ID: <169556563227.2592.7908020161516725770(a)example.com> > Date: Sun, 24 Sep 2023 07:27:12 -0700 > Precedence: bulk > X-Mailman-Version: 3.3.9b1 > List-Id: A test list <list.example.com> > List-Help: <mailto:list-request@example.com?subject=help> > List-Owner: <mailto:list-owner@example.com> > List-Subscribe: <mailto:list-join@example.com> > List-Unsubscribe: <mailto:list-leave@example.com> > > The results of your email command are provided below. > > - Original message details: > From: Mark Sapiro <mark(a)example.com> > Subject: Re: Your confirmation is needed to join the > list.example.com mailing list. > Date: Sun, 24 Sep 2023 07:27:10 -0700 > Message-ID: <20230924142710.GA23819(a)example.com> > > - Results: > Confirmation token did not match > > - Done. > > ``` > What do you get? > Well, that confirms it. I send the mail from an account at GMX and received the Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 with a properly (!) base64-encoded message body. I then send the mail both from my own mail system (which is also the one being used by Mailman) and got Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding on the message. Lastly, I send the same mail from a GoogleMail account, which also received Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding. ... which means this is almost surely a bug in the MTA of GMX, which will be much, much more difficult and unlikely to be fixed - that is why I had hoped for this to be an issue in/with Mailman ;) Thank you for the pointers and help!

2 years, 1 month

[MM3-users] MM3 Postfix FROM header issue

by Stephen J. Turnbull

eboltz(a)lhtservices.com writes: > When I check the /var/log/mail.log without the > sender_canonical_maps setting enabled, The meaning of "canonical" here is that this is the original and universally acceptable accept-no-substitutes-or-aliases version of the sender's address. If you don't want to see it *literally everywhere* in the header of a message coming out of Postfix, you shouldn't put it in a canonical_map. > then the initial email sender is either rejected because 'Recipient > address rejected: User unknown in virtual alias table' Postfix is configured to relay only local senders to anywhere, or remote senders to local recipients and to relay_domains. This means that the list address doesn't look like a local address (I think it's a bad idea to set myhostname=localhost!) and it isn't in relay_domains (not sure why that might be if the postfix_domains file is present as a compiled .db), so the last try is virtual address (Postfix's way of delivering a possibly remote recipient address to a local recipient). You should use postconf to check that all of the my* variables are set sanely. > or '550-From header sender domain not verified (example.com) > 550-On your sending Verified senders page > 550 verify the sender domain or email to be allowed to send' Not sure where the "example.com" is coming from. If that is being set by the remote smtpd (smtp2go?), and isn't a hard-coded string, something's wrong either with your Postfix configuration or your test email -- that should be the envelope sender domain, which should be your host. The example.com domain actually exists, and I'm sure it doesn't allow you to send email! As others mention, you probably need to have a valid SPF record in your DNS for your host as well. > Here is my main.cf setup Check that both the .txt (produced by Mailman) and .db (produced by /usr/sbin/postmap) files exist for the postfix_lmtp and postfix_domains maps. The function that produces the .txt source is supposed to call postmap to generate the compiled .db database, you shouldn't need to do it by hand. But that's the only Mailman-specific reason for the "not in virtual address table" message. Postfix itself only looks at the .db file, it will not compile or even read the .txt. > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains Make sure there are no Mailman mailing lists in the aliases file. > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases As mentioned, this is not a good idea: > myhostname = localhost Steve

1 year, 10 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/6/24 14:27, Mark Sapiro wrote: > > > > Is this with only one browser? It's a long shot, but clearing browser > > cache might work. > > > Actually, I see the same issues from my browsers, so it's not a browser > caching issue. The only thing left is nginx caching, but, while I know > very little about nginx, I think it doesn't cache by default and I don't > see where in your posted config it's enabled. Perhaps there's more in > your config that you didn't post. > There is nothing I didn't post :) I finally found a way to purge the files cached by Cloudflare. It's in their Dashboard. But not before I had migrated everything to apache2! So now I have all my sites configured in both webservers and I can use whichever I like. Right now I am using apache2, but I am seeing something odd: https://mm3-lists.kictanet.or.ke/archives/ is empty. Is this normal? I am expecting my most active list to appear there or am I overthinking? Like this: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… > If there is a proxy_cache_path directive in your config try > > find /the/proxy/cache/path -type f -delete > > to clear the cache. > There isn't. All the caching mess was coming from Cloudflare proxy servers. If you host your DNS with CF, you will realize they proxy/cache your traffic by default unless you turn that off when creating an A record. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should > contain a css/ directory with 3 files and a js directory containing one > file and a manifest.json file with a template for the `link` directives > referencing those files. > I have seen those files. The js/ directory is easy as its only one file, so your server is > looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create > a symlink in the js/ directory from output.3aaa7705d68a.js to the actual > file. For the css directory, your server is looking for > output.158acc288604.css and output.6dab123e4897.css, and I don't see the > third file in the logs you posted, but if I go to pages in your archive > that I see as unstyled and look at the stylesheet references, they are > to output.44ea6c55e917.css, output.e68c4908b3de.css and > output.9efeb5f3d52b.css so you could just symlink those to the actual > files, it doesn't matter which as all three are loaded on each page I did the symlinks and they helped with nginx, but because I have never had to do that before, I did not like it. That's why I switched to apache2 to see what the effects are and apache2 had/has no problem. Because I have purged the CF cache, I reverted back to nginx and to see from the logs what they are looking for: ``` root@eu:/opt/mailman/mm/static/CACHE/js# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:19:55 [error] 2403078#2403078: *62 open() "/usr/share/nginx/html/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.111, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" ^C root@eu:/opt/mailman/mm/static/CACHE/js# cd ../css/ root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Aug 16 16:55 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 15:55 .. -rw-r--r-- 1 mailman mailman 1209 Mar 21 15:55 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 15:55 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 15:55 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css# ``` So I am left wondering why nginx is prefixing "usr/share/nginx/html" to /static. I then decided to specify a root directive in the vhost pointing to /opt/mailman/mm/static, and I saw nginx prefixing that path to the /static/ again: ``` root@eu:/opt/mailman/mm/static/CACHE/css# cp /dev/null /var/log/nginx/mm3-lists_error.log root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:28:11 [error] 2404382#2404382: *239 open() "/opt/mailman/mm/static/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` Finally, I changed the root directory to /opt/mailman/mm and this time, I see nginx getting the path correctly, but still looking for the same nonexistent file from above and another file: ``` root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:32:25 [error] 2405076#2405076: *38 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:36:17 [error] 2405080#2405080: *841 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 108.162.238.56, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` From the above logs, that IP making requests is not my IP! It's the CF proxies. I then disabled the A record proxying for the site and accessed it from a browser that I havven't used in months, and there was still some errors: The IP showing is my IP. ``` root@eu:/opt/mailman/mm/static/CACHE/css# systemctl restart nginx root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:12 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` And the issue is something about accessing the archives. Not sure if there is something to do for nginx to behave. Apache does not display any single error. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: Mailman Core 3.2.2 is now out

by Abhilash Raj

On Sat, Mar 30, 2019, at 1:11 PM, Danil Smirnov wrote: > Hi Abhilash, > > Docker builds are failing for the last few days so we don't have this > update in the images: > https://circleci.com/gh/maxking/docker-mailman/tree/master > > Could you look at the issue please? Yes, thanks for letting me know. I am aware of the failing builds, but I am having some weird issues getting uwsgi to start off with recent releases and I don't want to pin versions, so I have been trying to dig into the reason why it doesn't boot up with new releases. And then my local docker has been misbehaving a whole lot too, but I am on it whenever I can :) > > Best regards, > Danil Smirnov > > вс, 24 мар. 2019 г. в 07:59, Abhilash Raj <maxking(a)asynchronous.in>: > > > Hello Everyone, > > > > Mailman Core 3.2.2 is released and available on PyPI[1]. > > > > This is a regular bugfix release and I had to do that to fix a version > > constraint > > which pulled in a pre-release of a dependency (falcon) when installed via > > pip > > and caused the default install to break. > > > > There are few other changes included in this release, including a big > > refactor > > of error reporting in Core's REST API. All the error responses are now > > correctly > > formatted as JSON with more information about the error. For example, > > invalid > > inputs for Enum data types return the valid options. Other error message > > are > > now generated from the input validtor and will be more informative. > > > > REST API also accepts input as JSON formatted body, alongside the > > x-www-form-urlencoded. > > > > A full list of changes are available here: > > > > > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 > > > > This release supports Python 3.5-3.7. > > > > Thanks very much to all the contributors involved in this release. > > > > > > [1]: https://pypi.org/project/mailman/ > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > 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/ > > > _______________________________________________ > 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)

6 years, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Hi Mark, Thank you Mark and Phil for your help. It seems I got stuck! 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" 2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size 3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, > you can set max_message_size in your list configuration. It defaults > to 40; units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 1 month

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

by Andrew Hodgson

Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. 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. 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' Thanks. Andrew. _______________________________________________ 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 andrew(a)hodgson.io

2 years, 1 month

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Andrew Hodder

Well, that can't be true, I'm running DEBUG = False and Django is certainly trying to provide static files (as you'll see below): I found the issue in the nginx logs (it's connecting to both postorius and hyperkitty via uwsgi), it appears when I'm only viewing Hyperkitty's pages, I'm getting these type of errors (some changes inserted to hide my server details): 2017/11/01 19:22:04 [error] 64082#0: *75 open() "/opt/mailman/postorius/ example_project/static/CACHE/js/4ce1260ef558.js" failed (2: No such file or directory), client: 10.10.44.29, server: blah.blah.blah, request: "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1", host: "blah.blah.blah", referrer: "https://blah.blah.blah/hyperkitty/hyperkitty/list/ mailinglist(a)domain.com/2017/10/" So it appears Hyperkitty is attempting to load static files from postorius's side instead of it's own (I have postorius running under https://domain.tld and hyperkitty running under https://domain.tld/hyperkitty/ via nginx). I checked and confirmed the variables in settings.py: STATIC_ROOT = os.path.join(BASE_DIR, 'static') STATIC_URL = '/hyperkitty/static/' STATICFILES_DIRS = ('/opt/mailman/hyperkitty/example_project/static/') And for good measure, here's the nginx config: ------------------------------ server { listen 80; server_name DOMAIN.TLD; #Redirect to SSL if ($scheme = http) { return 301 https://$server_name$request_uri; } } server { listen 443 ssl http2 default_server; listen [::]:443 ssl http2 default_server; server_name DOMAIN.TLD; ssl_certificate "/etc/pki/nginx/DOMAIN.TLD.crt"; ssl_certificate_key "/etc/pki/nginx/private/DOMAIN.TLD.key"; ssl_session_cache shared:SSL:1m; ssl_session_timeout 10m; ssl_ciphers HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; location / { include uwsgi_params; uwsgi_pass unix:/opt/mailman/postorius.sock; } location ~ /hyperkitty(?<path_info>/.*|$) { include uwsgi_params; uwsgi_pass unix:/opt/mailman/hyperkitty.sock; uwsgi_param PATH_INFO $path_info; uwsgi_param SCRIPT_NAME /hyperkitty; } #Make nginx aware of postorius static location /static/ { alias /opt/mailman/postorius/example_project/static/; } #for hyperkitty static location /hyperkitty/static/ { alias /opt/mailman/hyperkitty/example_project/static/; } error_page 404 /404.html; location = /40x.html { } error_page 500 502 503 504 /50x.html; location = /50x.html { } } Any thoughts would be appreciated, I'm getting stumped on this one. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Fri, Oct 27, 2017 at 11:01 AM, Simon Hanna <simon(a)hannaweb.eu> wrote: > > On 10/27/2017 04:58 PM, Andrew Hodder wrote: > >> Sure thing: >> >> https://imgur.com/a/EXv3B >> >> Looks like your stylesheets aren't loaded. > > if you are running in production (with DEBUG=False) django won't serve > static files > You need to configure your webserver to do that. > You need to make sure to load all the static files using > `python manage.py collectstatic` > to gather everything and put them in one directory that can then be served > by your webserver > > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

[MM3-users] Re: Monthly job failure

by Abhilash Raj

On Wed, Jun 26, 2019, at 2:46 AM, andrew.bernard(a)gmail.com wrote: > Hi Mark. Indeed, I am confused. I am not yet familiar with Hyperkiity > internals and code, and I must say it is currently like fog to me. :-) > > Indeed, rebuild_mailinglist_cache_for_month made me think this was a > monthly job. > > I had made some lists and deleted them shortly thereafter. I managed to > add some lines likes raise Exception(locals()) in some of the code, > which revealed that a deleted list was being referred to. I have no > idea how to purge this. I looked everywhere in every table in the > database to find references to the deleted table, to no avail. I > deleted all the queued, jobs in Django, to no avail. I rebooted three > times to no avail (highly unscientific), And now, for no obvious > reason, the error has stopped appearing. it definitely did not stop > after deleting Django queued jobs - although perhaps something takes > time to propagate, or there is something stuck cached in RAM? > > It's nice that it stopped but I feel a bit uncomfortable that creating > a list and deleting it a couple of hours later can cause the log to > fill up every minute with these tracebacks. The exception raised in the > code simply says <MailingList matching query does not exist>. It would > be great if the error could name the list. I think that would be > helpful. It would make it clearer to people what is happening at least, > a lot faster. Python tracebacks don't show the values of local > variables, unfortunately. The delete functionality isn't completely implemented yet and part of the problem lies in the way MailingList, Thread and Email objects are created in Hyperkitty. What you need to know is that once a MailingList has been created, several (routine and event based) tasks are added up in a queue. If at the time those tasks are ready to be executed, the mailinglist has gone away, it prints those errors. IMO, it is mostly harmless, but I can see so much of errors in logs would be worrisome to users. Right now, errors are logged unconditionally, but it is possible to filter them to skip `MailingList does not exist errors` altogether. Ofcourse, that is not the ideal solution, but I think it should at least stop the exceptions from being logged when us or the user can't do anything about it. > > Andrew > _______________________________________________ > 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)

6 years, 4 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Please help me understand what steps are missing and I will try to > >> provide the information. > > > > > > Okay. > > > > At the installation stage, you say the following: > > "I already had some things set up in /opt/mailman including a git > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > postorius projects. On the third server I have added mailman-suite > > because I use the settings.py from that project as the basis for mine." > > > > Please assume that the reader is a newbie to python3 virtualenv and give > the > > details of the commands they need to execute to (a) clone all the > projects > > needed > > and (b) create the virtualenv. > > > > The next steps are: > > mkdir /opt/mailman/mm > > > > Then you say "I then created a /opt/mailman/mm directory and within that > a > > Python 3.6 virtualenv" > > What happens here is something that needs clarification, because you are > > specific about "python3.6". > > I have googled and realized that one has to be specific about the python > > version they want to use in their virtualenv > > as shown here -> > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > exact command to execute to create the /opt/mailman/mm/venv > > exact command to execute to activate virtualenv > > > I have added a comment to the page which I hope gives you what you want. > > I also added a section on templates instead of referring to a prior > version of the page. > That makes it better. However, as a newbie, something is not yet clear: "When active in a particular shell, it can be deactivated with the command deactivate or by exiting that shell." HI am trying to understand the effect of detaching from a venv. I am assuming that a virtualenv is a container that is supposed to be always active for the services within to be accessible. Is that right? So, how do I ensure it's always running/up, or that does not matter as the scripts which run the services will always refer to the files? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 9 months

[MM3-users] Re: Deliverability and Spam Filtering

by Abhilash Raj

On Thu, Jan 30, 2020, at 8:44 AM, tom(a)gather.coop wrote: > Hi folks! First time poster, long time Mailman user. > > I am setting up a new Mailman 3 instance, and am super excited about > the REST API. I plan to use it to enable tight integration with a > separate web app that I maintain. > > As I am setting up the mail server, I am wondering about two related > things: deliverability (for outgoing mail) and spam filtering (for > incoming mail). > > What solutions have folks used for these? I know it is generally common > now to outsource this critical task to a cloud provider like Mailgun or > etc. Have folks needed this or is running ones own incoming and > outgoing mail not a big deal? So many horror stories out there... > > As far as Mailgun goes, I think it should be straightforward to > configure it for outgoing mail, but I'm not sure how I'd use it for > incoming. Mailgun can forward mail via HTTP or to another email > address. Neither I think would work out of the box. It would be great > if there were a REST API endpoint for incoming mail, but I don't think > such a thing exists, right? Perhaps I could add one? There does exist a way to insert messages into Mailman via REST API, if you want to do that. It is done via Queue API, which exposes the internal store where messages sit after they are received from LMTP before they are processed. You can just inject the message in "IN" queue and it should be processed like a regular incoming message. https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/queues.html Although, it seems to only accept string representation of Email, which may not be ideal for your use case. It might be some work to make it work for raw bytes. > > Another thought I had was that I could write a simple HTTP server that > receives mail from Mailgun and forwards it to Mailman via LMTP. But it > seems simpler to go right to Mailman's core API given that one exist > already. > > Or am I thinking about this all wrong? Are there other more suitable > services out there? I looked for cloud MTA providers but didn't turn up > much except for in the large enterprise space, which I'm sure I can't > afford. > > Thanks for any thoughts! > _______________________________________________ > 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, 9 months

[MM3-users] Re: Mailman backend maintenance task

by Abhilash Raj

> On Aug 24, 2021, at 11:22 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Eugenio Jordan (external) writes: > >> The idea we were considering was more or less stopping all of the >> components, then starting up only PostGRESQL, and then performing each >> one of the mentioned tasks. > > In that case, your Mailman installation will basically be down (no web > presence, no deliveries) for the duration of the database maintenance. > >> You mention that regardless the connectivity that >> Mailman's core processes might have with the database, the emails will >> be received by and queued until the connection is back again and they >> can be delivered to the distribution lists' members. Could you please >> confirm whether this task would be actually delegated to Postfix (or >> any MTA integrated with Mailman)? > > If Mailman core is running, it will accept the mail and store it in > its own queue. If not, the MTA will store it in its deferred queue > until Mailman comes back up. > > The big problem with delegating this to the MTA is that after two days > the MTA probably won't retry for whole days, but if you do an MTA > queue flush, it will probably stop other mail delivery for quite a > while, since it will be occupied with processing the Mailman backlog. > > The way Mailman works is that there is a master process, which manages > a suite of runners. Each runner is responsible for a particular > stage. The LMTP runner does nothing except accept messages from the > MTA, and store each one in a file for the next runner in the chain. Although, looking at the code[1], it seems like LMTP runner will actually try to verify that the incoming email in destined to a valid email address before it will accept the email. [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… So, if the database isn’t reachable, I think LMTP runner will start rejecting emails from MTA. This is perhaps handling the situation where the transport maps are out-of-date and Mailman receives an email from MTA for a list that has been deleted. While I haven’t tested this situation, I don’t think it would work. So far I am seeing that holding emails off at MTA level and letting it retry after the database maintenance has been complete might be the only thing that works if the entire Postgresql instance has to be brought down. If MTA will retry continuously for 2 days, would that not be enough time to complete the migration and bring the database back up? -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: problem with postorius initial setup

by Abhilash Raj

-- thanks, Abhilash Raj (maxking) > On Mar 16, 2021, at 11:35 AM, John Covici <covici(a)ccs.covici.com> wrote: > > On Tue, 16 Mar 2021 12:14:36 -0400, > Stephen J. Turnbull wrote: >> >> John Covici writes: >> >>> Hi. I am trying to setup postorius, but I have run into a problem. I >>> am using the example project, except I am using postgresql instead of >>> sqlite3. I ran python manage.py migrate which was successful. >>> >>> On running the development server I get: >>> Exception in thread django-main-thread: >>> Traceback (most recent call last): >>> File >>> "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", >>> line 20, in import_string >>> return getattr(module, class_name) >>> AttributeError: module 'postorius.middleware' has no attribute >>> 'APICountingMiddleware' >> >> This appears to be another version mismatch. The >> APICountingMiddleware appears to be a debugging or development >> instrumentation tool. It was added on 2021-02-28, so it's very >> recent. Somehow your Postorius settings.py is newer than your >> Postorius middleware.py. I would guess you have checked out or pip'ed >> a very recent version of Postorius but the example_project is picking >> up an older version, possibly from the Gentoo package. Why that could >> happen depends on whether you've set up a venv for the up-to-date >> Postorius, whether it's active, and so on. > > I think I know what is happening, but not how to fix. The > example_project which the docs told me to get is from the postorius > git which is, of course, recent, whereas the postorius I have from the > gentoo package is 1.3.3, which is not that old, but maybe not up to > the git version. Should I be using the git version? You want to follow this guide[1] for installing from pip. It covers both Postorius and Hyperkitty. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… I am assuming you saw it in this doc [2] to use the example_project. That is very specific to development installations. I will update the document to make it clearer and point to [1] for any production setup. [2]: https://docs.mailman3.org/projects/postorius/en/latest/setup.html#setup-you… > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.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/

4 years, 7 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/22/22 16:03, Odhiambo Washington wrote: >> > >> > There is just one more thing - I have this in settings.py: >> > LOGGING['handlers']['file']['filename'] = >> > '/opt/mailman/mm/var/logs/mailmanweb.log' >> >> >> And what are LOGGING['handlers']['file']['level'], >> LOGGING['handlers']['file']['class'] and >> LOGGING['handlers']['file']['formatter'] >> > > Those are left as defaults in my setup.py. > > >> > However, the referenced file is ever empty. At what point is it >> supposed to >> > record anything? >> >> What is logged depends on `level` but even with `DEBUG` not much routine >> stuff is logged. See >> https://docs.djangoproject.com/en/3.2/topics/logging/ > > > I will read that and see if I get to pick up something. > > And now I am having a problem with mod_wsgi. > First, the URL displayed when I load the page looks bogus to me. > While I expect the URL to be > https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an > extra /mailman3! > > So I have; > 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, > or appears to. > 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, > or appears to. > 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or > appears to > 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or > appears to > 5. > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… > - This throws an exception error when I click "Manage Subscription". > > -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ > > And while I do not quite understand the error itself, there is also one > particular line that I also saw that has left me baffled: > [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client > 197.232.81.246:13865] AH00128: File does not exist: > /usr/local/www/apache24/data/archives/list/ > kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, > refe > rer: > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke > > I also need to add the fact that at the point where I am clicking "Manage Subscription", the URL has changed to https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… (just a single /mailman3). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 12:04 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 21/4/23 a las 10:37, Odhiambo Washington escribió: > > > > > > On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > > > > I'm having troubles with Django and cannot access to web admin. > > > > I need to unhold a message while figures out what is happening. > > > > Searching the mailman cli help commands didn't help me. > > > > Anyone who knows how to unhold a message, please? > > > > > > TBH, I find it a lot easier to fix the web UI than mess with the > > python shell :-) > > > > While you wait for @Mark Sapiro <mailto:mark@msapiro.net> to save you, > > you can be reading the following: > > > > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Thanks: it seems the place to do it (I didn't find it) > > I'm fighting the web UI problem. It seems that something in wsgi has > changed and is no more compatible with my version of things. Error log > from apache shows: > > mod_wsgi (pid=30632): Failed to exec Python script file > '/usr/local/mailman3/wsgi.py'. > mod_wsgi (pid=30632): Exception occurred processing WSGI script > '/usr/local/mailman3/wsgi.py'. > Traceback (most recent call last): > File "/usr/local/mailman3/wsgi.py", line 34, in <module> > from django.core.wsgi import get_wsgi_application > File "/usr/local/lib/python3.9/site-packages/django/core/wsgi.py", line > 2, in <module> > from django.core.handlers.wsgi import WSGIHandler > File > "/usr/local/lib/python3.9/site-packages/django/core/handlers/wsgi.py", > line 3, in <module> > from django.conf import settings > File "/usr/local/lib/python3.9/site-packages/django/conf/__init__.py", > line 19, in <module> > from django.utils.deprecation import RemovedInDjango50Warning, > RemovedInDjango51Warning > File > "/usr/local/lib/python3.9/site-packages/django/utils/deprecation.py", > line 4, in <module> > from asgiref.sync import iscoroutinefunction, markcoroutinefunction, > sync_to_async > ImportError: cannot import name 'iscoroutinefunction' from > 'asgiref.sync' (/usr/local/lib/python3.9/site-packages/asgiref/sync.py) > If you did some system updates then that is where you need to check. Obviously, something did update, leading to the breakage. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 6 months

[MM3-users] Re: Mailman 3 install questions: HAYSTACK_CONNECTIONS

by Odhiambo Washington

On Sun, Jul 7, 2024 at 6:24 AM <heller(a)deepsoft.com> wrote: > I am using the debian 12 repo versions of mailman3, django, posterious, > hyperkitty, and xapian: > > sharky5% dpkg-query -l > python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} > mailman3\* | grep '^ii' > ii mailman3 3.3.8-2~deb12u2 all Mailing list > management system > ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list > management system documentation > ii mailman3-web 0+20200530-2.1 all Django > project integrating Mailman3 Postorius and HyperKitty > ii python3-django 3:3.2.19-1+deb12u1 all High-level > Python web development framework > ii python3-django-hyperkitty 1.3.7-1 all Web user > interface to access GNU Mailman3 archives > ii python3-django-mailman3 1.3.9-1 all Django > library to help interaction with Mailman3 (Python 3 version) > ii python3-django-postorius 1.3.8-3 all Web user > interface to access GNU Mailman3 > ii python3-xapian 1.4.22-1 amd64 Xapian > search engine interface for Python3 > > Before adding the HAYSTACK_CONNECTIONS options, I have this: > > sharky5% sudo mailman-web haystack_info --no-color --skip-checks > Number of handled 1 index(es). > - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at > 0x7fd0de1b0470> > > When I add this to /etc/mailman3/maymail_web.py (adapted from the section > titled: > "Setting up Fulltext search (xapian)" on > https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian > > HAYSTACK_CONNECTIONS = { > > 'default': { > > 'PATH': "/var/lib/mailman3/web/fulltext_index", > > 'ENGINE': 'xapian_backend.XapianEngine' > > }, > > } > > I get: > > File "/usr/lib/python3.11/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "<frozen importlib._bootstrap>", line 1206, in _gcd_import > File "<frozen importlib._bootstrap>", line 1178, in _find_and_load > File "<frozen importlib._bootstrap>", line 1142, in > _find_and_load_unlocked > ModuleNotFoundError: No module named 'xapian_backend' > > So, do I use Xapian or not? Is something missing somewhere? Is this a > documentation bug or something else? > It cannot be a documentation bug since you are NOT using/following the documentation! The message is good enough. Where is your xapian_backend,py?? ``` wash@gw:~$ locate xapian_backend.py /opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py wash@gw:~$ ``` I hope the above gives you a clue as to where it should be found. However, since you aren't following the documentation I am familiar with, and I am not a Python expert, my end-of-thinking capacity (/etc) is here :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Re: Migrating to Mailman3

by Dennis Putnam

On 10/19/2025 2:42 AM, Stephen J. Turnbull wrote: > Dennis Putnam via Mailman-users writes: > > > Thanks for the info. I thought I had followed everything but I an > > unable to start mailman3 because all the expected directories in > > /var are missing. What steps did I miss? > > If you are setting up according to the virtual environment > instructions, Mailman shouldn't be looking for anything in /var that > you didn't explicitly configure to be there. > > With the venv active, try running just "mailman info". If that > succeeds and reports something other than /etc/mailman3/mailman.cfg, > then check the file it reports for "layout" and "var_dir" settings, > and remove the var_dir hierachy because it's just confusing. Then run > > mailman -C /etc/mailman3/mailman.cfg info > > If that succeeds, try starting Mailman with > > mailman -f -C /etc/mailman3/mailman.cfg start > > The "-f" is short for "--force" and it just cleans up any stale lock > files that might prevent Mailman from starting. (We now recommend > using it in the init script or systemd unit file ExecStart command.) > > If either of those fails, or Mailman starts but "doesn't work", look > in the logs (systemctl status, journalctl -eu, and > $var_dir/logs/mailman.log for error messages, and send those along > with /etc/mailman3/mailman.cfg to us. In the case of "doesn't work", > tell us what you mean by "doesn't work": Mailman doesn't accept mail, > Mailman crashes, Mailman doesn't send mail, etc. > Hi Steve, Thanks again. I think I found the problem. When I created the mailman.cfg file, for some reason everything was commented out. After saving I didn't bother to look at it. My bad. I then went though and uncommented as appropriate however I have one problem. I don't know what to do with this section for MySQL. [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql://mailman:MYPASSWORD@localhost/mailman Just as an FYI here is my full mailman.cfg: # /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here # # This address is the "site owner" address. Certain messages which must be # # delivered to a human, but which can't be delivered to a list owner (e.g. a # # bounce from a list owner), will be sent to this address. It should point to # # a human. site_owner: xxxxxx@ddddddddddd [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql://mailman:MYPASSWORD@localhost/mailman [archiver.prototype] enable: yes # # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1

2 weeks, 2 days

[MM3-users] Daily Cronjob fails

by Stefan Tatschner

Hey hey, I applied a recent Update from Debian Buster, und this night a received an email about a failing cronjob. The traceback can be reproduced using: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) psycopg2.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 35, in execute sync_with_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 131, in sync_with_mailman mlist.update_from_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 192, in update_from_mailman self.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 808, in save force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 838, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 905, in _save_table forced_update) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 955, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 667, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1204, in execute_sql cursor = super(SQLUpdateCompiler, self).execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 899, in execute_sql raise original_exception File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 889, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). END TRACEBACK Appearently there is something wrong with the database. Is there anything what I can do about this? Running the migrations doesn't help: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py migrate 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. Thanks! Stefan

6 years, 8 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

The only way I've gotten it to work so far is by using the FQN. I can switch back to 127.0.0.1 but that wasn't working. Here's the configuration I have. incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: 127.0.0.1 smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 and the end result: https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 I tried setting the smtp_host to 127.0.0.1 and list.domain.org both result in the same issue. ie: Here's the combinations I've tried: smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 #fail smtp_host: lists.domain.org lmtp_host: 127.0.0.1 #fail Finally I even tried the exact copy from the documentation: incoming: mailman.mta.postfix.LMTPoutgoing: mailman.mta.deliver.deliverlmtp_host: 127.0.0.1lmtp_port: 8024smtp_host: localhostsmtp_port: 25configuration: python:mailman.config.postfix ## Fail. smtp_host: lists.domain.org lmtp_host: lists.domain.org # success. The error I get if I don't open port 8024 is below and in the gist i linked earlier. May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: Connection refused) The only way I've gotten it to work so far is by binding both the smtp_host and lmtp_host to be lists.domain.org and opening up port 8024. I'd rather not have that port open but I'm open to suggestions on what else to try. Locally on the server: PING lists.domain.org (198.199.98.177) 56(84) bytes of data. 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=3 ttl=64 time=0.069 ms -- Samir Faci On Mon, May 4, 2020 at 9:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 10:04 PM, Samir Faci wrote: > > > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead > of > > # localhost for Postfix integration, because Postfix only consults DNS > > # (e.g. not /etc/hosts). > > lmtp_host: lists.domain.org > > lmtp_port: 8024 > > Why, in spite of the comment, do you have > > lmtp_host: lists.domain.org > > and not > > lmtp_host: 127.0.0.1 > > Note that > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > are the defaults. > > > > So, now it's finally working but here's a question. Does 8024 need to be > > publically accessible from the outside? > > > No. Port 8024 is only for LMTP delivery from Postfix to Mailman. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 6 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > But whatever is listening on port 8001 is apparently not Mailman's rest > server. What does > ps -fww 14080 > or whatever PID is currently listening on port 8001 show. UID PID PPID C STIME TTY STAT TIME CMD list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 > > OK. > Perhaps instead you should have > uid: list > gid: list > in your uwsgi configuration if you don't already. Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. What the logs say: *** Starting uWSGI 2.0.18-debian (64bit) on [Thu Aug 12 08:46:37 2021] *** compiled with version: 8.2.0 on 10 February 2019 02:42:46 os: Linux-4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) nodename: mail machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 2 current working directory: / detected binary path: /usr/bin/uwsgi-core chdir() to /usr/share/mailman3-web your processes number limit is 3831 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) error removing unix socket, unlink(): Permission denied [core/socket.c line 198] bind(): Address already in use [core/socket.c line 230] Not sure if that means the two directories need to be owned by list, currently they are owned by root > > I'm not familiar enough with this form of ProxyPass using sockets to > understand what the localhost:8001 does in this context, but uwsgi > should not be doing anything with port 8001. In a configuration using > TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API > server listens. uwsgi should receive connects in your case via the unix > socket and then pass them to Django via the application in wsgi.py > Also, you may want other paths proxied to uwsgi, namely at least some of > hyperkitty, postorius, archives, accounts, admin and user-profile. Ok, I removed that port again, now it's exctly like in the automatically generated config file. And you mean like <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> > > These should be 'list', not 'www-data'. That's your permissions issue on > settings.py

4 years, 2 months

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

Well, I understand that it might take a while, but the process is running for over 200h now, I doubt it can really take _that_ long if everything is working properly. Especially because the rebuild_index command is only taking a few hours at most, doesn't that essentially do the same? We have ~700k messages in ~300 mailing lists in case that helps you estimate how long it could take. I can take a look at alternative backends, though. On 5/7/19 4:32 PM, Abhilash Raj wrote: > On Sat, Apr 27, 2019, at 6:22 PM, Alain Kohli wrote: >> I'm running a custom image which is based on an older version of the one >> here: https://github.com/maxking/docker-mailman. I attached it below. >> But I separated postorius and hyperkitty, so hyperkitty is running in >> its own container. I'm deploying the image with a plain 'docker run' >> behind nginx. I made fulltext_index persistent now, but it didn't get >> populated with anything yet. I don't really have an error traceback >> because there is never an error thrown. The only thing with some content >> is uwsgi-error.log, which you can find below. I'm also still getting the >> "A string literal cannot contain NUL (0x00) characters." messages. I >> also noticed that it takes incredibly long for the webinterface to load >> (several minutes) even though there doesn't seem to be any process >> consuming notable resources apart from the minutely job. >> >> Funnily enough, I have the exact same image deployed on a second server >> as well for testing. On that one everything works fine. The only >> difference is that on the problematic one I have a lot more mailing >> lists/archives and that I imported them from mailman2. Could something >> have gone wrong during the import? I used the regular hyperkitty_import >> command. > Yes, this is because `whoosh`, the library set by default to run fulltext > indexing is a pure python implementation and quite slow in busy lists. > > We do support more backends though, see [1] for a list of all the supported > search backends. Something like Xapian(C++) or Elasticsearch/Solr(Java) > should be much better in terms of performance. > > [1]: https://django-haystack.readthedocs.io/en/master/backend_support.html > >> uwsgi-error.log: >> >> *** Starting uWSGI 2.0.18 (64bit) on [Sat Apr 27 22:50:17 2019] *** >> compiled with version: 6.4.0 on 27 April 2019 22:48:42 >> os: Linux-4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) >> nodename: hyperkitty.docker >> machine: x86_64 >> clock source: unix >> detected number of CPU cores: 4 >> current working directory: /home/hyperkitty >> detected binary path: /usr/local/bin/uwsgi >> !!! no internal routing support, rebuild with pcre support !!! >> setgid() to 82 >> setuid() to 82 >> chdir() to /home/hyperkitty >> your memory page size is 4096 bytes >> detected max file descriptor number: 1048576 >> lock engine: pthread robust mutexes >> thunder lock: disabled (you can enable it with --thunder-lock) >> uwsgi socket 0 bound to TCP address 0.0.0.0:8081 fd 8 >> uwsgi socket 1 bound to TCP address 0.0.0.0:8080 fd 9 >> Python version: 3.6.8 (default, Jan 30 2019, 23:54:38) [GCC 6.4.0] >> Python main interpreter initialized at 0x55dfaa41c980 >> python threads support enabled >> your server socket listen backlog is limited to 100 connections >> your mercy for graceful operations on workers is 60 seconds >> [uwsgi-cron] command "./manage.py runjobs minutely" registered as >> cron task >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" registered >> as cron task >> [uwsgi-cron] command "./manage.py runjobs hourly" registered as cron >> task >> [uwsgi-cron] command "./manage.py runjobs daily" registered as cron task >> [uwsgi-cron] command "./manage.py runjobs monthly" registered as >> cron task >> [uwsgi-cron] command "./manage.py runjobs weekly" registered as cron >> task >> [uwsgi-cron] command "./manage.py runjobs yearly" registered as cron >> task >> mapped 208576 bytes (203 KB) for 4 cores >> *** Operational MODE: threaded *** >> WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter >> 0x55dfaa41c980 pid: 1 (default app) >> *** uWSGI is running in multiple interpreter mode *** >> spawned uWSGI master process (pid: 1) >> spawned uWSGI worker 1 (pid: 40, cores: 4) >> Sat Apr 27 22:50:18 2019 - [uwsgi-cron] running "./manage.py runjobs >> minutely" (pid 45) >> [uwsgi-daemons] spawning "./manage.py qcluster" (uid: 82 gid: 82) >> 22:50:21 [Q] INFO Q Cluster-47 starting. >> 22:50:21 [Q] INFO Process-1:1 ready for work at 59 >> 22:50:21 [Q] INFO Process-1:2 ready for work at 60 >> 22:50:21 [Q] INFO Process-1:3 ready for work at 61 >> 22:50:21 [Q] INFO Process-1:4 ready for work at 62 >> 22:50:21 [Q] INFO Process-1:5 monitoring at 63 >> 22:50:21 [Q] INFO Process-1 guarding cluster at 58 >> 22:50:21 [Q] INFO Process-1:6 pushing tasks at 64 >> 22:50:21 [Q] INFO Q Cluster-47 running. >> 22:59:31 [Q] INFO Enqueued 3403 >> 22:59:31 [Q] INFO Process-1:1 processing [update_from_mailman] >> 22:59:33 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 73) >> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> hourly" (pid 74) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 73 exited after 64 second(s) >> 23:01:28 [Q] INFO Enqueued 3404 >> 23:01:29 [Q] INFO Process-1:2 processing >> [rebuild_mailinglist_cache_recent] >> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >> 74 exited after 91 second(s) >> Sat Apr 27 23:01:36 2019 - uwsgi_response_write_body_do(): Broken >> pipe [core/writer.c line 341] during GET / (212.203.58.154) >> OSError: write error >> 23:01:36 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >> Sat Apr 27 23:15:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 88) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 88 exited after 4 second(s) >> 23:28:24 [Q] INFO Enqueued 3405 >> 23:28:24 [Q] INFO Process-1:3 processing [update_from_mailman] >> 23:28:25 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:30:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 96) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 96 exited after 4 second(s) >> 23:44:40 [Q] INFO Enqueued 3406 >> 23:44:40 [Q] INFO Process-1:4 processing [update_from_mailman] >> 23:44:41 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:45:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 104) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 104 exited after 4 second(s) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 113) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> hourly" (pid 114) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> daily" (pid 115) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> weekly" (pid 116) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 113 exited after 55 second(s) >> [uwsgi-cron] command "./manage.py runjobs weekly" running with pid >> 116 exited after 55 second(s) >> 00:01:36 [Q] INFO Enqueued 3407 >> 00:01:36 [Q] INFO Process-1:1 processing >> [rebuild_mailinglist_cache_recent] >> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >> 114 exited after 99 second(s) >> 00:01:50 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >> 00:04:52 [Q] INFO Enqueued 3408 >> 00:04:52 [Q] INFO Process-1:2 processing [update_from_mailman] >> 00:04:54 [Q] INFO Processed [update_from_mailman] >> >> Dockerfile: >> >> FROM python:3.6-alpine3.7 # Add startup script to container COPY >> assets/docker-entrypoint.sh /usr/local/bin/ # Install packages and >> dependencies for hyperkitty and add user for executing apps. # It's >> important that the user has the UID/GID 82 so nginx can access the >> files. RUN set -ex \&& apk add --no-cache --virtual .build-deps gcc >> libc-dev linux-headers git \postgresql-dev \&& apk add --no-cache >> --virtual .mailman-rundeps bash sassc mailcap \postgresql-client >> curl \&& pip install -U django==2.2 \&& pip install >> git+https://gitlab.com/eestec/mailmanclient >> >> \git+https://gitlab.com/mailman/hyperkitty@c9fa4d4bfc295438d3e01cd93090064d004cf44d >> \git+https://gitlab.com/eestec/django-mailman3 \whoosh \uwsgi >> \psycopg2 \dj-database-url \typing \&& apk del .build-deps \&& >> addgroup -S -g 82 hyperkitty \&& adduser -S -u 82 -G hyperkitty >> hyperkitty \&& chmod u+x /usr/local/bin/docker-entrypoint.sh# Add >> needed files for uwsgi server + settings for django COPY >> assets/__init__.py /home/hyperkittyCOPY assets/manage.py >> /home/hyperkittyCOPY assets/urls.py /home/hyperkittyCOPY >> assets/wsgi.py /home/hyperkittyCOPY assets/uwsgi.ini >> /home/hyperkittyCOPY assets/settings.py /home/hyperkitty# Change >> ownership for uwsgi+django files and set execution rights for >> management script RUN chown -R hyperkitty /home/hyperkitty && chmod >> u+x /home/hyperkitty/manage.py# Make sure we are in the correct >> working dir WORKDIR /home/hyperkittyEXPOSE 8080 8081# Use stop >> signal for uwsgi server STOPSIGNAL SIGINTENTRYPOINT >> ["docker-entrypoint.sh"]CMD ["uwsgi", "--ini", >> "/home/hyperkitty/uwsgi.ini"] >> >> On 4/27/19 7:58 PM, Abhilash Raj wrote: >>> On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: >>>> I have run "python manage.py rebuild_index" before, doesn't that do >>>> clear_index as well? Apart from that, I run hyperkitty in a docker >>>> container and didn't know fulltext_index should be persistent, so that >>>> got deleted after every version update for sure. >>> Which images are you using and how are you deploying them? >>> >>> You should persist fulltext_index, yes, and possibly logs if you need >>> them for debugging later. >>> >>> Can you paste the entire error traceback? >>> >>>> On 4/26/19 10:18 PM, Mark Sapiro wrote: >>>>> On 4/26/19 11:14 AM, Alain Kohli wrote: >>>>>> I see loads of "A string literal cannot contain NUL (0x00) characters." >>>>>> messages, but I haven't found missing messages in the archives yet. Not >>>>>> sure how that could be related, though. Apart from that I don't see >>>>>> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to >>>>>> run and finish normally. >>>>> Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 >>>>> version? The Haystack/Whoosh search engine databases are not compatible >>>>> between the two and "A string literal cannot contain NUL (0x00) >>>>> characters." is the symptom. >>>>> >>>>> You need to run 'python manage.py clear_index' or just remove all the >>>>> files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in >>>>> your settings file (normally 'fulltext_index' in the same directory that >>>>> contains your settings.py. >>>>> >>>> _______________________________________________ >>>> 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/ >>>> >> _______________________________________________ >> 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/ >>

6 years, 5 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- 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

Search results for query "dO"