Search results for "2021" - Mailman-users

Re: Header Filter madness

by Brian Carpenter

On 1/13/21 3:05 PM, Mark Sapiro wrote: > On 1/12/21 9:57 PM, Mark Sapiro wrote: >> On 1/11/21 6:14 PM, Brian Carpenter wrote: >>> On 1/11/21 8:48 PM, Mark Sapiro wrote: >>>> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >>>> <brian_carpenter(a)emwd.com> wrote: >>>>> I have a client whose header filters seemed to have stop working. No >>>>> matter what I try, it seems none of their header filters are being >>>>> applied. Other lists on the same server that use header filters, are >>>>> working fine. This particular header is the subject header. I can >>>>> duplicate their problem but only with their list. If I create the exact >>>>> same header on a test list using the exact same subject line, the >>>>> header >>>>> filter does its job (moderate). Just not with this one list. >> >> What's in the X-Mailman-Rule-* headers of the post that should be but >> isn't held? >> >> Are there other header filter rules besides the one that doesn't work? > Also, on your test list, did you copy/paste the regexp or retype it. If > the latter, there is possibly trailing whitespace that breaks it. Thanks Mark. I am currently waiting for feedback from my client. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

Re: postfix malformed address with confirm replies

by Mark Sapiro

On 2/26/21 3:34 PM, Stephen Willey Mats Mats wrote: > > I’m getting bounces back from postfix (553 5.1.3 Error: malformed address) for my confirm replies. ... > I’m pretty sure I have all of the mailman settings in postix: > " > # Support the default VERP delimiter. > recipient_delimiter = + Yes, this is the relevant one and is correct. ... >> The mail system >> >> <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: >> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address >> (in reply to RCPT TO command) >> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal >> X-Postfix-Queue-ID: E144B8BC3C5 >> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com >> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) >> >> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >> Action: failed >> Status: 5.1.3 >> Remote-MTA: dns; 172.19.199.2 >> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address I have no idea why Postfix is saying `matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu` is a malformed address, but this is a Postfix issue, not Mailman. Can you successfully post to `matsmats-mm3-test1 @mm3.aca-aws.s.uw.edu` how about a `help` command to `matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Mark Sapiro

On 3/13/21 7:08 PM, John Covici wrote: > On Sat, 13 Mar 2021 16:22:59 -0500, > Abhilash Raj wrote: >> >> My guess is that you updated the database (perhaps, by invoking the mailman >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes >> up and sees a new revision for the database migration added from 3.3.3 but >> can’t find the same migration in its source (because it is 3.3.2). > > That is sort of what happened, except in the opposite direction, it > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > update this alembic_version when I upgrade mailman to a newer version? > That is what I was getting at. Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Postorius no connection to REST API

by Stephen J. Turnbull

Hi, Richard, I don't recall the details, so I could be way off base, but this > [Sun Aug 15 09:19:52.318582 2021] [core:notice] > [pid 19706:tid 140315143705728] > AH00094: Command line: '/usr/sbin/apache2' > [Sun Aug 15 09:19:52.732381 2021] [proxy_http:error] > [pid 19707:tid 140314912167680] (20014) > Internal error (specific information not available): > client 37.201.214.82:9292] AH01102: > error reading status line from remote server 127.0.0.1:8000 indicates that Apache's (?) proxy_http server expects to find something that isn't there running on the same host on port 8000. Since it's not "refused connection" or similar, evidently it's connecting (presumably to Mailman core's REST API) but not getting the "status line" (greeting?) it expects. Now, for a proxy to know what status line to expect, either it's speaking a well-known protocol (such as SMTP or HTTP), or it's part of the same application suite. But Mailman is neither. So I suspect you have your proxy configured to proxy Apache to Mailman instead of the other way round. Or maybe it's proxying from client 37.201.214.82 to Mailman, but it should be proxying from client to Apache. I guess the latter is more plausible, in the former there'd be some kind of triangular relationship among client, Apache, and Mailman, which doesn't fit the model of "proxy". Is either possible? HTH, but if it doesn't ring a bell, say so and we'll try something else. Steve

