Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This my settings.py email config: #DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' # Change this when you have a real email backend # EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Mailing <mailing(a)labbrands.com>' El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

9 years, 3 months

[MM3-users] Re: Maximum number of recipients error

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:57 AM, Mark Sapiro wrote: > On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > > > "An error occured: Unknown attribute: max_num_recipients" > > > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? > > > It works for me. It was added by > <https://gitlab.com/mailman/postorius/merge_requests/358>, but it > requires Mailman core >= 3.2.1. What's in the docker image you're using? > This may be an issue for <https://github.com/maxking/docker-mailman>. It is an issue for images repo. I haven't yet updated to the latest releases, sorry! > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 7 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

and: When I put the stanza >> [language.en] into the mailman.cfg, the service doesn’t restart: … PermissionError: [Errno 13] Permission denied: '//var/templates' somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Mark Sapiro wrote: >> >> You can change this for English by putting >> >> [language.en] >> charset: utf-8 >> >> in your mailman.cfg. This works because us-ascii is a proper subset of >> utf-8. > > > I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. > _______________________________________________ > 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/

7 years, 10 months

[MM3-users] Re: installation choices for mm3

by Mark Sapiro

On 5/16/19 10:33 AM, John Griessen wrote: > I've been reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > > and see that a virtual is recommended, which is not something I have > done yet, and wonder > if just putting the mm3 on a different server is easier? I am the author of that document. I started with virtualenv because my first Mailman 3 installation used the now obsolete mailman-bundler and it installed things in virtualenvs. It is not at all necessary to use virtualenv. Note that the first paragraph of the "Installation" section in that document says: For these installs, I opted to install the entire Mailman suite in a virtualenv. The biggest motivation for this choice was the fact that there are already production lists on both servers and using a virtualenv allowed me to do a lot of the work in advance without interfering with the production install. Possibly influenced by these experiences, I am now using virtualenv for all installs. There are pros and cons to using a virtualenv. The big plus is it isolates your installation and avoids conflicts due to the installed software requiring versions of dependencies that are different from those that might be installed and required system wide. It also avoids the need to install as root although things like web server and MTA configuration still require root. The downside is a potentially larger footprint in the file system. > I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, > mm2, nsd on it. Another server has just web pages and nsd doing backup > DNS for mail1.cibolo.us DNS server. I could do a straight debian > install of mailman3-full on the 2nd server > and keep it simple, let debian setup a blank database installation, > right? Has anyone seen a good write up on how to do that on a debian > server step by step? I can't speak to the installation of the Debian package. It should be straightforward, but I don't really know. The one potential glitch is if you don't have an MTA on the Mailman server. This is doable. Mailman has it's own LMTP server to receive mail and can be configured to use a remote MTA to deliver mail. Mailman also generates transport mappings to control delivery of mail to Mailman and these get updated when lists are added or deleted. There is a configurable postmap_command which is invoked when the maps are updated to update the .db files. That can point to a shell script to rsync the files to the other server if needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Post-installation documentation?

by David Newman

On 11/26/21 10:21 AM, Mark Sapiro wrote: > On 11/26/21 9:49 AM, David Newman wrote: >> On 11/25/21 1:16 PM, Mark Sapiro wrote: >>> >>> What django admin command are you running? >> >> As the mailman user, with venv activated: >> >> (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com >> /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox > > > hyperkitty_import is not a command. it is a subcommand to the django > administration command. You need to run > ``` > mailman-web hyperkitty_import -l testlist(a)lists.domain.com > /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox Bingo. Thank you! When running the subsequent 'mailman-web update_index_one_list' command to index the imported archive, the command failed with a permissions error on '/opt/mailman/web/fulltext_index' because that directory didn't yet exist. Creating that directory and chown'ing it to mailman resolved that. I'm still getting an error from the list page when clicking archives, but I'll investigate further and open a new thread if needed. Let's close this already overly long thread here. Thanks *very* much for your patience in resolving the import issue. If nothing else this is good fodder for an eventual admin guide. dn

4 years, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can I use it for mailing lists? like MailChimp? El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:07 PM, Rafael Mora wrote: > > I want to use Mailman to send emails to our customers. > > > So you need to create a list and add your customers as members. > > Please note that Mailman is not a substitute for a customer relations > management system. It can be used in that way, but a true CRM system has > advantages ove Mailman. Mailman is primarily designed to support > discussion lists such as this one. > > > > I´m getting this error when I click on sign up and log in: > > > > FilterError at /accounts/login/ > > /bin/sh: sassc: command not found > > > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > -- > 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

9 years, 3 months

[MM3-users] Re: footer message

by Henrik Rasmussen

From lists imported by import21, the colon in the files are substituted with underscores. Instead of list:member:regular:footer.txt the file are called list_member_regular_footer.txt And I wonder why having a footer text makes the mail contain the original HTML message sent to the list as attachment both in .txt and .html and the footer-text from list_member_regular_footer.txt as inline message. 'collapse_alternatives': False, 'convert_html_to_plaintext': False, 'filter_content': False, 'include_rfc2369_headers': True, 'posting_pipeline': 'default-posting-pipeline', -- Henrik Rasmussen her(a)adm.ku.dk University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 1. september 2018 20:17 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: footer message On 09/01/2018 10:51 AM, Abhijith PA via Mailman-users wrote: > > If I understand correctly, temp@lists.example.com:member:regular:footer > file need to created for /temp mailinglist/ ? Not exactly. Assuming default settings and English the file would go in Mailman's var/ directory at var/templates/lists/temp.lists.example.com/en/list:member:regular:footer.txt -- 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/

8 years, 1 month

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

1 year, 7 months

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I get the same error as before: Did you post this traceback before? If so, I missed it. > root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c > "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r > lmtp" > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Traceback (most recent call last): > File "/usr/local/bin/runner", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', > 'runner')()) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1128, in __call__ > return self.main(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1053, in main > rv = self.invoke(ctx) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1395, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 754, in invoke > return __callback(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/decorators.py", > line 26, in new_func > return f(get_current_context(), *args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 184, in main > runner = make_runner(*runner_spec, once=once) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 70, in make_runner > return runner_class(name, slice) > File > "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line > 295, in __init__ > self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, > port=port) > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 417, in __init__ > self._localhost = get_localhost() > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 66, in get_localhost > with makesock(AF_INET6, SOCK_STREAM) as sock: > File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ > _socket.socket.__init__(self, family, type, proto, fileno) > OSError: [Errno 43] Protocol not supported > The issue is in aiosmtpd which is trying to determine if it can use IPv6 "::1" for localhost. It does this before it checks if we've provided a hostname which we have. The issue is in aiosmtp/controller.py in the get_localhost() function, but it's even deeper than that in socket which is raising the Protocol not supported error. There is something strange on your server in that IPv6 seems to be only partially supported. I don't know for sure what the underlying issue is, but look at https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49 Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages directory and change that return has_ipv6 line to return False to work around the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 11:00 AM, Mark Dadgar wrote: > On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >> everytime I receive a mail for moderation it says: >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. There's no overall dashboard per se. The message actually refers to whatever web UI you use to manage the list. The default template for this message is non-specific because it comes from Mailman core, and core doesn't know if you are using Postorius or some other web management system or non at all, and even if it were to assume Postorius, it doesn't know the URL. >> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >> >> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? As I said, there is no overall dashboard in Postorius, just the individual list management pages. > This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. I explained above why this is the case, but you can fix it. You do so by making a sitewide template for this message. In the case of this list, we have a template in Mailman's var/templates/site/en/ directory (the default directory for sitewide english templates. This template is named list:admin:action:post.txt and its content on this site is: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: $listname > From: $sender_email > Subject: $subject > > The message is being held because: > > $reasons > > At your convenience, visit > https://lists.mailman3.org/mailman3/lists/$list_id/held_messages Of course, in your case the <https://lists.mailman3.org/mailman3/> part of the URL will be different. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> for the other templates I also install. You can also put domain specific templates in var/templates/domains/$domain/$lc/ which override site templates for the domain and list specific templates in var/templates/lists/$list_id/$lc/ which override site and domain templates for the list, and you can also set list templates via Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: why owner mails rerouted to list

by Mark Sapiro

On 10/22/19 2:20 AM, Tamas HOLCZER via Mailman-users wrote: > Hi All, > > we have moved to Mailman3 from Mailman2 recently, and have a quite > strange problem: > > Every message sent to owners is forwarded to the lists instead of the > owner's mail address. ... > We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian > Buster repo. As MTA we use exim4 (running on the same machine as > Mailman), and have Amavisd on a separate machine for spam filtering. This may be an exim configuration issue. You can stop the mail from being delivered to the list by ensuring the Postorius Settings - Message Acceptance -> Acceptable aliases is empty and Settings - Message Acceptance -> Require Explicit Destination is Yes. This will cause the messages to -owner, etc to be held. First ensure exim, particularly the router for list messages is configured as in <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim4-co…>. > From MYLIST-bounces(a)MYDOMAIN.COM Mon Oct 21 21:13:59 2019 > Return-path: <MYLIST-bounces(a)MYDOMAIN.COM> > Envelope-to: MYADDRESS(a)MYDOMAIN.COM > Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 > Received: from [SPAMFILTER] (helo=localhost) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 > X-Virus-Scanned: by amavis-dc > Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) > by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) > with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 It seems the issue occurs here. The Received: header below is the receipt of the message from Mailman to MYLIST-owner. That header clearly says the envelope recipient is MYLIST-owner(a)MYDOMAIN.COM. Then the header above looks like the delivery of the message from the Mailman list to one or more list members. What we don't see is the intermediate step of LMTP delivery of the message to Mailman's LMTP server. That delivery must have had envelope recipient MYLIST(a)MYDOMAIN.COM rather than MYLIST-owner(a)MYDOMAIN.COM I think what's missing is `rcpt_include_affixes = true` in the exim transport for Mailman. > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7r-0007pR-JZ > for MYLIST-owner(a)MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 > From: MYLIST-owner(a)MYDOMAIN.COM > To: MYLIST-owner(a)MYDOMAIN.COM -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/24/23 9:54 PM, Ken Alker wrote: > I am working on a mail server that was migrated from mailman V2 to > mailman V3 in February. I just noticed that there are over 1000 > messages in the bad queue. All of the messages in the bad queue are > dated 2/2/23 and all have a timestamp within a one-hour window of each > other. > > I used mailman qfile to inspect five random emails in the bad queue and > so far they are all "successfully subscribed" emails, This is a bit strange. See below. > but I presume > there are no guarantees there aren't others mixed in there that might be > legitimate emails (ie. I just unshunted 140 emails in the shunt queue > and they were all good emails and all got processed). Presumably these were shunted due to some issue that was subsequently fixed. > I figure that the easiest way to inspect these 1000 emails is just to > have them re-delivered. I tried moving one from the bad queue to the > shunt queue and I ran "mailman unshunt" but nothing happened. What does nothing happened mean? "mailman unshunt" should move the message to the original queue which was stored in the 'whichq' attribute in the msgdata when the message was shunted. Since this wasn't a shunted message, there's no 'whichq' attribute so it goes to the 'in' queue. I.e., "mailman unshunt" would have moved the message from the 'shunt' queue to the 'in' queue. If the message wound up back in the shunt queue, there should be messages in mailman.log indicating why. > Is there a way to reprocess the bad queue? You could just move the messages to the 'in' queue. > Also, what exactly is the bad queue? If Mailman's content filtering is enabled and Filter Action is Preserve, messages which have no remaining content after content filtering are put in the 'bad' queue. These are the only messages put there. When this happens there should a log message like <message-id> preserved in file base <queue_file> It is unclear to me how these 1000+ messages wound up in the 'bad' queue. If you have logs from Feb 2, they might help. My guess is there was some MTA misrouting that caused these list welcome messages (from some mass subscribe?) to be rerouted to the list posting address combined with some bad content filtering settings that removed all the content, but that seems pretty far fetched. -- 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

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

If this has been implemented already then that’s good. I have not tested with latest. Does this also happen when a user unsubscribes or a list admin unsubscribes? > On Oct 28, 2020, at 1:29 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. > > -- > 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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I could setup env with python3 and env2 with python 2.7 I visited http://192.168.1.42:8000 in my browser and I could not see the web UI. Should I install WSGI server?? doing: pip3 install uwsgi ??? Thanks El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:44 PM, Rafael Mora wrote: > > I did this: > > > > (env) [mailman@localhost mailman-suite_project]$ pip install Django > > Requirement already satisfied: Django in > > /var/lib/mailman/env/lib/python3.6/site-packages > > Requirement already satisfied: pytz in > > /var/lib/mailman/env/lib/python3.6/site-packages (from Django) > > > > > > Does Django is already installed?? with python3.6 ??? > > > Your 'env' vitrualenv is a Python 3 virtualenv. You need this for > Mailman core, but Django and mailman-suite are Python 2. They need to be > installed and run in a Python 2 virtualenv. > > -- > 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

9 years, 3 months

[MM3-users] Re: Hyperkitty failure?

by Stephen Daniel

Thanks! The thread pointed to at the end of your email, specifically replacing the base URL with http://127.0.0.1:8000/archives did the trick. On Thu, Feb 24, 2022 at 1:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/24/22 09:24, Stephen Daniel wrote: > > > > In the log I see messages that look like this: > > > > Feb 24 11:43:44 2022 (28621) HyperKitty failure on > > https://lists.example.com/archives/api/mailman/archive: <html> > > <head><title>401 Authorization Required</title> > > > What are the exact versions of HyperKitty and mailman-hyperkitty > HyperKitty >=1.3.5 requires mailman-hyperkitty >=1.2.0. Earlier versions > of HyperKitty require earlier versions of mailman-hyperkitty. > > If you have HyperKitty >=1.3.5 and > mailman-hyperkitty >=1.2.0 there is a thread on this at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > See the last two posts in that thread. > > -- > 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/ >

4 years, 8 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/27/20 9:52 PM, joseverde(a)gmail.com wrote: > The settings match the Django settings, yes. As far as the rest runner, the following shows on that command: > > root 25868 25475 0 21:50 pts/0 00:00:00 grep --color=auto runner=rest So the rest runner is not running as all you see is your grep command. On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: > On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: >> And one last infopoint for tonight, I checked on a whim to see if mailman3 was still running, it wasn't since the last time I checked. (the command mailman status, on the other hand, shows it is up and running. The following error was shown when starting to start: >> >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 88, in process >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: status, lock = master_state() >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 133, in master_state >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: hostname, pid, tempfile = lock.details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 145, in details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: with open(self._lockfile) as fp: >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/master.lck' >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Control process exited, code=exited status=1 >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Failed with result 'exit-code'. >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: Failed to start Mailman3 server. >> It appears there is a permissions issue in trying to read the locks. Does your systemd script set the user to the Mailman user, and does the Mailman user have read/write permission on Mailman's var/locks/? Also, is any of Mailman core running? Try ps -fwwA|egrep 'master|runner' If a master is running, try service mailman stop If that doesn't stop it, send it a sigterm or, only if necessary, a sigkill. Then if there are an runners left, sigterm them. Finally if there's anything in var/locks, remove it. Then try to start Mailman. Note that if you've previously started Mailman as root, there may be locks and or other files owned by root that are now inaccessible to mailman. You may need to `chown -R mailman` in Mailman's var directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Stefan Bauer

Mother: Anonymous list: No First strip reply to: No Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Daughter: Anonymous list: No First strip reply to: Yes Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Am Mi., 24. Nov. 2021 um 21:53 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/24/21 2:05 AM, Stefan Bauer wrote: > > That is already set. No change. > > This completely removes the reply-to: header and sets the iu-all > > list-address as new and only reply-to. > > > What are your current settings on both the mother and daughter lists for > Anonymous list, First strip reply to, Reply goes to list and under DMARC > Mitigations for DMARC mitigation action and DMARC Mitigate unconditionally? > > > -- > 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/ >

4 years, 11 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/12/22 11:45, David Newman wrote: > > To rule out the smtp module, I sent a PGP-signed message using a > different MUA (Thunderbird, in my case). Mailman3 accepted this post > without complaint, and I reported back to list users that this appears > to be an Apple Mail encoding issue. > > Normally, that'd be the end of it. But this is a list for a bunch of > Internet graybeards, including one of the authors of the SMTP protocols > and the subscriber is a former IETF chair. He's grumbling that if this > really were an Apple Mail issue, wouldn't it be far more widespread? Maybe, but who knows. The issue is with at least macOS 12.0.1, Mail.app Version 15.0 (3693.20.0.1.32), and GPG Mail 6.0, Build 2023. That combination at least produces multipart/signed messages with multipart/* parts containing a Content-Transfer-Encoding: header. The Python 3 email library considers this to be a InvalidMultipartContentTransferEncodingDefect() message defect. I had a long exchange with Barry Warsaw about this. an excerpt is It's definitely an Apple Mail issue. Both the message you sent and the original message part have the same defect: InvalidMultipartContentTransferEncodingDefect() Also, My Thunderbird MUA wouldn't display the message content at all. Interesting though that your original message was also signed and sent by Apple Mail and didn't have the defect. It's structure was multipart/signed multipart/alternative text/plain text/html application/pgp-signature and none of the multipart parts have Content-Transfer-Encoding. The follow up you sent with the original message was multipart/signed multipart/mixed * text/plain message/rfc822 (the attached message) * multipart/signed * text/plain application/pgp-signature text/plain (an empty plain text part) text/plain (a quote of my message to you) application/pgp-signature All the asterisked parts have a Content-Transfer-Encoding header which is the defect. It seems to be related to the presence of the empty text/plain part following the signature. > I don't think it would be, because (a) Mailman2 is still far more > pervasive than Mailman3 and (b) the combination of PGP signing and Apple > Mail on MacOS and Mailman3 is still pretty unusual. > > Has anyone else hit this encoding issue, other than the post above? And > did Mailman2 silently accept this because it was less strict about > checking for bad encoding? To my knowledge it's only been hit by Barry and the poster of the original report Mailman 2.1 is has the Python 2 email package which doesn't report InvalidMultipartContentTransferEncodingDefect(). I reported it in November at https://feedbackassistant.apple.com/feedback/9768496 which is open with no reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Does this have anything to do with the problem?: (env) [mailman@localhost logs]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project/logs (env) [mailman@localhost logs]$ tail -f mailmansuite.log File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 204, in hunks precompiled, value = self.precompile(value, **options) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 265, in precompile return True, filter.input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sassc: command not found Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

9 years, 3 months

[MM3-users] Re: MIME Digests with posts and index inline likewise Plain Text Digests

by Mark Sapiro

On 1/18/19 5:11 AM, Henrik Rasmussen wrote: > Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. > > Would it be possible for Mailman to send both posts and index inline in the MIME digest? The format of the MIME digest is specified by RFC 2046 which defines the multipart/digest format in section 5.1.5. This defines the MIME digest as a multipart/digest message part containing the individual messages as message/rfc822 sub-parts. It also says (after spelling corrections - ErrataID: 510): Note: Though it is possible to specify a Content-Type value for a body part in a digest which is other than "message/rfc822", such as a "text/plain" part containing a description of the material in the digest, actually doing so is undesirable. The "multipart/digest" Content-Type is intended to be used to send collections of messages. If a "text/plain" part is needed, it should be included as a separate part of a "multipart/mixed" message. The MIME format digest Mailman produces has the structure multipart/mixed text/plain the "masthead" text/plain (only if a digest header) the digest header text/plain the table of contents multipart/digest message/rfc822 the first message message/rfc822 the next message ... message/rfc822 the last message text/plain (only if a digest footer) the digest footer The only change that could be made while keeping the digest compliant would be to combine the masthead, digest header if any and table of contents in a single text/plain part. While this might solve the the issue of the table of contents being an "attachment" in some MUA's rendering, it won't address the larger issue of the messages being rendered as attachments. As you note, Gmail's web mail does an OK job of rendering the MIME digest as do other mainstream MUAs such as Thunderbird. The real solution is for those people who insist on using non-compliant MUAs to subscribe to the plain format digest. The whole point here is if you want a digest which has everything in line, that's what the plain text digest is. If you want a digest which maintains the original structure of the messages without flattening them to plain text, the messages have to be separate message/rfc822 parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is the content of my /var/log: [root@localhost log]# pwd /var/log [root@localhost log]# ls anaconda grubby messages-20170716 spooler-20170710 audit grubby_prune_debug messages-20170723 spooler-20170716 boot.log httpd mysqld.log spooler-20170723 btmp lastlog php-fpm tallylog btmp-20170701 letsencrypt ppp tuned chrony maillog rhsm wtmp cron maillog-20170702 samba xferlog cron-20170702 maillog-20170710 secure xferlog-20170702 cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 cron-20170723 mailman secure-20170716 xferlog-20170723 dmesg messages secure-20170723 yum.log dmesg.old messages-20170702 spooler firewalld messages-20170710 spooler-20170702 El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/22/2017 05:29 PM, Rafael Mora wrote: > > > > How can I config Mailman/Postfix to send the confirmation email for the > > superuser I created this morning??? > > > What is in Postfix's logs relevant to the attempt to send the mail > (probably /var/log/mail.log)? > > What is the output from 'postconf -n' > > -- > 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

9 years, 3 months

[MM3-users] Re: Accept these non-members

by Mark Sapiro

On 3/6/26 12:52, Lars Bjørndal wrote: > Thanks! You wrote: > >> On 3/6/26 02:43, Lars Bjørndal wrote: >>> Hi, list! >>> >>> I have an announce only Mailman3 list. When I log into the web interface >>> as an admin user, and go to the specified list, and choose Settings, I find >>> the Message Acceptance tab. There, I find the edit field Accept these >>> non-members. But this field is empty, although I know that some people >>> have permissions and are able to post to this list. How can I find the >>> list of these non-members and add more people or delete someone? >>> >>> I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. >> >> I don't know what mailman-web version 4.2.21 is. Is this some downstream >> package? > > With `pip list`, some of the packages is: > > Django 4.2.21 > django-mailman3 1.3.15 > HyperKitty 1.3.12 > mailman 3.3.10 > mailman-hyperkitty 1.2.1 > mailman-web 0.0.9 > mailmanclient 3.3.5 > postorius 1.3.13 So your mailman-web is 0.0.9 and it's Django that's 4.2.21. I understand. >> These are nonmembers whose moderation action is accept or defer. If your >> Postorius is >= 1.3.6, and the number of nonmembers is manageable you can >> just view the nonmembers list in Postorius and see their moderation action. > > You mean from the web interface at example.com/mailman3 > list? Yes >> Otherwise a `mailman shell` interaction like >> ``` >> $ 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 >>>>> for nm in m.nonmembers.members: >> ... if nm.moderation_action in (Action.accept, Action.defer): >> ... print(f'{nm} {nm.moderation_action}') >> ... >>>>> >> ``` >> will print those nonmembers with Action.accept or Action.defer. > > What's the difference between Action.accept and Action.defer? Action.accept accepts the message immediately with no further checks. Action.defer passes the membership checks but still goes on to check other things like mis-addressed email commands messages with implicit destination messages with too many explicit recipients messages that are bigger than a specified maximum messages with no, or empty, Subject headers messages with digest Subject or boilerplate quote messages matching a bounce_matching_header line -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: New install - The Message have no valid senders

by Mark Sapiro

On 3/30/22 04:30, kenneth.karlsson(a)eco.cept.org wrote: > > The command: > EHLO contoso.com > mail from: <xxx(a)xxx.com> > rcpt to: <mhtest(a)list.cept.org> > DATA > This is a test message > . Some headers in the message might be nice. > Accepted by Postfix: > Mar 29 11:17:17 lits01a postfix/smtpd[4088]: B86DD6A04B9: client=unknown[192.168.200.157] > Mar 29 11:17:30 lits01a postfix/cleanup[4091]: B86DD6A04B9: message-id=<> In my case, Postfix adds a Message-ID: header and logs it here. > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: from=<xxx(a)xxx.com>, size=200, nrcpt=1 (queue active) > Mar 29 11:17:30 lits01a postfix/lmtp[4109]: B86DD6A04B9: to=<mhtest(a)list.cept.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=24, delays=24/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: removed > > MM receives it: > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) handling connection > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'LHLO list.cept.org' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'MAIL FROM:<xxx(a)xxx.com>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) sender: xxx(a)xxx.com > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'RCPT TO:<mhtest(a)list.cept.org>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) recip: mhtest(a)list.cept.org > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'DATA' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'QUIT' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) connection lost > Mar 29 11:17:30 2022 (3940) Connection lost during _handle_client() These log messages come from aiosmtpd which is used by mailman/runners/lmtp.py to implement Mailman's LMTP server. Clearly, aiosmtpd sees the envelope sender as xxx(a)xxx.com, but > But MM3 discards it: > Mar 29 10:08:03 2022 (1767) DISCARD: <164854848338.1768.3954079936807939297@lits01a>; ['The message has no valid senders'] This is because Mailman's NoSenders rule gets an empty response from the messages `sender` method. This means there is no address in any of the messages From:, Reply-To: or Sender: headers which is expected, but it also says that the message's get_unixfrom() method didn't return an address as this is checked between From: and Reply-To:. I tried a similar test, but in my case, Postfix (3.4.13) added Message-Id:, Date: and From: headers, so that wasn't definitive, but I then added logging to the LMTP runner at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… to log the unixfrom and the message and the message did have a unixfrom as added by the LMTP runner, so even without the Postfix added header, it had a sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' I have checked if there is already a subscription with that email address, but that's not the case. Best Regards,Eric On Thursday, January 14, 2021, 08:43:54 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/9/21 5:39 AM, Eric Broens via Mailman-users wrote: > For one of our mailinglists we also have a problem with accepting a subscription request. > When Clicking "Accept", we get a 404 Not found error. > See the attached screenshot. > Is there a way to solve this? Content filtering removed your screenshot so we can't see it. What is the URL that gives the 404? How does this compare to the URL of the held message view? -- 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/

5 years, 9 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/10/19 5:35 AM, Marvin Gülker wrote: > Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > >> I would guess this is in the shunt queue. If there's only one file >> there, you can just delete it. The issue in this case is not a shunted message. it is a message held for moderation. The message itself is in Mailman's var/messages/ directory. It is pointed to by an entry in the database 'message' table. The var/messages/ directory contains two levels of subdirectories and the message files. The file name is the message-id hash. The first subdirectory is the first two characters of the name and the second subdirectory is the next two characters of the name. E.g. a message with message-id hash = UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X will be stored as a pickle in the file var/messages/UP/ZX/UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X. The underlying issue here is probably <https://bugs.python.org/issue32330>, but that knowledge doesn't help us. We need to get rid of the offending message in the message store. The first step is in mailman shell. Note the paths /opt/mailman/mm/bin/ and /opt/mailman/mm/var/ will need to be adjusted. /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/opt/mailman/mm/var/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID-Hash']) ... This should print the file name and Message-ID-Hash (two lines the same) for each message in the messages directory until it prints only one line followed by the UnicodeEncodeError exception. That list line is the file name/Message-ID-Hash of the offending message. Then you need to run the query DELETE FROM message WHERE message_id_hash = xxx; against the mailman database where xxx is the hash value you found above. > I confess that I haven't visited the held messages page for a very long > time (because I didn't have a reason to; I received no notifications of > held messages). Only after I received the notification that my > errorneous message was being held, I visited it, and I was faced with > the 500 error. If Mailman failed to notify me of held messages > previously, they might have been in hold status already and one of them > might be the cause. As of Mailman core 3.3.0 there is a 'mailman notify' command designed to be run periodically by cron to notify owners/moderators of prnding requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Michael Sage

Thanks for your tip about digging deeper into the logs! Turns out it was a postfix issue (the hash files hadn't been created), which was causing it to loop and crash out. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: 12 June 2019 17:56 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup On 6/12/19 9:53 AM, Michael Sage wrote: >> This seems like something I've seen reported before, but I can't find it now. > >> Is anything logged in the various Mailman, Django, Apache logs? > > Nothing at the time in the Mailman, Mailman web or apache (error or > access) logs, I can't find any Django logs I am afraid. I only have > standard logging, happy to turn any debugging logging that you think > might help The Django log is most likely the one named mailman_web. -- 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/

7 years, 4 months

[MM3-users] Re: list owner creation

by Christian Stalberg

Via Postorius. I added the user back using the same page. Thank you! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, February 21, 2021 4:29 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list owner creation On 2/21/21 4:15 PM, Brian Carpenter wrote: > On 2/21/21 6:50 PM, Christian Stalberg via Mailman-users wrote: >> If one inadvertently deleted a list owner account, how could one >> either create a new account and make them a list owner -or- make an >> existing account a list owner? Thanks! > > Are you talking about deleting the account via the Django admin > interface or via Postorius? > Yes, the answer depends on what you did and what tools you have available. For example, if you deleted the owner via the Delete button on the page at <https://example.com/mailman3/lists/list.example.com>/members/owner/>, you can add it back on the same page. You need to tell us what you did. -- 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/

5 years, 8 months

[MM3-users] Re: Cannot Run Web Frontend

by Mark Sapiro

On 12/26/25 08:02, dap1--- via Mailman-users wrote: > SELECT name FROM hyperkitty_mailinglist; > +--------------------------+ > | name | > +--------------------------+ > | lllllllll(a)ddddddddd.net | > | lllllllll(a)gmail.com | > +--------------------------+ > 2 rows in set (0.00 sec) > > It seems just deleting lllllllll(a)ddddddddd.net is non-trivial. > Cannot delete or update a parent row: a foreign key constraint fails (`mailmanweb`.`hyperkitty_email > `, CONSTRAINT `hyperkitty_email_mailinglist_id_2c2b6f03_fk_hyperkitt` FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperki > tty_mailinglist` (`id`)) This is not a critical issue so you can just ignore it until you get the web UI working at which time a Django superuser or the list owner can delete the list in HyperKitty's web UI. If you want to do it in the database, I think you can first do DELETE FROM hyperkitty_attachment WHERE hyperkitty_attachment.email_id IN (SELECT id FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net')); to delete attachments and then do DELETE FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net'); to delete the emails and finally DELETE FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net'; But this may possibly run into other foreign key constraint issues. It's probably easier to get the web UI up and do it there. > netstat -lntp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 1103/systemd-resolv > tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1407/mysqld > tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1644/smbd > tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1644/smbd > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 74794/python3 > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 74791/python3 > tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 1103/systemd-resolv > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 74696/master > tcp 0 0 0.0.0.0:26 0.0.0.0:* LISTEN 1/init > tcp 0 0 127.0.0.1:33060 0.0.0.0:* LISTEN 1407/mysqld > tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 160003/cupsd > tcp6 0 0 :::443 :::* LISTEN 132763/apache2 > tcp6 0 0 :::445 :::* LISTEN 1644/smbd > tcp6 0 0 :::139 :::* LISTEN 1644/smbd > tcp6 0 0 :::80 :::* LISTEN 132763/apache2 > tcp6 0 0 :::25 :::* LISTEN 74696/master > tcp6 0 0 :::26 :::* LISTEN 1/init > tcp6 0 0 ::1:631 :::* LISTEN 160003/cupsd > > I'm not using IPV6. Nothing is listening on 8000, just 8001 and 8024. > > It appears that guicorn is not running if there is supposed to be a process by that name. There is also no such service. See https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… Particularly the part that says: If using Gunicorn, the ExecStart line above becomes: ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application Do you have that and is the mailmanweb service running? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Mark, Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow. Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image. The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error... Now answering your questions: ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? > I've checked settings.py inside the container and I haven't found any of the mentioned configurations there. Does the manage.py that's being run here point to the right settings.py? > No clue. Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image? https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Danil > -- > 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/ >

