Search results for "Postorius" - Mailman-users

Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 4:05 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > It should be pointing to Exim running on host, so > > > > EMAIL_HOST = 172.19.199.1 > > That fixed the network not found error. Thank you for your help there. > > Now I am back to the verification error: > > "smtplib.SMTPRecipientsRefused: {'brian(a)emwd.com': (550, b'Verification > failed for <postorius(a)host.name.com>\nUnknown user\nSender verify > failed')}" > > I am at a lost on how to get exim to allow mail sent from > postorius(a)host.name.com. Obviously host.name.com is the mm3 domain that > I am using. A quick search says that Exim is trying to verify that `postorius(a)host.name.com` is a real mailbox (which I am assuming it is not), and rejecting the email coming from Postorius. You probably have verify = sender somewhere in your exim.conf, which is causing this. You can either modify the DEFAULT_FROM_EMAIL in your settings_local.py so that it is a real address that Exim can verify, or, you can remove verify = sender from your Exim configuration. 2nd option might not be the best if you want to properly combat spam. Exim experts would be able to help you better with this. > > 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)

6 years, 5 months

Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 12:06 AM, Paul Arenson wrote: > Mark Sapiro wrote: > >> If by "read only" you mean the "Announce only mailing list style" as >> opposed to the "Ordinary discussion mailing list style" the only >> difference is that for the Announce only style the list attribute >> allow_list_posts is False and for the Discussion style, it's True. >> >> This is the setting in Postorius -> Settings -> Alter Messages -> >> Include the list post header an all it does is include or not include >> the List-Post: header in mail from the list. > > Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? allow_list_posts is the name of the attribute in Mailman core. It is exposed in Postorius as "Include the list post header". I.e., they are the same thing. Note however that unless your users are using MUAs to reply by email and their MUAs offer a "reply-list" function for replies to mailing list posts, this setting will make no difference. It is the presence of the List-Post: header in the message that allows the MUA to offer/process the "reply-list" function. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/7/23 10:51, Volkmar Grote wrote: > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: >> >> >> Page not found (404) >> >> Request Method: GET >> Request URL: >> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >> >> ... > > Nginx, /etc/nginx/conf.d/me.domain.de.conf >> server { >> listen 80; >> listen [::]:80; >> >> server_name me.domain.de; >> ... >> location /static/ { >> alias /opt/mailman/mm/static/; >> } > > Again, many thanks in advance for any clue The above in nginx is correct, but you aren't getting the static files via nginx. You need to go to a URL like http://me.domain.de/postorius/lists/. Going to http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi server and doesn't involve nginx at all. You need to go to port 80 where nginx is listening and nginx then proxys requests to 127.0.0.1:8000. Do you also have location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } in /etc/nginx/conf.d/me.domain.de.conf. You need that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Re: I have issue where it does not send emails on to people in the list I create.

by Mark Sapiro

