Search results for "Postorius" - Mailman-users

Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > Of course, I want to keep this mailing list "read only" for members, and > I want only selected people to post to that mailing list. > > Any idea on how to achieve that? There is only one difference between the `Discussion` and `Announce` list styles, and that is for an `Announce` list, the `allow_list_posts` attribute is set to `False`. In turn, all that does is cause the List-Post: header to be set to NO rather than the list posting address. There is a discussion at <https://wiki.list.org/x/4030685> of how to set up an announce list for Mailman 2.1. Most of this translates straightforwardly to Mailman 3, although not all the relevant settings are exposed in Postorius. In short, you need to set this up manually using things like moderation settings and custom templates for the welcome message. -- 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: Docker mailman3 delete social logins, did something change?

by bob B

I even just tried to add in what is there ie ********* #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] ALLOWED_HOSTS = ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'Redacted' EMAIL_PORT = 25 INSTALLED_APPS = [ 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ] ********* this this does not work the mailmanweb.log shows ERROR 2021-09-16 13:19:07,479 1647 django.security.DisallowedHost Invalid HTTP_HOST header: '`[REDACTED]`'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-09-16 13:19:07,520 1647 django.request Bad Request: / WARNING 2021-09-16 13:19:07,520 1647 django.request Bad Request: / So that shows me that my opt/mailman/web/settings_local.py. is no longer being loaded??

4 years, 5 months

Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:29 PM, Thomas G wrote: > Yes, of course. > > Nginx and Apache works on the same server. (Nginx is stopped) > I would like switch to Apache to add in front of hyperkitty a ldap > connection.> I need to re-compile nginx for this feature. It's directly available > in apache with a module. Not sure the reason for this, the docs mention that what you had initially and also what Mark mentioned should have worked. Both of them seem to be supported syntax from the docs[1]. The only difference that I can see is quotes, not sure if that would affect things. [1]: https://httpd.apache.org/docs/2.4/mod/mod_alias.html#alias > > In fact, a tried directly to integrade LDAP with django > (https://gitlab.com/mailman/postorius/issues/132) without results.> > > > > > > > > Le ven. 19 oct. 2018 à 20:18, Abhilash Raj <maxking(a)asynchronous.in> > a écrit :>> >> >> On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: >> > Hi tried both. >> > >> > Same result. >> > >> > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET >> > /static/postorius/js/script.js>> > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >> > Gecko/20100101 Firefox/60.0" >> >> >> And, you have verified that the files exist at `/opt/mailman/static` >> on your host?>> >> > >> > >> > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a >> > écrit :>> > >> > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: >> > > > Hi, >> > > > Currently, I use a nginx configuration for mailman. It's work >> > > > perfectly.>> > > > >> > > > I tried to do the same with Apache, but the statics files are >> > > > not>> > > > delivered (404). >> > > ... >> > > > <VirtualHost *:80> >> > > > ServerName mailing.ddd.fr >> > > > >> > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log >> > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined >> > > > >> > > > <Location /static/> >> > > > Alias "/opt/mailman/static/" >> > > > </Location> >> > > > >> > > > <Location /> >> > > > ProxyPass http://localhost:8000/ >> > > > ProxyPassReverse http://localhost:8000/ >> > > > ProxyPreserveHost On >> > > > </Location> >> > > > </VirtualHost>/ >> > > >> > > >> > > In Apache, location >> > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not>> > > appropriate for resources in the file system. >> > > >> > > Try >> > > >> > > Alias /static/ /opt/mailman/static/ >> > > >> > > not within a location block. >> > > >> > > -- >> > > 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)

7 years, 4 months

Re: Mailman REST API not available. Please start Mailman core.

by joseverde＠gmail.com

> > It would help to know how you did that. Did you wipe the server and > start over? Did you just purge Mailman3 and its configuration files? > Something else? It's a bit hard to say, my brain got mushy after a few hours of staring at bash. What was happening was the install was never completing, there was always an error blocking it. One of the main ones I found was pymysql for python2 wasn't installed. Once I installed that, it started to be happy. I also had to run dpkg-reconfigure for mailman3-web and after that I had a working web service. As far as Hyper Kitty, the web service is up (the webpage runs, at least). And I did check systemctl status mailman3, it was inactive. So I did systemctl start mailman3 and it is now running. However, the same error still shows up on postorius. >>Something went wrong >Mailman REST API not available. Please start Mailman core.

5 years, 7 months

Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 09:53, Élodie BOSSIER via Mailman-users wrote: > > Now, I need to find how to set it automatic when I will add a new list. > Perhaps I could do it with an an SQL command if there are no bash > command ? I will check with "mailman create" and the --domain argument. Part of adding a new list is specifying the domain. If it's one of the existing domains, i.e., ml.franceserv.fr, or ml.viticreation.fr, that's all that needs to be done. e.g. `mailman create newlist(a)ml.franceserv.fr`. If it's a new domain, you need to add the domain to the django_site table perhaps directly or via the django admin UI and then after `mailman create newlist(a)new.domain` you may need to edit the domain via Postorius' domains view to specify the correct Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: Mailman3 via Docker and NGINX

by brian＠emwd.com

Abhilash Raj wrote: > On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote: > > On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > > > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe > > the installation went fine and running "curl > > http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will > > be using exim and nginx with this installation. > > ... > > > location / { > > > include uwsgi_params; > > > uwsgi_pass 172.19.199.3:8000; > Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for > uwsgi protocol. > > See the docs[1]. > > [1]: https://github.com/maxking/docker-mailman#setting-up-your-web-server Thanks Abhilash. It is working now. FYI, I made the change directly in the nginx.conf file. I got rid of trying to use the conf.d/sitename.conf file. I now move on to getting exim to work. If I need help, I will start a separate thread. Brian

