Search results for "Postorius" - Mailman-users

Re: sending messages in response to posts from non-members

by Mark Sapiro

On 2/26/22 04:26, David Bremner wrote: > > I'd like to turn off the "bounce messages" sent by mailman to > non-members. My reasoning is that most such posts are spammers, and > often use forged return-paths / From's, so I end of sending steady > stream of backscatter to amazon.com etc... > > Is this configurable (without postorius) somehow? What exactly do you want? Do you want to discard without notice any nonmember posts or do you want to hold them but not send a notice of the hold to the poster? For the former, you want to set the list's default_nonmember_action to discard. For the latter you want to set the list's respond_to_post_requests to False. To make either of these settings the default for new lists, you'd need to patch mailman/styles/base.py. To set them for all lists you could do the following in `mailman shell` ``` $ bin/mailman shell 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. >>> for mlist in getUtility(IListManager).mailing_lists: ... # Pick the appropriate one of the following. ... mlist.default_nonmember_action = Action.discard ... mlist.respond_to_post_requests = False ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Apache Conf

by Thomas G

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" 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/ >

6 years, 8 months

Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 00:51, Mark Sapiro wrote: >> Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> > > Probably because (in Postorius) Settings->Digest->Enable Digests is No Double checked that Enabled Digest s= Yes >> Then, as "mailman", I ran "mailman digests --periodic" manually and >> got the same error (as expected since there is nothing there) ... > This error should not occur if there is no digests.mmdf. It only does > occur because you have set Digest size threshold to 0 under the > assumption that 0 means unlimited which it doesn't. If you don't want > digests sent on size, you need to set Digest size threshold to a very > large number. > > I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid > throwing the exception, but setting the threshold to 0 is still wrong Oh? I was indeed assuming that 0 meant unlimited. The threshold was set at 0. My thinking was that meant the file size was not a factor in determining when the digest was sent and that the sending would be triggered by the daily cron. When I set the threshold very low - 10kB - it sends a digest on every post. So my understanding of what you are saying is: if the threshold is set very large, say 100,000 kB - then a digest will be be sent by the daily cron even if it is smaller than 100,000 kB. Am I understanding correctly?

1 year

Re: [Mailman-Developers] Mailman Core 3.3.2 is now out

by Brian Carpenter

On 11/6/20 8:38 PM, Abhilash Raj wrote: > Hi Everyone, > > I am pleased to announce that with a week long delay from the planned date, > GNU Mailman Core 3.3.2 is now finally out. This release includes both bug fixes > and some new features. > > Some notable changes include: > - Support for inviting users to join mailing lists. > - New adddmembers, delmembers and syncmembers command to manage membership from CLI. > - Addition of new REST API endpoints that return the count of held messages and subscription requests of much faster page loads in Postorius. > - Addition of support for filtering in some API endpoints like Members and Subscription requests. > - Support for address= option in email join command to subscribe an address other then sending address. > - Addition of who email command to lookup memberships. > - Expose emergency field for MailingList resource in REST API. > - Several bug fixes to support new major version of libraries like dnspython, flufl.* etc. > > You can install it using: > > $ pip install --upgrade mailman > > The tarball for the release is available at PyPI: > > https://pypi.org/project/mailman/ > > Finally, many thanks to all the contributors who have helped make this release a success! Thank you for the hard work that went into this release. Is there a change log somewhere that documents the complete changes/bug fixes that went into this release? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:58 PM, Rafael Mora wrote: > > > > Does the rDNS PTR record should be placed in my Centos7 server? > > You can't do this. Hostgator or whoever manages the network (Telmex > Colombia S.A. ?) has to do this. > > > > I've created the DNS A record for lists.labbrands.com with the IP but I > > don't know the port that it uses so I can make a port redirect to my > local > > ip address wich is 192.168.1.42, do you know the port????? > > > You need to forward port 25 for SMTP mail delivery and if you want the > web UI (Postorius and HyperKitty) accessible from the outside, port 80 > for http and/or port 443 for https > < > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >. > I mean for incoming mail redirected from my hostgator hosting, because when I suscribe an email address MM3 sends a confirmation email, so I have to reply to be suscribed to the list. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 11 months