7 years, 8 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:15 PM, Rafael Mora wrote: > > > > Should I configure my private Centos7 server with subdomain > > lists.labbrands.com? > > Doing so how do I redirect the email to the private Centos where postfix > > and MM3 are installed? > > > Create a DNS A record for lists.labbrands.com with the IP of the Mailman > server. You will also want a rDNS PTR record pointing from the IP to > lists.labbrands.com. > Does the rDNS PTR record should be placed in my Centos7 server? 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????? > > -- > 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

9 years, 3 months

[MM3-users] Re: Mailman will not restart

by Christian

Yes, thank you Mark & Peter. I did that and also eliminated locks that were appearing and it is now working. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, March 8, 2023 3:10 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman will not restart On 3/8/23 12:34, peter(a)chubb.wattle.id.au wrote: >>>>>> "Christian" == Christian via Mailman-users <mailman-users(a)mailman3.org> writes: > > Christian> , line 36, in <module> Mar 08 20:17:45 > Christian> zarathustra.ccalternatives.org mailman[31893]: from > Christian> typing_extensions import Concatenate as Concatenate # 3.10 > > You probably need to update the typing_extensions package. inside your > venv. Yes, but why? Something upgraded sqlalchemy > 2.0 but didn't install all its dependencies. The latest versions of sqlalchemy require typing-extensions but sqlalchemy<2.0 didn't require that. So in the venv, `pip install typing-extensions` will probably solve this. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ 2SXACQYNAHYSUYY4G33PQQDJKKAIBZZM/ This message sent to csa(a)web-analysts.net

3 years, 8 months

[MM3-users] Re: Mail control not given from Mailman 3 to postfix

by Mark Sapiro

To follow up, I received the traceback and the dump of the shunted message off-list. The traceback is ``` Jul 07 21:36:47 2020 (26815) Uncaught runner exception: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues) TypeError: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) SHUNTING: 1594138007.5613732+1a5932f41fb4cfcd18c9b0b0ac6f999c84408577 ``` This was apparently caused by an invalid RFC 2047 encoded To: header which encoded the entire header including the address as one base64, unknown-8bit character set encoded word. However, despite trying with several different Python versions, I was unable to recreate the TypeError, so the reason for this exception remains unknown.

6 years, 4 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 1:37 PM, Ruth Ivimey-Cook wrote: > Thanks Mark, Ignore bracketed numbers below ([1], [2], etc.) They come from conversion of the HTML only post to plain text. > On 20/06/2020 03:53, Mark Sapiro wrote: > > What are your Django settings for MAILMAN_REST_API_URL, > MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with > the [webservice] settings for hostname, port, use_https, admin_user and > admin_pass in mailman.cfg in core and is the port open to the outside on > the core machine? > > greyarea-post is the mailman-core and exim server. > > greyarea-web1 is the postorius and hyperkitty server. > > On greyarea-web1, in django-settings.py, > > MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = XXXX > > and both the above-named hosts are also included in ALLOWED_HOSTS along > with localhost. > > On greyarea-post, in mailman.cfg: > > [webservice] > admin_pass: XXXXX > admin_user: restadmin > api_version: 3.1 > hostname: 0.0.0.0 > port: 8870 > use_https: no > > The password and username are as on web1. That all looks good. > Do you see REST requests from the Postorius machine in core's > mailman.log and access.log? > > Yes, there are lots of requests of the form: > > [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 > HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" > > I made a new list using the core CLI, and as a result of navigating > directly to the list archive page I get to see: > > [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk > HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" > > ... but in neither case do I get a complete screen on the browser or > 'follow-up' requests. > > I don't have a file access.log on the greyarea-post. Yes, that's actually a gunicorn log so would only be on greyarea-web1, but the mailman.log tells us the requests are getting to the core REST API, so we don't need that info. > On the greyarea-web1 I have mailmansuite.log with the last few lines: > > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba > se.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co > nnection.py", line 124, in call > 'Could not connect to Mailman API: ', repr(e)) > mailmanclient.restbase.connection.MailmanConnectionError: ('Could > not connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > ERROR 2020-06-03 01:02:06,115 29002 django.request Service > Unavailable: /postorius/lists/ OK. This is telling us that mailmanclient (the REST API Python bindings that Postorius uses to access core) is having trouble establishing a connestion to the core REST server, but it clearly gets there some of the time based on the mailman.log entries. > the uwsgi-error_*.log contains many lines of the form: > > api: url is > [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > api: url is > [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > > My reason for thinking, in my original post, that the wrong host > address is being used is that the ConnectionError above contains > 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as > the listen address on the core web service and does not appear in the > config for postorius. The ConnectionError above comes from requests.request (docs at <https://requests.readthedocs.io/en/master/>). Client only provides a URL in the call to request and the URL is the baseurl + the path and the baseurl is MAILMAN_REST_API_URL which you have as http://greyarea-post:8870. Entries above have http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? I suspect a DNS lookup issue. How does greyarea-web1 resolve greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS rather than relying on /etc/resolv.conf and/or /etc/hosts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: moving list from mm3 -> mm3

by Mark Sapiro

On 12/8/23 08:01, Jens Günther wrote: > > This is a nice collection of the configuration of a certain list. Does > anybody know how I would get this data back to the newly created list in > the second working mm3-instance? Shouldn't it be possible via POST > command? I thought of something like: > > curl -u restadmin:restpass -d @short.domain -H "Content-Type: > application/json" localhost:8001/3.1/lists/&short.&domain/config > > But it returns {"title": "405 Method Not Allowed"} and I don't know > where to look in the docs, since it shows almost always a way through > mailman shell. You need a PUT command, not POST. Try the above with `-X PUT`. > ## Members, moderators, owners > > To export all members I normally run within mm-core-container as user > mailman the following command: > > mailman members &short.&domain > &short.txt > > To fill them back in, it can be done in Postorius (or is there a way > through API?). You can use Postorius -> Mass operations -> Mass subscribe to add the members, but you can't do that for owners and moderators. Also you lose information about the members such as Delivery status, Delivery mode and other user settings. > What I would love to know is how to get out Owners of the corresponding > lists and reimport them in the new one (which will be the same at the > end :-D but different instance). You can use the --role option with `mailman members` to get owners and moderators, but short of a custom script, you have to add them manually. > ## registered users > > This part is somehow tricky, since I have no clue how to do it. Some of > the mailinglist-admins don't want to bother their list-owners again with > registering newly on the other system. Is there a way to export all > users (I think I found them in the DB in the table auth_users, somehow > in combination with account_emailaddress) and get them over to the new > instance (actually I just need part of them, but that's another question > that I might solve lateron on my own). > > Maybe the answer is already here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > -> but can somebody help to get this working (import/export)? That is not the answer. Those are Mailman core users, not Django (web login) users. You need to get the relevant entries from the auth_users and account_emailaddress tables and add them to the new DB. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Enable delivery

by Mark Sapiro

On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… Also see the various tabs at https://www.example.com/mailman3/accounts/subscriptions/ > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` 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 list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

ok, thanks Mark, I'm getting an error doing: (env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management What do you suggest?? El vie., 21 jul. 2017 a las 14:31, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:07 PM, Rafael Mora wrote: > > Installing mailman-suite for web ui. I did this: > > > > (env) [mailman@localhost ~]$ git clone > > https://gitlab.com/mailman/mailman-suite/ > > Cloning into 'mailman-suite'... > > error: RPC failed; result=22, HTTP code = 404 > > fatal: The remote end hung up unexpectedly > > > > > > but it returned an error, what should I do?? > > > It's another case of incorrect docs. It should be > > git clone https://gitlab.com/mailman/mailman-suite.git > > See <https://gitlab.com/mailman/mailman-suite-doc/issues/15>. > > -- > 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

9 years, 3 months

[MM3-users] Re: user self registration

by Christian Stalberg

That worked. Thank you! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, December 7, 2025 9:26 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user self registration On 12/7/25 07:46, Christian Stalberg via Mailman-users wrote: > Spammers have been registering and not subscribing. I want to turn off > the user self registration at https://lists.ccalternatives.org/mailman3/ . > > I edited /etc/mailman3/settings.py adding ACCOUNT_ALLOW_REGISTRATION = > False and restarted the services, but the ' Sign Up' option remains. I > assume /etc/mailman3/settings.py is my active settings file. > > What am I doing wrong? Web searches may find reference to a django-allauth setting ACCOUNT_ALLOW_REGISTRATION, but this setting doesn't exist in current django-allauth The setting you want is ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ See https://docs.mailman3.org/en/latest/faq.html#how-to-disable-signup or https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail… -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to csa(a)web-analysts.net

11 months

[MM3-users] Re: Messages disappearing into hole??

by Mark Sapiro

On 8/30/20 6:15 AM, Ruth Ivimey-Cook wrote: > > I looked around the interface and decided to set up the sender as a > non-member, as that appeared to permit them to be "special" and outside > of the normal access rules for the list. Before I did that I could send > a message from this sender and that would be sent to me as list owner > for moderation, so both incoming (from my mailserver) and outgoing (to > it) can be completed. > > However, with a non-member who is auto-accepted the message is passed > from my mailserver to mailman and then disappears. I cannot find > anything in the logs to indicate what happened next. I have tried > setting the default non-member policy to both 'hold' and 'default' with > no change in that behaviour. The logs for the mailserver show the > message being sent to mailman; mailman's "smtp.log" shows an LMTP > message being received ok, and then nothing. > > Any ideas how to find out what is going on? I can share config if that > helps but not sure what would be useful. First, this is a bad way to configure an announce list because anyone can post by spoofing the authorized posting address. The better way is to set a list moderator password and post using an Approved: <password> header or pseudo header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> for details. As far as the disappearing message is concerned, it's hard to say. What is the non-member's moderation action? Unless it is 'list default' setting the list's default non-member policy has no effect. Also, if the non-member's address or a pattern matching it is in accept_these_nonmembers, that takes precedence over whatever the non-member's moderation action is. One guess about the disappearing message is content filtering may be removing all the message. What is the setting for Filter Action? > As a side-issue, at one point I added a regex matching the sender > address to the acceptable members list, but find that I cannot now > delete it (using postorius): If I delete the field and Save, it returns > on page refresh. There is an issue with Postorius. You can't empty these settings. If you clear the box or or have it contain only whitespace, Postorius won't change the prior setting. In order to remove the only entry in Postorius, you have to replace it with a bogus entry or you can remove it with `mailman shell`. I've just filed <https://gitlab.com/mailman/postorius/-/issues/444> for 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, 2 months

[MM3-users] Re: archiving problem & updates

by Mark Sapiro

On 2/19/21 7:19 AM, Christian Stalberg via Mailman-users wrote: > I see two messages waiting to be archived. Below is excerpt from the > logfile: > > Feb 10 13:40:49 2021 (974) held message approved, message-id: > <CAGrL7FsaX8EG9pMUZreJrQt1xkEyR3ySuw2-xn3m443O0N3j1A(a)mail.gmail.com> > [10/Feb/2021:13:40:49 +0000] "POST > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held/5 HTTP/1.1" 204 0 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=0&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:49 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=10&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/requests HTTP/1.1" 200 90 "-" "GNU > Mailman REST client v3.3.1" > [10/Feb/2021:13:40:50 +0000] "GET > /3.1/lists/ncpoa(a)lists.ccalternatives.org/held?count=50&page=1 HTTP/1.1" 200 > 90 "-" "GNU Mailman REST client v3.3.1" > Feb 10 13:40:55 2021 (846) HyperKitty failure on > https://lists.ccalternatives.org/archives/api/mailman/archive: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > (413) > Feb 10 13:40:55 2021 (846) Exception in the HyperKitty archiver: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M > </html>^M > Feb 10 13:40:55 2021 (846) Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ > _.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: <html>^M > <head><title>413 Request Entity Too Large</title></head>^M > <body bgcolor="white">^M > <center><h1>413 Request Entity Too Large</h1></center>^M > <hr><center>nginx/1.14.2</center>^M > </body>^M The issue is that one of the messages in var/archives/hyperkitty/spool/ is throwing this exception and that effectively stops archiving of new messages. I'm not sure what causes Request Entity Too Large, but I suspect it is a very large message body. You can examine the messages in var/archives/hyperkitty/spool/ with Mailman's `bin/mailman qfile` command, but I suspect the problem is caused by the largest of the files. You can just move it aside, and that should allow archiving to resume. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Another interesting error...

by Mark Sapiro

On 04/23/2018 01:31 PM, Darren Smith wrote: > So it appears that there was a message sent to one of our mailing lists > that was put into the held message queue. However, when attempting to go to > the message to do the moderation, the web page returns and Error 500. > > Looking in the mailman log, I found this: > > Apr 23 14:21:02 2018 (17878) REST request handler error: > Traceback (most recent call last): > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line 137, > in run > self.result = application(self.environ, self.start_response) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/transac > tion.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/wsgiapp.py" > , line 214, in __call__ > return super().__call__(environ, start_response) > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", > line 227 , in __call__ > responder(req, resp, **params) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 167, in on_get > resource = self._make_collection(request) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" > , line 159, in _make_collection > for resource in collection] > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" > , line 159, in <listcomp> > for resource in collection] > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera > tion.py", line 100, in _make_resource > make_header(decode_header(resource['subject']))) > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in > make_he ader > h.append(s, charset) > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in > append > s = s.decode(input_charset, errors) > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > illegal multibyte sequence > > It LOOKS as if there might be a character in the email somewhere - possibly > in the subject or sender fields? - that is somehow unexpected. It appears that the Subject: header is RFC 2047 encoded and there is an encoded word with charset gb2312 that contains an invalid encoding. The message is apparently defective, but this kind of defect shouldn't cause a 500 error. I can't tell for sure from the traceback if this is Postorius or some other application accessing the REST api. Is it Postorius or something else? > I am attempting to find the held message - can someone point me where I can > go to see the message so that I can see what might be causing the problem? It's in Mailman's database in the 'message' table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > The smtp.log I refer to is Mailman's smtp.log which is in Mailman's > var/logs/ directory. There are no entries in the /var/log/mailman3/smtp.log that get created when I try to log in (and authenticate) in Postorius. Jul 28 15:30:18 2024 (516) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:30:18 2024 (516) Peer: ('192.168.161.103', 54464) Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) handling connection Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) EOF received Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) Connection lost during _handle_client() Jul 28 15:30:18 2024 (516) ('192.168.161.103', 54464) connection lost Jul 28 15:50:22 2024 (1059) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 28 15:50:22 2024 (1059) Peer: ('192.168.161.103', 34814) Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) handling connection Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) EOF received Jul 28 15:50:22 2024 (1059) ('192.168.161.103', 34814) Connection lost during _handle_client() The recent attempts I made where after 18:00.

2 years, 3 months

[MM3-users] Re: Editing "automatic responses" tab i Postorius does not work

by David Krantz

But this one is already exposed. But I cannot change it anyway as the tab requires URIs for the different templates to allow saving. I do not use those URIs as I have configured the defaults as I like them. I tried once and it failed so I decided to set the defaults instead. cheers. // David On Sun, May 21, 2017 at 3:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/21/17 5:22 AM, David Krantz wrote: >> >> I am trying to change e.g. the value of "notify admin on membership >> changes" through postorius. > > > There are still many settings not yet exposed in Postorius. We are > painfully aware of this and will probably be working on some of this at > the PyCon sprints starting tomorrow. > > Until we get more of these addressed, you will need to use tools like > "mailman withlist" to set these things. > > -- > 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/

9 years, 5 months

[MM3-users] so many instances of mailman.cfg

by Christian Stalberg

Question: I've five copies of mailman.cfg on my box. How can I tell which one is actually being used please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 26, 2021 11:06 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote: > After the first time where users were unsubscribed automatically, I > added back one at a time all the subscribers who were unsubscribed. > Now they have all been unsubscribed again automatically. They are > valid working email addresses. How can I stop this behavior from occurring please? Do you have the bounce processing notifications `Notify owner on disable` and `Notify owner on removal` set to `Yes`. If not, set them. Then, what's in the notices you receive? You might also consider setting `verp_probes: yes` in the `[mta]` section of mailman.cfg. This will avoid some issues with users being disabled/unsubscribed due to list posts being rejected as spam. -- 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/

4 years, 11 months

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/2/25 22:11, Steve Brown via Mailman-users wrote: > I may include more info than you really want to know. Here is the gist of the complaint: > > "For a while now, my e-mail for this list (but not other lists) just shows "To RADG" from "RADG" with a "CC" showing the actual sender's address. > That becomes a PITA when I need to find a post by a particular person, because the e-mail list does not show the CCs in the list, so I need to open each one to see who actually sent it." The user is using T-bird and does not need to scroll through the email list to find a post from a particular user. They should be using quick filter for this. I will send you more detail about this off list as details about the T-bird UI are off topic here. > This subscriber is not very savvy about email, and doesn't seem to understand fully when I tell him how it works, so if I start talking about headers, that's a PITA, too. He claims: > > "RADG is the only list that is afflicted by this, out of 21 that include groups.io, yahoo, google, Lyris, and probably a few I don't recall." > > Because some other members, including me, have had problems with unexpected entries in both From and To lines, I suspect that Mailman 3 does the DMARC enough differently than other lists and forums to cause conflicts with the way the MUAs try to help the user autocomplete an address. Most of those problems go away if they put an association of RADG (Risk Analysis Discussion Group) with radg(a)lists.radg.us in their address book. We chose the "use your own URL" option. The actual server address is deu.mailmanlists.eu; I don't know whether their customization of the MM3 installation might cause some of the problem. > > My understanding is that all of the recent posts are missing the poster's name, after behaving as expected for some time. Something must have changed, but what is baffling me. If you have any further ideas, fine, but don't waste a lot of time on this. Mailman, both 2.1 and 3, have been modifying the From: header for DMARC in exactly the same way for years. If anything changed is this regard it is specific to the deu.mailmanlists.eu installation, but I doubt it was Mailman that changed, particularly because you are still seeing the From: as it always was. It is much more likely that the users T-bird changed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/23/20 6:32 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As I already said, your suggestion worked well on one list. > > But when I tried to implement the same trick on another list, I > found the below error messages in the mailman.log. > > >> * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno >> 2] No such file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> >> >> *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* >> * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* >> * f = open(self._path, 'rb+')* >> *FileNotFoundError: [Errno 2] No such file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> *During handling of the above exception, another exception occurred:* >> *Traceback (most recent call last):* >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, >> in _one_iteration* >> * self._process_one_file(msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, >> in _process_one_file* >> * keepqueued = self._dispose(mlist, msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line >> 37, in _dispose* >> * process(mlist, msg, msgdata, pipeline)* >> * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, >> in process* >> * handler.process(mlist, msg, msgdata)* >> * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line >> 47, in process* >> * with Mailbox(mailbox_path, create=True) as mbox:* >> * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* >> * _mboxMMDF.__init__(self, path, factory, create)* >> * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* >> * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such >> file or directory: >> '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* >> >> I ran in both the ways you suggested i.e. through "mailman shell" > and "mailman remove". But no luck. > > Could you please suggest me at this point ? Mailman is trying to add a message to the digest of the press.dpr-pb.lsmgr.nic.in list, but the /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory doesn't exist, presumably because the list has been removed. The question is why is Mailman trying to write to this list's digest.mmdf? Did the above result from unshunting something from before the list was removed? -- 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

[MM3-users] Re: Debian upgrade Hyperkitty not archiving

by Mark Sapiro