On 4/30/20 8:30 AM, john_warland(a)hotmail.com wrote: > Hello, > > I am quite new to Mailman3 and have been trying to get a working local test setup on a single VM (Centos07) > > I have issue where if I send an email to the list. it does not send emails on to the people subscribed to that list. > > Note the steps below were put together from memory after a few days of repeatably trying different things so there will be some inaccuracies > > > I have mailman running on same local box as postfix, postorius and hyperkitty. > > I have root as the superuser in Postorius and have tried the following: > > In unix shell created new user 'developer' > In unix shell created new user 'tester' > > In shell send an email from developer user to tester: > echo 'Hello' | mailx -s 'Hello Subject line' tester(a)sandbox.mytest.com > > Confirmed user tester received email in cat /home/tester/Maildir/new/ folder: > > Return-Path: <developer(a)cloud7.sandbox.mytest.com> > X-Original-To: tester(a)cloud7.sandbox.mytest.com > Delivered-To: tester(a)cloud7.sandbox.mytest.com > Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) > > In Postorius web frontend: > > Signed up as root > Received confirmation email in /root/Maildir/new/ folder so cut and pasted the Url in the email to activate account. > Created new list called testlist(a)sandbox.mytest.com > Logged out > > Signed up as tester > Received confirmation email in /home/tester/Maildir/new/ folder so cut and pasted the Url to activate account. > Subscribed tester to the testlist. > > Next in unix shell su as developer and send an email to testlist(a)sandbox.mytest.com > > The root user gets the following email > > Content-Transfer-Encoding: 7bit > Subject: Your message to testlist(a)cloud7.sandbox.mytest.com awaits moderator approval > From: testlist-bounces(a)cloud7.sandbox.mytest.com > To: developer(a)cloud7.sandbox.mytest.com > Message-ID: <158824480291.3035.17408340520496115243(a)localhost.localdomain> > Date: Thu, 30 Apr 2020 11:06:42 +0000 > Precedence: bulk > X-Mailman-Version: 3.3.0 > > Your mail to 'testlist(a)cloud7.sandbox.mytest.com' with the subject > > hello there 2 > > Is being held until the list moderator can review it for approval. > > The message is being held because: > > The message is not from a list member > > Either the message will get posted to the list, or you will receive notification of the moderator's decision. > > Once I have gone back into Postorius as root and approved the message, root user gets a second email: > > Return-Path: <testlist-bounces(a)cloud7.sandbox.mytest.com> > X-Original-To: root(a)cloud7.sandbox.mytest.com > Delivered-To: root(a)cloud7.sandbox.mytest.com > Received: from localhost.localdomain (localhost [IPv6:::1]) > by cloud7.sandbox.mytest.com (Postfix) with ESMTP id E056A84CE4 > for <root(a)cloud7.sandbox.mytest.com>; Thu, 30 Apr 2020 11:09:10 +0000 (UTC) > Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) > id 8F1B684CE4; Thu, 30 Apr 2020 11:06:41 +0000 (UTC) > Date: Thu, 30 Apr 2020 11:06:41 +0000 > To: testlist(a)cloud7.sandbox.mytest.com > User-Agent: Heirloom mailx 12.5 7/5/10 > MIME-Version: 1.0 > Message-Id: <20200430110641.8F1B684CE4(a)sandbox.mytest.com> > From: developer(a)cloud7.sandbox.mytest.com > X-MailFrom: developer(a)cloud7.sandbox.mytest.com > X-Mailman-Rule-Hits: nonmember-moderation > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation > Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY > X-Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY > X-Mailman-Approved-At: Thu, 30 Apr 2020 11:09:10 +0000 > X-Mailman-Version: 3.3.0 > Precedence: list > > Subject: [Testlist] hello there 2 > > List-Id: A test list <testlist.sandbox.mytest.com> > List-Help: <mailto:testlist-request@sandbox.mytest.com?subject=help> > List-Post: <mailto:testlist@sandbox.mytest.com> > List-Subscribe: <mailto:testlist-join@sandbox.mytest.com> > List-Unsubscribe: <mailto:testlist-leave@sandbox.mytest.com> > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > > A test email 2 > _______________________________________________ > Testlist mailing list -- testlist(a)sandbox.mytest.com > To unsubscribe send an email to testlist-leave(a)sandbox.mytest.com > > > At no point does the email appear in the tester(a)sandbox.mytest.com Maildir Why does root get the list post? Is root also a member of the list. What's in logs? Mailman's logs and the MTA logs > > Configs as follows.. tl;dr and mostly irrelevant. What do the following shell commands show mailman members testlist.sandbox.mytest.com mailman members -r testlist.sandbox.mytest.com mailman members -n any testlist.sandbox.mytest.com -- 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

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: Emergency moderation and clearing out a lot of held messages

by Stephen J. Turnbull

Dan Caballero writes: > We're running Mailman in AWS using and RDS MySQL database. It seems > to take unusually long to approve or discard even a few messages. I assume you are use Postorius for this? > What should be a normal response time for processing as few as 10 > messages? I don't know about MySQL/Maria. All of the production instances I have access to are backed by PostgreSQL. Response using Postorius is not instantaneous, but 2-3 seconds is maximum. Also, I don't think I've seen multiple messages with the same treatment in visit in many months (maybe a year), but I don't recall those "feeling" longer than a single message request. > I've done some testing in the pass running Mailman3 in a Docker > container and using a local instance of MariaDB. Even in that > situation I still found the processing slow. I guess since you talk about "10 at once" you have a much larger lists and/or much larger user databases and/or heavier traffic per user and/or more "spam". It would help to know what the scale of your Mailman installation is in those dimensions. I don't think Mailman's Python code is likely to be the bottleneck, rather it's probably database queries. Have you looked at MySQL's logs for queries related to those operations? Steve

