Search results for "2021" - Mailman-users

Re: Mixing Mailman 3 with AWS SES

by Abhilash Raj

Hi Ralph, > On Mar 17, 2021, at 5:14 PM, Ralph Weber <roweber(a)ieee.org> wrote: > > I am moving the website www.t10.org from a private/corporate VM to AWS EC2s. > > For many years, t10.org has had very happy results with using Mailman 2 for its email reflector, and I have no real concerns about moving to Mailman 3. My bugbear is the fact that I need the following mixed bag of incoming email addresses to work in concert with each other to receive and handle emails. > >> t10(a)t10.org (Primary Mailman Reflector) >> chair(a)t10.org (Mailman Reflector to direct messages to the T10 chair and his designates) > * docs(a)t10.org (document posting mechanics - serviced by a small mountain of home-grown code code) > * bbs(a)t10.org (other publicly accessible services - serviced by code that recalls the days when everything as done on a Bulletin Board System, BBS) I am not entirely sure what a “Reflector” really is. > > My best guess is that the AWS Simple Email Service (SES) needs to sit in front of both Mailman and the home-grown code, to properly direct the incoming emails to the right places. The big worry is as follows... > > All available evidence read to date suggests that the default AWS installation of Mailman 3 assumes that Mailman 3 is the *only* receiver of emails in the configuration. If true, then putting SES in front of Mailman could be a Herculean challenge. Which specific AWS installation guide are you referring to? Mailman doesn’t really care about being the only receiver of emails. Mailman can receive emails via LMTP or HTTP protocols. If you can do either of those two, you should be good. I don’t remember offhand someone sharing SES configs/setups for receiving emails, but maybe if someone did get that working, hopefully they’ll chime in. Sending out emails with SES is easy, you just need to setup the right SMTP server in Mailman’s config. -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Brian Carpenter

On 2/26/21 6:55 AM, Andreas Barth wrote: > * Lars Schimmer (l.schimmer(a)cgv.tugraz.at) [210226 10:15]: >> On 26/02/2021 00:55, Brian Carpenter wrote: >>> I have finished my how-to install Mailman 3 on Debian 10 completed to >>> the point where you can use it to get a fully functional Mailman 3 >>> environment up and running. This is a comprehensive guide that walks you >>> through installing EVERYTHING (currently!) that Mailman 3 needs to run. >>> It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have >>> not added the update directions yet but will very soon. I also plan on >>> adding a section on setting up DKIM and Xapian with Mailman 3. >>> >>> I hope this helps those who wish to get a Mailman 3 server up and >>> running quickly and brings a sense of sanity to the confusion regarding >>> the various documentation out there concerning the installation of >>> Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 >>> at some point. >>> >>> Without further ado: >>> >>> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 >>> >>> I am sure the above guide can use improvements. Feel free to contact me >>> off-list to point out mistakes/improvements, etc. >>> >> Hm, it completely ignores the standard way for Debian: >> apt-get install mailman3-full >> also exim4 as standard mailer. >> And apache2. > That's how I did it (for my first installation), and it worked out of > the box. However I would recommend to directly use a real database > (e.g. postgresql). > > > > Andi > _______________________________________________ > Except my How-to will give you the latest stable versions of Mailman 3, Postorius, and Hyperkitty and PostgreSQL instead of sqlite. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

Re: Error on timeout vs retry values

by Abhilash Raj

On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: > Hi everyone, > > I have recently setup a new mailman3 service using the venv method. > Everything is functionally working however I keep getting an error sent > to the mailman email every min which I can not seem to figure out why. > > /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: > UserWarning: Retry and timeout are misconfigured. Set retry larger than > timeout, > failure to do so will cause the tasks to be retriggered before > completion. > See > https://django-q.readthedocs.io/en/latest/configure.html#retry for details. > See https://django-q.readthedocs.io/en/latest/configure.html#retry > for details.""" > > I have edited the timeout and retry values in the > /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and > restarted both mailman and mailman-web however this still keeps repeating. You shouldn't edit files in `site-packages` directory as they are part of the package itself and could cause issues. What you want to do is override it in your settings.py (or settings_local.py) file for Django. I am not sure which guide you followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). It should look something like this https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… Just the value of retry should be just > than timeout as the error says, so not necessarily same values, but so far 300 and 360 has been working good for us and I haven't seen any report to increase them. > > Any ideas? > > Regards, > > Robert > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > 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)

