Search results for "Postorius" - Mailman-users

Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

> > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > When you say nothing happens, you just mean that you don't see anything in > the > UI or you don't see anything in the logs? > In the UI, I get a green line with text saying the message has been sent. However, the new message is not added to the the thread in any way. In the logs there is nothing that pertains to that particular action > > Logs for mailman-web are in /opt/mailman/web/logs/mailmanweb.log (on the > host). > The log mailmanweb.log is empty. uwsgi.log is not empty. Interestingly, in the mailman-web container, there is a mailmanweb.log in the root of the server which gets updated like this: INFO 2017-11-21 10:53:33,765 36 hyperkitty.views.mailman Archived message <20171121115328.2dc8970f@thor-E6530> to https://mailer.domain.com/ hyperkitty/list/aaa(a)klubb.domain.com/message/2XYZL6G35IJYOW5WG6IGXI424Q44DG FK/ but nothing is written when I try to send message from Postorius. > > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > > mailman:10000:65536 > > This ideally shouldn't affect anything, I haven't tried running this way > though. > > > > > > > and in /etc/docker/daemon.json: > > > > { > > "userns-remap": "mailman" > > } > > > > So I get the following ownership in /opt/mailman: > > > > > > drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core > > drwx------ 19 10070 10000 4096 nov. 21 09:27 database > > drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web > > > > (I have created a user named mailman with uid 10100 so, in reality, it > says > > "mailman" there instead of 10100 but I guess that is irrelevant here) > > If would be interesting to see what processes are running inside each > containers > and who their owners are, in case this is at all relevant to the issue, > which I > am not so sure about. > > Web container: bash-4.3# ps aux PID USER TIME COMMAND 1 mailman 0:00 uwsgi --ini /opt/mailman-web/uwsgi.ini 36 mailman 0:00 uwsgi --ini /opt/mailman-web/uwsgi.ini 37 mailman 0:00 /bin/sh -c ./manage.py qcluster 41 mailman 0:00 python ./manage.py qcluster 54 mailman 0:00 python ./manage.py qcluster 55 mailman 0:00 python ./manage.py qcluster 56 mailman 0:00 python ./manage.py qcluster 57 mailman 0:00 python ./manage.py qcluster bash-4.3# ls -l total 96 -rw-rw-r-- 1 mailman root 0 Mar 29 2017 __init__.py -rw-rw-r-- 1 mailman root 42308 Nov 21 10:53 mailmanweb.log -rwxrwxr-x 1 mailman root 242 Mar 29 2017 manage.py -rw-rw-r-- 1 mailman root 12171 Oct 1 22:26 settings.py -rw-r--r-- 1 root root 9643 Nov 21 09:21 settings.pyc -rw-rw-r-- 1 mailman root 1777 May 23 21:31 settings_local.py -rw-r--r-- 1 root root 1196 Nov 21 09:21 settings_local.pyc -rw-rw-r-- 1 mailman root 1314 Mar 29 2017 urls.py -rw-r--r-- 1 root root 791 Nov 21 09:21 urls.pyc -rw-rw-r-- 1 mailman root 1425 Aug 6 17:04 uwsgi.ini -rwxrwxr-x 1 mailman root 1173 Mar 29 2017 wsgi.py core container: bash-4.3# ps aux PID USER TIME COMMAND 1 mailman 0:00 {master} /usr/local/bin/python /usr/local/bin/master 26 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=archive:0:1 -C /etc/mailman.cfg 27 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=bounces:0:1 -C /etc/mailman.cfg 28 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=command:0:1 -C /etc/mailman.cfg 29 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=in:0:1 -C /etc/mailman.cfg 30 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=lmtp:0:1 -C /etc/mailman.cfg 31 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=nntp:0:1 -C /etc/mailman.cfg 32 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=out:0:1 -C /etc/mailman.cfg 33 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=pipeline:0:1 -C /etc/mailman.cfg 34 mailman 0:01 /usr/local/bin/python /usr/local/bin/runner --runner=rest:0:1 -C /etc/mailman.cfg 35 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=retry:0:1 -C /etc/mailman.cfg 36 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=virgin:0:1 -C /etc/mailman.cfg 37 mailman 0:00 /usr/local/bin/python /usr/local/bin/runner --runner=digest:0:1 -C /etc/mailman.cfg 2017-11-21 11:18 GMT+01:00 Abhilash Raj <maxking(a)asynchronous.in>: > Hi Thor, > > On Tue, 2017-11-21 at 10:53 +0100, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > When you say nothing happens, you just mean that you don't see anything in > the > UI or you don't see anything in the logs? > > Logs for mailman-web are in /opt/mailman/web/logs/mailmanweb.log (on the > host). > > > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > > mailman:10000:65536 > > This ideally shouldn't affect anything, I haven't tried running this way > though. > > > > > > > and in /etc/docker/daemon.json: > > > > { > > "userns-remap": "mailman" > > } > > > > So I get the following ownership in /opt/mailman: > > > > > > drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core > > drwx------ 19 10070 10000 4096 nov. 21 09:27 database > > drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web > > > > (I have created a user named mailman with uid 10100 so, in reality, it > says > > "mailman" there instead of 10100 but I guess that is irrelevant here) > > If would be interesting to see what processes are running inside each > containers > and who their owners are, in case this is at all relevant to the issue, > which I > am not so sure about. > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > thanks, > Abhilash Raj >

