Search results for "2021" - Mailman-users

Re: mailman3 postorius cannot retrieve template

by Quanah Gibson-Mount

--On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >> >> My conclusion: >> I ask you to consider these experiences in an update for the mailman3 >> packages in debian bullseye. It would save time, questions and nerves. > > > Issues with Debian packaging should be directed to Debian. Or as previously discussed, the debian packages should be avoided entirely. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

3 years, 8 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I am pleased to announce new stable releases for Mailman Core, Postorius, > Hyperkitty. > > These include both new features and bug fixes. Complete change log for > each components: > > Mailman Core 3.3.3: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… May I ask if this is a typo? I am asking because Mailman Core 3.3.4 was announced on Marc 22nd. So is this new one version 3.3.3 or 3.3.5? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

Re: New messages not being archived

by Philip Colmer

On Mon, 6 Sept 2021 at 20:48, Abhilash Raj <maxking(a)asynchronous.in> wrote: > You don't *need* to update urls.py to change suburl from `/archives' to > `/hyperkitty`, you can just change the reference to it. > > As it turns out, it is another mistake in the install docs :( > > Can you update /opt/mailman/mm/mailman-hyperkitty.cfg in to use > > base_url: http://127.0.0.1:8000/archives/ > > instead of the original > > base_url: http://127.0.0.1:8000/hyperkitty/ > > That should fix the issue without having to edit the urls.py. Thank you - that has, indeed, fixed it (and I did back out my change to urls.py as well). Regards Philip

3 years, 10 months

Re: Mixing Mailman 3 with AWS SES

by Andrew Hodgson

Danil Smirnov wrote: >пт, 26 мар. 2021 г., 23:29 Andrew Hodgson <andrew(a)hodgson.io>: >> Danil Smirnov wrote: > [...] >> Getting this back on topic, would you be willing to share how you are >> sending outbound mail through AWS servers without it being marked as >> spam by nearly every blacklist out there? [...] >I suspect you are talking about ESPs marking incoming mails as spam rather than anti-spam blacklists here. >I've posted an article on the topic a while ago: Thanks for this, I may try and get my VPS onto AWS in the coming months. I note Azure now let you set reverse DNS as well. Andrew.

4 years, 3 months

Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/

by Mark Sapiro

On 12/6/21 8:20 AM, Christian Stalberg via Mailman-users wrote: > What is causing this error please? > > > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Sunday, December 5, 2021 10:46 PM > To: > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/ > > Internal Server Error: /archives/ > > Report at /archives/ > Internal Server Error: /archives/ > > Request Method: GET > Request URL: https://lists.ccalternatives.org/archives/?sort=active%22'! ... > GET: > sort = 'active"\'!' The invalid sort= query fragment -- 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

False attachments in Outlook 2019?

by Brian Olesen

Dear Mailman 3 users, I seriously think of upgrading from Mailman 2.1.33 to this new RC2 or the final one, when it comes out. But there is an annoying issue that I'd like to ask you about. It's the false attachments that Outlook creates for the footer. Is this still an issue when using Mailman 3, or have you made some sort of work around? I mean here in 2021 it could be nice to use html as the default mail format to be able to create nice looking mails, and due to EU regulations an unsubscription is a requirement. Best regards Brian Olesen from Denmark P.S. If this issue has been solved I will happily translate the mail templates into Danish if wanted.

4 years, 5 months

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Thu, May 13, 2021, at 1:46 PM, Odhiambo Washington wrote: > > > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for each components: >> >> Mailman Core 3.3.3: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> Postorius 1.3.4 https://docs.mailman3.org/projects/postorius/en/latest/news.html >> Hyperkitty 1.3.4 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html >> >> Minimum supported Python version is 3.6. >> >> You can install them using: >> >> $ pip install --upgrade postorius hyperkitty mailman >> >> We have also recently been working on making the installation instructions[1] to be >> more detailed and added a new FAQ[2] section for administrators where I hope >> to capture common questions from mailman-users list. >> >> Feedback or Merge Requests to improve these docs are welcome. You can either >> send an email or open an issue on Gitlab (easier to track) here[3]. >> >> [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > Hi Abhilash, > > What's the reason behind the exclusion of MySQL & Apache instructions in the installation instructions? :-) Really no reason, the intent was to pick some options in that page and point to additional documentation for using other alternatives. I will be more than happy to accept patches to add the documentation about alternatives like MySQL and Apache and other variations in the tech stack. Just add a new page under install/ and add a "Note" in the above page to point to it. I had documented some time ago how to contribute to our documentation[1] and folks on this list would be happy to answer any questions regarding contribution too. [1]: https://docs.mailman3.org/en/latest/documentation.html -- thanks, Abhilash Raj (maxking)

4 years, 1 month

Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <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

3 years, 8 months

Re: Equivalent of listadmin Perl script for Mailman 3?

by Philip Colmer

On Fri, 19 Nov 2021 at 09:13, Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > It probably wouldn't be hard to write a bare-bones workalike if the > admin has shell access to the mailman host. > I was hoping that I could write an alternative using the REST API, but I'd overlooked the fact that there is a single username and password protecting the API. Unfortunately, even trying to solve this via shell access would have a similar problem because I can't see how one person running the command can be restricted to just the lists they administer. Oh well ... maybe something for the project to consider as an improvement in the future, particularly for the REST API. Philip

3 years, 7 months

Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Abhilash Raj

> On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > On Sat, 13 Mar 2021 14:46:55 -0500, > Mark Sapiro wrote: >> >> On 3/13/21 11:14 AM, John Covici wrote: >>> >>> Now one thing came up while trying to create the database, I got a >>> traceback complaining about a revision error because gentoo had a >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I >>> upgrade mailman, am I going to have to do something to the database as >>> well and why should the database have some kind of reference to the >>> mailman version? >> >> >> I don't know why this is an issue. You shouldn't need to do anything >> with the database when you upgrade. Please post the full traceback and >> error message. > > Sorry I can't reproduce it, after dropping and recreating the database > the error went away, but it was in alembic and it was talking about an > invalid revision and gave a long hex string. > My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2). But that’s just my guess without looking at the traceback. > -- > 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 <mailto:covici@ccs.covici.com> > _______________________________________________ > 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/>

4 years, 3 months

Mailman-users search results for query "2021"