Re: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Re: Archive Policy not reflecting in Hyperkitty

by Nathan Dixon

The change to the archiving policy aren't reflected in Hyperkitty after many days for all the lists. The only error that I am seeing in the /web/mailmanweb.log is: INFO 2019-05-02 14:16:55,062 38 hyperkitty.tasks AsyncTask task "<function unlock_and_call at 0x7f5d8851f048>" with args "(<function update_from_mailman at 0x7f5d88544a60>, 'task:status:%s:%s', '<list address>')" and kwargs "{}" finished with errors. I'm not sure if that could be related? (I have changed the actual list address to <list address> for security reasons) Thank you On Sat, 4 May 2019 at 16:24, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Fri, May 3, 2019, at 8:38 AM, Nathan Dixon wrote: > > So the issue I am seeing is that when I set a lists archive policy to > > prviate, it isn't reflecting that in Hyperkitty. > > > > I am running the docker installation of Mailman, postorius and > hyperkitty. > > So I go into the docker instance of mailman-core and run this: > > > > python3 manage.py shell from hyperkitty.models.mailinglist import > > MailingList MailingList.objects.all().values_list('name', > 'archive_policy') > > > > And all my lists are showing '2', regardless of how I set the mailing > list > > archive policy. > > > > This might be a duplicate of > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > Am I missing something in my install? Or is this a bug? > > It can take upto an hour for this change to reflect in Hyperkitty. Did you > wait > for that long? > > This happens because Hyperkitty stores it's own data, and queries Mailman > Core periodically to fetch updates every hour. In future, we might be able > to > do this in more realtime fashion by using an event based pub/sub model. > But, > we are not there yet. > > > > > > Many thanks for your attention, > > > > -- > > > > *Nathan Dixon* MEng > > Senior Software Architect > > m: +44 (0)7402 690311 > > > > t: +44 (0)20 81231252 > > e: nathan.dixon(a)evadon.com > > w: www.evadon.com > > > > This e-mail and any attachments are confidential and may be protected by > > legal, professional or other privilege. If you are not the intended > > recipient you should not store it, copy it, re-transmit it, use it or > > disclose its contents, but should return it to the sender immediately and > > delete your copy from your system. The views expressed are those of the > > sender and not necessarily those of Evadon. Please note that whilst we > scan > > all e-mails for viruses we cannot guarantee that any e-mail is > virus-free. > > Please be advised that we expressly reserve the right to monitor email > > content for the purposes of ensuring compliance with legal requirements > and > > company policies and your sending to, or receiving from, us of any email > > constitutes your agreement to these terms. > > > > > > Evadon Dynamics Limited, registered in England No. 09494097. Registered > > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, > Sheffield, > > S1 2BJ > > _______________________________________________ > > 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) > _______________________________________________ > 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/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 2 months

Re: list of subscribers

by Peter Münster

On Mon, Feb 05 2018, Simon Hanna wrote: >> from django.contrib.auth.models import User >> user = User.objects.get(email='address(a)of.user') >> print(user.first_name) >> print(user.last_name) >> >> So, I'll try to make some loop over a list with email addresses, that I >> can get on the web interface. > > These are names that are saved in Postorius' (django) database and have > nothing to do with mailman. I know, but for my use case, it's just what I want, and it seems to work. > Displaying the names stored in django probably won't happen. > Matching the names in django with the members in lists > would require lots of code Really? I don't know Python, but wouldn't it be possible (just as an option) to do something like this: user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name If there is no Django account associated to the email address, the columns would just be empty. I think, that my use case is perhaps not so special: whenever you manage a sports club, you'll need lists like - members(a)my-club.com - board(a)my-club.com - team-1(a)my-club.com - team-2(a)my-club.com - and so on Whenever there is a new member, the administrator will do the sign up with create_user(...) and subscribe him to the right lists. And the members (or the moderators) should be able to check the subscriber list sometimes. -- Peter

7 years, 5 months

Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Mailman-users search results for query "Postorius"