Search results for "Postorius" - Mailman-users

Help Setting Up Mailman 3 on an Ubuntu Server

by smith.ja1ck＠gmail.com

Hello All Community Member, I am in the process of setting up Mailman 3 on an Ubuntu 22.04 server & have faced some challenges during the configuration phase. Also I have followed the installation guide & while Mailman Core and Postorius seem to be working I am struggling to configure the Mailman web interface correctly with NGINX. Also I have tried a few different configurations for the reverse proxy but I m running into 502 Bad Gateway errors. Does anyone have experience setting up Mailman 3 with NGINX who might be able to offer some guidance? ?I am interested in seeing a working configuration file for NGINX and any tips on troubleshooting Mailman 3 issues during this phase. As well, I found these resources when doing research on this; https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://redacted If anyone have any resources, tutorials or personal experiences please share with me, It would be greatly appreciated!!

1 year, 8 months

Re: archiving problem & updates

by Brian Carpenter

On 2/18/21 1:00 PM, Christian Stalberg via Mailman-users wrote: > Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? > > Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? > > Thank you! > _______________________________________________ > 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/ If this is in regards to the server I install Mailman on, then here are the update instructions to use: # cd /opt/mailman/mm # su mailman # source /opt/mailman/mm/venv/bin/activate # pip install --upgrade mailman hyperkitty postorius # pip install --upgrade django-mailman3 mailmanclient mailman-hyperkitty You may need to update flufl.lock as well: # pip install --upgrade flufl.lock # bin/mailman-post-update # deactivate # exit (this should take you back to root user) # systemctl restart mailman # systemctl restart qcluster # systemct restart gunicorn -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

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

2 years, 9 months

Re: Held messages page not rendering the message

by Odhiambo Washington

On Sun, Mar 19, 2023 at 1:12 PM <mike-mailman(a)earth.li> wrote: > Thanks - may be on to something. > > The sources tab shows everything ok except for > /mailman3/static/postorius/js/script.js for which it says "Unable to fetch > script source" > However the network tab shows it successfully retrieving it. > > /var/lib/mailman3/web/static/postorius/js/script.js exists and contains > only comments > Is anything showing up in your webserver logs that is related to this? Just maybe. I have tested on my setup (although I use a virtualenv setup) and I see as a click on a held message corresponds to a log entry in my webserver log. I do get a pop-up like this: ``` https://imgur.com/a/esxmDsK ``` And that is the same across all my browsers. My Desktop is running Winblows11 though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

Re: Can't deliver mails in queue

by Nathanael Schneider