2 years, 7 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/22/20 12:23 PM, Ruth Ivimey-Cook wrote: > >> I agree with this, we need a setting for which interface for Gunicorn >> to listen on, and what Mailman Core sends out in the self_link >> attribute when responding to REST requests. >> > Exactly! :-) Except if there were a `bind_host` setting to specify the host to bind the REST API to and you set that to `0.0.0.0` you would have exactly what leads to the situation below, so we need to understand what's happening there (although I think I do - see below). On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. > > > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Tracebacks would really help. You should be able to find them in the log configured as LOGGING['handlers']['file']['filename'] in your Django settings. > Previously, the process stopped at line {1}. Now that and line {2} is > executed (AFAIK) correctly, but then line {3} is isssued. I have no idea > why something is looking for "domains/greyarea-web1": > > - Only the "ch-bc.org.uk" domain is listed in the reply to line {1}, as > expected; Go to your Django admin web UI and look at your Django Mailman 3 Mail domains. This will be at a URL like https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ Do you see this domain there? If so, delete it. > - "greyarea-web1" doesn't appear in any lists I can show with the > "mailman" cli command (and I think I tried them all); But that's looking at Mailman core which is not where Postorius is getting this list. > - "greyarea-web1" doesn't appear anywhere in the source or config other > than as the name of the host its running on or as an ALLOWED_HOST; > > - I tried using "curl -X DELETE" (from the api docs) to delete a domain > called that and it says no such list exists. Again, you're talking to core, not Django. > My only possible clue is that I think, at some point in the journey of > configuring mailman, I might have created a list called that on the > host. However since then I have wiped the install files and reinstalled. > I cannot make sense of this being the answer given the checks just listed. Did you wipe the database on greyarea-web1? > I went looking through the python source and can see that the get() > function does indeed throw a 404 exception if the domain isn't found, > but I cannot see which code is parsing the reply from the first line > > So I have two questions: > > 1) How can I fix this problem? See above. > 2) why does getting an 404 reply here cause the postorius web page to > produce a "something went wrong" /404 and nothing else, when it could > have simply reported that something had gone wrong with one specific > domain; Because the code isn't robust enough :( ... > Ideally, and this is icing on the cake, a listen address specification > should allow multiple IPs to be passed in, in which case the server > listens on all of them. I expect the python libraries already support this. We could implement a bind_address setting that would pass to gunicorns --bind parameter anything acceptable to gunicorn, although multiple values are tricky as they apparently require multiple -b/--bind options and a single -b/--bind doesn't support a list of values. But, I'm not convinced that this is something anyone needs. I'm still waiting for a response to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- 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

Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/14/24 21:40, adam.heathcote(a)utas.edu.au wrote: > Hi Mark, > > Sorry about the delay in replying. > > You're correct, I am clicking on the list in the Mailing List view. > > Navigating to the list URL directly while not logged in produces the same error and even produces the error when a different user is logged in. Now it's my turn to apologize. I've been traveling. In your original post you wrote "I've tried removing it and reimporting it to no avail." What exactly does this mean. You removed the list how? Then you reran the import21. Was the list broken at that point, or only after removing the old owners and adding yourself? What if you try the following steps in order and try to view the list in Postorius after each step. - remove the list with `mailman remove list(a)example.com` and recreate it with `mailman create list(a)example.com` - run `mailman import21 list(a)example.com path/to/config.pck` - in Postorius, add yourself as owner. - in Postorius, delete one of the other owners. - repeat the deletion and viewing the list for the other unwanted owners one at a time. If the view throws the error at some point, after which step? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

Re: How to set up mailman 3

by Mark Sapiro

On 03/25/2017 04:55 PM, Mark Sapiro wrote: > > A list's message_size can't currently be set in Postorius. File an issue > at <https://gitlab.com/mailman/postorius/issues/new>. Actually the attribute name is max_message_size, not message_size. It exists in core and can be set, e.g., from the command line via 'mailman shell', but it needs to be exposed in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Displaying new lists in Hyperkitty (Re: "Private archives" aren't private)

by Simon Liebold

> settings in postorius are not reflected in hyperkitty. That's not yet fixed, or is it? Am 28.07.2017 um 10:55 schrieb cyp(a)trojina.si: > but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. I am unsure where/how to use this workaround. Can anyone explain how I get Hyperkitty to display (and archive for) new lists created via Postorius. Simon

7 years, 8 months

Mailman-users search results for query "Postorius"