Search results for "Postorius" - Mailman-users

Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 7/8/21 20:03, Mark Sapiro wrote: > This is the way MM 3 works. The only reason *_these_nonmembers exists > in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp > addresses the address is a nonmember with the appropriate moderation > action. > > I actually find this convenient. When a nonmember posts spam to a list > and that spam is held, I discard the spam in Postorius and at the same > time set the nonmember's moderation action to discard so I never see > any more from that address. Also, when someone who I recognize as a > list member posts from an alternate nonmember address, I can accept > that post and set the nonmember address moderation action to default > processing. > I find it very convenient too, but it concerns me that spammers, really "profesional" spammers and senders of phising mail change the forged address and sender domain too rapidly to track them. As of it, the non-member database is growing more and more. It could be a "monster" in two or three years... Not a problem now. And I know now how to delete them in one go :) --

4 years, 11 months

Re: Migration of the e-mail templates

by Mark Sapiro

On 3/6/25 2:24 PM, Markus Grandpré wrote: > > Thank you for your prompt reply. Based on a customer request, it seems > that custom templates need to be copied manually. Could you kindly > indicate which files and locations should be considered when > transferring them from the source to the target system? In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>. In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/. However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documentation of the MM 3 templating system. -- 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

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Torge Riedel

Am 16.01.20 um 21:43 schrieb Mark Sapiro: > On 1/16/20 10:51 AM, Torge Riedel wrote: >> Such SPAM mails are currently hold for moderation with reason "not from >> a list member". Is there no check for the "X-Spam: Yes" header or is >> this check done later? > > If you set a Header Filter (in Postorius the Header filters tab) those > checks are done before non-member moderation. > > This won't work for posts from members because the header checks are > done between member moderation checks and non-member moderation checks, > but if you create a Header Filter for header 'x-spam' and pattern 'yes' > with action hold, a message from a non-member which has an X-Spam: Yes > header should be held for that reason. > > Hi Mark, thank you for your answer. Just to understand that right: In case a posting with an "X-Spam: Yes" header comes from a member, it will not be held? It will be directly forwarded to the list? If yes, is there any chance to change or extend this? Best regards Torge

6 years, 6 months

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, 6 months

List Migration from MM2.1 -> MM3

by Odhiambo Washington

So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04. I have created a list in postorius - it has the same name as my old list in MM2. [image: MM3.png] Now, following - https://docs.mailman3.org/en/latest/migration.html - I change user to mailman so as to run the migration. mailman@lists:~$ pwd /opt/mailman mailman@lists:~$ id uid=1003(mailman) gid=1002(mailman) groups=1002(mailman),4(adm),38(list) mailman@lists:~$ */opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke <skunkworks(a)lists.my.co.ke> /var/list/lists/skunkworks/config.pck *# running without specifying the absolute path is not working! Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help. Error: No such list: skunkworks(a)lists.my.co.ke mailman@lists:~$ ls -al /var/list/lists/skunkworks/config.pck -rw-rw---- 1 root list 63765 Aug 14 11:10 /var/list/lists/skunkworks/config.pck mailman@lists:~$ exim -bt skunkworks(a)lists.my.co.ke skunkworks(a)lists.my.co.ke router = mailman3_router, transport = mailman3_transport mailman@lists:~$ What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: MM3.png Replaced multipart/alternative part with first alternative.

3 years, 11 months

Re: Welcome message template errors

by Mark

On 2024-04-23 11:33, Mark Sapiro wrote: > On 4/22/24 17:06, Mark wrote: >> >> There was no line POSTORIUS_TEMPLATE_BASE_URL in >> /etc/mailman3/settings.py > So presumably you were getting the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > > from mailman-web/settings/mailman.py because of > from mailman_web.settings.mailman import * > in your settings.py. Yes. # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * ... > >> Then, as site-owner, creating a new custom Welcome template (again via >> the WebUI) I can see it correctly added to the database in >> mailman.template.uri >> >> - >> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… That URI should have been; https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… If I go to the above URL, the text of the list's Custom welcome message displays on an otherwise empty webpage. > > > And what happens if you go to that URL in a web browser? Also what do > you get when going to https://lists.mydomain.com/mailman3? I get the Postorius page "Mailing Lists" that displays the table of lists.

2 years, 3 months

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, 5 months

Re: Welcome Message

by brian＠emwd.com

Abhilash Raj wrote: > If the URL for template is wrong, or Postorius is down for whatever reason, > the subscription will fail with the error that you saw before. Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That is not wrong. I am confident of that. It is back to "http://mailman-web:8000". I can successfully ping mailman-web:8000 from bash. > > I logged out of Postorious and subscribed using the > > subscribe form on > > the info page and the change to the welcome template showed up. So it > > looks like being logged in as admin while trying to subscribe someone > > was what was causing the problem. Is that a bug I discovered? > I suspect stopping-restarting and re-creating the template (idk, if you > really did that) might have something to do with it. I am not sure if this > is a bug unless you can reliably reproduce this. This error is absolutely reproducible. It even impacts other list admins who are trying to use a custom welcome message and subscribing a member while logged into Postorious. Everything else is working fine on this server and I followed your directions precisely when I set this server up. Please help. Thanks, Brian

7 years, 3 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/17/21 6:52 AM, Andreas Barth wrote: > Just from the top of my head, for example I want to differentiate > between private, member and public lists. So if a member logs in, they > see more lists than a non-member. This is currently not possible, not > too big a deal (all member lists are currently configured as private) > but of course would be nice. Also archiv access should be aligned with > these permissions. What I have done with Affinity is design everything around roles. Roles are List Owner, Moderator, and List Member. So when a registered user logs in they will see: All their lists that they have a role in and an icon assigned to each role that they play. Those lists are shown at top. Below their lists associations, public lists are shown. These they do not have a associations with for the logged in user. Here is an image in what I am referring to: https://www.mailmanhost.com/wp-content/uploads/2021/02/Screenshot_2021-02-1… Is the above image what you are thinking about? If it is then I do think that is possible with Postorius with some customization. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

1 year, 1 month

Mailman-users search results for query "Postorius"