3 years, 10 months

Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Hi Steve, thank you for your time. Thats it :) Works now. I had to set it in /etc/mailman3/mailman-web.py After first logon, django tries to send a mail to confirm email address. Nov 10 08:44:56 mal02 postfix/qmgr[2893767]: 9255C5E0BE2: from=<postorius(a)lists.mydomain.tld>, size=920, nrcpt=1 (queue active) Nov 10 08:44:56 mal02 postfix/smtpd[879486]: disconnect from localhost[::1] ehlo=2 *starttls=1* mail=1 rcpt=1 data=1 quit=1 commands=7 This now works with STARTTLS. Hoooray :) Am Di., 9. Nov. 2021 um 16:50 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > No matter what i try, mailman still only connects without STARTTLS: > > Earlier you wrote: > > > SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a > STARTTLS command first', 'postorius(a)lists.mydomain.tld') > > Request Method: POST > > Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ > > Django Version: 2.2.12 > > This looks like Django errors, not Postorius (Mailman). So this is > something Django is doing, not Mailman (including Postorius). I'm not > sure why Django is sending email (somebody made a password reset > request seems likely, but I'm not that familiar with Django authn > stuff). Anyway, if it's internal to Django, it would not consult > Mailman's configs. This recent StackOverflow seems relevant: > > > https://stackoverflow.com/questions/60025730/530-5-7-0-must-issue-a-starttl… > > HTH > > Steve > >

3 years, 7 months

Re: Mailman3 Issue with Sending Mail to Yahoo/AOL

by Mark Dadgar

Yes. I have been running a private motorsports community mailing list in the SF Bay Area for ~20 years and the only ISP that consistently does this is anything Yahoo touches. And there’s not much you can do about it, other than continue to follow deliverability best practices. Fortunately, most of the time the email is merely deferred semi-briefly. But it is a gigantic PITA. - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On May 12, 2021, at 8:53 AM, Apollinaris Schöll <aschoell(a)gmail.com> wrote: > > It’s not you. I am managing a neighborhood list too and yahoo flags them for many users as spam. And few times yahoo bounced messages for a day for at least 50% of subscribers. ATT has been even worse. Full bounce of all emails for a week at a time. No problems with any other provider > >> On May 12, 2021, at 8:00 AM, chris--- via Mailman-users <mailman-users(a)mailman3.org> wrote: >> >> That's the trouble ... I'm certain SPF and DKIM are correct. I've ran them thru the checker, and all appears to pass properly. So I'm really at a loss. >> _______________________________________________ >> 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, 1 month

Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/8/21 4:41 AM, Thomas Möhle via Mailman-users wrote: > Hey Mark, > > thanks for your reply!> In what way? Do list posts get delivered? What > works and what doesn't? > > What are the observable symptoms for things that don't work? > Yes, mails are not delivered. You can send a mail to the mailinglist > without getting a bounce, but you will not receive the mail back through > mailman. > In addition to that, I'm unable to edit mailing lists in the web > interface. After clicking on a list, I'll get a 404. > Plus, I noticed that mailman is constantly writing files to > /var/lib/mailman3/queue/out/ but they seem to get deleted right away > again. I'm getting alot of IO there though. So messages are being queued for the outgoing runner and then something is done with them. If there are no errors in mailman.log about this and nothing in the shunt queue, they are being delivered to the MTA. What's in the MTAs logs? > > What do you get for example if you go in a web browser with hyperkitty > > running to > > > > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… > > I get a small gziped json file back. Key is "url", value is a link to a > message. OK. That's correct and it seems that Mailman core can communicate with the HyperKitty API, at least when HyperKitty is running. > > And please don't post secret keys and change the value of api_key: in > > mailman-hyperkitty.cfg and the corresponding value in > > MAILMAN_ARCHIVER_KEY in your Django settings. > I actually tried to redact the logs and config files, but I must have > failed to save my edits on that one file. I'll change it right away. The key was in the mailman-hyperkitty.cfg file you posted and was in multiple entries in mailman-web.log. There is some strangeness in the logs you posted. Mailman.log contains many of these: Aug 07 12:49:55 2021 (2343598) HyperKitty failure on https://mail.example.com/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> (503) and mailman-web log contains many of these [pid: 2343625|app: 0|req: 1/1] 10.133.3.2 () {60 vars in 1350 bytes} [Sat Aug 7 12:49:58 2021] GET /mailman3/hyperkitty/api/mailman/urls?mlist=aussen%40lists.example2.com&msgid=002601d777e2%244c34c540%24e49e4fc0%24%40example2.com&key=g8nOyDVbCNsi18L%2FjgTj%2BWDVKUQ2XeQM => generated 131 bytes in 279 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) which actually seem normal except for the quantity, but the time stamps don't correlate. There's nothing in mailman-web.log for the times of the 'HyperKitty failure' messages in mailman.log. Was the web service even up during those times. -- 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

Re: at the finish line of mailman3 docker, but can't sign in.

by John Covici

OK, thanks a lot -- if anyone here can help with proper config for those, that would be great. I do have a web server, but its apache rather than mginx and I am not sure how to properly translate. Also, doing a separate container for an mta which would just talk to mailman would get around the sendmail situation I have, although there may be a decent way to do that as well. I guess the hard part is to tie the multiple containers together. On Sat, 31 Jul 2021 17:56:15 -0400, Abhilash Raj wrote: > > > > On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote: > > I have a couple of questions about the container, if its OK. > > Sure it is :) > > > > > First, it says to run you create the directory > > /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the > > git clone. What directory should the git clone be in? > > You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones. > > I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too. > > > A couple of more questions -- is there a way to install the web server > > and the mta in the container, this way I could make the whole thing > > be independent of my host configs? > > You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager. > > You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives. > > > > > On Fri, 30 Jul 2021 16:04:48 -0400, > > bob B wrote: > > > > > > is this the info you need for the container version > > > > > > [root@..... docker-mailman]# docker ps > > > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > > > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > > > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > > > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > > > > > > > for smtp host > > > ------------ > > > cat /opt/mailman/web/settings_local.py > > > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > > > ALLOWED_HOSTS = ['*'] > > > DEBUG = True > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > > EMAIL_HOST = 'smtp.example.com' > > > EMAIL_PORT = 25 > > > --------------------------- > > > cat /opt/mailman/core/mailman-extra.cfg > > > # 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_port: 8024 > > > # Postfix server's hostname or IP from mailman-core > > > smtp_host: smtp.example.com > > > 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: my_real_email_is_in_the_file.com > > > __________________________________ > > > > > > My docker most machine /etc/postfix/main.cf has > > > > > > transport_maps = > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > local_recipient_maps = > > > regexp:/opt/mailman/core/var/data/postfix_lmtp > > > relay_domains = > > > regexp:/opt/mailman/core/var/data/postfix_domains > > > > > > > > > # Support the default VERP delimiter. > > > recipient_delimiter = + > > > unknown_local_recipient_reject_code = 550 > > > owner_request_special = no > > > > > > ------------------------------ > > > > > > > > > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > > > > > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > > > _______________________________________________ > > > 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/ > > > > > > > -- > > 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/ > > > > > -- > thanks, > Abhilash Raj (maxking) > -- 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

