Search results for "Postorius" - Mailman-users

Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Sat, 2021-12-25 at 10:19 -0800, Mark Sapiro wrote: > On 12/25/21 7:13 AM, William Oliver wrote: > > > > Just out of curiosity, if I could not have guessed a valid ID > > number > > and did not have the admin interface, how could I have figured out > > what > > site IDs were available? > > > If Postorius is working, recent versions show the SITE_ID in the > domains > view. I.e. after you added your domain you could have noted the > SITE_ID > and made the change in settings before deleting the example.com > domain. > > In any case, the django_site table in Mailman's database has the > information. > Thanks. Yep, I peeked at the database and there it was. That would probably been more efficient than randomly choosing numbers... billo

4 years, 1 month

Re: New messages not being archived

by Matt Wilbur EFS

I apologize if this is off-track, but when I originally was setting up lists in mm3 I made the mistake of using the Postorius "Create List" button. I found that when I did this, I saw no archives and I don't recall if mails flowed OK. The setup was incomplete for me. I had to delete, and then create my lists using the mailman command and then everything just magically worked. matt On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number > _______________________________________________ > 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, 6 months

Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

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. > 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. -- 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

Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

On 10/21/20 8:53 AM, Brian Carpenter wrote: > If you set the unsubscription policy to confirm then moderate for a list > and someone unsubscribes, they receive a confirmation request. That is > good. They respond to it. That is also working fine. However the list > owner/moderator than gets a request to approve the unsubscribe request > and well, unless I am missing something, I don't see an interface to > handles such requests via Postorius. This is <https://gitlab.com/mailman/postorius/-/issues/332>. > How does one handle an unsubscribe request that requires moderator > approval? I'm not sure at this point, I can look further later, but if the notice to the admin has a token, it might work to send a `confirm <token>` command to the list-request address. Otherwise, don't moderate unsubscription requests. -- 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

Re: Default setting for Delivery status

by Mark Dale

>> Where and how do I set the default setting of "Delivery status" to be "Enabled". > > It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… >> At the moment, a new subscriber is neither "Enabled" or "Disabled". > > That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. > > Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. > > New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. > Ahhhh. Thanks very much Mark. I did some experimenting to get my head around what you've explained and I can see how it works now.

3 years, 3 months

Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). In the Postorius held messages view, click on the message's subject to open a dialog showing the messages content and a dropdown to set the moderation for this user and a box to enter a reject reason if you are going to reject the message. If you want to accept further messages from this yser, it is best to set moderation to Default processing rather than Accept immediately as the latter bypasses other checks that could result in the message being held. Note that even though the dropdown says Set member moderation, it works for non-members too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Re: repeated headers in mails from mailinglists

by Mark Sapiro

On 7/12/24 11:30 PM, Tobias Diekershoff wrote: > Dear all, > > we have recently migrated from Mailman2 to Mailman3 and now discovered > that all mails going through Mailman3 have the headers Archived-At and > List-Archive repeated identically in the mail header ~100 times each. This should definitely not happen unless mailman/handlers/rfc_2369.py is broken. > We are running Mailman3 on Debian Bookworm from the Debian repositories > (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and > hyperkitty (1.2.1-1). This may be a Debian issue. See https://wiki.list.org/x/12812344 > Can somebody of you help me to get rid of the repeated header? You could in Postorius set Alter Messages -> Include RFC2369 headers to No, but this will not include any of the List-* or Archived-At headers at all which is not what you want. -- 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

Re: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 9/30/24 03:00, Chupin Maxime via Mailman-users wrote: > Hi, > I upgraded my debian version, Issues with the Debian Mailman packages should be reported to Debian. Please see https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… > and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: > ``` > CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). > To fix them run 'python manage.py makemigrations --merge' > ``` > So I tried `mailman-web makemigrations --merge` that ended with > ``` > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' > ``` Did you run this as the Mailman user (`list` in the Debian packages)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Mailman-users search results for query "Postorius"