On 2/27/26 13:23, Phil Steel-Wilson via Mailman-users wrote: > > I'm working at a volunteer organization with around a dozen mailing > lists that were previously on mm2 that have been upgraded to mm3 with > the upgrade to debian trixie. Mailman is running and the lists all work > ok but i found 1800 mails in the shunt queue. Hyperkitty also shows all > the old archives pre 2020 the same as in the django console. When i > tried to unshunt the mails they moved to the bad queue. How do i find > whats wrong here? If this is the Debian package, you should be working with Debian. See <https://wiki.list.org/x/12812344>. > Mailman Core Version GNU Mailman 3.3.10 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC > 14.2.0] There is a compatibility issue between Mailman 3.3.10 from PyPI and Python 3.13, but this is apparently fixed in the Debian package. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and near the end of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> Mails are shunted because of some uncaught exception in processing. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info on dealing with shunted messages. Messages can end up in the bad queue in multiple ways. One way is content filtering ends up with an empty message and the list's content filtering Filter Action is Preserve. This requires ``` filtered_messages_are_preservable: yes ``` in the [mailman] section of mailman.cfg. The only other way messages end up in the bad queue is in reprocessing messages. When a message is picked up for processing by a queue runner it's extension is changed from .pck to .bak. Then if that runner crashes for some reason without finishing processing of that message, the .bak file remains and when the runner restarts, the entry is reprocessed. If unpickling the .bak throws an exception or if reprocessing the same message is tried 3 times without success, the message is placed in the bad queue. The following errors have nothing to do with messages in the shunt or bad queues. They are the result of trying to log in to the web UI with the fedora oAuth login method which is apparently misconfigured. > Traceback (most recent call last): ... > TypeError: OpenIDProvider.get_server_settings() missing 1 required > positional argument: 'endpoint' > ERROR 2026-02-27 20:50:19,995 1769748 django.request Internal Server > Error: /mailman3/accounts/fedora/login/ > Traceback (most recent call last): ... > TypeError: OpenIDProvider.get_server_settings() missing 1 required > positional argument: 'endpoint' ... > ERROR 2026-02-27 20:51:20,841 1769748 django.request Internal Server > Error: /mailman3/accounts/fedora/login/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:13 PM, Paul Arenson wrote: > Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: > > The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) > > 1) So, for both subscribers vi postorius only and hyperkitty users: > email to discuss-leave(a)list.tokyoprogressive.org (or > discuss-unsubscribe(a)list.tokyoprogressive.org) Yes, but you seem to have some confusion about how things work. Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html…>. As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework. What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account. When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't. > 2) Only for hyperkitty users, you can login, go to > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > and click the big red unsubscribe button. You need to be logged in for this so Postorius knows who to unsubscribe. > 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/ and click the Delete > Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/delete This deletes your Django account, but does not affect your list memberships. > (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) That's right. The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later. I hope this helps rather than adding confusion. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/24/22 00:00, Odhiambo Washington wrote: > > These are my files: > 1. urls.py > <CUT > > from django.conf.urls import include > from django.urls import re_path > from django.contrib import admin > from django.urls import reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > re_path(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > re_path(r'', include('django_mailman3.urls')), > re_path(r'^accounts/', include('allauth.urls')), > # Django admin > re_path(r'^admin/', admin.site.urls), > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ] > </CUT> You don't need all of those. ^postorius/ and ^mailman3/ are two different ways to access Postorius, and ^hyperkitty/ and ^archives/ are two different ways to access HypereKitty. You only need one of each, but having both is OK. > 2. apache.conf > <CUT> > ... > Alias /static "/opt/mailman/mm/static" > <Directory "/opt/mailman/mm/static"> > Require all granted > </Directory> > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > WSGIScriptAlias / /opt/mailman/mm/wsgi.py This will send every http request to mod_wsgi except for requests to /static. This is OK if there are no other web sites on this server and the only http requests are for Django related things. ... > I have tested with creating all those commented out aliases and that ended > up still giving me /mailman3/mailman3/* which I did not > like, although everything appeared to work. > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > and now when I type https://mm3-lists.kictanet.or.ke I end > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course something > has appended "/mailman3" > So this has resulted in all URLs having /mailman3/ appended, except for the > /archives link. How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > Now my question is about what could be adding the /mailman3. Is it possible > that I installed something out of the ordinary? It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time (I now use gunicorn on all the sites I manage), but when I did I think I had WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py and all the URLs were like https://example.com/mm3/mailman3/..., https://example.com/mm3/archives/..., etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: slow restart time for mailmanweb

by David Newman

On 12/28/21 7:52 PM, Mark Sapiro wrote: > On 12/28/21 3:51 PM, David Newman wrote: >> On 12/28/21 1:20 PM, Mark Sapiro wrote: >> >> > If so, try adding >> > >> > KillSignal=SIGQUIT >> > >> > to the Service section and see if that fixes it. >> >> root@myhost:/etc/mailman3# time systemctl restart mailmanweb >> >> real 0m1.026s >> user 0m0.008s >> sys 0m0.004s >> >> My limited understanding of SIGQUIT is that it dumps core, but 'find / >> -type f -name '*.core' did not return any core dumps from this event. > > > Actually, SIGINT is probably better, SIGINT does fine: root@myhost:/etc/systemd/system# time systemctl restart mailmanweb real 0m1.024s user 0m0.009s sys 0m0.006s > but they should be equivalent. See > https://uwsgi-docs.readthedocs.io/en/latest/Management.html#signals-for-con… > and > https://uwsgi-docs.readthedocs.io/en/latest/Management.html#stopping-the-se… > > > I'll update the doc. Thank you! > >> Still unsure why the service hung on stop, but thanks! > > It hung on stop because systemd wasn't told how to stop uwsgi so it sent > a SIGTERM which doesn't stop it. Got it. Again, many thanks. dn

4 years, 10 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

On 10/24/23 18:53, Mark Sapiro wrote: > On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 10/24/23 18:29, Mark Sapiro wrote: >>> What if you try this with `mailman-web shell`? >>> >> Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem. > > I was confused. I should have said ` mailman shell`, not `mailman-web shell`. Insert "circular problem" here. When I DO NOT have the module loaded in the configuration, `mailman shell` works. Since that was functional, I went into the shell and executed this: > from mailman_customizations.hooks import MailmanCustomizations This worked fine, but obviously importing the class doesn't necessarily *activate* the class. So something is up with how I'm *supposed* to activate the plugin in the config, and we know that it's visible to Mailman in its shell, but it can't autoload it. So, again, not sure where to look next for debugging. Thomas

3 years

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Johannes Rohr

Am 24.01.2023 um 01:26 schrieb Mark Sapiro: > On 1/23/23 14:00, Johannes Rohr wrote: >> >> Am 23.01.23 um 21:08 schrieb Mark Sapiro: >>> e.g. >>> ``` >>> HAYSTACK_CONNECTIONS['default']['PATH'] = >>> '/opt/mailman/mm/var/fulltext_index' >> >> Thanks! Indeed. Including this line helps. It makes the error go >> away. So I guess the instructions should be amended. >> >> After that, for some reason, I have to re-index all lists, because >> initially, empty results were returned for any query, only after >> re-indexing to I get results. > > Did you adjust the path to point to your existing fulltext_index? yes, I did. > If not and if you had, I don't thing you would have needed to reindex. That's precisely, why I was surprised. > > The question is what changed so that the relative "fulltext_index" no > longer pointed to where the actual directory was. I don't think that anything had changed, I just don't think I never checked whether the fulltext search actually works and so I spotted this error rather late in the game. Thanks, Johannes > >

3 years, 9 months

[MM3-users] Re: Internal Server Error: /archives/api/mailman/archive OperationalError at /archives/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1")

by Mark Sapiro

1 year, 2 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/27/23 23:53, Odhiambo Washington wrote: > > I have reread what you wrote now and I'm beginning to get the hang of this > method. > My observation is that it can only be _obvious_ to someone very familiar > with Python config > to decipher that *additional* settings *that can be augmented or overridden > in /etc/mailman3/settings.py* can be obtained from: > /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed > these two lines in > the sample settings given in /etc/mailman3/settings.py: > > from mailman_web.settings.base import *from > mailman_web.settings.mailman import * This is how it was always done in Mailman 2.1 and how it should have been done in Mailman 3's Django web UI from the start, but wasn't. MM 2.1 had mm_cfg.py which had ``` from Defaults import * ################################################## # Put YOUR site-specific settings below this line. ``` > [At first instance, it is not obvious that mailman_web.settings.base and > mailman_web.settings.mailman are > actually paths in Python - which magically translates to > mailman_web/settings/base.py and mailman_web/settings/mailman.py] This is very basic Python. > Granted, I am a slow learner, and perhaps already so mixed up after reading > the myriad HOWTOs for > installing MM3 that are available online. I am tempted to say there are > many like me who are likely to > miss "where to obtain" other settings from. > > For example, my mind all along has been tuned to having a settings_local.py > for overriding the settings.py. > However, with this particular documentation, it would appear that > everything is intended to just go into /etc/mailman3/settings.py. In that method you had the defaults in settings.py which at the end imported settings_local.py. This method has defaults in /PATH-TO/mailman_web/settings/{base|mailman}.py and those are imported at the beginning of settings.py which then has overrides. This is preferable because it allows things in settings.py like ``` HAYSTACK_CONNECTIONS['default']['PATH'] = 'some path' ``` to just override that one thing rather than having to redefine all of HAYSTACK_CONNECTIONS or import it from settings in settings_local.py. > Is it possible to modify the documentation to somehow make it obvious (in a > language that a layman can easily understand, > that those two "import *" _DO establish a base set of settings that can be > augmented or overridden in /etc/mailman3/settings.py_ > and that those settings are in what file(s) ? Again, this is very basic Python, but if you submit a merge request to update https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/install/v…, we'll certainly consider it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: MM2 -> MM3 Migration

by Odhiambo Washington

On Fri, Dec 30, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/29/22 23:17, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> The default without the since= option is to import only those messages > >> from the mbox which are newer than the newest message in the existing > >> archive which is exactly what you want. > >> > > > > So I ended up using this and I can see the list metrics indicating that > the > > last post was on 29Dec22, but > > I don't seem to be able to see those posts in the archives. > > > If Postorius list metrics show the last post was 29 Dec, that was a post > to the MM3 list and if it was archived, then running hyperkitty_import > without a since= option will not import any messages older than that. > Is there a way to delete the whole archive and re-import afresh? I checked the django-admin options for hyperkitty and did not see any such option. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 3:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 11:37, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 21:46, Odhiambo Washington wrote: > >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >>>> > >>>> I see from another post that you've decided against using Twitter, but > >>>> to answer the question, Twitter does not require adding anything to > >>>> SOCIALACCOUNT_PROVIDERS. > >>>> > >>> > >>> I tried it and ended up with: > >>> > >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server > Error: > >>> /accounts/twitter/login/ > >>> Traceback (most recent call last): > >> ... > >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > >>> query does not exist. > >> > >> > >> Do you have > >> > >> 'allauth.socialaccount.providers.twitter', > >> > >> in INSTALLED_APPS? > >> > > > > Here is what I have in settings_local.py: > > > > 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', > > #'django_mailman3.lib.auth.fedora', > > #'allauth.socialaccount.providers.openid', > > 'allauth.socialaccount.providers.github', > > #'allauth.socialaccount.providers.gitlab', > > 'allauth.socialaccount.providers.google', > > 'allauth.socialaccount.providers.facebook', > > 'allauth.socialaccount.providers.twitter', > > #'allauth.socialaccount.providers.stackexchange', > > ) > > > Did you add an app at https://site.name/admin/socialaccount/socialapp/ > with twitter as a provider? See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… Exactly, and I have entered all the credentials from the "OAuth 2.0 Client ID and Client Secret" of the twitter developer portal. https://webmail.kictanet.or.ke/~wash/twitter-oauth.png I have checked my settings_local.py several times trying to find out why the entry is ignored. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- 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/

4 years, 5 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Tue, Jan 31, 2023 at 9:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:43, Mark Sapiro wrote: > > > > add another section header > > > > Regular Expression Tables > > ------------------------- > > > > and change that text to > > > > Regular Expression tables are less efficient than hash tables, but they > > remove the additional dependency of having ``postmap`` command available > > to Mailman. If you want to use ``regexp`` or Regular Expression tables, > > then add the following to Postfix's ``main.cf`` file > > > This is now done. > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > That is now quite clear, but I still have one question and this is cosmetic (because Postfix isn't my MTA of choice. You can ignore it if it feels like spoon-feeding a Postfix admin. In the section: ``` https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ``` .. the Postfix admin had to figure out whether they are using hash or regex tables and modify accordingly, right? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 9 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home from another episode of turkey overconsumption. I confess that I am not a python expert - once I create a new list, what’s the easiest way to inspect the object state? --Jered > On Nov 25, 2023, at 18:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/25/23 8:01 AM, Jered Floyd wrote: > >> This suggests that new lists in 3.3.9 may be getting mlist.dmarc_addresses set to None rather than an empty list (which seems to be expected). > > > How did you create this list? > > I have tried and when I create a new list it has mlist.dmarc_addresses set to an empty 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 11 months

[MM3-users] Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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/ >

8 years, 6 months

[MM3-users] Re: list archives bleeding across domains.

by Hugh Esco

Yes, ProxyPreserveHost is On by way of the haproxy, where: ``` backend mailman3 mode http option forwardfor if-none server server_mailman3 172.17.0.63:80 ``` for context, this is the apache2 config: ``` <VirtualHost *:80> ServerName lists02.campaignfoundations.com ServerAlias lists.campaignfoundations.com ServerAdmin hesco(a)campaignfoundations.com Alias /mailman3/static "/opt/mailman/web/static" <Location /mailman3/static> Require all granted </Location> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3/static" ! ProxyPass "/mailman3/" "http://127.0.0.1:8000/mailman3/" ProxyPassReverse "/mailman3/" "http://127.0.0.1:8000/mailman3/" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> # Possible values include: debug, info, notice, warn, error, crit, alert, emerg. LogLevel warn LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" common CustomLog /var/log/apache2/lists02.campaignfoundations.com-access.log combined ErrorLog /var/log/apache2/lists02.campaignfoundations.com-error.log </VirtualHost> ``` Mark Sapiro wrote: > > This should work. How is your web server accessing Postorius? Is it > passing the hostname? I.e., proxy_set_header Host $host; for nginx or > ProxyPreserveHost On for Apache. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

4 weeks, 1 day

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 10:45 AM, Mark Sapiro wrote: > On 4/14/22 10:18, David Newman wrote: >> On 4/14/22 9:50 AM, Mark Sapiro wrote: >>> >>> It could accept a defective message or one with specific defects, but >>> this is problematic for further processing. For example, at least one >>> MUA, Thunderbird, renders such a message with an empty body. >> >> That's not my experience. Mailman 3 accepted without complaint a >> PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to >> list subscribers with the message body intact. > > > Yes, and that's what we expect, but MM 3 does not accept the defective > message, and T-bird does not render the body of such a message. I.e., if > such a message composed by Apple Mail 15 is sent via a non-Mailman > channel to a T-bird user, the user can't read it. Sorry, I misspoke. The Apple Mail sender used S/MIME signing, not PGP signing. In Thunderbird, I was able to read an S/MIME-signed message the user sent directly to me complaining about the 501 bounce. Thunderbird said the signature was invalid due to the use of an untrusted CA, but I could read the message body. dn

4 years, 7 months

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

Sorry, I knew that. Thanks for your assistance today. Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, June 26, 2025 16:36 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 6/26/25 15:29, Hirayama, Pat wrote: > Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now..... 4500 lists is a lot, but not unheard of, but please don't call them listservs. See https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20… -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

1 year, 4 months

[MM3-users] Re: Permission denied for /list:member:digest:header.txt

by Eric Broens

Thanks again Mark, from the bash_history that seems to be the case, while I intended to run it as mailman user.It looks like only the ownership of the subdirectories and files in /var/lib/mailman3/templates are incorrect.Those in /var/lib/mailman3/lists and other directories are correct. I can't find back if I have changed the ownership of these manually. Is it sufficient to change the ownership manually, or is there another change required too? Best Regards,Eric On Monday, December 14, 2020, 01:59:06 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/14/20 3:19 AM, Eric Broens via Mailman-users wrote: > Thanks Andi, > I understand that it is a Unix permissions issue.The question is, what process created these files and directories? Mailman runs with its own user. Since these files and directories were created automatically, I expected that these would have been created with the correct permissions. You ran the hyperkitty_import job for these lists as root. It needs to be run as the Mailman user. -- 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/

5 years, 11 months

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/25/23 1:31 PM, Ken Alker wrote: > > I moved the .psv file from the bad queue into the shunt queue. I then > ran "mailman unshunt" (as user 'mailman' while in the virtual > environment). I tailed mailman.log during this process and no logs were > spit out. The date stamp on the .psv file never changed (maybe it does > not when being moved between queues?) and, AFAICT, the file never moved > from the shunt queue. I waited maybe five minutes, tops. I forgot that the extension in the `bad` queue is `.psv` (for preserve). You have to rename it to `.pck`. >>> Is there a way to reprocess the bad queue? >> >> You could just move the messages to the 'in' queue. Changing .psv to .pck in the process. this can be done, e.g., by ``` for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file /var/queue/in/${file/psv/pck};done ``` > I just now tried moving the same message into the 'in' queue but, again, > nothing happened. I left it in there for five minutes. Do I have to > run a program to get it to act on the 'in' queue (I presume that there > is a "runner" that is always looking and taking care of this already as > I presume this is the queue where all 'normal' traffic is handled). Again, you need to change the extension to .pck. > Here are the (obfusacted) results of "mailman qfile > /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c96142c3fa9d03a8142bc.psv" (the message I was experimenting with): > > [----- start pickle -----] > <----- start object 1 -----> > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Subject: THE-list subscription notification > From: email(a)obfuscated.com > To: the-list-owner(a)lists.obfuscated.com > Message-ID: <167538979369.2390432.521344217673230839(a)obfuscated.net> > Date: Thu, 02 Feb 2023 18:03:13 -0800 > Precedence: bulk > > user(a)domain.tld has been successfully subscribed to THE-list. > > <----- start object 2 -----> > { '_parsemsg': False, > 'envsender': 'email(a)obfuscated.com', > 'listid': 'the-list.obfusacted.com', > 'nodecorate': True, > 'recipients': {'person(a)domain.tld'}, > 'reduced_list_headers': True, > 'version': 3} > [----- end pickle -----] I was assuming these were list welcome messages which they aren't. They are owner notifications, so they were sent to the -owner address and processed through the owner-pipeline, but unless the Debian package changed the default-owner-pipeline, it doesn't contain mime-delete so how they ended up in the `bad` queue is still a mystery. However, what would be the point of resending these at this time? -- 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

[MM3-users] Re: Migration from 2.1 to 3

by Ryan Morash

I figured it out. It was a stupid mistake on my part, running the ‘mailman create’ commands as root… chown’ing the /var/lib/mailman3/lists directories to lists:lists solved the issues. From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, January 8, 2020 at 1:20 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Migration from 2.1 to 3 On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the issue isn't with the import21 command. I'm running into the same issue when I create a list using 'mailman create' without importing anything. New lists created through Postorius work fine. Can you please post the `mailman create` command options you are using to create 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

6 years, 10 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

That explains a lot. Is there any documentation you can provide to show me where I can set a static config/db? On Tue, Jul 31, 2018, 4:22 PM Mark Sapiro, <mark(a)msapiro.net> wrote: > On 07/31/2018 12:39 PM, Ryan McClung wrote: > > I do see the output of the script and it shows the mailing lists being > > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > > > Also, to that end, the output of lists changes depending on which > directory > > I am in which makes 0 sense. > > > That is the problem. Either your mailman.cfg does not specify a fixed > directory for var_dir or the mailman command(s) you run do not specify a > fixed mailman.cfg. > > If you look, you will probably see a var/ directory is every directory > in which you ran a 'mailman' command and they will all have different > databases, etc. > > -- > 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/ >

8 years, 3 months

[MM3-users] Re: Join a Mailman 3 list?

by Mark Sapiro

On 6/8/25 20:18, Cathryn McGuire wrote: > Hi Mark, Stephen & Thomas, > > We've successfully merged our Mailman 2 list into Mailman 3. EMWD worked over the weekend to get it done for our members. We're pretty grateful. > > There are a few things we're trying to get our heads around, specifically to do with the Affinity Web UI. Most of it is pretty self explanatory, and I can see where it will be more aesthetically pleasing to manage, but a few things that aren't so intuitive. Affinity is a proprietary product of EMWD. At one point during the development of Affinity, when Brian C was still alive, I had access to a demo version, but no more. I don't know if there are any EMWD Mailman 3 users on this list, but I suspect your best resource for Affinity questions is EMWD. > Is anyone working with Mailman 3 and Affinity that could help us through the set up? For instance, when I log in as owner and go to change my password, it won't take a new one and asks me (with a pull down menu box) which account I want to change the password for, and it gives me a list of my emails, and also the other owner's email address. When I choose the email I'm logged in under, it says it's not the correct "credentials." > > Has anyone had this issue? Have you actually created an Affinity login? I believe initially, you have to sign up before you can sign in, even if you are the listowner. > Another thing is, and Stephen J. Turnbull prepared us for this, that the transferred membership are all "enabled" but not "registered." I understand we have to send a membership wide notification with a link to the Affinity log in page, and instructions going to the top right hand and clicking on the login icon, putting in their email address (the one in the system) and adding a password OR do they have to "create" a new sign in? If it works like our web UI, they have to create a new sign in. You do too. The process that imports a Mailman 2.1 list to a Mailman 3 list does not create web UI logins. > Thanks for any info you can give us about Affinity. (I see Brian Carpenter was beta testing it 4 years ago.) Cheers, Cathryn I was one of the people working with Brian back then to try out and give feedback on Affinity, but I've probably forgotten all I knew at that time. There may be current EMWD/Affinity users on this list, but as I said, your best support resource is probably EMWD. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Thank you Mark for your response. All the mentioned versions of all the components are taken from my currently running system only in which I am facing the issue. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 10:54 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 12:46 AM, Shashikanth Komandoor wrote: > > > > *### Mailmanclient Version ###* > > > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > > *Merge: ff39dd8 8670751* > > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in > >>* > > *Date: Thu Oct 15 01:09:32 2020 +0000* > > > This mailmanclient is up to date and does define the get_requests_count > mailing list attribute, so this version must not be whats running in > your mailman installation. Did you install it? > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 7/14/20 3:54 AM, Brian Carpenter wrote: > On 7/14/20 6:49 AM, Gilles Filippini wrote: >> Mailman Core logs: >> [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) >> [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) >> [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 > > I am pretty sure that timeout is related to gunicorn. If it is, then > increasing the worker out timeout setting for gunicorn should work. You > tend to get such errors when doing an export of a large membership > roster. This is the first time I have seen it related to a held message. It seems weird that a gunicorn worker would run for more that the default 30 seconds because of a 23MB message, but I think Brian is correct. > I have this in my setup: > > mailman.cfg: > > [webservice] > configuration: /opt/mailman/mm/gunicorn.cfg > > gunicorn.cfg: > > [gunicorn] > workers = 4 > timeout = 900 > > You will need to restart gunicorn after adjusting the timeout setting. It's confusing, but after adjusting that setting, you need to restart Mailman core, not gunicorn. If you are running a gunicorn service, that is what is providing WSGI support for Django (Postorius and/or HyperKitty). You may be using gunicorn for this or uWSGI or Apache mod_wsgi, but is any case, that is not the gunicorn we are considering here. Regardless of what you use to provide WSGI support for Django, Mailman core uses gunicorn to support the REST API, and that is the gunicorn affected by the settings in the gunicorn.cfg pointed to by [webservice] configuration: /opt/mailman/mm/gunicorn.cfg If, with the above configuration, you do `ps -fwwA|grep runner=rest` you will see something like: mailman 20582 20561 0 01:21 ? 00:00:16 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20722 20582 0 01:21 ? 00:01:19 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20725 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20726 20582 0 01:21 ? 00:01:18 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 mailman 20727 20582 0 01:21 ? 00:01:50 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/deployment/mailman.cfg --runner=rest:0:1 The first of these, pid 20582, is Mailman's actual REST runner. The other 4 with parent pid 20582 are the 4 gunicorn worker processes forked from the REST runner. It's the REST runner or Mailman core that needs to be restarted to pick up that change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Domain Issue with MM3

by Mark Sapiro

On 10/23/19 12:53 PM, Liebeskind Uri (luri) wrote: > > I have setup this mailing list test(a)digital.lists.zhaw.ch but subscribing failed. How did you create the list and the digital.lists.zhaw.ch domain in Mailman? > * Subscribing via the Mass Import Form failed with a Server Error message in the browser. Log messages may help here. I can't tell you where to find them in your installation, but your Django settings or local settings will define LOGGING['handlers']['file']['filename'] which is where your Django logs are. and your various Mailman logs are generally in Mailman's var/logs/ directory. You may find a traceback from this error in the Django log or in Mailman's error.log or access.log. > * Subscribing via e-mail test-join(a)digital.lists.zhaw.ch<mailto:test-join@digital.lists.zhaw.ch> because no response came from MM3. This is Postfix. See below. > The mail to join has been delivered properly to MM3 but MM3 has swallowed the mail w/o response or error message. There also has not been any pending subscription. MM3 did respond. See below. > 2019-10-23T19:51:33.678705+02:00 svma-s-01321 postfix/smtpd[98348]: connect from srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.692258+02:00 svma-s-01321 postfix/smtpd[98348]: A8EFC3FA6A: client=srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.693192+02:00 svma-s-01321 postfix/cleanup[98351]: A8EFC3FA6A: message-id=<eb90deb6-58af-a873-3382-c27ce6d05031(a)anydomain.org> > > 2019-10-23T19:51:33.704102+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: from=<name(a)anydomain.org>, size=5329, nrcpt=1 (queue active) > > 2019-10-23T19:51:33.704864+02:00 svma-s-01321 postfix/smtpd[98348]: disconnect from srv-mail-013.zhaw.ch[160.85.104.123] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > 2019-10-23T19:51:33.763670+02:00 svma-s-01321 postfix/lmtp[98352]: A8EFC3FA6A: to=<test-join(a)digital.lists.zhaw.ch>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (250 Ok) Per the above the message was delivered to Mailman. > 2019-10-23T19:51:33.764485+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: removed > > 2019-10-23T19:52:29.278529+02:00 svma-s-01321 postfix/smtpd[98348]: table hash:/var/lib/mailman3/data/postfix_lmtp(0,lock|fold_fix|utf8_request) has changed -- restarting Why all these table changes/restarts? > 2019-10-23T19:52:29.286154+02:00 svma-s-01321 postfix/smtpd[98558]: connect from localhost[127.0.0.1] Mailman has connected to Postfix. > 2019-10-23T19:52:29.288612+02:00 svma-s-01321 postfix/cleanup[98351]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.292655+02:00 svma-s-01321 postfix/smtpd[98558]: 476AD3FA6A: client=localhost[127.0.0.1] > > 2019-10-23T19:52:29.293671+02:00 svma-s-01321 postfix/cleanup[98559]: 476AD3FA6A: message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> And delivered its response, message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> to Postfix. > 2019-10-23T19:52:29.296393+02:00 svma-s-01321 postfix/qmgr[90603]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.298231+02:00 svma-s-01321 postfix/smtpd[98558]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 So the message was delivered to Postfix with the four commands ehlo, mail, rcpt and data. This is normal. What did Postfix do with the message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, This is what I've got in /var/lib/mailman/var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 100 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db -rw-rw---- 1 mailman mailman 315 Jul 24 10:41 postfix_domains -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_domains.db -rw-rw---- 1 mailman mailman 318 Jul 24 10:41 postfix_lmtp -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_lmtp.db What should be the next step? El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 06:00 PM, Rafael Mora wrote: > > Hello guys, > > > > This is what I've got on ../var/data: > > > > [root@localhost data]# pwd > > /var/lib/mailman/var/data > > [root@localhost data]# ls -l > > total 76 > > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > > > > What should I do in order to let mailman install the DB files? > > > Run > > bin/mailman aliases > > -- > 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

9 years, 3 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Fri, May 3, 2024 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = > 13; > > delete from hyperkitty_mailinglist where id = 13; > > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > > 'list.lists.nog.ke' where id = 2; > > Or instead of that you could just go to the new list(a)lists.nog.ke > archive in HyperKitty and delete it and then just do the > ``` > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; > ``` > I went with this approach and worked super! Thank you. So, seeing as deleting a list retains its archives, if I want to delete a list together with its archives, do I first delete the archives, then follow with the list? -- 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]

2 years, 6 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, I forgot to mention that, but there is no mailman-web on ubuntu packages on 18.04. So I can't find a way to run it. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 10:19, Jered Floyd wrote: > > > > Did you run the upgrade steps? > > > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > > > For schema upgrades you will at least need to do "mailman-web migrate", > but please read the entire section as 3.1.1 to 3.3.9 is a big step. > > > These are all important and necessary steps, but "mailman-web migrate" > updates schemas for the mailman-web database. It does not update the > alembic migrations for the mailman database. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

2 years, 10 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/9/25 14:23, Dan Caballero wrote: > Hello, > > At the request of a list owner, we changed the settings on a list to "Anonymous = No" so that list members could see who a message was coming from. > > It seems a side effect of the setting is that users are now using "reply-to" and some messages are going out to the list addressed in the manner below. > > "Last Name, First Name via list-name <list-name(a)caltech.edu>" This is a consequence of DMARC mitigations. > The list owner feels this is confusing and some members may inadvertently email the list when they intend to email the individual. When the From is munged in that way for DMARC the orikinal From is put in Reply-To: or perhaps Cc: depending on other settings. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… for details of this process and its goals. Assuming your list's Reply goes to list setting is No Munging The original From: should be in Reply-To: of the delivered. It appears that the messages that are sent To: Last Name, First Name via list-name <list-name(a)caltech.edu> are sent by an MUA that is ignoring Reply-To: and replying to From:. > I understand this is likely a client side caching issue since most email clients create an index of contacts based on previously received emails. > > Aside from reverting back to "Anonymous = Yes", is there any setting we can change at the list level to force the "to" field to persist as the list email address? Do you mean you want the From: in delivered messages to be the original poster's From: so that replies to the From: go to the OP. You can accomplish this by setting DMARC mitigation action to No DMARC mitigations, however this will ensure that any mail whose From: domain publishes a DMARC policy of quarantine or reject will most likely be bounced by all large ESPs. We do are best to ensure that a simple reply to a message to which DMARC mitigations are applied will go to the poster unless the Reply goes to list setting says otherwise. But I am confused as to your goal. Previously when the list was anonymous, all replies went to the list. Maybe your goal is to have list replies be addressed to <list-name(a)caltech.edu> rather than Last Name, First Name via list-name <list-name(a)caltech.edu>. If that is the goal, you could try setting Reply goes to list setting to Reply goes to list. That will set a Reply-To: list's short description <list-name(a)caltech.edu>. That may be what you want as long as the responder's MUA honors Reply-To: over From: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 12:26 PM, Mark Sapiro wrote: > On 7/7/22 11:10 AM, David Newman wrote: >> On 7/7/22 10:25 AM, Mark Sapiro wrote: >> >> pip install -U mailman postorius django-mailman3 hyperkitty >> mailman-web uwsgi >> >> and it downgraded Django back to 3.0.14. > > > Because mailman-web 0.0.5 has in its setup.cfg > ``` > install_requires = > Django<3.1 > ``` > try > ``` > pip install -U git+https://gitlab.com/mailman/mailman-web.git > ``` > to get the latest mailman-web whose Django requirement is > ``` > install_requires = > django >=2.2, !=3.0, <4 That seemed to work OK, thanks. mailman-web is now on a dev version of 0.0.6 and Django is now on 3.2.14. However, pip now throws a warning when looking at package info: (venv) mailman@somehost:/home/dnewman$ pip show mailman-web WARNING: Ignoring invalid distribution -jango (/opt/mailman/venv/lib/python3.9/site-packages) Name: mailman-web Version: 0.0.6.dev9+gc606169 Summary: Mailman 3 Web interface. Home-page: https://gitlab.com/mailman/mailman-web Author: Mailman Developers Author-email: mailman-developers(a)python.org License: GPLv3 Location: /opt/mailman/venv/lib/python3.9/site-packages Requires: django, hyperkitty, postorius, whoosh Required-by: How to correct that so the command runs clean with no warnings or errors? This is on a host running Debian 11 with mailman3 and friends installed in a venv. Thanks. dn

4 years, 4 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 9:51 AM, Andy Smith wrote: > > Over in Exim's mainlog I then see that delivered out to list > members. One of them rejects it at SMTP time, which I think causes > this: > > Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost > Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address. > …and I think that bounce message somehow incremented the bounce > score for andy(a)bitfolk.com even though that address was only present > in the original post's Cc: and body. If the original post was the message delivered to users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body. > Is there a good way to further debug this? Maybe by being able to > see the full content of the DSNs that Mailman generates? As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…, but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message. If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces. You might also be able to find the fake dsn and/or the message received via SMTP to users-bounces(a)mailman.bitfolk.com in Mailman's var/messages/ directory, although these are pickles and need to be examined with `mailman qfile`. > I think I've seen this before in the last couple of weeks so I'm > sure it'll crop up again soon. I've seen it mention about bounce > score for users-leave before, but I only really paid attention today > when it also listed my own address. users-leave probably is parsed out of the message footer. -- 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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I read the doc and it says that when the DEBUG var is set to False we should do these commands: django-admin collectstatic --pythonpath example_project --settings settings django-admin compress --pythonpath example_project --settings settings I did the first one and got this: (env2) [mailman@localhost mailman-suite]$ pwd /var/lib/mailman/mailman-suite (env2) [mailman@localhost mailman-suite]$ django-admin collectstatic --pythonpath mailman-suite_project --settings settings You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/var/lib/mailman/mailman-suite/mailman-suite_project/static', 345 unmodified. why it did not copy the files??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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

9 years, 3 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you for your help. I have traced the versions of different components of mailman 3. I am downloading through GIT LAB because I need to modify the code according to my organization's requirements like to add SMS notifications when a mail is waiting for pending approval and so. With your help, I have found out the commits I am using in my environment. I got them using the way you suggested "git log". That may be helpful for you to help dummies like me. *### Mailman Core Version ###* *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* *Merge: 98cf97b 0bca998* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Thu Oct 15 14:02:36 2020 -0700* * Merge branch 'template' into 'master'* * Clarify the posting instruction in the list welcome message.* * See merge request mailman/mailman!723* *### django-mailman3 Version ###* *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* *Merge: ea2b33a c091e43* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:40:51 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/django-mailman3!108* *### Hyperkitty Version ###* *commit 36f43466763c2686cf4d69c982ea64b956c30939* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Mon Oct 5 04:54:44 2020 +0000* * Use GH registry to pull CI image.* *### Mailmanclient Version ###* *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* *Merge: ff39dd8 8670751* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 01:09:32 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use GHCR for the CI image* * See merge request mailman/mailmanclient!130* *### Mailman Hyperkitty Version ###* *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* *Merge: 35ff801 04deff5* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Fri Jun 19 18:15:57 2020 +0000* * Merge branch 'fix_25' into 'master'* * Add a test for the presence of surrogates in the stringified message.* * Closes #25* * See merge request mailman/mailman-hyperkitty!7* *### Mailman-suite Version ###* *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* *Merge: 74e7927 4463b31* *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* *Date: Sat May 30 00:32:40 2020 +0000* * Merge branch 'doc_mb4' into 'master'* * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* * See merge request mailman/mailman-suite!8* *### Postorius Version ###* *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* *Merge: 61242d2 321310c* *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* *Date: Thu Oct 15 00:43:14 2020 +0000* * Merge branch 'fix-ci' into 'master'* * Use the GHCR registry for CI image.* * See merge request mailman/postorius!549* I have removed only mailmanclient and re-cloned it from gitlab and ran the python setup.py develop command. But still the same error. Is there anything else I can do to get rid of that error. Thanks in advance. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: > > > > How to find out the versions of the each and every component > > of the mailman 3 like mailman core, mailmancilent, postorius, > > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, > > after installation? > > > cd to the directory in which you cloned the gitlab project for the > component and do `git log` > > > > If I am running an old mailmanclient or older version of any > > other mailman component, please suggest how to upgrade either one or > > multiple components based on the requirement. Is there any link that > > would help me to upgrade ? > > > > I have used the > > link https://docs.mailman3.org/en/latest/devsetup.html to install the > > mailman 3 components. I expected that the procedure followed in this > > link would install the latest versions of the mailman 3 components. > > Please correct me if I am wrong. Is there any latest version > > compatibility table ? > > > If you installed each of mailman, mailmanclient, django-mailman3, > postorius and hyperkitty according to instructions like > > $ cd ~/mailman > $ git clone https://gitlab.com/mailman/mailmanclient.git > > Then set up mailmanclient: > > $ cd mailmanclient > $ python setup.py develop > $ cd .. > > from that document, you should have the latest version. If that is the > case, `git log` in the mailmanclient directory should begin like > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, > origin/master, origin/HEAD) > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master' > > Use GHCR for the CI image > > See merge request mailman/mailmanclient!130 > > commit 8670751caff689733751ef323ef521c4a3fa1237 > Author: Abhilash Raj <raj.abhilash1(a)gmail.com> > Date: Wed Oct 14 17:36:58 2020 -0700 > > Use GHCR for the CI image > > commit ff39dd8f03a820f442f2251553c444370df3b914 > Merge: 80ebed4 76d44e1 > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Fri Aug 7 19:35:05 2020 +0000 > > Merge branch 'invite' into 'master' > > Add support for inviting an email address to join a list. > > See merge request mailman/mailmanclient!129 > > or if you did this before Oct 15, maybe it starts with > commit ff39dd8f03a820f442f2251553c444370df3b914 > > The particular commit you need for your issue is > > commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 > Merge: c8dcb1e 28d1c3a > Author: Abhilash Raj <maxking(a)asynchronous.in> > Date: Sat May 16 08:02:21 2020 +0000 > > Merge branch 'held-count' into 'master' > > Add a new get_held_count() API to get a count of held messages. > > See merge request mailman/mailmanclient!122 > > > > Note that unless you intend to do actual development of Mailman 3, you > should be following > <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather > than <https://docs.mailman3.org/en/latest/devsetup.html>. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/20/22 11:40 PM, Josef Dietl wrote: > Dear all, > > > > Sorry for coming back to a topic that seems to be done for 18 months now. > > I'm staring at this issue for a few days now (on and off). But I still get > these messages: > > > > Jan 19 22:43:27 2022 (149439) HyperKitty failure on > https://lists.[...]/hyperkitty/api/mailman/urls: > <html><title>Forbidden</title><body> > > <h1>Access is forbidden</h1><p>Please check the IP addresses > > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > > </p></body></html> (403) > > > > . and consequently, nothing ends up in the archive. > > > > I have checked (among others): > - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP > address, different orders, '*'. OK. > (Asterisk makes a difference, see at the bottom) ??? I didn't see what. > - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in > mailman-hyperkitty.cfg (except for the quotes). According to the editor's > color coding, the quotes are "right", too. I have removed special characters > to circumvent diverging treatment in different environments > > - I guess it doesn't matter, but wget --user restadmin --password [.] > http://localhost:8001/3.1/lists works, too. That is Mailman core's REST API which is not the issue here. > - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter > > > > I'm running a fresh package installation from Debian Bullseye with > certificates from Certbot with nginx, so Certbot may have messed with my > nginx config, but even that seems to be OK: Yes, Certbot has inserted > http->https redirection, but I'd expect that a https base_url and > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. It should. Note that your primary resource for help with issue with Debian packages should be Debian. > Mailman info says ... > To provide all possible information, I'm also adding the nginx log that > seems to correspond to that request (no other requests at that time, give or > take five minutes): Yes, everything yields 403 response codes. > > > > [.] - - [19/Jan/2022:22:43:27 +0000] "GET > /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] > HTTP/1.1" 403 175 "-" "python-requests/2.25.1" The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like `http(s)://host.example.com/hyperkitty/` If you append `api/` to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as the > Django settings. > > -- > 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/

7 years, 2 months

[MM3-users] Re: Apache shows No Lists

by Mark Sapiro

On 5/22/23 14:48, ceo(a)sartrack.nz wrote: > Thanks; > There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. So what I refer to as the Mailman user (a generic term) is `list` in your case. > I may have run the import fuction as root, but I then used chown() to set the directory tree /var/lib/mailman3/* to user 'list'. OK > So I upgraded Debian 10 to Debian 11. > This also upgraded Apache2 I assume, but I kept the original (single) config file. > > I then installed the whole Mailman3 package with 'apt'. I may also have installed additional missing bits afterwards, as I think it was not complete. I initially tried to use MariaDB but the installation failed completly because it never asked for the MariaDB root password, and as a result of that everyting else failed too. > Then I un-installed 5 times, and then I finally went for the 'default' database system. > > I then edited the file with the recommended settings for Mailman3: > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > So clearly Apache2 manages to access the data supplied by Postorius because it sees the lists (at least the empty ones). > -What user should the whole system running under: 'list'? of 'www-data'? > - Is there anything else I should tell Apache2? All the web based stuff is a Django application. Django is run by uWSGI which probably runs as www-data, but Django only accesses hyperkitty, postorius and django-mailman3 and other Django related tables in the database. It doesn't need access to file system files other than things like wsgi.py, urls.py, settings.py and settings_local.py and only read access to these. All the mailman3 file system stuff has to be read/write/searchable by `list`. > Now I tried to use "django-admin createsuperuser". This also fails because of this error: > ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) > And I cannot find where this 'force_text' is called from. It must be removed as it is too old. It seems your Django installation is broken. Do cd /usr/local/lib/python3.9/dist-packages/django grep -r force_text to find where force_text is called, or maybe add def force_text(s, encoding='utf-8', strings_only=False, errors='strict'): return force_str(s, encoding, strings_only, errors) to /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > When held mails are released in Mailman (maybe also mails which are not held) they are sometimes not sent nor archived, as mentioned in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > One of my list admins reported that he released two mails on Sep 25 07:20:48 2017 UTC, and only the first was sent to the members. In the mailman.log I found the following from that particular release: > ... I will look at the above as time permits, but ... > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 This one at least is a known issue. See <https://gitlab.com/mailman/mailman/issues/256>. As noted there, the underlying cause is <https://bugs.python.org/issue27321>, a bug in the Python email library (not yet fixed as of Python 3.6.2, but there are references to patches in the bug report). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 8:58 AM, Quanah Gibson-Mount wrote: > Now that we are on mailman3, I'm finding things that were really useful > in mailman2 are completely missing in mailman3, which seems odd, since > they in particular affect the ability of list moderators to do their job > well. > > a) When a post was made to a moderated list in mailman2, I would get an > email that included a LINK to the held email. Now I just get a canned > email saying I need to go to the dashboard, blah blah. Why was this > link removed? It was extremely useful and now I have to jump through > extra hoops. The message comes from Mailman core. Mailman core does not know what web management UI you are using or the URI to access it. You need to change the template for the message to include the URL. E.g. on this iist, in var/templates/sitr/en/list\:admin\:action\:post.txt we have As list administrator, your authorization is requested for the following mailing list posting: List: $listname From: $sender_email Subject: $subject The message is being held because: $reasons At your convenience, visit https://lists.mailman3.org/mailman3/lists/$list_id/held_messages to approve or deny the request. > b) When a post is made to a moderated list in mailman2, when I went to > the page to approve/deny/discard, there was additionally an option to > remove the moderated flag from the user for all future emails. This > option no longer exists. This was EXTREMELY useful, as we force all new > members of the list to be moderated for a time while we evaluate the > quality of their postings. Now I have to go manually track down the > user and their settings. Unnecessary extra hoops to jump through Click on the subject in the held messages list. At the bottom of the dialog that opens, there is a drop down to set the user's moderation. Normally, you would set it to 'default processing'. > c) When a post is made to a moderated list, one of the options when > selecting REJECT was it allowed me to set a custom message when > rejecting the email. This was extremely useful. For example today, > someone emailed our bug tracking list directly instead of filing a bug. > In the past, I would have added a note to them about what they should do > (in this case, I would have told them to send their email to our > community technical discussion list). Now I can no longer do that, I > can only reject it or discard it. Why was this removed? This was not "removed". It just hasn't been implemented in MM 3 yet. See, e.g., <https://gitlab.com/mailman/postorius/-/issues/368> and <https://gitlab.com/mailman/postorius/-/issues/368>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Installing Mailman for the first time

by Jim Berg, Jr.

I am not so sure what I am doing. Is there someone who does this for a fee? Jim Berg > On Mar 24, 2023, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/24/23 16:43, comprepair_jimberg--- via Mailman-users wrote: >> I am running Debian 11 Server and wanting to install Mailman 3 >> Will this work for what I am trying to do? >> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > > Yes, but <https://docs.mailman3.org/en/latest/install/virtualenv.html> is our current recommendation. > >> If not is there a shorter list of steps to accomplish what I am trying to do? > > The above may not be shorter. There are a lot of steps no matter how you do it. > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to comprepair_jimberg(a)icloud.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 7 months

[MM3-users] Re: how should I implement multiple domains for receiving emails to a list

by Mark Sapiro

On 4/15/25 16:51, Philip Bondi wrote: > > I have two domains: systemdatabase.ca, systemdatabase.homelinux.com > > All my lists should be on both domains. So h(a)systemdatabase.ca is the same list as h(a)systemdatabase.homelinux.com. I found this was the mailman2 behaviour on my old CentOS 7 installation and I am accustomed to it. While Mailman 2.1 had some support for multiple domains, list names had to be globally unique because a given list name referred to that one list regardless of domain. Mailman 3 is different in that the domain is part of the list name so h(a)systemdatabase.ca and h(a)systemdatabase.homelinux.com are different lists. > I edited /opt/mailman/venv_mm/var/data/postfix_lmtp directly. Duplicated and edited all the lines. And compiled with postmap /opt/mailman/venv_mm/var/data/postfix_lmtp > > I sent a test email. This appears to work. > > Is this the best method to achieve this goal? What would you recommend? If all you want is for mail to h(a)systemdatabase.ca or h(a)systemdatabase.homelinux.com to wind up at the same list, what you've done is OK, but whatever fqdn name your list is created as, it needs the other fqdn name added to it's Acceptable aliases setting, at least if Require Explicit Destination is Yes. The other issue is every time you start Mailman core it will implicitly run `mailman aliases` and overwrite your changes. I have a similar situation on one of the servers I support. The lists are all in a domain I'll call example.com, but we also want to allow mail to <list>@otherexample.com to reach the <list>@example.com list. We use this patch to add all those names. ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -261,5 +261,10 @@ class LMTP: '{}@{}'.format(alias, mlist.true_mail_host)) line = VMAPTMPL.format(true_addr, width, addr) print(line, file=fp) + if mlist.true_mail_host == 'example.com': + true_addr = self._decorate( + '{}@{}'.format(alias, 'otherexample.com')) + line = VMAPTMPL.format(true_addr, width, addr) + print(line, file=fp) print(file=fp) return True ``` However, this only works because example.com has an alias domain. If that weren't the case, we would need something like this instead. ``` --- a/src/mailman/mta/aliases.py +++ b/src/mailman/mta/aliases.py @@ -43,9 +43,14 @@ class MailTransportAgentAliases: """See `IMailTransportAgentAliases`.""" # Always return yield mlist.posting_address + if mlist.mail_host == 'example.com': + yield '{}(a)otherexample.com'.format(mlist.list_name) for destination in sorted(SUBDESTINATIONS): yield '{}-{}@{}'.format( mlist.list_name, destination, mlist.mail_host) + if mlist.mail_host == 'example.com': + yield '{}-{}@{}'.format( + mlist.list_name, destination, 'otherexample.com') def destinations(self, mlist): """See `IMailTransportAgentAliases`.""" ``` Do not use both those patches. If your list domain has an alias domain, use only the first one and if not, only the second. -- 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

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

On 1/6/20 11:16 PM, hansen(a)rc.org wrote: > Mark Sapiro wrote: > >> What's the setting for base_url in mailman-hyperkitty.cfg? > > It's > base_url: https://<OLDHOSTNAME>/archives > > I suppose it should be changed to > base_url: https://<NEWHOSTNAME>/archives That's part of it, but see below. > But: > What if we decided to have more than one domain, as the UI indicates is kosher? Again, see below. >> Are there any errors in var/logs/mailman.log? > > Yep. Lots. They all are of this nature: > > Exception in "hyperkitty" archiver > Traceback: > ... > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", line 430, in _match_hostname > match_hostname(cert, asserted_hostname) > File "/usr/lib/python3.7/ssl.py", line 327, in match_hostname > % (hostname, dnsnames[0])) > ssl.SSLCertVerificationError: ("hostname 'OLDHOSTNAME' doesn't match 'NEWHOSTNAME'",) OK. So the real issue is you are trying to access HyperKitty via an https URL and the certificate presented by the web server doesn't allow the domain in the URL. The domain in the URL doesn't really matter as long as it resolves to the HyperKitty host, but if it's an https URL the host's certificate must include that domain. It looks like in your case, the certificate is for 'NEWHOSTNAME', so setting base_url: https://<NEWHOSTNAME>/archives should be enough >> qcluster is not what you need to restart. You need to restart whatever >> is supporting the wsgi interface to Django. This may be uwsgi or >> gunicorn or ??. Whatever it is, that's what needs to be restarted. > > Beats me, Mark. Brian, do you know? Brian has answered: systemctl restart gunicorn >> If you do ps ax|grep runner=, what do you see? If you don't see at >> least three processes with --runner=rest:0:1, stop Mailman and start >> Mailman. > > Yep. I did not get the whole string before. With your options I see three > of these rest:0:1 processes. So I guess the REST stuff is running anyway. OK >> If so, what's >> in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as filename in the file handler in the LOGGING >> definition in settings(_local).py. > >> hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log >> return Site.objects.get_current(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 60, in get_current >> return self._get_site_by_request(request) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", >> line 45, in _get_site_by_request >> SITE_CACHE[domain] = self.get(domain__iexact=domain) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", >> line 82, in manager_method >> return getattr(self.get_queryset(), name)(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line >> 408, in get >> self.model._meta.object_name >> django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. > >> This is because of the domain change. In settings(_local).py you have a >> setting for SITE_ID. Possibly, setting that in settings_local.py to a >> value one greater that the current setting will do. > > Trying setting it to 1 (it was 0 before). OK. You can just shotgun trying numbers until one works, or >> To be certain of the >> correct value, you need to look at the django_site table in mailman's >> database. That table has 3 columns, id, domain and name. The id for the >> row of your domain is what needs to be set as SITE_ID. > > You lost me here. No idea how to access the Mailman database. > Brian, do you know? It depends on the database engine. In the database section in your mailman.cfg there is a class: definition which will mention sqlite, mysql or postgresql. The tools for interacting with these are sqlite3, mysql and psql respectively. >> Stop Mailman and then start it. > > No idea here, either. I looked online and found this: > > $ from mailman.commands.cli_control import Stop > But it complained: > from: too many arguments That's a Python statement, not a shell command. You would do systemctl stop mailman systemctl start mailman alternatively, you could do /path/to/bin/mailman stop /path/to/bin/mailman start but that appears to not be the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: MM3 & postfix ... (mail loops back to myself)

by Abhilash Raj

On Thu, Jan 18, 2018, at 2:39 PM, Mark Sapiro wrote: > On 01/18/2018 02:25 PM, Dmitry Makovey wrote: > > > > transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > > local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp > > relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains > > The initial implementation of Mailman's regexp maps for Postfix was > broken. This was fixed by > <https://gitlab.com/mailman/mailman/merge_requests/323>. The bottom line > is if /opt/mailman/core/var/data/postfix_lmtp contains entries like > Also, MR 323 was backported to Core's 3.1 release. So if you are running the newer images with 3.1.1 release, you should ideally have the fix. > /^foo-bounces(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > /^foo-confirm(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > > these entries (only the -confirm and -bounces, not the others) need to be > > /^foo-bounces(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > /^foo-confirm(\+.*)?(a)lists\.my\.com$/ lmtp:[172.19.199.2]:8024 > > because Postfix recipient_delimiter = + is not effective for regexp tables. > > -- > 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/ > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

8 years, 9 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/25/22 07:54, denis.bitouze(a)univ-littoral.fr wrote: > > > Mark Sapiro wrote: > > The difference between Reject and Discard is Reject notifies the > > sender of the rejection whereas Discard just discards the message > > without notification. > > IMHO, even in English, “Reject” and “Discard” are not > > self-explanatory. > > They seem so to me, but in any case, if you look at Postorius -> > Settings -> Message Acceptance -> Default action to take when a > (non-)member posts to the list, they are described there in much more > detail. OK: not easy to figure out. A tooltip on the corresponding buttons would be helpful. > > BTW, no clue about an automatic banishment of emails from discarded > > messages? > > In the pop-up dialog from clicking the subject of a held post you can > set the sender's moderation status when discarding the post. Sorry but I can only see: - “--- Set member moderation ---” (non selectable, I guess) - “Hold for moderation” - “Reject (with notification)” - “Discard (no notification)” - “Accept immediately (bypass other rules)” - “Default processing” and cannot see how I can at the same time “Discard (no notification)” and “Banish the email of the post's sender”.

4 years, 4 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 11:06 AM, David Newman wrote: > > 1. In Users/Members, moderation action for the newly resubscribed users > shows as "None". Is there a method, either in the UI or the command > line, to change this to "Default processing" for all users? I assume you don't want to set `Default action to take when a member posts to the list` to Default Processing because you want new member posts to be held. This is a good practice. To set all members to default processing in 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 >>> from mailman.interfaces.action import Action >>> for mbr in m.members.members: ... mbr.moderation_action = Action.defer ... >>> commit() >>> ``` > 2. Although Delivery Mode shows as "Regular" for all users in > Users/Members list, clicking on a member's name shows all options such > as delivery status, delivery mode, etc., as undefined. They show as undefined, but if you look at your own settings by selecting `Mailman settings` from the dropdown under your username at the upper right in Postorius, you will see you have Global Mailman preferences, Address-based preferences and List-based preferences. If a list based preference is unset for a list, it falls back to the address based preference for the address and if that's unset, to the global preference. When you as an admin look at a user, you only see the user's list based preferences. > Similar question: How to set subscriber options for all members in one go? Per the above, you only need to set the user's preferences if they don't have address based preferences and the preference differs from the global (default) preferences. However, if you want to set the member's list preferences, you could add to the beginning of the above: ``` >>> from mailman.interfaces.member import DeliveryMode, DeliveryStatus >>> english = getUtility(ILanguageManager).get('en') ``` and to the `for` loop in the above: ``` ... mbr.preferences.acknowledge_posts = False ... mbr.preferences.delivery_mode = DeliveryMode.regular ... mbr.preferences.delivery_status = DeliveryStatus.enabled ... mbr.preferences.hide_address = False ... mbr.preferences.preferred_language = english ... mbr.preferences.receive_list_copy = False ... mbr.preferences.receive_own_postings = True ``` Or whatever you think these settings should be. > 3. As a subscriber to this list, I received email notification that I'd > been unsubscribed. Where is the control for enabling/disabling > subscription notifications? Settings -> Automatic Responses > Settings/Member Policy/Un-subscription Policy is set to Confirm, but I > don't think that's relevant here since I unsubscribed users as the > Django superuser. Correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 8:36 AM, bryan.kartzman(a)yu.edu wrote: > > I'd like to say it worked flawlessly (and it did allow the archives to be displayed, which wasn't happening before, but I'm getting the following two errors (or maybe KeyError 1365 and 1366 are the same error?) every minute: > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1365 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1365 > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1366 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1366 > > Is this an error only in the archives or might I also have a problem with other timestamp fields in the database? If its just the archives, is there a simple way to fix it? If no simple way to fix the archives, is there an easy way to erase all list archives? If no easy way to erase all list archives, would deleting all the lists and recreating them remove the archives? The above errors have nothing to do with timestamps. There are entries in the hyperkitty_thread table with starting_email_id = 1365 and 1366, i.e., `SELECT * FROM hyperkitty_thread WHERE starting_email_id in (1365, 1366);`, but there are no entries in the hyperkitty_email table with id = 1365 or 1366. You could look at the thread_id for those entries in the hyperkitty_thread table and see if there are entries in the hyperkitty_email table with message_id_hash = those thread_id values. if those entries exist, you can fix this by altering the starting_email_id of those entries to the respective id values for those messages from the hyperkitty_email table. If those messages don't exist in the hyperkitty_email table, you could just delete the offending entries from the hyperkitty_thread table. As far as deleting archives is concerned, a Django superuser should have a `Delete Archive` button on the top level Hyperkitty view for the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

ok Thank you Mark for your valuable time. I will try this method and let you know the status. Thanks once again. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/20 12:08 AM, Shashikanth Komandoor wrote: > > I tried this way but in this method I don't find any files to edit for my > > customizations like > > 1. Removal of social accounts, > > 2. Addition of SMS integration and so. > > > > If I can do my required customizations through pip installation I am fine > > with that. > > If you follow the instructions for installing in a virtualenv, in say > /opt/mailman/venv, all the component files will be in > /opt/mailman/venv/lib/python3.x/site-packages > > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Mark Sapiro

On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > Now that I look at it, I think you should clarify that if one is not > interested in using PostgreSQL (which is what `pip install psycopg2-binary` > is for), > then there should be some different binary they need to install, no? And > which one is it? I have added a note to the comment at https://wiki.list.org/DOC/Mailman%203%20installation%20experience which says: """Also, please note the first paragraph of the introduction. This is documentation of my decisions and experiences. It is not a how-to and does not replace the documentation at http://docs.list.org/""" In particular, documentation of the requirements for different databases is at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > Under your "*Recommended Configuration*", I have followed each step, > getting the files and editing them to suite my needs, until I got to where > you refer to: > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file but > with DEBUG = False) > I tried to get this file using `git clone > https://gitlab.com/mailman/mailman_suite.git` and realized that > authentication is required in order to get it. Because you should be getting <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) which works without authentication. Or you could just go to <https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/…> and copy it from there. > What is the reason you did not include a copy like for the rest?? Because it's available on GitLab. > I have created the executables - all of them. > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > mailman3.org/mydomain.name/g' {} \;` > Maybe you should state explicitly that once one gets these templates, they > need to change the url to match theirs. You said it, but it doesn't come out > forcefully :0 I added "Of course, if you use these you need to edit the URLs for your site." > In your "MTA" section, I suppose you need to be a little more generic as > well and accommodate Exim users. > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > mailman.cf to ensure that the values under [mta] match what is required. > Maybe there is a different file to edit for MTA settings??? Again, I'm documenting MY experience, not trying to replace the official documentation. I refer to <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> because I use Postfix. That same page also has Exim documentation. > So far ..... > > Next, I will be looking into "Running Things".... which is where I believe > things will get thicker .... Perhaps when you're done you will write u your experiences with FreeBSD and Exim. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Errors while importing mm2 list archives

by Mark Sapiro

On 12/10/22 01:13, Odhiambo Washington wrote: > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> In the DATABASES['default'] definition, you need to set `'OPTIONS': >> {'charset': 'utf8mb4'}` >> > > I added that: > > [database] > class: mailman.database.mysql.MySQLDatabase > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > /mailmansuite?charset=utf8mb4&use_unicode=1 The above is for Mailman core. It doesn't affect HyperKitty. For that you need to look at the DATABASES definition in /etc/mailman3/settings.py <https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> and ensure that in addition to the other settings under `default {` you have ``` 'OPTIONS': {'charset': 'utf8mb4'}, ``` ... >> You might also need to modify the tables, particularly hyperkitty_email >> with something like >> ``` >> ALTER TABLE hyperkitty_email >> DEFAULT CHARACTER SET utf8mb4, >> MODIFY subject varchar(512) >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, >> MODIFY content >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; >> > > > So I removed my list, dropped the database, and proceeded as follows: > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > utf8mb4_0900_ai_ci; > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET utf8mb4 > COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER SET > utf8mb4 COLLATE utf8mb4_unicode_ci; > > I did all those (although looks overzealous) just to be on the safe side. I > have seen people putting emojis in their names. None of that should be necessary. `mailman-web migrate` should create the database and tables as needed. > After that, I did the mailman-web migrate, created the list, imported the > config from MM2 and then proceeded to import the archives. > However, the errors still are there, and several messages were not imported Do you have the OPTIONS setting in your DATABASES definition in settings.py? ... > Warming up cache > Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 402, in run_from_argv > self.execute(*args, **cmd_options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_import.py", > line 411, in handle > call_command("hyperkitty_warm_up_cache", list_address) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/__init__.py", > line 198, in call_command > return command.execute(*args, **defaults) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/management/base.py", > line 448, in execute > output = self.handle(*args, **options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 53, in handle > self.warm_up_mlist(mlist, options) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/management/commands/hyperkitty_warm_up_cache.py", > line 61, in warm_up_mlist > for thread in mlist.recent_threads: > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 162, in recent_threads > return self.cached_values["recent_threads"]() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/common.py", > line 58, in __call__ > return self.get_or_set(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in get_or_set > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/models/mailinglist.py", > line 317, in <listcomp> > return [Thread.objects.get(pk=pk) for pk in thread_ids] > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/manager.py", > line 85, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/models/query.py", > line 650, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does > not exist. > (venv) [mailman@gw ~/mm]$ I have no idea what would cause this in a newly created database with no archives before running hyperkitty_import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 8/27/20 5:44 PM, Simon Handfield via Mailman-users wrote: > > Traceback (most recent call last): > File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text > msg.set_payload(payload, charset) > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) > > I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Sorry for not answering earlier and for not being able to devote more time to this now as I'm going away within the hour, but this looks as if the message is somehow defective. Basically, the message can't be flattened by its as_string() method because of unicode issues. This can occur because of non-ascii characters is the message headers or in body parts explicitly or implicitly declared as ascii. We have had workarounds for this for some time, but I don't think they are in 3.1.1, See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/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, 2 months

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Thank you very much for the quick fix, Mark and Abhilash! Abhilash, could you include the fix into the "latest" version of mailman-web container please? Btw I wasn't able to find a changelog of Mailman docker images anywhere and 'Releases' page in Github is quite outdated too... Is there any other place I should check? Danil вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > What could be a reason of HyperKitty failing to create a thread from > > chained emails? > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > "Openvpn and Network mapping" discussion displayed as five threads > instead > > of only one... > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > Thanks for the report. > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > will fix this. > > -- > 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/ >

7 years, 8 months

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Zaheer Abbas

Thanks, Mark & Odhiambo for providing options for the solution. I will try the 'postorius header filters' hacky way as it's more suitable to my requirement, however, if it didn't work as expected, then filtration through exim filter is also an acceptable option. Thanks again for the quick response. On Thu, Mar 30, 2023 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/30/23 11:07, Odhiambo Washington wrote: > > So the MTA option that doesn't involve any regex is better than no? > > Partly it's a matter of taste and possibly a matter of necessity. I.e. a > list admin can do this with header filters and may not have access to > the MTA config. > > Also, it's not clear to me that doing this in Postfix is less > complicated than understanding a regex. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to zaheer.psg(a)gmail.com >

3 years, 7 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/29/22 05:48, Jacob Sievert via Mailman-users wrote: > Hello, > > we seem to have the same problem right now. > > We are still on python3.6 and postgresql 12.9 > > I looked at our Table pendedkeyvalue and we have roughly 35k rows in > that table, > is that normal or shouldn't those get cleaned up after a while? Yes they should. This is https://gitlab.com/mailman/mailman/-/issues/257 fixed in Mailman core 3.3.5. Also in Mailman 3.3.5 is a new Task runner that runs periodic tasks, one of which is to remove orphaned pendings. This may also be the issue for the OP in this thread if that pendedkeyvalue table is also large. Here is a `mailman shell` script that will clean that up. ``` # Prior to Mailman 3.3.5, some tokens for user confirmations were pended with # too long a lifetime. This script removes those pendings based on when they # were pended and the configured pending_request_life rather than their # expiration. # Also prior to Mailman 3.3.5, pended held_message tokens for email handling # of the message were not removed when the message was handled via REST. This # script removes those pendings too. # This is run with # mailman shell -r delete_orphans_expireds # after saving it as # /opt/mailman/mm/venv/bin/delete_orphans_expireds.py from datetime import datetime from lazr.config import as_timedelta from mailman.config import config from mailman.database.transaction import transactional from mailman.interfaces.pending import IPendings from zope.component import getUtility pendings = getUtility(IPendings) def is_request(id): if config.db.store.execute( 'SELECT * FROM _request WHERE id = {};'.format(id)).rowcount > 0: return True return False then = datetime.now() - as_timedelta(config.mailman.pending_request_life) thenm = datetime.now() - as_timedelta(config.mailman.moderator_request_life) def fromisoformat(x): if hasattr(datetime, 'fromisoformat'): return datetime.fromisoformat(x) try: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S.%f') except ValueError: return datetime.strptime(x, '%Y-%m-%dT%H:%M:%S') @transactional def delete_orphans_expireds(): count = 0 for token, data in pendings.find(pend_type='held message'): if data and not is_request(data['id']): result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} orphaned pended held messages') count = 0 for token, data in pendings.find(pend_type='data'): if data and data['_mod_hold_date']: when = data['_mod_hold_date'] if isinstance(when, str): when = fromisoformat(when) if when < thenm: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired held messages') pends = list(pendings.find(pend_type='subscription')) pends += list(pendings.find(pend_type='unsubscription')) count = 0 for token, values in pends: if values and values['token_owner'] == 'subscriber': when = values['when'] if isinstance(when, str): when = fromisoformat(when) if when < then: result = pendings.confirm(token, expunge=True) count += 1 print(f'expunged {count} expired (un)subscription confirmations') ``` The above says to save the script at /opt/mailman/mm/venv/bin/delete_orphans_expireds.py but that path may need to be adjusted based in where Mailman's bin/ directory is in your installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: installing a new instance of mm3

by Christian Stalberg

mailman.log is showing this: ERROR 2021-10-18 22:19:12,385 616 django.security.DisallowedHost Invalid HTTP_HOST header: 'subdomain.domain.tld'. You may need to add 'subdomain.domain.tld' to ALLOWED_HOSTS. ERROR 2021-10-18 23:01:15,318 616 django.security.DisallowedHost Invalid HTTP_HOST header: '192.168.0.1'. You may need to add '192.168.0.1' to ALLOWED_HOSTS. Where do those entries go? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 11:44 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: installing a new instance of mm3 On 10/22/21 6:37 AM, Christian Stalberg via Mailman-users wrote: > Is this document that Brian Carpenter wrote still valid? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 As Steve said, it should be. > Brian installed my instance. Now its broken. My lists are down. I'm > getting nowhere with diagnostics and troubleshooting (which was easier > with mailman 2). What's broken? Postorius, Hyperkitty, mail delivery, all of them? Do you find any clues in the logs at /opt/mailman/mm/var/logs/? Particularly mailman.log for core and mailmansuite.log for Postorius and Hyperkitty. We will try to help if we have information to help identify the problem. -- 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/

5 years

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Andrew Hodgson

bin/mailman import21 I saw this in the image, do you have any idea about what may be missing from this? I may shelve this project again for the time being if we can't do the migration, but good to know I can get a production like Docker instance running relatively painlessly. Andrew. -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: 01 September 2017 16:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman3 Docker question and importing lists from MM2 On 09/01/2017 07:09 AM, Andrew Hodgson wrote: > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > I want to use multiple domains, what is the best way to specify multiple domains in this environment variable? I don't know the answer to this. > Furthermore, is there a recommended way to get data from MM2 (list configs and archives) into MM3? There are two things. For importing list configs there is bin/mailman import21 but it is not up to date and probably doesn't work. For importing archives there is django-admin hyperkitty_import [--settings=if.needed] which works well using the MM 2.1 LISTNAME.mbox/LISTNAME.mbox file as input. -- 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/

9 years, 2 months

[MM3-users] Re: Mail configuration

by Darren Smith

Mark, This is Mailman3. On Mon, Mar 26, 2018 at 1:53 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 03/23/2018 10:05 AM, Darren Smith wrote: > > > > We have been told that "warming up" the IP is the way to go - that is, > > cutting over just some of the traffic a little at a time. So what I am > > looking for is a way for all mail on our domain to be sent to our current > > mailman installation, and based on some configuration (certain mailing > > lists?) certain emails being sent out to the list subscribers will first > be > > forwarded to the new server and be sent from the new IP address. > > > > Does that make sense? > > > > Does anyone know a way that mailman/postfix can be configured to > accomplish > > this? > > > Is this Mailman 3 or Mailman 2.1? The Mailman side of this would be > different depending on which. If it's Mailman 2.1, a better list is > mailman-users(a)python.org > <https://mail.python.org/mailman/listinfo/mailman-users> > > > -- > 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/ >

8 years, 7 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 11:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 12:50 PM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: > >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >>> > >>>> > >>>> > >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >>>> wrote: > >>>> > >>>> /bin/sh: sass: Permission denied* > ... > >> Try `which sass` > >> > > > > root@gw:/usr/home/wash # su mailman3 > > (venv) [mailman3@gw /usr/home/wash]$ which sass > > (venv) [mailman3@gw /usr/home/wash]$ > > > > There is no sass. > > > There has to be. You can't get a permissions error on sass if it doesn't > exist (well, maybe if you don't have permission to search a > superordinate directory, but that's unlikely). > > Try `find /usr -name sass` > /usr/local/include/sass That is the only thing found that is in the base system. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 5 months

[MM3-users] Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Mark Sapiro

On 2/8/22 09:01, Lucio Chiappetti wrote: Snipping to what I thing are the issues. > What I found now (after the migration done by the administrators of the > central seat) is that in mailman3: > > - accept_these_nonmembers is empty > - there are 189 entries listed in Non-members (which look those > formerly in accept_these_nonmembers) And those non-members all have there moderation action set to Defer which means their posts will be accepted but the additional checks such as too big, etc. will still be applied. > - hold_these_nonmembers was copied identical with the same regexp's > as in mailman2 This is all expected. MM 3, unlike MM 2.1 has a concept of nonmembers with moderation action, and this is intended to replace *_these_nonmembers. The legacy *_these nonmembers attributes still exist to support regexps. This is why the addresses were made nonmembers with the appropriate moderation action, but the regexps were retained. > - I have inspected a few of them and found that they have > Administration options Moderation set to List default I'm not sure what you are looking at here. Imported nonmembers should all have moderation action set according to which *_these_nonmembers they came from. Imported members should have their moderation action set to Defer if they were unmoderated and if they were moderated, it should be set based on the 2.1 list's member_moderation_action. > - the effect of this apparently was that a post from some.guy(a)inaf.it > (whose subscription address is guy(a)somewhere.inaf.it) was hold for > moderation > > is this due to a loop with the regexp in hold_these_nonmembers ? It is because all the legacy *_these_nonmember actions are applied before nonmember moderation checks, so if an address matches a regex in hold_these_nonmembers, the post will be held regardless of the nonmember's moderation action. This may actually be a bug. I'll have to think about that. I've filed https://gitlab.com/mailman/mailman/-/issues/978 on this. > the default action would be to let it pass > > Or should we set Administration options Moderation to Accept > immediately ? No. You can avoid this issue by adding the 189 nonmember addresses to accept_these_nonmembers (as addresses, not regexps). Addresses still work, and accept_these_nonmembers takes precedence over hold_these_nonmembers just as in MM 2.1. > - if so, how can we do it automatically for all 189 entries ? > - or move back the 189 addresses to accept_these_nonmembers ? Yes, move them back. > - or for the future have persons posting with alternate addrresses > accepted for the future WITH ONE CLICk ? If they are nonmembers, you can accept the post and set moderation action in one operation in Postorius, but the regexps in hold_these_nonmembers will still take precedence. > - AND LAST BUT NOT LEAST would the syntax @list1 in > accept_these_nonmembers work in mailman3 ? This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/8/25 18:45, MegaBrutal via Mailman-users wrote: > > User-profile shows my GMail address as primary and my own-domain address as > secondary. The third address is not present, because I actually wanted to > get rid of it, and it seems I succeeded in that. This is your Django user which has the two addresses associated with it. > Mailman3/users shows me with the address I wanted to get rid of. If I click > Manage, I see all 3 addresses, with (for some reason) only the GMail one > being verified (strange because I'm sure I verified the other as well). And > here's something interesting: it shows me as a member with my GMail address > under subscriptions, but shows me with my megabrutal.com domain under > ownerships. These are your Mailman user and its addresses. They are not the same as your Django user and its addresses. I don't think you can unlink an address from your Mailman user in Postorius/HyperKitty. You can do that in `mailman shell`. ``` $ 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. >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') # any of the three addresses >>> usr.addresses prints a list of the 3 addresses. These are indexed as 0, 1, 2 >>> usr.preferred_address prints the preferred address. If this is the one you want to delete, do >>> usr.preferred_address = usr.addresses[n] # n is the index of one you want >>> del usr.addresses[n] # n is the index of the address you don't want >>> usr.addresses.remove(n) # n is the index of the address you don't want >>> commit() ``` It may not be clear from the above, but the idea is that you are deleting the address you don't want from usr.addresses, but before that if the one you don't want is the preferred_address, you need to set the preferred address to one of the others. Also, `del usr.addresses[n]` deletes the address record, but it is still in the addresses list, thus the `usr.addresses.remove(n)`. This is untested, so before committing you may want to verify that `usr.addresses` now lists just the two addresses you want > This might be the cause? Maybe HyperKitty wants to use my owner identity, > which is not subscribed? Btw, is the owner not automatically considered as > someone who can post to the list, they also need to be subscribed? An owner is not a list member and has no special posting privileges. If only members are allowed to post, the owner address must also be a member to be allowed to post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Execute assorted Mailman functions via Mailman shell terminal

by Mark Sapiro

On 5/13/25 12:40, Andy Matthews wrote: > When my company migrated from MM2 to MM3, they discovered there were things that didn't work as expected (don't get me started). So they developed a set of Python functions which allowed then to fill in the missing functionality. However, they've discovered that some of those functions either never worked properly, or no longer work. For example, > > ``` > def list_nonmembers(mlist): > for accepted in mlist.accept_these_nonmembers: > print("Accepted: ",accepted) > for held in mlist.hold_these_nonmembers: > print("Held: ",held) > ``` > They're run by shelling into the machine which hosts mailman and executed like so (where scripts is `scripts.py`) > > ``` > sudo -iu mailman mailman shell -l MAILING_LIST_ID --run scripts.list_nonmembers > ``` That should work. What happens when you run it? Possibly it prints nothing because the list's accept_these_nonmembers and hold_these_nonmembers attributes are empty. > I'm recommending that we install Postorius, as I suspect many of the functions they've written are already present in that UI, but it's not as simple as that. Instead they're wanting a handful of these functions (including the one listed above) replaced sooner than we could get Postorius up and running. > > I've gotten this far: > ``` > from mailman.interfaces.listmanager import IListManager > from zope.component import getUtility > mylist_id = 'bravo-open1(a)tena-sda.org' > list_manager = getUtility(IListManager) > mylist = list_manager.get(mylist_id) > ``` > > The mylist variable is of type `mailman.model.mailinglist.MailingList`, and includes an Attributes for nonmembers: > ``` > mylist.nonmembers > <mailman.model.roster.NonmemberRoster object at 0x7ffffa3e65b0> > ``` > > But this nonmembers property doesn't output any users/addresses when printed, and throws a TypeError when I try to iterate over it: First of all I think there may be some confusion between the list's nonmembers and the *_these_nonmembers attributes. *_these_nonmembers are legacy attributes which exist to support `^...` regexps and `@list_id` entries, but the preferred way to accept, hold, reject or discard individual nonmembers is to set the nonmember's moderation action. > ``` > Traceback (most recent call last): > File "<console>", line 1, in <module> > TypeError: 'NonmemberRoster' object is not iterable > ``` You need to iterate over mylist.nonmembers.members, i.e. the roster's members, not the roster. > So, given a mailing list instance, retrieved via `list_manager.get(mylist_id)`, how would I go about printing all nonmembers and their current roles in a list (held, accepted, etc.)? Alternately, is there a different question I should be asking in order to retrieve that information? It's not roles as you've already limited the role to nonmember. It's moderation_action. ``` for nonmember in mylist.nonmembers.members: print(f'Nonmember: {nonmember.address.email},' f' moderation_action: {nonmember.moderation_action}') ``` Note that moderation_action: None means list default. -- 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

[MM3-users] Re: install v3.3.11

by Jose Bernal

Thank you - that worked and pip also uninstalled the 3.3.10 package. I appreciate the help. --------------------- José Bernal Web/Application Engineer Oregon Criminal Defense Lawyers Association Cell 541-228-8481 jbernal.web.dev(a)gmail.com On Fri, Feb 14, 2025 at 9:05 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/14/25 08:50, Jose Bernal via Mailman-users wrote: > > I'd like to install Mailman v3.3.11. Are there instructions for > installing > > from pip? If not, is there an alternate way to install this latest > > version? When executing: > > > > pip install mailman==3.3.11 > > > > I get: ERROR: No matching distribution found for mailman==3.3.11 > > > 3.3.11 is still in development and hasn't yet been released to PyPI so > if you want to install it in its current state, you have to install from > GitLab. > > pip install git+https://gitlab.com/mailman/mailman@master > > will install the head of the master branch in GitLab. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jbernal.web.dev(a)gmail.com >

1 year, 9 months

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/29/20 4:15 PM, Massimo Zappalà wrote: > Hi Mark, > > /usr/lib/python3/dist-packages/mailman/templates/it$ ls -la > > -rw-r--r-- 1 root root 484 Jul 25 17:21 domain:admin:notice:new-list.txt > -rw-r--r-- 1 root root 825 Jul 25 17:06 help.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 __init__.py > -rw-r--r-- 1 root root 701 Jul 25 17:19 invite.txt > -rw-r--r-- 1 root root 337 Jul 26 16:36 list:admin:action:post.txt > -rw-r--r-- 1 root root 145 Jul 26 16:36 list:admin:action:subscribe.txt > -rw-r--r-- 1 root root 157 Jul 26 16:36 list:admin:action:unsubscribe.txt > -rw-r--r-- 1 root root 56 Jul 26 16:23 list:admin:notice:subscribe.txt > -rw-r--r-- 1 root root 334 Jul 26 16:49 list:admin:notice:unrecognized.txt > -rw-r--r-- 1 root root 43 Jul 26 16:49 list:admin:notice:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:digest:header.txt > -rw-r--r-- 1 root root 423 Jul 26 17:07 list:member:digest:masthead.txt > -rw-r--r-- 1 root root 160 Jul 26 17:08 list:member:generic:footer.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:regular:header.txt > -rw-r--r-- 1 root root 658 Jul 26 17:18 list:user:action:subscribe.txt > -rw-r--r-- 1 root root 675 Jul 26 17:18 list:user:action:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:user:notice:goodbye.txt > -rw-r--r-- 1 root root 328 Jul 26 17:23 list:user:notice:hold.txt > -rw-r--r-- 1 root root 464 Jul 26 17:31 list:user:notice:no-more-today.txt > -rw-r--r-- 1 root root 108 Jul 26 17:32 list:user:notice:post.txt > -rw-r--r-- 1 root root 634 Jul 26 17:38 list:user:notice:probe.txt > -rw-r--r-- 1 root root 318 Jul 26 17:40 list:user:notice:refuse.txt > -rw-r--r-- 1 root root 155 Jul 26 17:42 list:user:notice:rejected.txt > -rw-r--r-- 1 root root 554 Jul 26 17:47 list:user:notice:welcome.txt > drwxr-xr-x 2 root root 4096 Jul 29 22:14 __pycache__ What is the ownership of the other directories in /usr/lib/python3/dist-packages/mailman/? They are probably also owned by root and that should be OK as long as they are world readable. >> I may need more information about messages that are and aren't >> delivered. I.e. what's different between them and the way they are >> submitted, or is this one message only delivered to some users? > > After copying the template files in the path indicated by you, the translated emails arrive only to the administrator user while the members of the list arrive in English. Please tell me what messages. Do you mean if I subscribe to the list, I get a welcome message in English, but the list owner gets the notification of a new member in Italian? I think you need to set the system default_language. In mailman.cfg, set [mailman] default_language: it -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is from the file /var/log/maillog: Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the Postfix mail system Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 from=<root> Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: message-id=<20170725073005.03F4160D143F(a)localhost.localdomain> Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: from=<root(a)localhost.localdomain>, size=508, nrcpt=1 (queue active) Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: to=<root(a)localhost.localdomain>, orig_to=<root>, relay=local, delay=0.11, delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed It seems that postfix is working, isn't it? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > 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

9 years, 3 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Stanisław Findeisen

Thank you for your clarification. I am now wildcard (*) DKIM-signing the (arbitrary) From: address domain with the host domain key. However my mailing list is a virtual host (actually there are several of them), which is different than the host domain. Do you know if such a setup is harmful? Or if there is a way to select the VHOST key? This is Postfix + OpenDKIM. With DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = Yes the VHOST key gets selected, which also results in (existing and) valid DMARC. Perhaps this setup makes it easier to pass through the spam filters?... But the cost is the abused From:. Thank you Stanisław On Sat, Mar 12, 2022 at 12:49:38PM -0800, Mark Sapiro wrote: > On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: > > > Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your > > > valid DKIM signature and no prior Authentication-Results:. > > > > Ok, you mean after replacing the From address with the list address, right? > > I can see no way (or sense) to DKIM sign arbitrary From: addresses. > > > Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. > validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. > > If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we > have DMARC mitigations suck as replacing the From: with the list address. > > > > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). > > > And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you > shouldn't need to rewrite From:. If it is because of DMARC, you do. > > > > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? > > > This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. > > We DKIM sign all outgoing mail from lists.mailman3.org. > > -- > 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/

4 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

It's ok now, but still I can't make it send the confirmation email This is from mailman.log: [mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90 What should I do? El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > Why does it say Address already in use? > > > Because you are starting lm tp runner and it's already running. > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > any if necessary. Then do 'mailman start'. > > -- > 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

9 years, 3 months

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Ugnius

Mark, Thank You for your guidance. Yes, seems my installed mailman3 package is not full. I have tried to install it on my Debian 9, but I got package broken error and all possible proposals how to fix it did not help. But it is normal - official OS version 9 has no this package included. Then I have decided to play on another machine where is installed Debian 10. I have successfully installed mailman3-full. It already came pre-configured with keys included. Mailman3-web packige was something new for me. I understand it replaces mailman- suite, but like I did not find where to read about it, I did not find how to open the administration or postorius site. Kind regards Ugnius > On 23 Aug 2019, at 23:18, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 8/23/19 12:17 PM, Ugnius S wrote: >> >> It would be good to read about working example how to setup, and which >> moments are important. > > > See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. > > > -- > 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/

7 years, 2 months

[MM3-users] Re: Error when sending customized welcome message template

by Markus Grandpré

Dear Mr. Sapiro, Thank you once again for your help. The templates are now being sent without any errors. However, while using the many variables that can be sent with a template, I noticed that the resolution of the variable $hyperkitty_url is not working, even though i am using a private archive in this list and a URL to this archive exists. Best regards, Markus Grandpré Am 13.03.25 um 14:12 schrieb Mark Sapiro: > On 3/13/25 2:54 PM, Markus Grandpré wrote: >> Dear List, >> >> As soon as a template "[list:user:notice:welcome]" exists, and at >> least one email address is provided during mass subscribe, while >> sending an invitation is disabled and sending a welcome message is >> enabled, the following error occurs: >> >> HTTP Error 400: ('Connection aborted.', ConnectionResetError(104, >> 'Connection reset by peer')) > > Was this template set in Postorius? If so, there is an issue with your > setting for POSTORIUS_TEMPLATE_BASE_URL. The default is > ``` > POSTORIUS_TEMPLATE_BASE_URL = http://localhost:8000/ > ``` > which should work if your wsgi server is listening on the local host, > port 8000, but setting it to the base scheme and host you use to access > Postorius is generally good. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: +49 7531 88 4342

1 year, 7 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 12/28/21 11:56 AM, William Oliver wrote: > > 1) I got the error > > django.template.library.InvalidTemplateLibrary: Invalid template > library specified. ImportError raised when trying to load > 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' > from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- > packages/mistune/scanner.py) > > when I ran 'mailman-web migrate' > > The fix was trivial: I just added the lines: > > from mistune.util import escape_html > from mistune.util import escape_url > to > /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py This is fixed at https://gitlab.com/mailman/hyperkitty/-/merge_requests/379. Unfortunately, that fix is not in the latest release version. We will need to address that as mistune 2.0.0 moved those functions from their prior location in mistune 2.0.0rc1 > 2) Similarly, migrate (using postgres) also gave the error: > > File "/opt/mailman/venv/lib/python3.9/site- > packages/django/db/backends/postgresql/utils.py", line 6, in > utc_tzinfo_factory > raise AssertionError("database connection isn't set to UTC") > > I was able to find a discusson of this one at > > https://stackoverflow.com/questions/68024060/assertionerror-database-connec… > > which had me downgrade to an older version of psycopg2-binary: > > pip install psycopg2-binary==2.8.6 > > There might be a different fix, but this worked. This should be fixed in psycopg2-binary, but it isn't. The work around is what you did and I'll update the doc. > 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the > error: > > ModuleNotFoundError: No module named 'settings' > > This was also trivially fixed by adding the path: > > export PYTHONPATH=$PYTHONPATH:/etc/mailman3 > > in /opt/mailman/.bashrc The recommended uwsgi.ini includes pythonpath = /etc/mailman3/ according to https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… this should work. Did you have that? If you did and it doesn't work, perhaps adding env = PYTHONPATH=/etc/mailman3 would work. > 4) Sometimes when I rebooted the machine, when I ran 'systemctl start > mailman3' I'd get the error that mailman wouldn't start because the > lock was stll there. I never could figure out where the lock was, so I > worked around it by replacing > > > ExecStart=/opt/mailman/venv/bin/mailman start > > with > ExecStart=/opt/mailman/venv/bin/mailman start --force > > in /etc/systemd/system/mailman3.service > > I'm sure there's something bad about doing that, but it works for me, > so far. The lock is /opt/mailman/mm/var/locks/master.lck* The problem with using --force unconditionally is you can start a second instance when mailman core is already running and that causes other issues. > 5) I had a problem with mail to outside people not being delivered > while mail to the local host was delivered. It turned out that this was > because in my mailman.cfg I had "smtp_host:my.listserver.tld when it > should have been localhost. The error was "relay access denied." To > fix this, I had to add my.listserver.tld to "mynetworks" in > /etc/postfix/main.cf, ie change: > > mynetworks = 127.0.0.0/8 10.0.0.0/24 > > to > > mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address > > However, Mark Sapiro (a God) told me this was because I had changed a > line in the [mta] section of mailman.cfg. I had changed > > smtp_host: localhost > > to > > smtp_host: mydomain.tld > > Here's the thing. The reason I did this was because the instructions at > https://docs.mailman3.org/en/latest/config-core.html > > give this as their model: > > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com <---- not localhost > smtp_port: 25 I'll add some clarification to the doc. > The instructions are good, but there are a few places where one size > does not fit all, I guess. > > 6) A second error in delivery to outside addresses resulted in an > "Access denied" error. A search on the internet revealed that this had > to do with (for me) smtpd_recipient_restrictions in postfix. See, for > instance: > https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… > > Changing this fixed things. > > I'm not sure, but I think this shows up mostly with installations that > include dovecot. This is a Postfix configuration issue. <big snip> Thanks for your feedback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Blocked by Hotmail

by Mark Sapiro

On 1/22/21 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? Yes, I've had this block at times. All the affected servers subscribe to SNDS and JMRP and never receive any bad reports. The process is to submit the form as you have done. This may result in mitigation without further action on your part, but if they reply to the ticket with Not qualified for mitigation (IP address) Our investigation has determined that the above IP(s) do not qualify for mitigation. The next step is to reply to that with an explanation of what you do. Here's a copy of such a reply: ------------------------------------------------------------ Beginning around 14:43 -0500 on Dec 31, mail from mail.python.org (IP 188.166.95.178) to various hotmail.com, outlook.com. live.com, etc. addresses is being blocked. A typical response to such mail is Jan 4 19:11:49 mail postfix/smtp[14283]: 4D8tGD3YZSzpFbf: to=<marksapiro(a)hotmail.com>, relay=hotmail-com.olc.protection.outlook.com[104.47.17.161]:25, delay=0.69, delays=0.55/0.01/0.11/0.03, dsn=5.7.1, status=bounced (host hotmail-com.olc.protection.outlook.com[104.47.17.161] said: 550 5.7.1 Unfortunately, messages from [188.166.95.178] 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. [VI1EUR05FT004.eop-eur05.prod.protection.outlook.com] (in reply to MAIL FROM command)) This mail is virtually all messages to confirmed opt-in subscribers of various python.org email lists. We do not send spam and we have various filters in place to block spam from reaching these lists. We publish SPF and DMARC records for our domain and DKIM sign our outgoing mail. We subscribe to your Junk Email Reporting Program (JMRP) and Smart Network Data Services (SNDS) and see no reports or unusual complaint rates. Our IP 188.166.95.178 is not found on any blacklists checked at <https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a188.166.95.178&run=…> Please stop blocking our mail. ------------------------------------------------------------ This usually works. If not, you just have to persist. > My mail server is on Digital Ocean if that makes any difference. It may. All of my recent blocks have been DigitalOcean servers including mail.python.org, but I think I've had this in the past from non- DigitalOcean servers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: templates

by Odhiambo Washington

Isn't that the same thing as not having them in the FS? I read (and asked questions about) templates almost 10x before I got to understand the locations and how MM uses them. It's not easy to understand the ones in the FS while the ones in the DB are easy. Then again, one needs to know that Postorius only writes to the DB. On Thu, May 4, 2023, 22:59 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/23 12:44, Odhiambo Washington wrote: > > If you don't have any templates in the file system and none in the DB > > table, then you must go to Jerusalem and pray, because you don't have any > > and nothing will work the way you want. > > It's either or! > > > He didn't say he didn't have templates in the file system. He said he > didn't have any custom templates in Mailman's var/templates/lists/ > directory. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

3 years, 6 months

[MM3-users] Re: How to hide sender completely

by Mark Sapiro

On 5/9/23 14:22, Roland Miyamoto via Mailman-users wrote: > • Anonymous list= Yes ... > As you can see, the header contains the sender's address > > sender(a)otherdomain.tld > > twice. ... > From - Fri Apr 21 23:18:21 2023 > X-Mozilla-Status: 0001 > X-Mozilla-Status2: 00000000 > X-Mozilla-Keys: > Return-Path: <ourlist-bounces(a)list.timebrain.org> > Received: from mail.timebrain.org > by mail.timebrain.org with LMTP > id Ph5sJ0XzQmSxBQAAMe3UBQ > (envelope-from <ourlist-bounces(a)list.timebrain.org>); Fri, 21 Apr > 2023 22:34:13 +0200 > Received: from timebrain.org (localhost [IPv6:::1]) > by mail.timebrain.org (Postfix) with ESMTP id 9110FC0082; > Fri, 21 Apr 2023 22:34:13 +0200 (CEST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=list.timebrain.org; > s=202205; t=1682109253; > bh=KEcouWpeNLb32k6bFssIJDhe16IGlOZEsBeJOIigkLs=; > h=Date:To:In-Reply-To:References:From:Reply-To:Subject:List-Id: > List-Help:List-Post:List-Subscribe:List-Unsubscribe:From; > b=MmI/E0AHnIway3V//e0KNbYj06VBWcDKGMlK4yA+tPGmgCAnje4NwZM9YXbZk/hc7 > FKM8O1RRkfUhC6iCUHMQa28XK4Nr9+45G/Yxl7Tgr8h6qt1B/1myOCLS8Mb+4XSwpm > CuShRI812x7GkCWVqpLoRBKwq4CP8j8BdDgN4rmrUF18Mdh0J/kkccV13dJvG9xapB > XzUkpqcJICWNyQ/1+GY59VEISP3EBQxUzg6Qkd6a4BXkPKNPCRzVUVM0irvQ0nLi8Z > nAKnV7iutn5nKMXOkEfX5K+8HuFm2Ixd1cWnSIfPY7gd0WK0DyjLVgsZIINA6Hnwt5 > 9fABm1Dsr6YeQ== > Received: from mail.timebrain.org (localhost [127.0.0.1]) > by mail.timebrain.org (Postfix) with ESMTP id C912FC0082 > for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 > (CEST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=demonetize.it; > s=201907; t=1682109251; > bh=799sMT9Q1QA5X8QRdz/ErDUnITC5MNct/qLMzA5zPSA=; > h=Date:From:To:Subject:In-Reply-To:References:From; > b=KKp8OdYRcEStg4A3qhDgKm4fJQg8U6xPL9w1jbcNJ3BozX8QKqg3NqVC6cbcptHtr > 9tUzsc1WBCYy1UHH7UOCFXowfNtRu+KlvT8YpBNeGgsa12nZ4Ljhw7IRuENcp1sqyj > tnZWWRW8T+wcsJlftOhcCudT59gq1LilZIEPpDNGJ63jgJIX5838IBaz2cXZyHQAWd > XMF6uTz/xc5sRutPHWOUtRETHySK0PEI59cpkRz1UvHwDu1opliv4ILZmR4BW32T6a > OeK06uv6uhRfH8Gc420zhkp+tYSgUc28Z4G93uDC12MypmKshnsZiR52MUFZp1JM8X > eJGEpnGP7xHew== > Received: from [IPv6:::1] ([2a02:560:4ca5:ea00:5c9f:6282:e0ec:582]) > by mail.timebrain.org with ESMTPSA > id zuaKLUPzQmSnBQAAMe3UBQ > (envelope-from <sender(a)otherdomain.tld>) > for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 Both this and all other incoming Received: headers are removed from posts to anonymous lists beginning with Mailman 3.3.4. > Date: Fri, 21 Apr 2023 22:31:08 +0200 > To: Ourlist Ourtown <ourlist(a)list.timebrain.org> > User-Agent: K-9 Mail for Android > In-Reply-To: <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> > References: <3e35f420-a766-095e-b79a-afb8e795f011(a)timebrain.org> > <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> > Message-ID: <7AB6FFA2-BDA7-4484-BF14-4CF512A4B8E8(a)demonetize.it> > MIME-Version: 1.0 > Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B > X-Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B > X-MailFrom: sender(a)otherdomain.tld X-MailFrom: headers are also removed as of Mailman 3.3.4. > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; > emergency; loop; banned-address; member-moderation; > nonmember-moderation; administrivia; implicit-dest; max-recipients; > max-size; news-moderation; no-subject; suspicious-header > From: Our List <ourlist(a)list.timebrain.org> > X-Mailman-Version: 3.2.1 > Precedence: list > Reply-To: Ourlist Ourtown <ourlist(a)list.timebrain.org> > Subject: [Ourlist] Re: whatever was the topic > List-Id: Our List <ourlist.list.timebrain.org> > List-Help: <mailto:ourlist-request@list.timebrain.org?subject=help> > List-Post: NO > List-Subscribe: <mailto:ourlist-join@list.timebrain.org> > List-Unsubscribe: <mailto:ourlist-leave@list.timebrain.org> > Content-Type: multipart/mixed; > boundary="===============6841522137146215921==" > > --===============6841522137146215921== > Content-Type: multipart/alternative; > boundary=----F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF > Content-Transfer-Encoding: 7bit > > ------F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF > Content-Type: text/plain; > charset=utf-8 > Content-Transfer-Encoding: quoted-printable -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 1:45 PM, summersan(a)nclack.k12.or.us wrote: > Hello, > > I've been setting up a new Mailman 3 installation earlier this year, and I think things have been going okay so far. > > I've noticed, however, that after a long amount of time passes (for example, a weekend), when I try to visit the local Mailman 3 web application (e.g., example.mailman.site/mailman3/lists/, where it says "Postorius" at the top left corner of the page and shows a list of mailing lists in the body of the page), I sometimes get a 502 Bad Gateway type of error (referenced from my notes). As far as I can tell, this looks like a normal web server (nginx?) error. If I try visiting the Mailman 3 server location again in a web browser shortly thereafter, I still might get a 502 Bad Gateway error. If I wait a while longer (maybe a minute or more?), the Mailman 3 web application appears to load as expected. What is your configuration for accessing Mailman. I gather you are proxying from nginx to something. Is that something gunicorn or uwsgi? You mention gunicorn but this can be confusing as mailman core's REST API uses gunicorn, but that is separate from the web server's wsgi interface to Django. In any case, this issue is probably with whatever nginx is proxying to (gunicorn or uwsgi) and not with Django or Mailman core. > I've tried looking at the gunicorn documentation (https://docs.gunicorn.org/en/stable/index.html) and searching online (including in this Mailman3 mailing list) to see if there's something that can be done to fix this issue. The closest thing I can find for now is advice for something that, while possibly being technologically unrelated, includes the idea of "warmup requests", which makes me think of simply setting up some sort of script to periodically load a page on the Mailman 3 web application in order to keep it more available for visitors (https://stackoverflow.com/a/57056170) That's certainly a possibility and may be a solution. It would be simple enough to set up an hourly cron to do a curl or wget to retrieve example.mailman.site/mailman3/lists/ and see if that helps. > Is there a setting or something in any of the Mailman 3 related programs that could help with keeping the Mailman 3 web application up and running more often without having to resort to making an ongoing, automated request to the Mailman 3 web application? Nothing that I'm aware of, but if so, it would most likely be a gunicorn or uwsgi setting rather than something in Mailman or Django, although it could be that gunicorn or uwsgi is timing out in trying to connect to Django in which case it could be a Django issue, but not one I've heard of. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Held Message view, JSONDecodeError: Invalid control character

by Mark Sapiro

On 9/14/20 5:22 AM, mm3(a)hovo.id.au wrote: > I am running the Debian 10 mailman3 and mailman3-web packages with mariadb. > I received an email to the list from an invoicing software and now I am unable to view or accept this email from the list. > All other lists seem to be still working fine. > I'm guessing there is a piece of data in my database that is corrupt or unable to be decoded, but I am at a loss on how to find and fix it. > Any help would be greatly appreciated > > ``` > Sep 11 12:29:23 2020 (11577) 127.0.0.1 - - "GET /3.1/lists/redacted(a)redacted.com/held?count=0&page=1 HTTP/1.1" 200 90 > Sep 11 12:29:23 2020 (11577) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.7/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 216, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ > File "falcon/api.py", line 189, in falcon.api.API.__call__ > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 160, in on_get > resource = self._make_collection(request) > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 150, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource > resource = super()._make_resource(request_id) > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource > results = requests.get_request(request_id) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line 142, in confirm > value = json.loads(keyvalue.value) There is some value with a key not 'type' in the pendedkeyvalue table which is the issue here. > File "/usr/lib/python3.7/json/__init__.py", line 348, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.7/json/decoder.py", line 337, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.7/json/decoder.py", line 353, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Invalid control character at: line 1 column 21 (char 20) > ``` Examine the table looking at the 21st character of values with keys not = 'type', most likely keys 'email' or 'message_id'. -- 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

[MM3-users] Re: Help! Duplicate DKIM key

by Jose Bernal

Mark - adjusting this setting in mailman.cfg seemed to do the trick. No more errors and postfix is able to send mail out to our Amazon SES relays just fine now. Thank you, On Mon, Mar 10, 2025 at 6:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/11/25 7:06 AM, Jose Bernal via Mailman-users wrote: > > > > Here is the message. We've got several thousand log entries like this > now: > > > > *554 Transaction failed: Duplicate header 'DKIM-Signature'* > > Mar 10 08:31:10 mail1 postfix/smtp[217753]: 738B53F15E: to=< > > brian(a)brianmichaelslaw.com>, relay=xxx.org[44.225.xxx.xx]:587, delay=37, > > delays=2/35/0.16/0.13, dsn=5.0.0, status=bounced (host said: 554 > > Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end > of > > DATA command)) > > This is Amazon SES being stupid, but you can avoid this issue by setting > ``` > remove_dkim_headers: yes > ``` > in the `[mta]` section of `mailman.cfg`. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jbernal.web.dev(a)gmail.com >

1 year, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

What would be the config for a simple one way announcement type list ???? El vie., 21 jul. 2017 a las 21:09, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 06:46 PM, Rafael Mora wrote: > > Can I use it for mailing lists? like MailChimp? > > > Yes, if all you want is a simple one way announcement type list, Mailman > can do that quite well, with appropriate list configuration[1], but as I > tried to say, MailChimp has many more features that are oriented towards > that kind of mailing. > > [1]There are many horror stories of people setting up a mailing list and > subscribing a bunch of people to it without ensuring that members can't > post back to the list. > > Then with the first post, people start posting back to be removed and > then others reply that they didn't send that mail and it snowballs and > within an hower, the poor list server is so backlogged that the clueful > replies take hours to be delivered. I personally have been added to more > that one list to which this happened. > > -- > 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

9 years, 3 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

Continuing the troubleshooting, I came around a very long list, over 3000, of "banned addresses" on the 'problem list'. I wonder if there is a way to delete them programmatically. I searched ourlist, but could not find a hint. It seems mailmanclient has a method to deal with this, but I could not find the details. Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, September 6, 2023 6:49 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/6/23 14:24, Mohsen Masoudfar wrote: > > Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? ``` $ /opt/mailman/mm/bin/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 >>> for x in dir(m): ... if not x.startswith('_'): ... print(f'{x}: {m.__getattribute__(x)}') ... ``` -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

3 years, 2 months

[MM3-users] Re: Spam sent to list owner causes bounce increment for list owner

by Mark Sapiro

On 12/18/23 9:59 AM, Allan Hansen wrote: > Hi all, > > Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. > > The scenario in more detail: > The list server forwards the message to me, as I’m the list owner. This message is sent from <list>-bounces+hansen=rc.org(a)list.rc.org to hansen(a)rc.org. > My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. > The list server sends a message to <list>-bounces+hansen=rc.org(a)list.rc.org (the fake sender) saying that the message to hansen(a)rc.org (the recipient) could not be delivered because it was spam. > The list server also blames hansen(a)rc.org (me) for the bounce and increments my bounce score, which, to me, is unfair. > > So I wonder: > Is the Mailman host at list.rc.org at fault for not catching the spam before it reaches the list server? (One could argue that) Depends on what kind of spam filtering if any you have on incoming mail to list.rc.org. > Is my rc.org service provider at fault for sending the bounce message to the server instead of the to the original sender? Absolutely not. The envelope sender of the mail was set by Mailman to <list>-bounces+hansen=rc.org(a)list.rc.org in order to enable automated bounce processing. rc.org correctly sent the bounce to the envelope sender. > Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? Arguably, yes, but not based on FROM. FROM has nothing to do with it. The message was sent TO you so if it bounces, it is a message to you that bounced, so you are the one bouncing this message. All Mailman knows is a message was sent to you and it bounced so it's your address that is bouncing. It doesn't matter whether this was a post to the list that bounced or a message to <list>-owner. A bounce is a bounce. Note that this list's bounce processing is very aggressive. If you got removed from the list after one bounce, the list must have Bounce score threshold = 1 and Bounce disable warnings = 0. You might consider adjusting these. There is an easy fix for this. Set `verp_probes: yes` in mailman.cfg. Then when your bounce score reaches threshold, instead of disabling/removing you, Mailman will send a probe message to you. It will only disable/remove you if the probe bounces which it presumably won't. Another avoidance would be to use an address for the owner which is not the address of a member. Then if the owner address bounces, nothing is done because the bouncing address isn't a list member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: hooking up mailman and sendmail

by John Covici

On Sun, 14 Mar 2021 14:05:33 -0400, OK, thanks a lot. Mark Sapiro wrote: > > On 3/14/21 7:56 AM, John Covici wrote: > > That post does not answer my question, it applies only to mailman2 and > > is a big mess. I was hoping to use lmtp, which sendmail will use and > > mailman seems to have some facilities to use it as well. > > > What that post describes is for Mailman 2.1, how to hijack Mailman's > generated aliases for Postfix and apply them to sendmail. The hope is > that someone who understands how to configure sendmail can take those > ideas and apply them to the Postfix transport and domain mappings > generated in var/data/postfix_lmtp and var/data/postfix_domains to > generate what is needed for sendmail. > > Hopefully, once people figure out how to do this, they will inform us of > the solution and we can update the docs. > > > -- > 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/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 8 months

[MM3-users] Re: Importing MBOX from custom listserv to MM3?

by Thomas Ward

Thank you kindly, Mark, for pointing me in the right direction on multiple questions so far! I'll dig into the import command and hopefully that resolves most of the chaos if the client decides to agree with the decision to move to Mailman 3 Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 24, 2023 6:41 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Importing MBOX from custom listserv to MM3? On 6/24/23 3:26 PM, Thomas Ward wrote: > We are looking at moving from a home grown listserv system at a client to potentially MailMan3 for the lists platform instead. > > We have historic thread data from the homegrown systems in mbox form. Is there a way to import that into MM3 for indexing in the archiver there so we dont need to keep the (literally massive) MBOX file? That's what the django admin hyperkitty_import command is for. You can check the mbox for anomalies that might cause issues with the scripts at https://gitlab.com/mailman/hyperkitty/-/tree/master/hyperkitty/contrib. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

3 years, 4 months

[MM3-users] Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Kyriakos Terzopoulos

Hi, It seems that what fixed it was to put in Exim4 conf the following: domainlist mm_domains = myproject.eu *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Thu, 12 Oct 2023 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/12/23 00:49, Kyriakos Terzopoulos wrote: > > I get this in mainlog of Exim: > > > > 2023-10-12 10:48:33 H=static.16.91.201.138.clients.your-server.de > > ([127.0.0.1]) [138.201.91.16] sender verify fail for > > <shinylist-bounces+kterzopoulos=myproject.eu(a)myproject.eu>: Unrouteable > > address > > When following > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > did you replace > ``` > domainlist mm_domains=list.example.net > > ``` > with > ``` > domainlist mm_domains=myproject.eu > ``` > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kyriakos.terzopoulos(a)gmail.com >

3 years

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Pierre Malard

Le 20 déc. 2023 à 09:14, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On December 20, 2023 7:20:17 AM GMT, Pierre Malard via Mailman-users <mailman-users(a)mailman3.org> wrote: >> Ok, don’t throw any more away! >> >> If you really don't recommend the Debian packaged solution, I just have one question: >> Why have you included it in the Debian "main" repositories for so long? > > We have no control over what's in Debian repositories. Maintenance and distribution of the Debian packages is done by Debian. > > We would love it if all the downstream distributions included up to date and bug free Mailman packages. The problem is when people encounter difficulty with a downstream package, we are often unable to help because we don't know the details of that package. Ok Mark, Sorry, I thought that the creation of the repository depended directly on you or, at least, on someone from the team. Obviously this is not really the case and I will address the person in charge: Jonas Meurer I presume? Good day > > > -- > Mark Sapiro <mark(a)msapiro.net> > Sent from my Not_an_iThing with standards compliant, open source software. -- Pierre ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 10 months

[MM3-users] Re: Internal Server Error: /archives/

by Christian

Thank you Mark! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 29, 2024 10:02 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /archives/ On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian > 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ XH5USTRI7JUHJT7UGWCGALENPDSSXWXE/ This message sent to csa(a)web-analysts.net

1 year, 11 months

[MM3-users] Re: templates

by Mark Sapiro

On 5/6/23 14:26, Christian via Mailman-users wrote: > It seems like something about my SPF or DKIM records are upsetting to gmail, > hence the bounces I'm guessing. That aside, this is what mail.log says: Could be, but If the issue is SPF or DKIM, Google is usually specific about that in the reject message. > ... > May 5 08:04:06 zarathustra postfix/smtp[25955]: AF07B1004A4: > to=<eappiah(a)dons.usfca.edu>, > relay=mxb-00277301.gslb.pphosted.com[148.163.158.109]:25, delay=76, > delays=0.01/0/61/15, dsn=2.0.0, status=sent (250 2.0.0 3qcf1p3wf4-1 Message > accepted for delivery) > ... > May 5 08:05:04 zarathustra postfix/smtp[25955]: C263A1004A4: > to=<adga(a)ucdavis.edu>, > relay=ucdavis-edu.mail.protection.outlook.com[104.47.66.10]:25, delay=2.5, > delays=0.01/0/0.15/2.3, dsn=2.6.0, status=sent (250 2.6.0 > <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> > [InternalId=117626269340390, > Hostname=BN8PR08MB6290.namprd08.prod.outlook.com] 16054 bytes in 0.131, > 119.439 KB/sec Queued mail for delivery) > ... > May 5 08:07:13 zarathustra postfix/smtp[27926]: D3CCE1004A4: > to=<chris.hebdon(a)yale.edu>, > relay=yale-edu.mail.protection.outlook.com[104.47.59.138]:25, delay=0.77, > delays=0.01/0.02/0.07/0.67, dsn=2.6.0, status=sent (250 2.6.0 > <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> > [InternalId=16887811415117, > Hostname=PH0PR08MB6757.namprd08.prod.outlook.com] 16093 bytes in 0.121, > 129.491 KB/sec Queued mail for delivery) The above 3 are successful deliveries. If those users did not receive the mail, it may have been delivered to a spam/bulk/junk/... folder or silently discarded, but it's not a Mailman issue. > ... > May 5 08:09:24 zarathustra postfix/smtp[28575]: E394C1005BA: > to=<vortexanthony(a)hotmail.com>, > relay=hotmail-com.olc.protection.outlook.com[104.47.17.161]:25, delay=0.58, > delays=0.01/0.02/0.41/0.14, dsn=5.7.1, status=bounced (host > hotmail-com.olc.protection.outlook.com[104.47.17.161] said: 550 5.7.1 > Unfortunately, messages from [192.46.218.224] 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. > [VI1EUR05FT042.eop-eur05.prod.protection.outlook.com > 2023-05-05T15:09:24.433Z 08DB4D70FA71385D] (in reply to MAIL FROM command)) > ... > May 5 08:09:24 zarathustra postfix/lmtp[28581]: 7C9B31005EB: > to=<degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0/0.01/0/0.02, > dsn=2.0.0, status=sent (250 Ok) These are a bounced mail (Hotmail/outlook is blocking your IP) and the subsequent successful delivery of the bounce DSN back to Mailman. > ... > May 5 08:11:35 zarathustra postfix/smtp[29219]: 016931005BA: > to=<alaitz.aritza(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.251.116.26]:25, delay=0.43, > delays=0.01/0.02/0.03/0.37, dsn=5.7.1, status=bounced (host > gmail-smtp-in.l.google.com[142.251.116.26] said: 550-5.7.1 [192.46.218.224 > 12] Our system has detected that this message is 550-5.7.1 likely > unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1 this > message has been blocked. Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedMessageError 550 5.7.1 for > more information. m12-20020a0568080f0c00b00389455db611si4492291oiw.127 - > gsmtp (in reply to end of DATA command)) > ... > May 5 08:11:35 zarathustra postfix/lmtp[29224]: 6ACFD1005EB: > to=<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0/0.01/0/0.01, > dsn=2.0.0, status=sent (250 Ok) And similarly for this one, Google thinks it's spam. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 11:17, dap1--- via Mailman-users wrote: > Sorry Mark: > > These hundreds of emails are distracting and I have too many irons in the fire between you and Stephen. That is not a criticism as I greatly appreciate the help from both of you. Just that I'm having difficulty keeping up with you both. ``` > sudo grep -r '/usr/share/mailman3-web/manage.py' /etc/cron* /var/spool/cron > > /etc/cron.d/mailman3-web:* * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely > /etc/cron.d/mailman3-web:2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.quarter_hourly /usr/share/mailman3-web/manage.py runjobs quarter_hourly > /etc/cron.d/mailman3-web:@hourly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly > /etc/cron.d/mailman3-web:@daily www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily > /etc/cron.d/mailman3-web:@weekly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.weekly /usr/share/mailman3-web/manage.py runjobs weekly > /etc/cron.d/mailman3-web:@monthly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly > /etc/cron.d/mailman3-web:@yearly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.yearly /usr/share/mailman3-web/manage.py runjobs yearly ``` This is not the crontab you reported at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… That one is probably /var/spool/cron/crontabs/mailman and wouldn't show here because it doesn't contain '/usr/share/mailman3-web/manage.py'. So the system crontab at /etc/cron.d/mailman3-web is your issue and should be removed. That will get rid of the cron failure emails. > This was a fresh install of Ubuntu server so the only packages installed so far are dump/restore, Ubuntu-desktop, MySQL, Postfix, fetchmail and mailman3. Apache2 comes preinstalled with Ubuntu but there may be others of which I am currently unaware. As far as I know the only other crontab is for root where I have the backup jobs scheduled. > > 0 3 * * 0 /usr/local/sbin/sysbackup Then the remaining question is how did that crontab get there in the system crontabs. The only way I know it could have gotten there if you didn't manually create it is via installation of Ubuntu Mailman packages. I think you probably also have a django-admin and perhaps other things in /usr/bin/ and also a /usr/share/mailman-web/ directory which you don't want or need. I suggest you do sudo apt list mailman3 mailman3-web mailman3-full mailman3-doc and see which of those unwanted packages are installed, and if any, `sudo apt remove` them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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/

5 years, 11 months

[MM3-users] Re: Template Ignored?

by Stephen Daniel

That pulls a 404 error. Thanks for the hint. I will investigate. On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 08:04, Stephen Daniel wrote: > > Mailman3 people -- > > > > I created a new list, and used postorius to create a template for " > > list:user:notice:welcome". I then used the mass subscription feature to > > add myself to the list, having checked "pre-confirmed", "pre-approved", > and > > "pre-verified". > > > > I received a welcome message that appears to be the default welcome > > message. It certainly wasn't what I put into my template. > > > > Any suggestions on how I get mailman to use my template? Things I might > be > > doing wrong? > > > What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a > full URL by appending > `/api/templates/list/list.example.com/list:user:notice:welcome` > <http://list.example.com/list:user:notice:welcome> to that > where `list.example.com` is the actual list_id of your list, and go to > that URL, what do you get? > > -- > 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/ >

4 years, 8 months

[MM3-users] Re: config incoming email in my domain cpanel

by tlhackque

I think you're confused. You already have mail.labbrands.com set up as the MX record for labbrands.com. And it has an A record with the same address as your webserver. So if you're getting e-mail on that domain, there's another e-mail server running on that IP address. You can't have 2 servers on port 25. In that case, as has been noted before, you'll need to setup a relay in that server, not a firewall redirect. Depending on your MTA, you would need to relay to your internal server. And make sure your firewall setup allows your MTA to do this. We can see it's EXIM: telnet mail.labbrands.com 25 Trying 192.185.51.89... Connected to mail.labbrands.com (192.185.51.89). Escape character is '^]'. help 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 -0500 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 214-Commands supported: 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP quit 221 gator4137.hostgator.com closing connection Connection closed by foreign host. Or, consolidate all your e-mail to one server - which is a lot easier to manage unless you have a really big operation. Postfix is probably the right choice, but requires more setup. Although Mailman3 configuration is not well documented (as you've discovered), you may want to get help from someone with more general network and mail experience. You're now into territory that is, as Simon indicated, not Mailman-specific. On 03-Aug-17 16:28, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) escribió: > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) >> escribió: >>>> 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. >> >> As I said, for mail delivery you need to forward port 25 to the Mailman >> server. >> > Ok so I'll redirect in my zentyal firewall the port 25 to my local centos7 > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > >> >> -- >> 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/ >> -- This communication may not represent my employer's views, if any, on the matters discussed.

9 years, 3 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Thank you Mark for you response in time. On Tue, Aug 11, 2020 at 9:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > > I am currently automating a few things using the CURL commands but > only > > postorius related as of now. Now I have a requirement. > > > > I need to create a lot many users and their mapping email ids through > > Site Administration almost daily. But it is becoming to do the same > through > > Graphical Interface. > > > > So, I just want to know the CURL commands that can be used to create > the > > user accounts and email ids mapped to user accounts. > > The accounts you are talking about are Django accounts. You cannot > create these via CURL to the Mailman core REST API. > > You might find > <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years, 3 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

No matter what i try, mailman still only connects without STARTTLS: /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: smtp_verify_hostname: false smtp_verify_cert: false smtp_secure_mode: starttls systemctl restart mailman3 Nov 9 12:14:52 al02 postfix/smtpd[4183267]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: disconnect from localhost[::1] ehlo=1 mail=0/1 rset=0/1 quit=1 commands=2/4 Did i miss something? Am Mo., 8. Nov. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com>: > awesome! Thank you a lot! > > Am Mo., 8. Nov. 2021 um 17:37 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > >> On 11/8/21 1:03 AM, Stefan Bauer wrote: >> > >> > how can we configure mailman3, to use STARTTLS when dropping mails to >> local >> > postfix for final delivery? >> >> >> Set `smtp_secure_mode: starttls` in the `mta` section of mailman.cfg. >> See >> >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… >> >> -- >> 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/ >> >

5 years

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Thanks for clarifying. All is working now!!! On Thu, Feb 17, 2022 at 1:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 10:10, Stephen Daniel wrote: > > Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. > > I've been playing with wget, and no matter what I put, I keep getting a > 404 > > error. > > > > So: this works: > > > > wget -O wget.out --user restadmin --password restpass ' > > http://localhost:8001/3.1/lists/list.example.com' > > > > but this does not (404 error): > > > > wget -O wget.out --user restadmin --password restpass ' > > > http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… > > > You are using Mailman core's REST API which is wrong. You need to get > the template from Postorius. Maybe something like > > > > http://localhost/postorius/api/templates/list/list.example.com/list:user:no… > > Where http://localhost/postorius/ is the URL you use to access > Postorius, maybe mailman3 instead of postorius. > > Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme > and domain part of that. > > -- > 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/ >

4 years, 8 months

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

Indeed, it was a domain problem. hatlab.fr is the general domain, mailing, the website to manage our mailinglist. And in this case "FILTER_VHOST" have to be switch on "False". Fixed ! Thanks . Le jeu. 4 oct. 2018 à 23:21, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/04/2018 03:49 AM, Thomas G wrote: > > I tried all job, without result. > > (and they are correctly in the crontab) > > > > [image: image.png] > > > > If I try to find my list in the form, hyperkitty can find it: > > > > [image: image.png] > > > Since you are a gmail user, you probably didn't see that content > filtering removed your screen shots, but see your post at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >. > > I did in fact see your screen shots in my direct copy, but I am unable > to determine what your issue is except there may be some domain > confusion between mailing.hatlab.fr and hatlab.fr. Are your list > settings set for Public archives and hyperkitty active? > > -- > 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/ >

8 years, 1 month

[MM3-users] Re: How to modify system preferences

by Allan Hansen

The other way is to tell all your users to use gmail, as that is how they handle messages from email lists, no matter how much I and others have complained to them about it. :-) Yours, Allan Hansen hansen(a)rc.org > On Feb 19, 2021, at 9:50 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/19/21 5:15 AM, Jack Lenox via Mailman-users wrote: >> >> The documentation states that these are only accessible in a read-only >> format via the REST API, but presumably there is a way of modifying >> these somewhere? I can't find a way of specifying this in my config and >> can't find a relevant example in the sample schema.cfg. >> >> At this stage, all I want to do is set the default for >> "receive_own_postings" to False. Can anyone point me in the right >> direction here? > > > The defaults for settings like this are not directly configurable. You > need to patch the relevant entry in mailman/core/constants.py > > I have just filed <https://gitlab.com/mailman/mailman/-/issues/832> for > this. > > -- > 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/

5 years, 8 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 5 Nov 2021, at 6:30 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. That should work well. I’m happy to do some testing of any patches you create in our test environment if you need extra testing. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> —Simon

5 years

[MM3-users] Re: Pkl files with ".last" extension

by Keith Christian

Mark, Alright, sounds logical, appreciate your reply, On Fri, Jul 12, 2024, 15:50 Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/24 2:20 PM, Keith Christian via Mailman-users wrote: > > In the MM2 to MM3 migration project I'm involved with, I see files with > > names like config.pkl.last along with config.pkl. > > > > Is there a special reason for the ".last" extension and if so, what is > it? > > > A Mailman 2.1 list has possibly as many as 4 configuration files. > > - config.pck (not pkl) is the current list configuration. > - config.pck.last is the immediately prior configuration > used in case config.pck is corrupt or missing. > > In addition there may be config.db and config.db.last files. These only > exist if the list predates MM 2.1 and should be removed because they're > old and could be used as a fallback if both config.pck and > config.pck.last are missing or corrupt. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to keith1christian(a)gmail.com >

2 years, 4 months

[MM3-users] Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:46 PM, Jeff wrote: > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > 1) some emails that arrived before I got the archive working are still sitting in: > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a collection of messages in maildir format. This is how the prototype archiver stores messages. This has nothing to do with HyperKitty. It is a separate archiver. If you don't want messages to be stored there, you can disable the prototype archiver for the list by unchecking prototype in Postorius -> Settings -> Archiving -> Active archivers or disable it entirely for the installation by setting ``` [archiver.prototype] enable: no ``` in mailman.cfg > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > /usr/local/mailman3/mm/var/queue/shunt > > What should I do to get these messages processed? Assuming the issues that caused them to be shunted have been fixed, just run the command ``` mailman unshunt ``` > 3) Similar to above, some messages are in: > > /usr/local/mailman3/mm/var/queue/bad > > How can I get these messages processed? First examine the messages with ``` mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> ``` To be sure you want them. Also examine mailman.log for the times they were stored in the `bad` queue. You are looking for 'Skipping and preserving unparseable message: <file>' and/or 'SHUNTING FAILED, preserving original entry: <file> messages and you want to determine which runner preserved the message. There may be a 'whichq' entry in the message's metadata in which case, that's the answer. Once you have determined the queue, you can just move the .psv file from the bad queue to the appropriate queue, renaming it from .psv to .pck in the process. > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? I know little about uwsgi. setting it to `uwsgi://localhost:8000` might work. You could also set it to the base URL that a user would use to access the web UI, e.g. `https://example.com` and that would presumably be proxied to uwsgi. For example, on the server for this list we have ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` which gets proxied to gunicorn, but the idea is the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 10:57 PM, Ken Alker wrote: > > I have studied the output, looked at the code lines referenced in the > Traceback, and I can't figure out the problem (I feel like the sad guy > on the side of the street with his hood up staring into the engine bay > with stream pouring out and not knowing what to do next). I did some > analyses on the log file and determined that there are 71 messages it is > having problems processing and there are 71 messages "stuck" in > /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to > process each message about 20 times). Each time there is a new post, it retries all the messages in the spool/ directory. > Since upgrading to V3.3.8 I've > not seen new messages get stuck like this (although it's only been > running smoothly for 24 hours now and there hasn't been much activity). > But I'm suspecting there was something awry between the conversion from > V2 to V3 in February and me installing V3.3.8 that caused this (based on > message time stamps). It is HIGHLY likely these messages are in the > archiving spool as a result of me unshunting the shunt queue and that > they are copies of the messages that got delivered to the subscribers > when I did that... but are now hung up in the archiving process. Are new messages being archived OK. If so, that is a real mystery. It says mailman-hyperkitty can talk to hyperkitty and archive new messages, but it can't talk to hyperkitty when attempting to process a queued message. > Following is an excerpt from mailman.log. Note that the "first section" > (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not > identical; but similar) (so I did not include it to save room) before > the Traceback appears. > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: I just went to that URL and got a 404. This is a serious problem. https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should return some documentation of the API. https://lists.netlojix.com/archives/api/ does work and returns the expected information. Your urls.py file probably contains in its urlpatterns list ``` re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ``` The simplest fix is to add ``` re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), ``` to that list. Another way to fix this is in your mailman-hyperkitty.cfg, you have ``` base_url: https://lists.netlojix.com/hyperkitty ``` Change that to ``` base_url: https://lists.netlojix.com/archives ``` but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns to urls.py anyway. -- 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

[MM3-users] Re: Changing default message limit (max_message_size)

by Abhilash Raj

On Mon, May 27, 2019, at 8:23 AM, Mark Sapiro wrote: > On 5/27/19 12:05 AM, roger(a)reasonal.com wrote: > > I found the field in settings that would appear to do this, but it just throws an error for whatever I give it ("An error occured**: Unknown attribute: max_message_size"). > > This should be fixed at > <https://gitlab.com/mailman/mailman/merge_requests/329>. > > Perhaps you need to update your Docker images > <https://asynchronous.in/docker-mailman/> That's right. You are probably using a new version of Postorius but not of Mailman Core. Please make sure the container images you have are updated. > > Also, see > <https://gitlab.com/mailman/postorius/issues/246#note_69323948> for a > not about changing this via `mailman shell` (withlist), but see the > subsequent comment about `quit()` > > > > PS As a suggestion, may be a good idea to indicate what units it's expecting... bytes? kB? Nybbles? > > Reported at <https://gitlab.com/mailman/postorius/issues/362>, thanks. > > > PPS ** Psst: occurred with two r's... > > Reported at <https://gitlab.com/mailman/postorius/issues/361>, thanks. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 5 months

[MM3-users] 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/ >

8 years

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Gelpi Andrea

Il 08/05/20 17:13, Mark Sapiro ha scritto: > On 5/8/20 8:06 AM, Seth Seeger wrote: >> On May 8, 2020, at 10:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> You have to edit the display name for the domain in the Django web admin >>> Sites section. >> >> Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for. > > > It should show the display name corresponding to the domain name that > matches the domain in the URL that you go to. If this doesn't seem > correct, perhaps there is some issue with the way you are proxying in > your web server. > Also in debian there is the some problem. The domain name is that of the installation site (example.com) and does not change if you change the webserver and the domian. It seems to be static. You can change it changing the site name in django admin console, but it doesn't change if you change the webserver name. Which file does provide it? Thanks -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

6 years, 6 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Tue, Dec 27, 2022 at 1:58 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/26/22 11:08, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > El 26/12/22 a las 19:19, Mark Sapiro escribió: > >> On 12/26/22 07:42, Odhiambo Washington wrote: > >> > >>> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> > >>> > >>> Does your https://site.name/user-profile/ work? > >> > >> Again, Guillermo is using uWSGI, not Apache mod_wsgi > > > > Well... now I am not sure, you know I've been confused before about that. > > > I was looking at what you posted at > https://forums.freebsd.org/threads/mailman-3.61050/#post-488128. I > focused on the part beginning with > > - initiated the uwsgi with a > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > [snip] Based on the above you ARE using Apache mod_wsgi and if you are still > also running uwsgi as > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > that is unnecessary. > Aha. This is interesting. I have been running the same, although via supervisord, thinking that it is necessary. So, this was a confusion! And it looks pretty easy to confuse mod_wsgi with uwsgi when dealing with the ever-evolving monster that most of us have been facing in MM3 over the years :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 10 months

[MM3-users] Re: using SSH/TLS with external MTA

by Odhiambo Washington

On Sat, Jul 27, 2024 at 11:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/24 01:32, Roland Giesler via Mailman-users wrote: > > On 2024/07/25 20:50, Mark Sapiro wrote: > >> > >> It is the mail server at box2.gtahardware.co.za that is refusing to > >> relay this message. I think this issue needs to be resolved in that > >> MTA's configuration. > > > > Indeed that is so, but that box is in daily use by a few different users > > and they authenticate and send email without any problems. I'm checking > > out the link you shared in my other thread now. > > Since I think you said the MTA at box2.gtahardware.co.za is Postfix, you > probably need to add the IP of the Mailman server to mynetworks in > Postfix main.cf on box2.gtahardware.co.za. > ASMTP works on the premise of "we can relay mail for you if we can authenticate you with certain credentials" Adding the IP to "hosts we can relay mail for" negates the need to authenticate, IMHO. So I am still waiting for how MM3 does ASMTP. Does it? -- 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]

2 years, 3 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 11/14/25 15:36, Cathryn McGuire wrote: > Hi Mark, > > "It appears in your case that Gateway to news is Yes and Newsgroup > moderation is Moderated" > > I don't see any Gateway to mail or Gateway to news, but Newsgroup moderation was set to Moderated (as you said). I changed it to Not Moderated. That's good. As I've said, I don't know what the affinity UI looks like. If you send me (off list) a screen shot of the page where you see Newsgroup moderation, I can advise you further, but basically, anything to do with Newsgroups should be set to Off or No. > In the following case, they are cc'ing to the mailist, and To: is to a member. Sometimes they are not members. Sometimes they To: to the mailist and cc: to the member or non-member. > > Subject:Re: [Neighbours] Furnace problems > To:Bill McCreery <billmccreery1(a)gmail.com> > Cc:neighbours@mailist.dunbar-vancouver.org > Content-Type:multipart/alternative; boundary="000000000000f9e5900643322d20" > X-MailFrom:dunontime@gmail.com > X-Mailman-Rule-Hits:header-match-neighbours.mailist.dunbar-vancouver.org-0 > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation My understanding is you want to hold for moderation any message with a Cc: unless it it To: the list with a Cc: to a member, and I said that with what's available to you in the list's settings, you can't distinguish between Cc: to a member and Cc: to a nonmember, so you have to hold any message with a Cc: > "If the reason was actually what is posted above with 'neighbors' > rather than 'cc:', that's a problem with EMWD's Mailman core." > > Does that mean that any cc: to neighbours or to a member or non-member should be blocked (held)? > Or, does that mean if the cc: is to neighbours, it should be allowed through? That quote was in response to your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… wherein you said > The message is being held because: > > Header "neighbours > > <neighbours(a)mailist.dunbar-vancouver.org>" matched a > header rule I thought that was a typo and the real reason was Header "Cc: <neighbours(a)mailist.dunbar-vancouver.org>" matched a header rule. If that was the case, it was expected and was due to your header filter on Cc: headers. My confusion was I couldn't see how the reason could have been Header "neighbours <neighbours(a)mailist.dunbar-vancouver.org>" matched a header rule. And if it was, that was an EMWD issue. I think the header rule you have will hold any post with a Cc: to anywhere. If you want to not hold posts with a Cc: <neighbours(a)mailist.dunbar-vancouver.org> regardless of To:, you can do that by adjusting your header rules, but I don't think you want that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

[MM3-users] Re: How to Unshunt Specific Message ?

by Shashikanth Komandoor

Hahahaha. Looks like a work around. I understood "moving out of the shunt queue" means "Moving the files from /var/lib/mailman/mailman/var/shunt directory to any other directory say /opt/...." in my environment. Because I installed mailman software inside /var/lib/mailman only. Please correct me if I am wrong. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Aug 11, 2020 at 8:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/20 1:46 AM, Shashikanth Komandoor wrote: > > > > I learnt how to unshunt the messages that got unshunted in > > mailman 3. But the command *mailman unshunt* would unshunt all the > messages > > in the shunt queue. > > > > I want only a specific message to be unshunted and resent. I > > don't find my requirement reached with the help of *mailman unshunt*. > > > You need to move all the unwanted messages out of the shunt queue before > running unshunt. > > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years, 3 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 11:45, Joel Lord wrote: > So I seem to have problems with both periodic AND size-triggered > digests. Size first, this is simpler. Just got one sent out, clearly > triggered by a new email getting added to the queued up messages, but > the setting for the list is the default 30KB and the digest came out at > 23.2 KB. Is it measuring the accumulated queue as size on disk > including metadata and filesystem block sizes or something, rather than > the size of what the emailed digest will be? The threshold is determined by the size in bytes of the MMDF format mailbox file in which the the messages for the digest are saved. This does not include metadata and is not affected by block sizes. It contains the raw messages with all headers and 8 bytes of message separators per message and a 'From ' line per message. Once the digest is triggered, the messages are configured into a digest message with boilerplate, a TOC and possibly a header and/or footer added. The messages themselves may be added as separate MIME message/rfc822 parts to a mime format digest or added as text to a plain format digest. Many headers are removed as the messages are added. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for what is kept. In addition any non text/plain parts in the message are not included in the plain format digest, but are replaced by notes that they have been removed. All this says that a MIME format may be larger or smaller than the threshold depending on the size of the removed headers vs. the added parts, and a plain text digest will probably be smaller if the messages have non text/plain parts, e.g. if content filtering doesn't collapse alternatives and leaves the text/html alternative part, this part will not be in a plain format digest. > Periodic is much more complicated, even to explain. I have the cron job > running nightly at 11:00 PM and it certainly seems to be working, except > for one really odd thing. The list also definitely has periodic digests > enabled in the web UI. This is a very bursty list, so it will go mad > with traffic for a few weeks and then will go mostly idle for a month or > so. The first digest of a burst is definitely size-triggered, but > pretty reliably it has the last few messages from the previous burst in > there. So the one I got today had three messages from today and one > message from May 4th. But that May 4th message should have gone out at > 11:00 PM on May 4th with the daily digest and then gotten flushed from > the pending digest queue, right? That's correct. Do you ever get periodic digests sent at 11:00 PM? If not, there is some issue either with configuration or something. If you get them sometimes, I don't know what could be wrong. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

I created a new list with this setting. This new created list can send to Gmail addresses, this is very strange, because I have changed the problem list (The list that cannot send to @gmail addresses) settings to match the new one, but still the issue is there. The only difference is that the problem list has been imported from mailman2. Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? Thanks Mohsen ________________________________ From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, September 6, 2023 1:32 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Issues with @gmail.com addresses Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

3 years, 2 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 9/29/24 00:59, Odhiambo Washington via Mailman-users wrote: > > Could you allow me to revisit this issue since I haven't solved it? First, > I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming > in between my browser and the web server. > That did not help with the issue of the "missing" CSS files. Then you have som other issue in your configuration. > Ideally, I should not be creating these symlinks, right? On my old server > the symlinks weren't necessary. That is correct. > I have created some symlinks and that appears to help with Apache. I will > test with Nginx and see how it goes. > ``` > root@eu:/opt/mailman/mm/static/CACHE/css# ls -al > total 196 > drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 . > drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 .. > lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css -> > output.d29798365ddb.css > lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css -> > output.e69dbb26da3b.css > -rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css > -rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css > -rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css > root@eu:/opt/mailman/mm/static/CACHE/css# > ``` > My question though: What is the source of truth for the files that should > be in /opt/mailman/mm/static/CACHE/css/ ?? When you run `django-admin collectstatic --clear ...` it removes all the old files from the static/ directory and installs new ones. At this point static/CACHE/ contains no files. Then when you run `django-admin compress` it creates three output.*.css files in static/CACHE/css and one output.*.js file in static/CACHE/js and creates a static/CACHE/manifest.json file that points to those four files and which is what Django uses for the paths to put in the relevant <script ...> and <link rel="stylesheet" ...> tags in the pages it serves. I.e. static/CACHE/manifest.json is the source of truth. > Maybe that is what I need to focus on. If need be, then I should *fix* the > contents of that file so that it doesn't contain the nonexistent files, no? I very much doubt that it does contain the nonexistent files since it is built by the same `django-admin compress` that creates the output* files. > Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does > not display content similar to what https://lists.mailman3.org/archives/ > does? > What change should I make in which settings.py? This is a clue. I presume you actually have archived lists. There is something very wrong in your configuration if HyperKitty is not finding those lists. Possibly you have more than one WSGI server running and you aren't always proxying to the correct one. That seems far fetched to me, but without seeing all your web server, WSGI server and Django configurations, I have no idea what the issue could be. -- 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

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/19/25 14:28, Cathryn McGuire wrote: > Hi Mark, > > 1. Since this post in July, I've been trying to work with EMWD to get the cc's blocked. I've tried every rule configuration in the Header Filter to no avail. EMWD can't seem to help. The setting options are as follows: > > Acceptable aliases > > This is a list, one per line, of addresses and regexps matching addresses that are acceptable in To: or Cc: in lieu of the list posting address when 'require_explicit_destination' is enabled. Entries are either email addresses or regexps matching email addresses.Regexps are entries beginning with '^ and are matched against every recipient address in the message. The matching is performed with Python's re.match () function, meaning they are anchored to the start of the string. What is the content of this? Probably should be empty. > 2. Require Explicit Destination (this is a checked box. Could it be interfering with the Header filters?) No, it doesn't interfere with header checks. > This checks to ensure that the list posting address or an acceptable alias explicitly appears in a To: or Cc: header in the post. > > 3. Default action to take when a member posts to the list > > Accept immediately (bypass other rules) > Default action to take when a member posts to the list. > Hold: This holds the message for approval by the list moderators. > Reject: this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. > Discard: this simply discards the message, with no notice sent to the post's author. > Accept: accepts any postings without any further checks. > Default Processing: run additional checks and accept the message. NOTE - when set here, all members are blocked. What does Blocked mean? If you mean held for moderation, what is the reason they are held? > 4. We also have the problem of large image file sizes being let through no matter what setting we have. We have it set to 500KB, but everything is accepted. > > Maximum message size > 500 > The maximum allowed message size in KB. This can be used to prevent emails with large attachments. A size of 0 disables the check. > > Perhaps some settings are over-riding others? If you have Default action to take when a member posts to the list set to Accept, that bypasses this check and many others. > What do you think? What do you have in your header filter rules? More importantly, what are you trying to accomplish? I.e. what do you want to happen in the following cases? 1. Message To: the list, no Cc: 2. Message To: the list, Cc: to other address 3. Message To: somewhere else, Cc: to the list 4. Message To: elsewhere, Bcc: to the list (require explicit destination will hold this one) Maybe others? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Issues with a DMARC record leading to message being shunted

by Mark Sapiro

On 12/23/23 1:57 AM, Ralf Hildebrandt via Mailman-users wrote: > Hi! > > Recently a mail was not being distributed via our MM3 instance; I searched the logs and found: > > Dec 22 04:54:27 2023 (24) ACCEPT: <1d431542-b386-467b-8bf2-305f19ee7eb4(a)somenet.org> > Dec 22 04:54:28 2023 (28) Uncaught runner exception: list index out of range > Dec 22 04:54:28 2023 (28) Traceback (most recent call last): > File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) > File "/usr/lib/python3.10/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 125, in process > authenticate(msg, msgdata) > File "/usr/lib/python3.10/site-packages/mailman/utilities/retry.py", line 44, in f_retry > return f(*args, **kwargs) > File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 93, in authenticate > auth_result = authenticate_message( > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 395, in authenticate_message > dmarc_result = check_dmarc(msg, spf_result, dkim_result, dnsfunc=dnsfunc, psddmarc=psddmarc) > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 343, in check_dmarc > result, result_comment, from_domain, policy = dmarc_per_from(from_domain, spf_result, dkim_result, dnsfunc, psddmarc) > File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 90, in dmarc_per_from > record, orgdomain = receiver_record(from_domain) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 117, in receiver_record > retval = lookup_receiver_record(hostSansDmarc, dnsfunc) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 92, in lookup_receiver_record > tags = answer_to_dict(str(result)) > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in answer_to_dict > retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} > File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in <dictcomp> > retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} > IndexError: list index out of range > > Dec 22 04:54:28 2023 (28) SHUNTING: 1703220868.1418982+b27f5db154375fcd2c418d467172e4aad0d3d57a > > So the message has been shunted, due to this error. Something with > DMARC and tags. So I checked the DMARC record for the sending domain > somenet.org. It is "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;mailto:postmaster@somenet.org;ri=3600;fo=1;" > which is syntactically incorrect. The extra ";mailto:postmaster@somenet.org" is wrong, I guess the tag "ruf=" is missing here! > > It should probably read "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;ruf=mailto:postmaster@somenet.org;ri=3600;fo=1;" > > So, should mm3 somehow "catch" this error somehow? Perhaps we should catch it. We already have other issues involving authheaders.authenticate_message. There's an invalid From: issue at https://gitlab.com/mailman/mailman/-/issues/1100 reported at https://github.com/ValiMail/authentication-headers/issues/25 and a different invalid DMARC issue at https://gitlab.com/mailman/mailman/-/issues/1109 reported at https://github.com/ValiMail/authentication-headers/issues/26. For now, I reported this at https://github.com/ValiMail/authentication-headers/issues/27 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Stephen J. Turnbull

Hi, Mark, Dan I'm no database expert, but is it possible that there's some index that's missing? (Just a WAG, feel free to ignore if you know more about databases than "adding indicies solves all problems" ;-) Mark Sapiro writes: > On 11/16/22 15:52, Dan Caballero wrote: > > Thanks Mark! > > > > We're using GNU Mailman 3.3.5 (Tom Sawyer). The tests I did via the Docker container used a database dump from our production MySQL server. > > > > We have 2050 lists. The address table in the database has 95028 rows. > > > For what it's worth, mail.python.org has 188 Mailman 3 lists and 85852 > rows in the address table, and handling a message waiting moderation > takes only a second or two. Thus, whatever the scaling issue is, it's > likely related to the number of lists as opposed to the number of list > members. > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to turnbull.stephen.fw(a)u.tsukuba.ac.jp > >

3 years, 11 months

[MM3-users] 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

9 years, 3 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Tim Cutts

Yup. I noticed that when I went through this two days ago. I hadn’t got around to mentioning it yet. :-) > On 8 Jul 2022, at 18:01, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/8/22 9:16 AM, kisner(a)live.com wrote: >> Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros. > > > The issue is when you do > ``` > pip install psycopg2-binary<2.9 > ``` > your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like > ``` > pip install psycopg2-binary\<2.9 > ``` > or > ``` > pip install 'psycopg2-binary<2.9' > ``` > I'll update the doc. > > -- > 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/

4 years, 4 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mohsen Masoudfar

Good morning Mark, You were right, the parameter m.filter_content was set to False, I believe the default. I changed it to True and it worked as expected. Thanks again. Mohsen -----Original Message----- From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Friday, October 2, 2020 2:54 AM To: Mark Sapiro <mark(a)msapiro.net> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list [EXTERNAL EMAIL] Mark Sapiro writes: > Filtering by extension only works on message parts that have an > associated file name. Thus, while you can add things like 'exe', 'bat', > 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it > won't be completely effective. > > A better approach is to use MIME types[1] and only allow those you want. > For a discussion list, a reasonable set is what this list uses: I wouldn't say "better" if you're concerned about the executables being malware. There's long history of concealing malware by giving it a MIME type different from what the extension implies, and there was at least one Windows exploit that used this technique to achieve automatic execution of malware simply by displaying the message. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 1 month

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Bob, Can you run the command "sudo docker logs mailman-core" and see what the end of that says? Another good command to run is "sudo docker ps" and make sure the mailman-core container is actually running. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, August 11, 2021 1:25 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: > DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: > DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost > connection with 127.0.0.1[127.0.0.1] while receiving the initial > server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- 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/

5 years, 3 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Where can I find the setting ``` POSTORIUS_TEMPLATE_BASE_URL ``` Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Tue, Jan 28, 2025 at 6:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/25 12:31, Arte Chambers via Mailman-users wrote: > > > > I'm getting the following error when using mass subscription on a testing > > list with a custom template loaded for [list:user:notice:welcome] > > ``` > > HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read > timed > > out. (read timeout=5) > > ``` > > > It appears you are setting the template in Postorius and there is an > issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. It looks like > this is something like > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' > ``` > and that connection is timing out. Try setting just the scheme and host > for access to Postorius. I.e., if you access Postorius at a URL like > https://www.example.com/mailman3/, try > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://www.example.com/' > ``` > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

1 year, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I installed whoosh, ran the server and got this: DisallowedHost at / Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Request Method: GET Request URL: http://192.168.1.42:8000/ Django Version: 1.11.3 Exception Type: DisallowedHost Exception Value: Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/django/http/request.py in get_host, line 113 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 Python Path: ['/var/lib/mailman/env2/lib/python2.7/site-packages/django_q', '/var/lib/mailman/mailman-suite/mailman-suite_project', '/var/lib/mailman/env2/lib64/python27.zip', '/var/lib/mailman/env2/lib64/python2.7', '/var/lib/mailman/env2/lib64/python2.7/plat-linux2', '/var/lib/mailman/env2/lib64/python2.7/lib-tk', '/var/lib/mailman/env2/lib64/python2.7/lib-old', '/var/lib/mailman/env2/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7', '/var/lib/mailman/env2/lib/python2.7/site-packages'] Server time: Fri, 21 Jul 2017 23:35:16 +0000 Where's the ALLOWED_HOSTS file???? El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > 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

9 years, 3 months

[MM3-users] Re: Migration of archives from Sympa to MM3

by Tom Fillmore

Great! ...appreciate your time. T The earth is but one country and mankind its citizens... - Baha'u'llah ------- Original Message ------- On Monday, February 28th, 2022 at 11:27 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/28/22 10:53, Tom Fillmore wrote: > > > Moving existing lists to MM3 looks doable the archives are a different story. Has anyone ever migrated archives from Sympa to MM3? > > Mailman can import archives where the messages are in a Unix format mbox > > file. It appears sympa can export archives as a zip file containing > > monthly files of messages > > https://sympa-community.github.io/manual/customize/archives.html. > > If these files are in Unix mbox format, HyperKitty's hyperkitty_import > > function can import them directly, either individually or concatenated. > > If not, they would need to be processed to add Unix `From` lines and > > possibly make other changes. In any case, the mbox to be imported should > > be checked for unescaped `From` lines in message bodies with a script > > such as the one at https://www.msapiro.net/scripts/cleanarch3. > > -- > > 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/

4 years, 8 months

[MM3-users] Re: Mailman3 via Docker and NGINX

by Abhilash Raj

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 > > uwsgi_read_timeout 300; > > proxy_set_header Host $host; > > proxy_set_header X-Forwarded-For $remote_addr; > > } > > } > > > Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the > correct output, uwsgi or whatever your wsgi process is is working at > that level, and I don't think you should be invoking uwsgi in nginx. I > think you should be using proxy_pass. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > for the nginx config used on lists.mailman3.org. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 10 months

[MM3-users] Re: Advice on migrating to Mailman 3

by Mark Sapiro

On 2/13/20 2:02 PM, Christoph Groth wrote: > > The only problem is that our list runs on Mailman 2. We would like to > move to Mailman 3, but this does not seem to be that simple. Perhaps > someone here would be so kind to give us advice? I think it's pretty simple, but I've been a Mailman developer for 15 years ;) > The number of (shared) hosters who offer Mailman 3 seems to be very > limited [3]. Would it be a good idea to book a virtual private server > (VPS) somewhere, that runs, say, Debian, and simply install Mailman > 3 through the distribution’s package system? I’m already running > a small personal box with nginx on it, and this is very little work, but > running Mailman would require sending out up to a few thousand email > messages per day (our list has a few hundred subscribers). Is this > something that one is commonly allowed to do on a VPS system? Most VPS > offers that I see are silent about mail. This list is on a VPS hosted by RackSpace. mail.python.org which hosts hundreds of lists is a VPS hosted by DigitalOcean, and my bicycling club's web site, email and mailing lists are on a VPS also hosted by DigitalOcean. These servers all run some version of Ubuntu, but because we are developers, they do not use the Debian/Ubuntu packages. They are all installed from the heads of the GitLab branches and kept pretty much up to date with those. All three servers use Postfix as an MTA. We have no issues with mail volume per se. What you will see with a new VPS is your IP being blocked by various ISPs. It takes a bit of communication and patience to work through these blocks, but once you develop a good reputation, they tend to go away. > If we setup such a system, can we assume that it will silently operate > without causing much administration work most of the time (like my nginx > server)? Or is maintaining a Mailman 3 server a significant burden ([2] [2], or [3]? > seems to imply that)? If yes, are you aware of organizations that > propose Mailman 3 hosting for open source projects? Python.org seems to > host some lists for third party projects, but otherwise I haven’t seen > much. I don't think a Mailman 3 installation needs an undue amount of baby sitting. I do run daily reports that list the contents of mailman's queues (normally empty, but messages in the shunt queue need investigation) and grep a couple of logs for errors. mail.python.org hosts lists for Python related open source projects. Kwant seems to be eligible. Ask postmaster(a)python.org specifying the desired list name and name and email address of the initial list owner(s). However, we don't normally import lists or archives from elsewhere. > [1] https://kwant-project.org/ > [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss > [3] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

Thanks Mark. Also, just to confirm, should the database connection string also be updated? In both the core and web configuration, I have something like: DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb Note the trailing UTF-8 encoding stuff isn't there. Should we be specifying utf8mb4 there as well? I'm planning to test this in a dev environment. If I can somewhat confirm the fix procedure won't break an existing install (like I have), I'll submit a PR(s) to the docker-mailman github. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, December 9, 2020 1:29 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing On 12/8/20 1:02 PM, matthew(a)alberti.us wrote: > Mark/Ruth/The List, > Thanks for the prompt responses. Before I try to figure out a way to > correct this... is the "character_set_database" the only thing I > should be looking at? You need to set 'OPTIONS': {'charset': 'utf8mb4'} in the DATABASES['default'] definition in your django settings. I'm not sure if this overrides the various collation, etc. settings in the DB or not, but it wouldn't hurt to update the DB. -- 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/

5 years, 11 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 26. April 2024 18:23:56 MESZ schrieb Mark Sapiro <mark(a)msapiro.net>: >On 4/25/24 22:30, Thomas Stein wrote: >> Am 2024-04-26 00:52, schrieb Mark Sapiro: >>> One thing you could try is in settings_local.py, put >>> ``` >>> from settings import MIDDLEWARE >>> x = list(MIDDLEWARE) >>> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >>> MIDDLEWARE = x >>> ``` >>> to work around the NameError. >> >> After that I get: >> >> File "/usr/share/mailman3-web/urls.py", line 20, in <module> >> from django.conf.urls import include, url >> ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) >> dpkg: error processing package mailman3-web (--configure): >> installed mailman3-web package post-installation script subprocess returned error exit status 1 >> Errors were encountered while processing: > > >This is another Debian/Ubuntu packaging issue. The packaged >/usr/share/mailman3-web/urls.py is incompatible with Django>=4.1. Replace it with the one at https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re… > >> I guess I'll wait for the new package for now. > >Hopefully that will fix it, or, as Odhiambo suggests, you can uninstall the Debian/Ubuntu packages and install per https://docs.mailman3.org/en/latest/install/virtualenv.html > I did that. It went actually quite well. Had to change the owner of the mailman databases with alter table though. cheers! t.

2 years, 6 months

[MM3-users] Re: messages with attachments, without text discarded silently

by Mark Sapiro

Thank you for providing the information below. I received both posts by direct mail, but the posts were discarded by the list because the attached .pck file was Content-Type: application/octet-stream and the list has a header filter on content-type with the pattern `^ *application/(?!(pgp|[^ ;]*signature))` and a discard action. In other words, the list will not accept any posts with MIME parts with Content-Type: application/* unless the subtype appears to be a signature. This is an anti-spam measure. Even if the message were accepted, that part would be removed by content filtering. On 1/31/25 12:14, Schulz wrote: > Hello, > here is the traceback: > Jan 28 20:31:16 2025 (25) it: DMARC lookup for js(a)jslz.de mailto:js@jslz.de (_dmarc.jslz.de) found p=reject in _dmarc.jslz.de. = v=DMARC1; p=reject; pct=100; rua=mailto:dmarc@faudin.de mailto:dmarc@faudin.de > Jan 28 20:31:16 2025 (25) ACCEPT: <17def72e63ed443458a88ec892a17fe01b8a287c(a)jslz.de mailto:17def72e63ed443458a88ec892a17fe01b8a287c@jslz.de > > Jan 28 20:31:16 2025 (28) Uncaught runner exception: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) > Jan 28 20:31:16 2025 (28) Traceback (most recent call last): > File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/lib/python3.12/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/lib/python3.12/site-packages/mailman/handlers/mime_delete.py", line 408, in process > process(mlist, msg, msgdata) > File "/usr/lib/python3.12/site-packages/mailman/handlers/mime_delete.py", line 180, in process > reset_payload(msg, useful) > File "/usr/lib/python3.12/site-packages/mailman/handlers/mime_delete.py", line 228, in reset_payload > msg.set_payload(subpart.get_payload(decode=True).decode( > File "/usr/lib/python3.12/email/message.py", line 343, in set_payload > payload = payload.encode(charset.output_charset, 'surrogateescape') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) > Jan 28 20:31:16 2025 (28) SHUNTING: 1738092676.7424345+fcb0d63d7b50bc797c3dd0a44de64bbd6b27eb92 > > > ---- > the .pck and the original email can't be attached I think (this msg didn't make it to the list) > > ---- > these are the first lines of the .eml: > > MIME-Version: 1.0 > Date: Tue, 28 Jan 2025 19:31:15 +0000 > Content-Type: multipart/mixed; > boundary="6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1" > From: "J. Schulz" <js(a)jslz.de> > Message-ID: <17def72e63ed443458a88ec892a17fe01b8a287c(a)jslz.de> > TLS-Required: No > Subject: empty, but another att > To: it(a)freie-dorfschule.de > > --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > > > --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 > Content-Type: application/pdf; name="someExample.pdf" > Content-Disposition: attachment; filename="someExample.pdf" > Content-Transfer-Encoding: base64 > > JVBERi0xLjcKJcOkw7zDtsOfCjIgMCBvYmoKPDwvTGVuZ3RoIDMgMCBSL0ZpbHRlci9GbGF0 > ZURlY29kZT4+CnN0cmVhbQp4nC2NTQvCMBiD7++vCHjz0L7t1q2DMXAfgoeBg4Ln4TpRULEU > 9OdbRB4SCISEhcKb5C7E6zqfI9qxoxcYLFhbmMoIXRrYXAlbKARPpy0eNKSWPAa/PsN9jtEv > G83Of2Jdy7E79OCmafv/UCJcqHVkCmFRlsmzCm6B3CsohltrVqw545wNF0llSjZRNe5Gg6Pp > 9zfhC14SKM4KZW5kc3RyZWFtCmVuZG9iagoKMyAwIG9iagoxNTMKZW5kb2JqCgo3IDAgb2Jq > Cjw8L0xlbmd0aCA4IDAgUi9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoMSA5MDc2Pj4Kc3Ry > ZWFtCnic5Vh9dFPHlb/zniTLH1iSP4RtGd4zwh9gW7ItTIAa/LAtYbDBso1BAgJ6lmQkYkta > SbZj0haTJoGYzyaEtEnOhuajTQgJz5AcTEqBLbs9yTZp04/ddje00G6a3Z4mkO02Pd3TYO+d > 0bP5aJKes2f/2yfPmzv3zr33N/feGWmcjA8GIQtGgQfJPyDH5s3K1APAWwAkxz+UFPsiGgfS > VwG4V/pi2weeOLPlDwCawwBpr27vH+n7k+ZkC0AWNm0sFJQD8rtQCWB6FW0sDiHjyRvHdTj+ > AMfzQwPJe/+Fe00DkGPEsbk/6pdbtKMoz6mg4wH53lhCU8/jWMKxGJEHgu+9/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Fwd: [GNC-dev] Passwords are Confidential

by flywire

Looking forward to Mailman 3. How can I get an indication of when Mailman 3 code is likely to run on Fedora 29? On Sun, Apr 26, 2020 at 1:42 AM Mark Sapiro wrote: > On 4/25/20 2:08 AM, flywire wrote: > > MailMan version 2.1.29 > > > > On Sat, Apr 25, 2020 at 6:08 PM Adrien Monteleone wrote: > > > > You can turn off the reminder in your mailman settings. > > > > As this is part of the mailman code, perhaps a bug report to them > > would be in order concerning the storage issue. > > > > Regards, > > Adrien > > > > > On Apr 24, 2020 w17d115, at 11:29 PM, flywire > > > > > > My password is confidential so please don't email it to me in > > plain text. > > > Don't even store it, instead encrypt what I entered and store that > > so you > > > can verify an encrypted version of the password I enter in the > future. > > > This is a well known, long standing issue which will not be fixed in > Mailman 2.1. See <https://bugs.launchpad.net/mailman/+bug/265179> > > It is fixed in Mailman 3. > > -- > Mark Sapiro > Derek Atkins 2020-04-25 18:32:15 EDT Code runs Fedora 29. Mailman 3 isn't available on F29. When code gets upgraded, mailman will be upgraded. As for turning off the reminder; you can turn it off yourself. Thank you.

6 years, 6 months

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Stefan Bauer

Thank you very much. But this is a _new_ mailman behavior. In previous versions, there was no checkbox at all and mass-subscription was done without any confirmation. Stefan Am Mo., 16. Mai 2022 um 18:35 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 5/16/22 07:16, Stefan Bauer wrote: > > > > Is there also a way to have this box checked by default or do not > request a > > verifcation at all? > > Could not find any flag in base.py. > > To have the box checked by default would require a patch to Postorius > like this. > ``` > --- a/src/postorius/forms/list_forms.py > +++ b/src/postorius/forms/list_forms.py > @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): > > pre_verified = forms.BooleanField( > label=_('Pre Verified'), > - initial=False, > + initial=True, > required=False, > help_text=_( > 'If checked, users will not have to verify that their ' > ``` > Not requiring verification at all would require patching Mailman core > but would be a bad idea as it could allow someone to subscribe anyone > without that person's consent. > > -- > 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/ >

4 years, 5 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

I tried this way but in this method I don't find any files to edit for my customizations like 1. Removal of social accounts, 2. Addition of SMS integration and so. If I can do my required customizations through pip installation I am fine with that. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 11:48 PM, Shashikanth Komandoor wrote: > > Though you are for sure that the current versions as I am claiming the > > above one is perfectly without any issue, please also suggest what would > be > > the best previous version which definitely does not have that issue > because > > I even checked out the immediate previous version of mailmanclient but > > still I am getting the same error. > > > Follow this document > < > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > and install with pip. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/25/26 2:43 PM, Ibiam Chihurumnaya via Mailman-users wrote: > > I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. > > I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save(). accept_these_nonmembers is a list hence the append, I didn't add the argument to append, maybe that's what caused the confusion. > > I don't understand what you are doing. The above makes no sense to me. > Please provide more detail on exactly what it is you are doing. > However, accept_these_nonmembersis an artifact from Mailman 2.1 and > only exists in Mailman 3 to support patterns as opposed to individual > email addresses. > In Mailman 3, there are two ways to accomplish this. One way is to > subscribe the user as a member and set the member's delivery to > disabled. The other way is to add the user as a nonmember and set the > nonmember's moderation_action to default processing. I had done the members part in the past, but the issue with it was I wanted certain members to not receive messages from the list, but only send 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

8 months, 2 weeks

[MM3-users] Re: "Must issue a STARTTLS command first" issue during social login 'send_email_confirmation'

by Mark Sapiro

On 12/17/19 3:05 AM, jean-christophe manciot wrote: > Ubuntu 20.04 > mailman3 3.2.2-1 > postfix 3.4.7-2 > > ```/etc/mailman3/mailman.cfg``` > ``` > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > smtp_host: localhost > smtp_port: 25 > smtp_user: user > smtp_pass: 'password' > smtp_secure_mode: SecureMode.STARTTLS > lmtp_host: 127.0.0.1 > lmtp_port: 9024 > configuration: python:mailman.config.postfix > ``` > The ```smtp_secure_mode``` value is based on https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…. > I am able to send emails using a mail client located on a remote device with the same user/password credentials. > Yet, trying to perform a social login leads to: > ``` > ERROR 2019-12-17 11:44:00,414 211904 django.request Internal Server Error: /accounts/github/login/callback/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner > response = get_response(request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 73, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/oauth2/views.py", line 143, in dispatch > return complete_social_login(request, login) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 152, in complete_social_login > return _complete_social_login(request, sociallogin) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 167, in _complete_social_login > ret = _login_social_account(request, sociallogin) > File "/usr/lib/python3/dist-packages/allauth/socialaccount/helpers.py", line 55, in _login_social_account > signal_kwargs={"sociallogin": sociallogin}) > File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 144, in perform_login > send_email_confirmation(request, user, signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/utils.py", line 312, in send_email_confirmation > signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 60, in send_confirmation > confirmation.send(request, signup=signup) > File "/usr/lib/python3/dist-packages/allauth/account/models.py", line 166, in send > get_adapter(request).send_confirmation_mail(request, self, signup) > File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 450, in send_confirmation_mail > ctx) > File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 137, in send_mail > msg.send() > File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 291, in send > return self.get_connection(fail_silently).send_messages([self]) > File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 110, in send_messages > sent = self._send(message) > File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 126, in _send > self.connection.sendmail(from_email, recipients, message.as_bytes(linesep='\r\n')) > File "/usr/lib/python3.7/smtplib.py", line 867, in sendmail > raise SMTPSenderRefused(code, resp, from_addr) > smtplib.SMTPSenderRefused: (530, b'5.7.0 Must issue a STARTTLS command first', 'user@mysite') > ``` > Any suggestion? I don't know the answer offhand, but this is Django encountering the issue and it appears that Mailman core for which the mailman.cfg [mta] settings and the doc to which you refer apply is not involved at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/8/21 4:41 AM, Thomas Möhle via Mailman-users wrote: > Hey Mark, > > thanks for your reply!> In what way? Do list posts get delivered? What > works and what doesn't? > > What are the observable symptoms for things that don't work? > Yes, mails are not delivered. You can send a mail to the mailinglist > without getting a bounce, but you will not receive the mail back through > mailman. > In addition to that, I'm unable to edit mailing lists in the web > interface. After clicking on a list, I'll get a 404. > Plus, I noticed that mailman is constantly writing files to > /var/lib/mailman3/queue/out/ but they seem to get deleted right away > again. I'm getting alot of IO there though. So messages are being queued for the outgoing runner and then something is done with them. If there are no errors in mailman.log about this and nothing in the shunt queue, they are being delivered to the MTA. What's in the MTAs logs? > > What do you get for example if you go in a web browser with hyperkitty > > running to > > > > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… > > I get a small gziped json file back. Key is "url", value is a link to a > message. OK. That's correct and it seems that Mailman core can communicate with the HyperKitty API, at least when HyperKitty is running. > > And please don't post secret keys and change the value of api_key: in > > mailman-hyperkitty.cfg and the corresponding value in > > MAILMAN_ARCHIVER_KEY in your Django settings. > I actually tried to redact the logs and config files, but I must have > failed to save my edits on that one file. I'll change it right away. The key was in the mailman-hyperkitty.cfg file you posted and was in multiple entries in mailman-web.log. There is some strangeness in the logs you posted. Mailman.log contains many of these: Aug 07 12:49:55 2021 (2343598) HyperKitty failure on https://mail.example.com/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> (503) and mailman-web log contains many of these [pid: 2343625|app: 0|req: 1/1] 10.133.3.2 () {60 vars in 1350 bytes} [Sat Aug 7 12:49:58 2021] GET /mailman3/hyperkitty/api/mailman/urls?mlist=aussen%40lists.example2.com&msgid=002601d777e2%244c34c540%24e49e4fc0%24%40example2.com&key=g8nOyDVbCNsi18L%2FjgTj%2BWDVKUQ2XeQM => generated 131 bytes in 279 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) which actually seem normal except for the quantity, but the time stamps don't correlate. There's nothing in mailman-web.log for the times of the 'HyperKitty failure' messages in mailman.log. Was the web service even up during those times. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Thats part of the issue. It looks like these are in the PendingsDB but not showing up in the UI. Even if I go into Subscription Requests -> Pending Approvals or Pending Confirmations no pending items are shown at all. But in the pendingDB via mailman shell I can see 3 pending unsubscriptions. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:26 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:15 PM, Simon Coggins wrote: The version of postorius is 1.3.4 Then you should be able to click Subscription requests even though the badge shows 0 and click Unsubscription Requests in the dropdown. I know it's an issue, but the badge only counts subscription requests pending approval and not unsubscription requests. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Hyperkitty CSS issue

by Ryan Morash

I tried both the –clear flag and removing everything in my static directory with no luck. From: Mark Sapiro <mark(a)msapiro.net> Date: Sunday, June 14, 2020 at 5:22 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Hyperkitty CSS issue On 6/14/20 1:48 PM, Ryan Morash wrote: > I migrated my existing mailman3 install from using the Debian packages to a virtualenv setup. For the most part everything seems to be running fine, but I'm running into an issue where Hyperkitty 1.3.3 is referencing an incorrect CSS file. It is trying to load "/static/CACHE/css/hyperkitty.39ef00cc7454.css" which does not exist. If I replace that reference (using my browser's dev tools) with "/static/CACHE/css/output.12a071da81b1.css" everything looks fine. I've ran the collectstatic, compress, and migrate commands successfully with no change. Any ideas on how to fix this? Have you tried running collectstatic with the --clear option or removing everything in STATIC_ROOT before running collectstatic?, See, e.g., <https://docs.djangoproject.com/en/2.2/ref/contrib/staticfiles/> -- 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://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

6 years, 4 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/28/20 2:34 AM, Odhiambo Washington wrote: > > So, now I remember why I had to chown -R mailman3 /opt/mailman > Then now it seems like I have been doing things incorrectly, because I have > been doing > a lot of operations as root by simply: > cd /opt/mailman/mm > virtualenv venv > source venv/bin/activate > Looks like the correct way is to start with su - mailman3 Yes. All those things should be done as the Mailman user. >>> PS: There is the issue with qcluster, which doesn't seem to have been ... > I have run it from supervisord. It has forked 30 processes and refuses to > kill them when I stop supervisord. > I will look for options around it. I know nothing about supervisord, but there should be a parent process. E.g., here > msapiro@mail:~$ ps -fwwu mailman|grep qcluster > mailman 2885 1 0 Jul18 ? 00:00:00 /bin/bash /opt/mailman/mm/bin/mailman-web-django-admin qcluster > mailman 2889 2885 0 Jul18 ? 00:01:57 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2930 2889 0 Jul18 ? 01:21:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2944 2930 0 Jul18 ? 00:04:17 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2945 2930 3 Jul18 ? 07:11:14 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 6467 2930 0 15:39 ? 00:00:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12337 2930 0 15:00 ? 00:00:07 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12639 2930 0 11:08 ? 00:00:11 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 14658 2930 0 Jul27 ? 00:00:22 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 15860 2930 0 01:41 ? 00:00:21 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 19205 2930 0 Jul27 ? 00:00:29 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > msapiro@mail:~$ pid 2885 is the parent which forked 2889 which in turn forked 2930 which forked all the others. stopping (sigterm) 2885 in this case will stop them all. I have seen an issue on one server where some of the qcluster workers become orphaned and their parent pid is 1. These are left when I stop the upstart service so I have this script. #! /bin/bash if echo `status qcluster` | grep -q 'running' ; then echo qcluster is running exit fi ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill to kill them. > PS: Did you by any chance find time to look into the issue about wsgi.py > that you had mentioned - the one that has me > stuck using it?? If you're referring to the issue at the end of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, I think that was caused by your not having the __init__.py file in /opt/mailman/mm/. If not, I probably need more information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/12/19 8:55 PM, Paul Arenson wrote: > I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. I'm guessing what you want and what you are saying First, I think you are saying your issue is that your users are using HyperKitty as a web forum and when replying to a message in an existing thread instead of using the 'reply' action on that message, they use the Start a new thread button. Is that really what you are saying? > MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? If by "read only" you mean the "Announce only mailing list style" as opposed to the "Ordinary discussion mailing list style" the only difference is that for the Announce only style the list attribute allow_list_posts is False and for the Discussion style, it's True. This is the setting in Postorius -> Settings -> Alter Messages -> Include the list post header an all it does is include or not include the List-Post: header in mail from the list. > ALTER MESSAGES > ----------------------- > Filter content Now YES > > Collapse Alternatives Now yes > > Convert html to plain text Now NO Above are not relevant. > Anonymous NOW YES Are you sure you want this. What it does is replace the From: address with the list posting address and removes all other headers that could aid in identifying the poster. It is intended for lists discussing things such as domestic abuse where people may want to be able to post anonymously. > Include RFC2369 headers Now Yes OK, but not relevant > Include the list post header Now Yes This is what the announce style will set to No. > Reply Goes to List Now No munging > > Pipeline Default > > > > DMARC MITIFGATIONS > ----------------------- > > Replace From with list address > > DMARC mitigate unconditionally Now NO > > > MESSAGE ACCEPTANCE > ----------------------- > > Require Explicit Destination Yes > > Administrivia YES The above are OK, but again not relevan to what I think you're asking. > > Default action to take when a member posts to the list Hold for moderation > > > Default action to take when a member posts to the list Hold for moderation Basically these two settings will hold all posts for moderator action, however if the user has a moderation setting other thgan list default, they won't apply. > OTHER? See the FAQ at <https://wiki.list.org/x/4030685>. This is written for Mailman 2.1 and older and some of the settings aren't relevant or exactly the same in Mailman 3, but it may help. On the other hand, if I'm not understanding what you want, please clarify. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Jim Ward

I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. 2) The 'Search Members' function appears to be limited to the email address only and does not include display name These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, January 10, 2020 7:05 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- 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://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Should Sign Up ?? Log In?? El vie., 21 jul. 2017 a las 18:56, Rafael Mora (<rafael.mora.guti(a)gmail.com>) escribió: > Nice! Up and running! > > How do I start using mailman? what are the steps?? > > REALLY thank you all for your patience and help! Really appreciated ! > > El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 04:43 PM, Rafael Mora wrote: >> > YEEEES! At last!!! I can see the web UI. >> > >> > Now I´m getting this message in the web UI: >> > >> > Something went wrong >> > Mailman REST API not available. Please start Mailman core. >> > >> > >> > >> > Where do I configure the REST API ????? >> >> >> So I guess you figured out that ALLOWED_HOSTS is a Django setting in >> settings.py or wherever your Django settings are. >> >> Now you have to start Mailman Core. In your Python 3 'env' where you >> installed Mailman Core, run 'bin/mailman start'. >> >> -- >> 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 > -- Atentamente / Best Regards Ing. Rafael Mora

9 years, 3 months

[MM3-users] How to Increase outgoing mail volume for Mailman 3

by Brian Carpenter

Hello everyone, We had a new client come on board that brought a list that had the largest out-going mail volume that I have ever dealt with. So I did what any sane server administrator would do that is running Mailman 3: I ran to Mark Sapiro for help! Here is what the Sage of all things Mailman counseled me to do: 1. Disabled VERP delivery. VERP can help improve mail delivery by delivering 1 message per SMTP transaction (I think I got that right). Using VERP is counter-productive as it can seriously delay outgoing mail delivery for a high-volume list. So you can use something like the following in the MTA section of your mailman.cfg: [mta] verp_confirmations: no verp_personalized_deliveries: no verp_delivery_interval: 0 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. This action was the game changer. It allows Mailman to handle 4 incoming messages at a time instead of 1. My client's incoming list volume was high enough where it was overwhelming the single outgoing runner. Here is what I added to the mailman.cfg file: [runner.out] instances: 4 Doing this step immediately solved the backlog in var/queue/out. 3. If you start up with a new server for a list that is high volume then keep an eye out for Proofpoint and Vade Security as they will block your new IP address quicker than Mark Sapiro can say "This is a bug. See <some Gitlab.com url>" Mark, thank you! -- Brian Carpenter Harmonylists.com Emwd.com

6 years

[MM3-users] Re: Link to account

by Lars Bjørndal

Thanks a lot! After further consideration, I will stay with the defaults, e.g. have accounts, archive etc at the same level as mailman3. Lars On Wed, Apr 12, 2023 at 08:32:27AM -0700, Mark Sapiro wrote: > On 4/11/23 23:08, Lars Bjørndal wrote: > > > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. > > > Try this. > > In urls.py > ``` > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), > permanent=True), > ), > path('mailman3/archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('mailman3/accounts/', include('allauth.urls')), > path('mailman3/admin/', admin.site.urls), > path('mailman3/', include('postorius.urls')), > ] > ``` > > In apache > ``` > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3/archives" > "http://127.0.0.1:8000/mailman3/archives" > ProxyPass "/mailman3/accounts" > "http://127.0.0.1:8000/mailman3/accounts" > ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" > ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > </IfModule> > ``` > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

3 years, 6 months

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

by Mark Sapiro

On 3/1/21 11:53 AM, David Partain via Mailman-users wrote: > Thanks for being patient with me. I'm still baffled but might have found the problem. > > > I've done the above, to no avail. > > > If I look at the queries being sent to mysql, I see stuff like this: > > > 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP > > 174 Query SET sql_mode='STRICT_TRANS_TABLES' > > 174 Query COMMIT > > 174 Query SET AUTOCOMMIT = 0 > > 174 Query SET AUTOCOMMIT = 1 > > 174 Query SET AUTOCOMMIT = 0 > > > I note that there is nothing about the charset, so something's clearly wonky. > > > As previously stated, /etc/mailman3/mailman-web.py has the right thing: > > > 'OPTIONS': { > > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > > 'charset': 'utf8mb4', > > }, > > > but that latter is having no effect. > > > I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset > > (but does have init_command), but I _think_ that's only about the package management system. I think that's correct. I doubt that that's the problem, but if all else fails, you might just remove it. I don't think that would hurt as it's purpose is just todetect on upgrade of the package if you've changed the file from the distributed one and ask you what you want to do about it. > So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py > > (which obviously has the right thing), but what about the .pyc file? > > > # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc > > Binary file /usr/share/mailman3-web/settings_local.pyc matches > > # grep -i charset /usr/share/mailman3-web/settings_local.pyc > > # > > > It ain't in the .pyc file. Am I overly optimistic that that might the be problem? > > > If so, I'd be grateful if someone'd tell the newbie how to recreate that file without > > trashing something. This is a bit strange: Here's how it works. .pyc files are byte-compiled versions of the corresponding .py file. When Python runs or imports from a .py file, it first looks for a corresponding .pyc file and if that is as new or newer than the .py, it uses the .pyc. If not, it uses the .py and byte-compiles it and if it has permission, writes an updated .pyc Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc in the same directory as the .py Its uses a __pycache__ directory in the same directory as the .py and within that directory a file like in this case settings_local.cpython-37.pyc (or whatever the python version is) In any case, I would remove the existing settings_local.pyc. That can't hurt, but I'm curious what ls -lR /usr/share/mailman3-web/ shows. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

2 years, 5 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 10:51 PM, joseverde(a)gmail.com wrote: > Okay, I *think* I killed the processes. When I run > > ps -fwwA|egrep 'master|runner' > > I just get > > root 7595 1 0 Jul26 ? 00:00:04 /usr/lib/postfix/sbin/master -w > mailer 21851 21001 0 22:45 pts/1 00:00:00 grep -E --color=auto master|runner Yes, there are no mailman processes running. > As far as the permissions, you asked does your systemd script set the user to the Mailman user? I don't know how to check that, but I saw many files in /var/lib/mailman3 were owned by a user named list. Last time I tried to run mailman status, it threw a permission error on mailman.cfg, which was owned by root. I changed owner to list, and it produced a different error. So I'm guessing we are on the right path? There was no mention of a user named mailman in the system before, but maybe I need to check something. You are apparently using the Debian/Ubuntu packages. In those, the Mailman user is `list`. There is no `mailman` user. As far as what user the systemd script sets, just look at the script, but if it was installed by the Debian/Ubuntu package, it's probably OK. The script is named xxx.service where 'xxx' is the name you might use in systemctl commands (probably 'mailman3'). It should be at /etc/systemd/service/ or one of the subdirectories. > Lastly, I deleted everything in /var/lib/mailman3/locks. > > However, running mailman status now throws this permission error > > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 188, in initialize > initialize_1(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 123, in initialize_1 > mailman.config.config.load(config_path) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 107, in load > self.push(filename, user_config.read()) > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 113, in push > self._post_process() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 125, in _post_process > self.ensure_directories_exist() > File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 227, in ensure_directories_exist > with Lock(lock_file): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 203, in lock > self._write() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 417, in _write > with open(self._claimfile, 'w') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/mailman-cfg.lck|[redacted server name]|21787|3720843219351355903' > > That file was removed when you told me to clear the locks folder (I save a copy, however). So I'm stuck again. Sorry for all the questions and thanks very much for the help. Does the `list` user own /var/lib/mailman3/ and /var/lib/mailman3/locks/? Are you running `mailman` commands as user `list`? Also see <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Before changing the DEBUG var to false everything was working fine after I changed it started the problems... El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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

9 years, 3 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. Also after clearing the browser cache, the above behavior is seen. Best Regards,Eric On Sunday, December 13, 2020, 03:58:47 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 5:24 PM, Eric Broens via Mailman-users wrote: > I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: > "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" Is there a message in Mailman's var/archives/hyperkitty/spool/ directory? If so, what's logged in mailman's mailman.log -- 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/

5 years, 11 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 3:00 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Those are headers for compiling some sass. Possibly you actually have a > >> `sassc` installed in which case you may need > >> > >> COMPRESS_PRECOMPILERS = ( > >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > >> ) > >> > >> > > This change makes the error I was getting to go away. However, I cannot > > login to manage lists, even after restarting mailman. > > > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ > > > The relevant part of which is > > OfflineGenerationError at /accounts/login/ > You have offline compression enabled but key > "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is > missing from offline manifest. You may need to run "python manage.py > compress". Here is the original content: > > I.e., something went wrong with your compress command. Try it again. > I have successfully run the following commands: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate But the error at https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ persists. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 5 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Mark Sapiro

On 7/27/20 2:48 AM, Shashikanth Komandoor wrote: > Hi Mark, > > Thank you for your response. And sorry for not giving you > complete information as I am not sue what to share with you. > > I am using Postgresql-11.7 as my backend database. The below is > the structure of the address table in* mailman *database: > > mailman=# \d address; > Table "public.address" > Column | Type | Collation | Nullable | > Default > ----------------+-----------------------------+-----------+----------+------------------------------------- > id | integer | | not null | > nextval('address_id_seq'::regclass) > email | character varying | | | > _original | character varying | | | > display_name | character varying | | | > verified_on | timestamp without time zone | | | > registered_on | timestamp without time zone | | | > user_id | integer | | | > preferences_id | integer | | | > Indexes: > "address_pkey" PRIMARY KEY, btree (id) > "ix_address_email" UNIQUE, btree (email) > "ix_address_preferences_id" btree (preferences_id) > "ix_address_user_id" btree (user_id) > Foreign-key constraints: > "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) > Referenced by: > TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY > (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL > TABLE "autoresponserecord" CONSTRAINT > "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES > address(id) > TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY > (address_id) REFERENCES address(id) > TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" > FOREIGN KEY (address_id) REFERENCES address(id) > > The below is the structure of *user* table: > > mailman=# \d user; > Table "public.user" > Column | Type | Collation | Nullable > | Default > -----------------------+-----------------------------+-----------+----------+---------------------------------- > id | integer | | not null > | nextval('user_id_seq'::regclass) > display_name | character varying | | > | > password | character varying | | > | > _user_id | uuid | | > | > _created_on | timestamp without time zone | | > | > is_server_owner | boolean | | > | > _preferred_address_id | integer | | > | > preferences_id | integer | | > | > Indexes: > "user_pkey" PRIMARY KEY, btree (id) > "ix_user__user_id" btree (_user_id) > "ix_user_preferences_id" btree (preferences_id) > Foreign-key constraints: > "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES > address(id) ON DELETE SET NULL > "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > preferences(id) > Referenced by: > TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN KEY > (user_id) REFERENCES "user"(id) > TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) > REFERENCES "user"(id) > > mailman=# \dn > List of schemas > Name | Owner > --------+---------- > public | postgres > (1 row) > > mailman=# select * from user; > user > ---------- > postgres > (1 row) > > *The above command output is not showing any fields. But if use the table > as public.user (schema.tablename) with select command, it is showing the > data. But without schema name this table is not showing those fields. Not > sure if this the expected behavior or not.* This is expected. psql gets confused because it has its own user table. The above table definitions look fine. Is there any entry in the `address` table for which `id` is not an integer? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

Yes, I have django_mailman3/templatetags/d_gravatar.py in my installation. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:11 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org > <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: > /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- 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/

5 years

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- 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, 10 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

Got it. Is there a command that one can manually run to test/expedite the process? ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 12:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/28/25 7:07 AM, willie.castillo(a)caemilusa.com wrote: > Looks like "hyperkitty" stopped archiving right after the CERT for the mailman3 website expired, How can I make the missing archives visible on the website? I see there "*pck" files in the/opt/mailman/mm/var/archives/hyperkitty/spool/ directory. The list archive does not show that last posting [of 25 July 2025. > > ~$ ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 98215 Jul 25 12:01 1753459289.7901242+f3fd7ee77272862f8c1023394bf88d0d4bbe9053.pck > -rw-rw---- 1 mailman mailman 98109 Jul 25 12:01 1753459289.7726512+ee1264c36a194eb0ec1a52089f053e6963f24369.pck > -rw-rw---- 1 mailman mailman 88479 Jul 25 12:01 1753459289.7564857+2e27f35a57f757f058dc95e34c56722a76307900.pck > > The CERT on the website is now up-to-date Those queued messages will be reprocessed on the next post. -- 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://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

1 year, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I want to use Mailman to send emails to our customers. I´m getting this error when I click on sign up and log in: FilterError at /accounts/login/ /bin/sh: sassc: command not found Request Method: GET Request URL: http://192.168.1.42:8000/accounts/login/?next=/postorius/lists/ Django Version: 1.11.3 Exception Type: FilterError Exception Value: /bin/sh: sassc: command not found Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py in input, line 196 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 What's missing??? El vie., 21 jul. 2017 a las 19:57, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:57 PM, Rafael Mora wrote: > > Should Sign Up ?? Log In?? > > > Yes. > > > > El vie., 21 jul. 2017 a las 18:56, Rafael Mora (< > rafael.mora.guti(a)gmail.com>) > > escribió: > > > >> Nice! Up and running! > >> > >> How do I start using mailman? what are the steps?? > > > What do you want to do with Mailman? This is the key question. > > There is some list subscriber documentation at > <http://docs.list.org/en/latest/userguide.html>. > > You can create domains and lists via Postorius or via the core's > bin/mailman commands ('bin/mailman --help' for a 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

9 years, 3 months

[MM3-users] Re: 'str' object has no attribute 'token_type'

by Mark Sapiro

On 11/15/21 6:06 AM, Marco Marinello wrote: > Hi everybody, > > I'm sorry for being always the strange guy with strange errors here but for some reason... I am. > On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: > > > Traceback (most recent call last): > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner > response = get_response(request) > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view > return view_func(*args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive > add_to_list(mlist_fqdn, msg) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list > from_str = header_to_unicode(message['From']) > File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ > the values matching a header field name. > File "/usr/lib/python3.9/email/message.py", line 471, in get > for k, v in self._headers: > File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse > return self.header_factory(name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ > return self[name](name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ > cls.parse(value, kwds) > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in parse > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name > if res[-1][-1].token_type == 'cfws': > > Exception Type: AttributeError at /hyperkitty/api/mailman/archive > Exception Value: 'str' object has no attribute 'token_type' > Request information: > USER: AnonymousUser > > > I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. > Any clue of what could have happened, why and how to fix it? The exception is thrown in the Python email package on HyperKitty's attempt to get the From: header of the message. This looks like https://bugs.python.org/issue43501 and/or https://bugs.python.org/issue30988. These issues refer to display names beginning or ending with a dot. Is that the case with the From: header of the problem messages? Note that display names containing dot should be quoted. It appears that at least one of the people posting posts with the problem From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by William Oliver

On Tue, 2021-12-28 at 20:05 -0800, Mark Sapiro wrote: > On 12/28/21 5:58 PM, William Oliver wrote: > > On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > > > The recommended uwsgi.ini includes > > > > > > pythonpath = /etc/mailman3/ > > > > > > according to > > > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > > > > > this should work. Did you have that? If you did and it doesn't > > > work, > > > perhaps adding > > > > > > env = PYTHONPATH=/etc/mailman3 > > > > > > > Yes, I had the first, and does not work. The second entry works. > > > I updated the doc to use > > env = PYTHONPATH=/etc/mailman3 > > I don't know enough about uwsgi to know for sure, but the issue may > be > that setting pythonpath in a running python process doesn't work - > it's > too late as the path is already set in python's initialization. > You might add that it may be necessary to do it in .bashrc for linux folk -- I got it to work but as I've demonstrated, I can sometimes make mistakes and leave detritus around. I may not have successfully cleared my previous setting. That being said, I think it works. I am, I am afraid not a details-oriented guy, which is a bit of a drawback for someone doing system admin...

4 years, 10 months

[MM3-users] Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 6:31 PM, Brian Carpenter wrote: > > This is with the configuration line enabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f > /opt/mailman/core/var/logs/mailman.log > Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner exiting. > Jul 22 01:25:17 2020 (21) command runner exiting. > Jul 22 01:25:17 2020 (22) in runner exiting. > Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (24) nntp runner exiting. > [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master > Jul 22 01:25:21 2020 (1) Master stopped > Jul 22 01:25:26 2020 (1) Master started > Jul 22 01:25:44 2020 (27) rest runner started. > Jul 22 01:25:44 2020 (26) pipeline runner started. > Jul 22 01:25:44 2020 (20) bounces runner started. > Jul 22 01:25:45 2020 (22) in runner started. > Jul 22 01:25:45 2020 (28) retry runner started. > Jul 22 01:25:46 2020 (29) virgin runner started. > Jul 22 01:25:46 2020 (25) out runner started. > Jul 22 01:25:46 2020 (23) lmtp runner started. > Jul 22 01:25:46 2020 (24) nntp runner started. > Jul 22 01:25:47 2020 (30) digest runner started. > Jul 22 01:25:47 2020 (19) archive runner started. > Jul 22 01:25:47 2020 (21) command runner started. > > This is with the configuration line disabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f > /opt/mailman/core/var/logs/mailman.log > Jul 22 01:27:49 2020 (1) Master stopped > Jul 22 01:27:53 2020 (1) Master started > Jul 22 01:28:10 2020 (30) digest runner started. > Jul 22 01:28:10 2020 (29) virgin runner started. > Jul 22 01:28:10 2020 (24) nntp runner started. > Jul 22 01:28:10 2020 (25) out runner started. > Jul 22 01:28:10 2020 (22) in runner started. > Jul 22 01:28:11 2020 (28) retry runner started. > Jul 22 01:28:11 2020 (27) rest runner started. > [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 > [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: > http://172.19.199.2:8001 (27) > [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync > [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 > [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 > [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 > [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 > Jul 22 01:28:11 2020 (19) archive runner started. > Jul 22 01:28:11 2020 (21) command runner started. > Jul 22 01:28:12 2020 (23) lmtp runner started. > Jul 22 01:28:12 2020 (20) bounces runner started. > Jul 22 01:28:12 2020 (26) pipeline runner started. > Is there perhaps some permissions issue in reading your added gonicorn.cfg? Also, note that gunicorn is set-up to log to the logging.http path, the default for which is mailman.log in the configured log_dir, but if this is changed to something other than mailman.log (see `mailman conf -k path -s logging.http`), it could be elsewhere. I'd expect gunicorn to log something if it couldn't start. Also, as Alan Hansen notes, you can export a list of members with `mailman members` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

Search results for query "sapiro"