Search results for "Postorius" - Mailman-users

Patch/kludge suggestion and a question on adding accepted addresses

by David Krantz

Hi. I found out that I had a broken email in one of my held messages queues). That gave a HTTP 500 error although that should be fixed . After some digging I found out that where the error occured. I'd suggest adding a catch for AttributeError similar to the one for KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my immediate problem at least. I run the version from git with the tag 263711b3b7988c7c474e3b8952dc7e0f02f04fa2 The message causing this was probably one where I had sent a minimal email via telnet to the SMTP port and forgot the MessageID-header or something similarily silly. But it prevented me from seeing the held messages-list in postorius. I have another question: In the old mailman you could add accepted senders without adding them to the list. Is that possible in Mailman 3/Postorius? cheers. // David

8 years, 1 month

No path configuration found: paths.master

by Pierre Abbat

I installed postorius and hyperkitty with pip and ran into another problem. I ran "mailman info" and got "No path configuration found: paths.master". I have three files named mailman.cfg: /etc/mailman.cfg /usr/local/lib/python3.5/dist-packages/mailman/config/mailman.cfg /var/etc/mailman.cfg The one in /etc contains the following: [mailman] layout: master The one in /var/etc is completely commented out. If I move the one in /etc/ out of the way and run "mailman info" again, I get this: GNU Mailman 3.1.0 (Between The Wheels) Python 3.5.2 (default, Sep 14 2017, 22:51:06) [GCC 5.4.0 20160609] config file: None db url: sqlite:////etc/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass It said "config file: /var/etc/mailman.cfg" before. What changed? Pierre -- La sal en el mar es más que en la sangre. Le sel dans la mer est plus que dans le sang.

7 years, 7 months

Re: proper update procedure for MM3 docker containers

by Abhilash Raj

On Mon, Aug 6, 2018, at 6:28 AM, Fabian A. Santiago wrote: > Hello, > > Can someone remind me of the proper / best way to update my docker > containers for MM3 / postorius based on maxking's images? Thanks. > > and this for both the stable and rolling releases. Well, the process is fairly straightforward, when moving form an older to a newer release, Stop and remove the container ($docker-compose stop, $docker-compose rm) and then start the new ones ($ docker compose up -d). That should be all! > > -- > Fabian S. > > OpenPGP: > > 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F (new key) > > *** > > 0x3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC (to be retired, still valid) > _______________________________________________ > 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, 10 months

Re: HTML post only showing as attachment

by Mark Sapiro

Mark Sapiro wrote: > On 7/4/19 7:13 AM, andrew.bernard(a)gmail.com wrote: >> I have a post come in that is in HTML and has an >> image attached. It is distributed fine to email subscribers. Hyperkitty shows a blank >> message, with the in an html attachment, and the image as a jpg attachment. >> >> Why doesn't the text show in Hyperkitty? > > Because there is no plain text. Non text/plain parts including text/html > parts are "scrubbed" and stored aside. If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

API errors making member changes to one list but not others

by Stephen Willey Mats Mats