3 years, 11 months

Re: Ann: Mailman Core 3.3.5 is out

by Odhiambo Washington

@Eggert, I believe you used apt to install and so you have to wait for the package maintainer to avail the upgrades via apt. On Wed, Sep 29, 2021 at 7:48 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would > have > to bypass the Debian installer. Or will there be Debian packages > available? > Same question for Postorius 1.3.6 > > > Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > > Hey Everyone, > > > > I just tagged and uploaded Mailman Core 3.3.5 release. > > > > This release includes both bug fixes and some new features. A full list > of > > changes is available here: > > > > > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS > . > > html#news-3-3-5 > > > > You can install this version using pip: > > > > $ pip install mailman==3.3.5 > > > > The release tarball is available on PyPI as well: > > > > https://pypi.org/project/mailman/3.3.5/#files > > > > Thanks to everyone who made this release possible! > > > > Abhilash > > > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > > wrote: > > > > > > Hey Everyone, > > > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > > > This is identical to 3.3.5b1 in code, the only changes that have been > made > > > are in utility scripts and testing configuration.> > > > You can install this version using: > > > $ pip install --pre mailman==3.3.5rc1 > > > > > > If you want to download a release tarball, you can do so from here: > > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > > > This is the first (and only) planned release candidate for 3.3.5 > release. > > > The stable release is planned for next week. > > > > > > thanks, > > > Abhilash > > > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > > >> Hello Everyone, > > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from > now. > > >> I am planning for a 2 week beta period, after which I'll release the > > >> first RC and then stable a week after. Right now I am not planning to > > >> release a second beta version, but if there are several changes in > Core > > >> in the next week or so, then I might. This release includes a lot of > bug > > >> fixes and some new features. It also includes a security enhancement > > >> that improves the authentication of REST API by adding resistance to > > >> some timing channel attacks. A full list of changes in this version > can > > >> be found here[1]. > > >> [1]: > > >> > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > > >> and now the email templates are updated from the translated messages > in > > >> the .po files that we get from Weblate. Documentation for translators > is > > >> available here[2] if you want to help translate Mailman into your > native > > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > > >> > > >> This is a pre-release version, if you want to test it with your > setup, > you can install it using: > > >> $ pip install --pre mailman==3.3.5b1 > > >> > > >> If you want to download a release tarball, you can do so from here: > > >> https://pypi.org/project/mailman/3.3.5b1/#files > > >> > > >> This release received a lot of contributions from community, which I > am > > >> really happy about! I'd like to thank everyone who made this release > > >> possible!> > > > -- > > > thanks, > > > Abhilash Raj (maxking) > > > > -- > > 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/ > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 9 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Eggert Ehmke

This makes it even stranger. Removing the trailing / did not help in my case, but replacing the mailman3 for mailman in the ProxyPass line did. Would be really nice to solve this problem at the root. Am Montag, 25. Oktober 2021, 18:09:21 CEST schrieb Mark Sapiro: > On 10/25/21 1:45 AM, Stefan Bauer wrote: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U > SXUYZYB5KIXT37APMCOAUZLKBRPARTL/ > > ... > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > Others have found that removing the trailing slash from > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > to make it > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > fixes the issue.

3 years, 8 months

Mailman-users search results for query "2021"