3 years, 11 months

Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. > > The list is trickier. If you are going to start over with a clean > install, and if you have a config.pck that you imported from MM 2.1, I > suggest the following: > > Use the `mailman members` command to get a list of all members. Then > depending on how much work you want to do, also get separate lists of > plaintext and mime digest members and members with delivery disabled. > > Then on the new install, import the config.pck with `mailman import21` > and import the archive mboxes with hyperkitty_import. > > Run `mailman members --sync` with the full current membership list, and > record the [ADD]s. Then you can match the [ADD]s against the plain and > mime digest members and those with delivery disabled and set their options. > > That's a lot to do, but it should get you close. I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > On the other hand, if you can wait, we might be able to figure out how > to fix this, and it's even possible the underlying issue isn't database > corruption. Sure - I can wait. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

Hi again, > On 3/2/21 12:10 AM, David Partain via Mailman-users wrote: > > > > I'm not on the latest mailman, unfortunately. I use the bundled packages on Ubuntu 18.04, which are > > > > mailman3 3.1.1-9 > > mailman3-doc 3.1.1-9 > > mailman3-full 3.1.1-9 > > mailman3-web 0+20170523-14 > > > >From the mailman-web logs, it looks like it's using python2. > > That would explain a lot. I was wrong... # ps -ef | grep python | grep mailman list 22170 1 0 08:30 ? 00:00:00 /usr/bin/python3 /usr/lib/mailman3/bin/master -C /etc/mailman3/mailman.cfg list 22176 22170 0 08:30 ? 00:00:05 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 -C /etc/mailman3/mailman.cfg list 22177 22170 0 08:30 ? 00:00:05 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1 -C /etc/mailman3/mailman.cfg (etc.) However, if I look in mailman-web.log, I see lots of logging like: DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x95\\xB5\\xF0\\x9F...' for column 'content' at row 1") ERROR 2021-03-02 08:58:29,407 24297 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): File "/usr/lib/python2.7/dist- packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) Note that it's pointing to /usr/lib/python2.7/dist- packages/django/core/handlers/exception.py This could explain all of this behavior... Clearly whoever installed this box included both. So mailman core seems to be using python3 and mailman-web python2? I assume this is because /usr/share/mailman3-web/manage.py, which has: '#!/usr/bin/env python' resolves to Python 2.7.17. Should I could try changing that to '#!/usr/bin/env python3' and see what happens? :) I could also uninstall python2 but that becomes more of a nail-biter... > I suggest removing all the .pyc files and restarting the services. > That will probably recreate .pyc files, but they should then be good. Nothing was regenerated yesterday when I removed them, but that could be because of the python2 issue. Cheers, David

4 years, 4 months

Re: postorius / adjusted settings menu

by Abhilash Raj

On Wed, Mar 3, 2021, at 9:59 AM, Andreas Barth wrote: > Hi together, > > I want to adjust the settings menu to reduce to the options really > needed. > > The easiest way would be to edit src/postorius/views/list* but I don't > think that's a good idea. There is an easier way actually, you can update the forms[1] that generate those views to remove the fields you don't want to be presented. [1]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… For example, see this form for creating a new list [2]. The layout defines the fields that show up and also the order that they show up in. [2]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… So, you can add those layout to all the list settings form, each one controlled with a setting and choose the fields and their order. You won't be able to move the fields around in different groups though. > So what comes to my mind is to have some variable in the configuration > that contains the menu items and - if set - the submenus. > > E.g. the following: > { > 'list_identity': ['!gateway_to_mail', '!gateway_to_news', > '!linked_newsgroup', '!newsgroup_moderation', > '!nntp_prefix_subject_too' ], > 'automatic_responses', > 'alter_messages', > 'dmarc_mitigations', > 'digest', > 'message_acceptance', > 'archiving', > 'subscription_policy', > 'bounce_processing' > } > > would express: default menu and just remove the mentioned items. > > Of course, something like ['advertised', 'description', 'info', > 'display_name', 'subject_prefix'] would work as well. > > > Resorting should also be possible, so something like > { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } > would give a very small list of items to select from. > > > > What do you think about the idea? > > > Andi > _______________________________________________ > 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)

4 years, 4 months

Re: Docker mailman3 delete social logins, did something change?

by Abhilash Raj