>> I then created a completely new List which did not exists in mm2.1, >> subscribed two addresses and sent myself an EMail. That one worked as >> intended. I then deleted the whole broken list and created it cleanly, >> added the same two people, sent an email and nothing. > > This seems strange. If I understand, you are essentially saying the two > lists are the same. I.e., you created a completely new List which did > not exists in mm2.1, and that one worked. Then you deleted the whole > broken list and created it cleanly ... What was different between this > cleanly created list and the completely new List? They were in fact not identical, as I changed some stuff in hopes to get it up and running again quickly. I now changed the completely new List to be identical with the cleanly created one (as far as postorius shows me) and it still works just fine. >> May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> >> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net >> May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> >> May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > > The fact that these are the only messages says that the attempt to send > that message via smtp raised no exception as exceptions would have been > logged, yet you say there's nothing in the maillog so there was no > connect to Postfix. What are your settings for smtp_host: and > smtp_port: in the [mta] section of mailman.cfg? I set nothing explicitly as the default options fit my needs, so localhost:25 it is to my knowledge. Postfix itself was configured by Plesk and the config for mailman3 was manually added as prescribed. A manual telnet on localhost 25 gives me the expected 220 message from postfix. >> I have no clue what to do with this. I then turned the debug module >> loglevel to debug. Also nothing useful. Just an endless list of >> >> [...] >> May 19 18:17:29 2021 (7209) [outgoing] <function deliver at >> 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> >> May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop >> May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 >> May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: >> 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd >> May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic >> May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction >> May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit >> May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 >> May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop >> May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: >> 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e >> May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile >> May 19 18:17:29 2021 (7209) [outgoing] <function deliver at >> 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> >> [...] >> >> Which also tells me nothing I can understand. > It says the message in queue entry > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled > but gets requeued as > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which > presumably is handled and requeued again ... Ok. Then I just need to figure out why it gets requeued. That also explains why the out-queue folder keeps creating a single message with different filenames over and over. But the logs keep silent about the reason.. >> I have no clue what's >> going wrong. (I've turned on debugging both on the original member list >> and the reduced member list. Both hang on the first delivery they do). >> If I restart mailman, the message gets correctly shunted as it is >> interrupted mid-delivery. My maillogs don't register any activity beside >> the listpost. Any ideas what I need to do to figure out what's not >> working here or where the culprit could be? Not sure if it is related to >> the mailinglist being in mailman2.1 before. > > I have no real understanding of why this isn't working. I don't think > it's likely that it has to do with the mailing list being imported from > MM 2.1, but I suppose it could be. > > How did you create and import the list? When you say you deleted the > whole broken list and created it cleanly, what did you actually do? My steps where basically what the migration guide told me to do. First, I created the new list in postorius, I then copied the config.pck over to the mailman directory, chowned it to mailman and imported it in the venv using mailman import21 list(a)example.com config.pck Does import21 expect anything besides the config.pck? Maybe it couldn't find the required files and botched something? I recreated the list by deleting it in postorius and creating it anew. It could be that there is some configuration that does not get cleaned properly? If it helps, I've also made a document containing all the specific steps I used for my server as I've tested the setup process first before rolling it out (not the migration though) on a different server to get it done without a hitch. -- Nathanael Schneider

5 years, 1 month

including a template failed

by Wolfgang Bock

Hi, I created a new mailinglist and got during the test-process the following errormessage in my mailman.log after: ... Sep 19 22:55:08 2020 (1433) ACCEPT: <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> Errors: Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max retries exceeded with url: /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer (Caused by NewConnectionError('<urllib3.connec tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to establish a new connection: [Errno -2] Name or service not known')) ... domain02.de isn't involved in mailman3 either as a user domain nor as a list-domain. After deleting the template mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member: regular:footer the mail to the list is processed without problems: Sep 19 22:56:22 2020 (1436) <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> smtp to mylist(a)list.domain-03.de for 1 recips, completed in 0.21389174461364746 seconds Sep 19 22:56:22 2020 (1436) <000001d68ec7$2553e6e0$6ffbb4a0$(a)wbock.de> post to mylist(a)list.domain-03.de from user(a)domain-01.de, 1331 bytes Please help to solve this problem? Thanks and regards Wolfgang

5 years, 9 months

Bulk changes to delivery mode and moderation action

by David Newman

I fat-fingered a command in the Postorius UI and accidentally unsubcribed all members of a list. Oops. Have added them back using Mass operations/Mass subscribe but this raised three questions: 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? 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. Similar question: How to set subscriber options for all members in one go? 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/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. Thanks. dn, chastened

4 years, 5 months

Re: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- 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

Re: Removing the footer from mailing list messages

by Mark Sapiro

On 12/7/25 14:00, MegaBrutal via Mailman-users wrote: > > What I already tried: define a custom template for > list:member:regular:footer. The result was that the mailing list stopped > operating altogether, no messages passed through until I deleted this > template. After I deleted it, all delayed e-mails were forwarded at once. How did you create the footer? If you created a file at Mailman's var/templates/whatever/list:member:regular:footer.txt, it probably was not readable by the Mailman user. If you created it via Postorius there is probably and issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. > What would be the right way to remove the footer? For all lists sudo -u mailman cp /dev/null var/templates/site/en/list:member:regular:footer.txt For a single list sudo -u mailman cp /dev/null var/templates/lists/LIST-ID/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

6 months, 2 weeks

Re: Issues with @gmail.com addresses

by Allan Hansen

Once this gets handled, Mohsen, Google has another issue with list servers: If a subscriber who uses GMail posts a message to a list, then that subscriber will not get his/her own message from the server - Google eats it. All other subscribers will get it, but not the author. My subscribers run into this all the time and are up in arms over it. I tell them to complain to Google. Yours, Allan On 9/5/23, 13:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: 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 <mailto:xxxx@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 <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/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/WZY5IC3OVHVBHIGDT4TE3EWSSGMF6CYI/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 9 months

Mailman-users search results for query "Postorius"