Search results for "Postorius" - Mailman-users

Re: Manage Member(s) Mailman Settings / Display Names

by Jim Ward

I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. 2) The 'Search Members' function appears to be limited to the email address only and does not include display name These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, January 10, 2020 7:05 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Manage Member(s) Mailman Settings / Display Names On 1/10/20 4:55 PM, Jim Ward wrote: > Mailman2 allowed me to list my members and modify a number of their attributes (display_name, etc) > > Postorius is a beautiful interface BUT I am evidently not finding how to manage my members to the extent that I could in Mailman2 It's not like MM 2.1 where you have a membership list with columns of checkboxes, but if you pull down the Users menu and select Members or Non-Members, each user has an options link that allows you to set/change options. -- 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://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 5 months

Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Email to list owner on list creation only sent when using mailman create --notify command

by Perry Kollmorgen

Ok, thanks for the information. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, 10 June 2024 2:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

1 year

Re: Verification emails 'helo' rejected

by Greg Newby

Thanks for this, Odhiambo. Unfortunately it doesn't address my situation. See below: On Tue, Oct 15, 2024 at 3:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Oct 14, 2024 at 10:43 PM Greg Newby via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Hi friends. >> >> I'm now getting a 500 server error upon signing up a new username on the >> web-based front end. The username is created in the back end, but the >> verification email does not get sent. >> >> This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, PostgreSQL, >> Postfix >> >> Here are the corresponding logfile entries from mailmanweb.log: >> smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 >> <mail>: >> Helo command rejected: need fully-qualified hostname')} >> >> and from mail.log: >> Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from >> localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need >> fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost >> > >> proto=ESMTP helo=<mail> >> > ^^^^ Note the problem isn't the "From:" address. That is being correctly configured from mailman-web.py and settings.py via the variables below. The problem is it's going "To:" root@localhost. I don't know why this is happening - shouldn't it be going to redacted(a)gmail.com? Also, based on settings below shouldn't this be From: postorius(a)lists.domain.tld not From: root(a)lists.domain.tld? More: > >> lists.domain.tld is the domain for Mailman3. I don't know why it's trying >> to send email from root@. >> >> I've seen places where 'localhost' appears in the Mailman settings >> (settings.py, mailman.cfg, mailman-web.py), and tried changing them to the >> host's FQDN and restarting mailman3 and mailman3-web, but the problem >> persists. >> > > Find and fix these values to what they should be as explained. > > # The sender of emails from Django such as address confirmation requests. > # Set this to a valid email address. > DEFAULT_FROM_EMAIL = 'johndoe(a)domain.name' > > # The sender of error messages from Django. Set this to a valid email > # address. > SERVER_EMAIL = 'johndoe(a)domain.name' > > I use listmaster(a)lists.domain.name in my servers. > In the default files via the venv installation, these were already set properly: EMAILNAME='lists.domain.tld' <-- I set this myself These were default in settings.py and mailman-web.py: DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) SERVER_EMAIL = 'root@{}'.format(EMAILNAME) I set them explicitly to postorius(a)lists.domain.tld and root(a)lists.domain.tld and restarted mailman and mailman web, and this did not change the problem with the server error and mail log entries above. > I am not sure what files on your server contains them in your server. > > And while at it, also fix the site_owner: email in mailman.cfg. > That was already set to my email address, and I do correctly get site emails, such as cron output. Further guidance would be appreciated. ~ Greg

8 months

Re: Ann: Mailman Core 3.3.5 is out

by Mark Sapiro

On 9/29/21 9:59 AM, Brett Delmage via Mailman-users wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > >> Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I >> would have >> to bypass the Debian installer. Or will there be Debian packages >> available? >> Same question for Postorius 1.3.6 Since Mailman 3.3.4 has been out for over six months and the latest Mailman 3 in even Debian sid is still 3.3.3, I would expect a long wait before these latest releases are available in Debian/Ubuntu. > I am excited to see 3.3.5 with its many updates available. Thanks to all > the contributors. > > I would like to know this too, as I was just about to install parallel > to the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of > 3.3.5 with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? I would suggest abandoning the Debian packages and installing as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. You should be able to keep all your existing configuration files and the database. You could even keep `list` as the Mailman user if desired. Once you have done this, upgrading via pip from PyPI or even from GitLab is very simple. -- 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: Dump/restore users (with passwords) via API

by Dmitry Makovey

On 09/17/2018 12:39 PM, Abhilash Raj wrote: > On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: >> We are trying to dump/restore users using API calls and it seems >> that API allows us to dump password hashes (a good thing), but then >> API does not allow to insert users back using saved password hashes >> - only cleartext passwords. > > I'd say that is intentional. You don't want people to be setting up > hashes as passwords. > >> Aside from create_user is there any other way to create >> users/change their password? > > Not that I know of, not using the API atleast. You could potentially > use the low level API that inserts records in the database or use SQL > to dump and restore that data. > > What do you use the Core's user/password for? Currently, the user > passwords are basically just a carry-over from Mailman2 and there > shouldn't be any use for it. I have been considering removing that > completely have Postorius do all the authentication/authorization. > > Email based authentication should rely on more reliable identities > like email signatures, intead of having to send cleartext passwords > over email. I think I am asking about the username/password auth for postorious and how to dump/restore it. At present we have no tools for dump/restoring users so that's what we're trying to build. -- Sr System and DevOps Engineer SoM IRT