7 years, 6 months

Re: Mm3 - new adventure

by Mark Sapiro

On 03/14/2017 09:14 AM, SP2L wrote: > > Lately started adventurous journey with Mailman3 > which is way, way different already from the beginning. > > Used Mailman bundler to install GNU Mailman, Postorius and HyperKitty > testing instance in virtual environment, mainly relaying on belows recipe: > > https://gitlab.com/mailman/mailman-bundler/ mailman-bundler is out of date and deprecated. You might find <https://wiki.list.org/x/17891998> of interest. > Present status. > > Above trio and MySQLServer are "talking" to each other > but because there isproper database on MySQLServer > I am facing strange and unexpected issues, Hi! > > Executing last two commands: > > (venv)$ ./bin/mailman start > (venv)$ ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 & > > I see Postorius and HyperKitty up & runningbut... > > Belowvery condensed messages from the console: > > > /HyperKitty/ > > DEBUG = False > > [12/Mar/2017 18:59:43] "GET /archives/ HTTP/1.1" 200 8002 > WARNING Not Found: > /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css ... Have you run the script that bundler installs as bin/mailman-post-update? > /mailman3/ > > DEBUG = False > > Server Error (500) > > > DEBUG = True > > HTTP Error 500: A server error occurred. Please contact the administrator. > > Exception Location: > /var/lib/mailman3/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py > in call, line 109 > > Then VERY, verylong list... Without knowing what the exception was and at least the start of the traceback, it's hard to say what this might be. > By means of PhpMyAdmin I created manually mailman3 database > and few tables (looking at 0001_initial.py) , but it is not working O.K. > This handmade table is not doing it's job. You shouldn't need to do this. If you have the proper settings and credentials in the DATABASES setting in mailman-web/settings_local.py and the [database] section in deployment/mailman.cfg, the tables should be created for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

On 11/9/24 17:09, Mark Sapiro wrote: > > Here's what's going on. In normal text, mistune disables HTML tags by > converting `<` to the html entity `<`, but your browser renders the > HTML entity `<` as `<` so you see what was written. > > The issue here is the text you quoted was originally in a markdown code > block, i.e. preceded and followed by lines of three backticks. Code > blocks are intended to be seen literally as written so they are wrapped > in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. > The problem is the tag disabling converts `<` to `<` but then the > HTML escaping converts `<` to `&lt;` which your browser then > renders as `<` rather than `<`. > > (aside, it will be interesting to see how that is rendered in the archive) The backtick quoting causes the < to be rendered as `<` Here are the above two paragraphs written in a way (removing the backticks from around <) that I hope will render as I intended. Here's what's going on. In normal text, mistune disables HTML tags by converting < to the html entity `<`, but your browser renders the HTML entity `<` as < so you see what was written. The issue here is the text you quoted was originally in a markdown code block, i.e. preceded and followed by lines of three backticks. Code blocks are intended to be seen literally as written so they are wrapped in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. The problem is the tag disabling converts < to `<` but then the HTML escaping converts `<` to `&lt;` which your browser then renders as `<` rather than <. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

Re: Default Setting for 'Results per Page' and other Web Pull-downs

by Mark Sapiro

On 5/5/23 14:25, Dave Hall via Mailman-users wrote: > > My question: when I go to any page that has a list (of lists, of members, > or archives), there are pulldowns like 'Results per page' that seem to > reset to the minimum number when I refresh the page. There are others like > 'Hide inactive' on the Archives page. What I'm looking for is a per-user > way to customize these values so I don't have to keep on setting them to > the value I prefer. > > If that is available in a later release then I have something to look > forward to. If not, it sure would be nice to have. No, it is not available. You can submit a wishlist issue at https://gitlab.com/mailman/postorius/-/issues/new for Postorius and https://gitlab.com/mailman/hyperkitty/-/issues/new for HyperKitty. -- 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: restrict sending to owner/moderator