On Thu, Sep 16, 2021, at 5:45 AM, bob B wrote: > for version tag you mean the docker images? > 509940b4c44f maxking/mailman-web:0.3 > mailman-web maxking/mailman-core:0.3 Yeah, the version is basically the version tag. Thanks. > > Also this works for /opt/mailman/web/settings_local.py > ************** > #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 > ******************* > > > But, > > > if I even add in one line like MAILMAN_WEB_SOCIAL_AUTH = []. so i > would have > ************** > #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 > MAILMAN_WEB_SOCIAL_AUTH = [] > *********** > > When I try to add the items in tot remove social media, It basically > acts like my /opt/mailman/web/settings_local.py. file is ignored and > does not load. Did you re-start your container after editing the settings_local.py file? It will not automatically read new configs. > I do not get debugging. The most authoritative way to see what the loaded settings are by running: $ docker exec -it mailman-web python manage.py print_settings And then look for the keys. > the log says my domian name is > not an allowed which is a sympton that this file did not load. > > > So it appears that adding a section to remove the social media apps, > stops this file from being loaded??? MAILMAN_WEB_SOCIAL_AUTH config was added in main branch but isn't released yet. The last release of 0.3.12 can be seen here[1] [1]: https://github.com/maxking/docker-mailman/blob/v0.3.12/web/mailman-web/sett… So, it basically should have no effect. If your configs are breaking due to something, it is probably not that. -- thanks, Abhilash Raj (maxking)

3 years, 9 months

Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell mailman shell -l list.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 list.example.com mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/4/21 2:09 AM, David Partain via Mailman-users wrote: >> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: >>> 1. Am I correct in assuming that I can just use my favorite editor >>> (vi) to remove the offending characters from the file? > >> No. The file is a Python pickle and you can't edit it. You would need >> to get the message and the metadata from the pickle (you could at > least >> view it with the `mailman qfile` command), edit the message and then >> re-pickle the message and metadata. > > And, in my impatience, I tried it before receiving your response and > now I seem to have done silliness in my database :( New error in > mailman-web.log: > > AttributeError: 'NoneType' object has no attribute 'subject' > > Sigh. Stupid me. If you have suggestions on fixing that... Is the file you edited still in the spool directory or is it gone? If it's still there, move it aside and see if that fixes the issue. What is the full traceback accompanying that AttributeError message from the log? > Right now, my plan is simply to remove the first message in the queue > (since I assume it'll be the "broken" one) and it'll just not be in > the archive. Life's hard. Even if I unpack 'em to edit, I'll find > mail in, for example, in base64, and I'm not going to fix the mail > by decoding, editing, re-encoding, ... Nope. Examine the messages in the spool with `mailman qfile var/archive/hyperkitty/spool/filename`. If any files throw exceptions on that, move them aside. Also, if you can see any 4-byte utf-8 encodings in the output, move that aside as well. Then see what happens after that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Blocked by Hotmail

by Morris Jones

Yes, I went through the same thing. I'm hosting at Linode, and they were very helpful. Generally Microsoft (hotmail, outlook, etc.) won't budge from their block unless the request comes from the owner of the IP address (Digital Ocean). Linode support did a great job for me. Scroll through the page referenced in the error message (https://postmaster.live.com/pm/troubleshooting.aspx#errors) and find the link to the Junk Email Reporting Program and sign up with them. Go through all the hoops. It took me about a week. Eventually they'll take a look at the email coming from your IP address and make a decision. It's such a pain to move an email server to a new IP address -- I lived with a machine with software that was so hopelessly out of date I couldn't update any packages, knowing I'd have to go through this when I rebuilt it on a new IP address. Good luck! Best regards, Mojo On 1/22/2021 4:11 PM, Tom @ Gather wrote: > I am getting rejections from Hotmail > > Jan 18 14:42:22 mail postfix/smtp[6571]: 046713F914: to=< > helen_maryd(a)hotmail.com>, > relay=hotmail-com.olc.protection.outlook.com[104.47.58.161]:25, > delay=0.14, delays=0.06/0.03/0.04/0.01, dsn=5.7.1, status=bounced (host > hotmail-com.olc.protection.outlook.com[104.47.58.161] said: 550 5.7.1 > Unfortunately, messages from [167.99.151.239] weren't sent. Please contact > your Internet service provider since part of their network is on our block > list (S3140). You can also refer your provider to > http://mail.live.com/mail/troubleshooting.aspx#errors. [ > BN8NAM11FT014.eop-nam11.prod.protection.outlook.com] (in reply to MAIL FROM > command)) > > I have submitted a ticket to > https://support.microsoft.com/en-us/supportrequestform/8ad563e3-288e-2a61-8… > > Not sure why they are blocking me. Not on any other blacklists per > mxtoolbox... > > Anyone else experienced this? How to resolve? > > My mail server is on Digital Ocean if that makes any difference. > > Thanks for any help > -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 5 months

Mailman-users search results for query "2021"