We had an issue with the UI getting API timeouts for a single list for specific functions but not other lists or other functions. This started happening after we accidentally filled the disk partition used by most of the system including the database. There was a single person testing at the time when the disk fullness happened and it was only the single list that got ‘damaged’. After disk cleanup and restarting the docker images the single list would give API errors ("HTTP Error 400: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5)” ) on the screen and logged errors (below) when list members were either subscribed or removed. The issue was repeatable in Postorius and did not ‘heal’. Oddly the issue was resolved by making seemingingly the same API calls from the command line via curl. Making the below call to add a member succeeded and fixed being able to add members in the UI. Similarly sending a DELETE cal from curl worked where unsubscribe requests from postorius (either mass removal or picking addresses from the list member and unsubscribing selected) failed. Again, the unsubscribe from the curl DELETE call ‘healed’ the list such that subsequent unsubscribes in Postorius worked. curl --user user:password -X POST -d 'list_id=laura-test.mm3.aca-aws.s.uw.edu' -d 'subscriber=ssw(a)uw.edu' -d 'pre_verified=true' -d 'pre_confirmed=true' -d 'pre_approved=true' http://172.19.199.2:8001/3.1/members We’re running the current rolling docker images (up to date as of 25Jan2021) Obviously, people should run their servers better than letting disk partitions fill-up but it’s going to happen and mailman3 should do a better job of reporting errors and recovering when accidents happen. thanks, steve I’ve included mailman.log lines from going to the mass subscribe [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:01 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" Jan 26 20:43:07 2021 (48) deque: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 426, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.8/http/client.py", line 1347, in getresponse response.begin() File "/usr/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.8/http/client.py", line 268, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.8/socket.py", line 669, in readinto return self._sock.recv_into(b) socket.timeout: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 724, in urlopen retries = retries.increment( File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 403, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3.8/site-packages/urllib3/packages/six.py", line 735, in reraise raise value File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 428, in _make_request self._raise_timeout(err=e, url=url, timeout_value=read_timeout) File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 335, in _raise_timeout raise ReadTimeoutError( urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 343, in _step_do_subscription self.member = self.mlist.subscribe( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 507, in subscribe notify(SubscriptionEvent( File "/usr/lib/python3.8/site-packages/zope/event/__init__.py", line 32, in notify subscriber(event) File "/usr/lib/python3.8/site-packages/mailman/app/membership.py", line 176, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3.8/site-packages/mailman/app/notifications.py", line 51, in send_welcome_message welcome_message = wrap(getUtility(ITemplateLoader).get( File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 188, in get contents = getUtility(ITemplateManager).get( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 529, in send raise ReadTimeout(e, request=request) requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) [26/Jan/2021:20:43:07 +0000] "POST /3.1/members HTTP/1.1" 400 130 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" Then the results of a successful subscribe: [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "POST /3.1/members HTTP/1.1" 201 0 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2” >

4 years, 4 months

Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/16/23 8:00 AM, eboltz(a)lhtservices.com wrote: > 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. In Postorius -> Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and 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

1 year, 6 months

Re: Functionailty of web host domains

by Mark Sapiro

On 06/15/2018 12:37 PM, Johannes Winter wrote: > > For each domain you can specify a "web host". But when I specify a > different one than the default for one domain, and make it accessible > with specifying `DJANGO_ALLOWED_HOSTS`, all mailinglists from the other > web hosts are also shown when I access the second site. > > So does this 'web host' option have a meaning, or is it just an alias > for the first site? This is a 'site' as implemented in Django <https://docs.djangoproject.com/en/2.0/ref/contrib/sites/>. I.e., it provides ways to do different things or retrieve different content based on site, but I don't see that either Postorius or HyperKitty makes use of it in this way. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Showing sender as ... via ... list

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and 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 _______________________________________________ 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, 7 months

Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/22/24 23:07, Gerald Vogt wrote: > > For testing I have set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' > > to the URL of our main domain, however, if I test an anonymous subscribe > through the list info page I still get the timeout error This will have no effect unless you delete and recreate the template in Postorius because simple changing the setting won't change the `uri` in the template table. > I can access > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. Can you do that as the Mailman user?, e.g. ``` sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` assuming the Mailman user is `mailman`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 4 weeks

Re: Dealing with confirmation requests for unsubscribes

by Brian Carpenter

On 11/18/20 6:17 PM, Mark Sapiro wrote: > On 11/18/20 7:41 AM, Brian Carpenter wrote: >> Hello List, >> >> I ran into the following issue for some mailman 3 lists that I am hosting: >> >> https://gitlab.com/mailman/mailman/-/issues/768 >> >> Since there is no way for a list owner to deal with a moderation request >> for an unsubscription task, I assume I need to do something via the >> command line. This is where I need some help with. How do I deal with >> these moderation requests that are unable to be reviewed in an admin gui >> (Postorius/Affinity)? > > 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 test.msapiro.net mailing list > > This > >>>> list(getUtility(IPendings).find(mlist=m, pend_type='unsubscription', > token_owner=TokenOwner.moderator)) > > will return something like > > [('a8df55f557b5718505280d2613937e25a3109252', {'type': 'unsubscription', > 'list_id': 'list.example.com', 'email': 'user(a)example.com', > 'display_name': 'Mark S', 'when': '2020-11-18T22:56:53', 'token_owner': > 'moderator'})] > > What you want is the token, in this case > 'a8df55f557b5718505280d2613937e25a3109252' > > Then do > > ISubscriptionManager(m).confirm('a8df55f557b5718505280d2613937e25a3109252') > > which will return > > (None, <TokenOwner.no_one: 0>, None) > > and finally: > >>>> commit() > > >> I do recommend removing such choices for Postorius for Member policy. I >> will be doing this for Affinity until issue 768 is resolved. > The correct thing to do is fix > <https://gitlab.com/mailman/mailman/-/issues/768>. We almost certainly > will do that rather than remove the moderate and confirm then moderate > unsubscription policies. > > Worked like a charm Mark. Thank you! I forget you guys have a slower process than I when it comes to implementing gui changes. For me, once you have fixed that issue (768), it will be easy for me to reintroduce those two policies for unsubscribing. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

Mailman-users search results for query "Postorius"