by Mark Sapiro

On 09/18/2017 02:28 AM, m.dohmen(a)xconnect.de wrote: > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. And on 09/19/2017 10:52 AM, David Krantz wrote: > > I have just tested a variant of this as I got curious: You find the > member you want to be able to send emails without moderation, then set > Administrative Options to "Accept Immediately (bypass other rules)". > That works. I have found no other ways, though. Or you may wish to set the owners/moderators subscriptions to "Default processing" which will still apply subsequent rule checks. I.e., set Default action to take when a member posts to the list to Reject (with notification) and set an appropriate notice (currently can't be set in Postorius - set it via 'mailman shell') and set Default action to take when a non-member posts to thelist to Discard or perhaps Reject but this creates backscatter. Then ordinary members have Moderation set to List default and owners/moderators have it set to Accept or Default. The problems with this are sall the owners/moderators need to be subscribers and there are maintenance issues with adding/removing owners/moderators. A better way to do this by sharing a "moderator password" for the list among the authorized posters. See <http://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.html> for how this is done to pre-approve posts. Then set the list to Discard/Reject all posts, and people who know the "moderator password" can still post. There is still an issue in that the password needs to be changed and redistributed when people become unauthorized, but this is more secure as regular moderation can be fooled by spoofing the sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

Installing MM3 requires Django<1.11

by Henrik Rasmussen

Two questions regarding Mailman 3 installation: 1) The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". In what file should I change the mail settings then? 2) While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty Regards Henrik

8 years, 2 months

Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 8:55 AM, Kevin Hurtley wrote: > > It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. The issue with the way Postorius displayed all the subscription requests was that it wasn't possible for the moderator to distinguish request waiting moderator approval from those waiting user confirmation, and in general a moderator shouldn't approve a request waiting user confirmation, but this thread shows there is sometimes a need for a moderator to be able to deal with these. I have reopened <https://gitlab.com/mailman/postorius/issues/314>, and will look at fixing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Simon Hanna

On 11/08/2017 12:03 AM, Abhilash Raj wrote: > New images are available on quay.io and, moving forward, the rest of > the image builds will also be moved to Quay[4][5]. Since docker deployment is currently the recommended install, with manual installs using the master branches for "experts" I wonder why you are using Quay. It looks like it's a non-free system. Why use Quay but refuse to use a non-free translation system like transifex? > These images are built using git-heads *only* if they are passing our > test suite and are re-generated weekly. You should be aware that while > all these components are tested with their individual test suites, their > combination might sometimes not be stable. This will get you > updates/bug-fixes much faster :) This contradicts what you said in my merge request for Postorius https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 You either use released versions, or make sure that the master branches are always compatible. You can't have both with the current development model. > If this campaign succeeds, here is a road map of what I intend to get > done: Sounds great, what is the limit where the campaign succeeds? What will happen to the funds if it doesn't? > - Add Admin Dashboard project from GSoC 2014 (maybe?) Didn't find anything using google. What is that project about? > - Add better testing of container images and provide deployment > instructions for Kubernetes & Docker Swarm To be honest, I don't think we should all in on containers. Yes they are nice, but I guess most people would prefer distro packages. Even if people want containers, I for instance would prefer plain systemd-nspawn > - Improve the container images to work with new micro-services > architecture, > to achieve scaling and redundancy in services. The current bottleneck is the rest api from core. IMO bulk actions, filtering and sorting should be added there before trying to have multiple postorius/hyperkitty instances serving the same core...

7 years, 7 months

Re: Mailman upgrade results in page not found error

by Andrew Hodgson

Abhilash Raj wrote: >On 11/3/22 18:30, Andrew Hodgson wrote: >> I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? >> urlpatterns = [ >> path( >> '', >> RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), >> ), >> path('mailman3/', include('postorius.urls')), >You _probably_ had DOMAIN/postorius as your URL? If that's the case, replace the 'mailman3/' above with your old 'posotorius/' in your new urls.py. >That should fix the problem you are having with 404 because you browser probably remembers the old URL and tries to auto-redirect root path to /postorius. Yep that was it. I actually left it be in the end as users were accessing the new page fine. I had to update mailman-hyperkitty with the new URL as archiving wasn't working but that has now been done and everything seems to be back to normal on the new setup. Thanks. Andrew.

2 years, 7 months

Mailman-users search results for query "Postorius"