Search results for "Postorius" - Mailman-users

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

3 years, 9 months

Re: how to become member of mailman-users list

by Shashikanth Komandoor

Thank you Steve for your response. On Tue, Aug 31, 2021 at 6:46 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Shashikanth Komandoor writes: > > > One of my colleagues is trying to become a member of the > > mailman-users list but she is not able to become so even after sending > > multiple emails to the list. > > Your colleague needs to either sign up via Postorius at > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > or send mail to mailman-users-subscribe(a)mailman3.org to subscribe. > She then needs to respond to the mail that the system sends her by > visiting the URL in that mail. > > Without a subscription, mail to the list will be discarded silently, I > believe. > > Once her subscription is active, her first post will be held for > moderation. After that, help posts will be unmoderated. > > Steve > -- Thanks & Regards, Shashi Kanth.K 9052671936

3 years, 11 months

Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > Does anyone know if there is an equivalent tool that works with Mailman 3? I don't know of one, but perhaps someone does. It probably wouldn't be hard to write a bare-bones workalike if the admin has shell access to the mailman host. UIn theory, shell access could be restricted to running the tool by using a 'command' option in the sshd authorized_keys file for the user's key. But I'm not competent to judge how secure that could be in principle, and of course if the tool is buggy in certain ways, all bets are off.) I can't estimate how hard it would be to write one without shell access, as I'm not sure how amenable the Postorius web UI is to scripting. Steve

3 years, 9 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

4 years, 3 months

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>

1 year, 11 months

Re: "Private archives" aren't private

by Simon HANNA

On July 28, 2017 10:55:43 AM GMT+02:00, cyp(a)trojina.si wrote: >Hi, > >I'm having the same problem: changes to the "Archive policy" settings >in postorius are not reflected in hyperkitty. Trying to use >mailman_sync to fix this gave me the same BaseCommand traceback as >above, but "mlist_object.update_from_mailman()" works. So luckily we >have a workaround, thanks. But I suspect that there's some >misconfiguration or permission problem on our server that's blocking >the automatic synchronisation from taking place. Any advice to >resolving this would be appreciated. :) It's fixed in master, and just needs a release. https://gitlab.com/mailman/hyperkitty/issues/135 @abompard what's the policy on bug fix releases? If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature" cheers Simon -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years

Re: Disable archives per list

by Mark Sapiro

On 2/25/21 1:57 AM, Bernd Wurst wrote: > > Can I as the server admin disable archiving (or set other list options) > in a way that the list admin can not change it via postorious? As the server admin, you can enable/disable archivers sitewide. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> et seq. Note that the prototype archiver, if enabled, stores messages in the file system in maildir format. Normally a list admin can select which of the enabled archivers is active for that list via Postorius. To prevent this, you would have to modify Postorius. It would be easy enough to just remove settings from the relevant templates. > Can I have custom archiver settings per list or per domain > (customer-specific hyperkitty)? I'm not sure what you mean by "custom archiver settings", but other than enable/disable and public/private, probably not. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Regards, Enrique On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings Archiving and they are: Public archives Private archives Do not archive this list This is interface of Mailman to set the archives. In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists Mailing List object(x) > Archive policy: never private public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. Enrique On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core. I have made a change which should fix this problem and the process would become synchronous. You can run `python manage.py runjobs --daily` command to force sync that information. https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… Am I misunderstanding what a private archive is? Not really, your expectation is right. Is something wrong with my setup (which is hosted)? Thank you. _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 11 months

Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> The real question is if a user has a subscription waiting confirmation >>> and the policy is changed to moderate, is a second request rejected >>> because of the request waiting confirmation. If so, I think this is a >>> bug which should be fixed. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

2 years, 2 months

Mailman-users search results for query "Postorius"