7 years, 2 months

Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On August 20, 2025 4:37:18 AM EDT, "Stephen J. Turnbull" <steve(a)turnbull.jp> wrote: >Odhiambo Washington via Mailman-users writes: > > > > > The superuser account uses my address - odhiambo at gmail dot > > > > com. I am also the listowner for most lists. > > > > I tried unsuccessfully to create an account on Postorious using the same > > > > email address. > >I don't see how you can do this. It's the same user database, and >email addresses are accepted as identifying a unique User object in >the database for authentication and authorization purposes in Django. That is correct. You can't have two accounts in Postorius/Django with the same email address. But why would you want to? There should be no problem with a single Django user being subscribed to a list with more than one role. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 months, 2 weeks

Re: Redundant and load balanced Mailman3

by Stephen J. Turnbull

Bottom line up front: 1. Mailman was designed in the context of a single host, and most installations do work that way; we at Mailman don't know a lot about multihost setups and performance yet. This can give you some pretty large installations (eg, mail.python.org is a single host, I believe). Maybe Mark will chime in on this point. 2. You might get better information from postmasters at the largest sites who may have experience with distributed setups. fedora.org might be a good candidate because their people put a ton of work into optimizing HyperKitty for their situation (that's why HyperKitty has all the options for redis caching etc). Pawel Grzywaczewski writes: > I'm a bit confused about dependency on local files? You mean files > that are created when an e-mail is processed? Yes. > So where is the problem with redundancy? If this host is gone there > will be another Mailman deployment able to deal with the load. Where does the file go if the host goes down? If it's local and the host goes down, you lose or delay mail -- that should not happen if your Mailman system is up. That's why Abhilash mentions NFS, which allows another "core" host to take over if a "core" host goes down -- but that's not necessarily a good solution either. (I'm not saying it's *bad*, just that NFS has known problems for *some* applications, and I don't know if Mailman is one.) And of course the NFS server becomes a SPOF (single point of failure). > What about having 3 VM where all components of Mailman are > installed. Those VMs connect to 1 database on a remote host. But they don't connect to 1 database. Each component has its own database, and HyperKitty and Postorius also connects indirectly to core's database via core. They *could* all connect to one database server, but that server becomes a SPOF. > A given VM handles a request HTTP or SMTP, and if there is a > problem (or very high load of SMTP) Mailman doesn't handle SMTP requests, I assume you mean LMTP. I don't think that LMTP handling is very strenuous (could be wrong). The aiosmtp module can handle quite high loads, spending most time waiting for the payload (during which it handles other connections), then it dumps a file to disk, also quite fast. As I understand it, the bottleneck is the database stuff. Mailman does a lot of database accesses to handle a post. > there are still 2 other VM that can do the job. So perhaps the > question is: can we plug 3 Mailman instances into 1 DB? Is Mailman > software developed taking into account that several Mailman > instance writes to the same database at the same time? I don't see why that would be an ACID problem -- the database takes care of that. I do think it would make the database bottleneck worse for performance. Note that we're currently seeing reports of long delays (enough to cause database connection timeouts, so on the order of minutes) in creating lists when there are already a lot of lists. If I had to put money on it, I would bet that there is some procedure iterating over incremental requests in Python that should be doing "one big request" to the database. But I don't know that that's true. I do know that there are some very big sites (such as fedora.org) that use Mailman 3. But they seem to have rather complex setups, with powerful databases and caches to speed up even that. Finally, Mailman 3 was originally designed and tested with a single host doing all the work in mind. The most obvious symptom is the lack of authentication on the REST API. (Of course you can simulate that model with an appropriate firewall and subnetting setup.)

5 years, 5 months

Re: Captcha or similar for new signups?

by Odhiambo Washington

On Wed, Nov 29, 2023 at 12:44 AM <peter(a)chubb.wattle.id.au> wrote: > Hi Folks, > Does anyone have a recipe for adding captcha or similar to stop bot > accounts signing up with Postorius? We're seeing a heap of fake signups > resulting in confirmation emails going to people who haven't signed > up, with user names like 'CAOXpYhPFPBFr' -- I'd like to make it > just a little harder for bots to sign up. > > Too many confirmation emails going to non-existent email addresses > reduces our mail reputation, and increases the likelihood that > legit email is flagged as spam. Maybe it will come soon seeing as it's already somewhere - https://gitlab.com/mailman/django-mailman3/-/issues/33 or you can patch your install by looking at the patches at https://github.com/pbiering/mailman3-rpm/ -- 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, 3 months

Re: Clean-up of non-members

by Torge Riedel

Feature request created: https://gitlab.com/mailman/postorius/-/issues/617 Am 22.12.24 um 14:25 schrieb Odhiambo Washington: > > > On Sun, Dec 22, 2024 at 3:18 PM Torge Riedel via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Dears, > > I am currently cleaning up a huge list of non-members. In contrast to the members list where I can select multiple entries and delete them at once, this is not possible in the list of non-members? > > Can this be enabled in a future release? > > > > Perhaps you can make a feature request in gitlab? > And while at it, please add: mailman nonmembers LISTSPEC > With the later, it would be easier to delete non-members from the CLI as well. > > -- > 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

Mailman-users search results for query "Postorius"