6 years, 9 months

Re: Clean-up of non-members

by Odhiambo Washington

On Tue, Dec 24, 2024 at 8:39 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 08:13, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> I saw that too. Reported > >> https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > >> https://gitlab.com/mailman/mailman/-/merge_requests/1297 > > > > > > It isn't clear to me what I should do to mitigate the error. > > > Apply this patch: > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -103,7 +103,12 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - dn = address.display_name or member.user.display_name > + # Non-members may have empty address.display_name and > member.user can > + # be None resulting in AttributeError on member.user.display_name. > + try: > + dn = address.display_name or member.user.display_name > + except AttributeError: > + dn = '' > if email_only or not dn: > print(address.original_email, file=outfp) > else: > ``` > Thank you. Now only if you can help me reconcile the fact that Postorius tells me that I have ``` List Nonmembers (872) ``` ..while the CLI command gives me only 13 addresses. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

5 months, 3 weeks

Re: Clean-up of non-members

by Odhiambo Washington

On Wed, Dec 25, 2024 at 8:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 23:35, Odhiambo Washington via Mailman-users wrote: > > > > Now only if you can help me reconcile the fact that Postorius tells me > that > > I have > > ``` > > List Nonmembers (872) > > > > ``` > > > > ..while the CLI command gives me only 13 addresses. > > > How are you invoking the `mailman nonmembers` command? I suspect it is > not using the proper mailman.cfg. Does `mailman info` show the correct > mailman.cfg. > ``` (venv) mailman@eu:~$ whoami mailman (venv) mailman@eu:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman:XXXXXXXXX@localhost /mailmansuite?charset=utf8mb4&use_unicode=1 devmode: DISABLED REST root url: https://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC Agnes <agnesa(a)REDACTED.com> Angela M <angelam(a)REDACTED.org> <beatiemaina!!(a)REDACTED.com> <psgimode(a)REDACTED.ke> <jwothaxxx(a)\REDACTED.ke> <lgichdhdh(a)REDACTED.ke> <mrussher(a)REDACTED.org> <mutwiXXj3(a)REDACTED.com> <news@REDACTED> Nesema <xxxxxx(a)kictanet.or.ke> Robert M <xxxxxxo(a)yahoo.com> <telasalma17@ REDACTED > <wambdddddd(a)REDACTED.ke> (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC | wc -l 13 (venv) mailman@eu:~$ ``` It uses the correct config file. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

5 months, 3 weeks

Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 7:03 PM, Paul Arenson wrote: > > MAILMAN 2 > What I got from the Mailman 2 Wiki is "How to restrict the list so only authorized persons can post (moderation). If there is an option like that in Mailman 3 I want that. There is, but you can't do it the best way. See below. > SUMMARY > I want to be able to reply personally to the user if necessary without his or her message going to the list. So something like moderation. > > So let me take a guess: > > Default action to take when a non-member posts to the list AND > Default action to take when a member posts to the list > > should be set to HOLD FOR MODERATION? That will work and is probably what you want anyway. Your own posts will also be held, but you can just accept them. Alternatively, you could set your own Moderation setting to Accept or Default Processing so your posts won't be held, but don't do that as it allows anyone to post by spoofing your address in From:, Sender: or Reply-To: or the envelope sender. The best way to post without the post being held is pre-approval with an Approved: <password> header, where <password> is the list's moderator_password, but you can't set that in postorius so it won't work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: Assistance with mailman3

by Andy Yen

Hi Abhilash Thanks for the response. Tried your suggestion I ran the command "pip install -U falcon==1.4.1" and started mailman but still getting same error. ==> var/logs/mailman.log <== Mar 15 10:10:43 2019 (3004) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 248, in __call__ responder, params, resource, req.uri_template = self._get_responder(req) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 664, in _get_responder route = self._router_search(path, req=req) TypeError: find() got an unexpected keyword argument 'req' Mar 15 10:10:43 2019 (3004) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 Kind regards Andy On Wed, Mar 13, 2019 at 12:51 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > > Hi all > > > > I'm pretty new to mailman but been trying to install mailman 3 and been > > running into issues, following the documentation at > > http://docs.mailman3.org/en/latest/prodsetup.html > > installed Python 3.6, nginx, ruby-sass > > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > > mailman > > > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > > (otherwise it wouldn't run) > > mailman core starts but when I hit the api url I get this in the logs > > > > File > > > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", > line 50, in wrapper > > rtn = function(*args, **kws) > > File > > > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", > line 218, in __call__ > > return super().__call__(environ, start_response) > > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > > 248, in __call__ > > responder, params, resource, req.uri_template = > > self._get_responder(req) > > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > > 664, in _get_responder > > route = self._router_search(path, req=req) > > TypeError: find() got an unexpected keyword argument 'req' > > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > > > and on frontend "A server error occurred. Please contact the > administrator." > > Inside your virtualenv, please run: > > $ pip install -U falcon==1.4.1 > > This should fix the above error. > > > > > that leads to my gnu not working and throwing keyerrors for postorius. > > > > I'm using a clean install of ubuntu 18.04 but have also tried to > > install on centos 7 with no success. > > > > Are there any missing dependencies or steps that I've missed any > > assistance would be appreciated. > > > > Andy > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) >

6 years, 3 months

Mailman-users search results for query "Postorius"