Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/1/21 1:55 PM, Mark Sapiro wrote: > > When Python runs or imports from a .py file, it first looks for a > corresponding .pyc file and if that is as new or newer than the .py, it > uses the .pyc. If not, it uses the .py and byte-compiles it and if it > has permission, writes an updated .pyc > > Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc > in the same directory as the .py Its uses a __pycache__ directory in the > same directory as the .py and within that directory a file like in this > case settings_local.cpython-37.pyc (or whatever the python version is) > > In any case, I would remove the existing settings_local.pyc. That can't > hurt, but I'm curious what > > ls -lR /usr/share/mailman3-web/ > > shows. It just occurred to me what the issue is. It is almost certainly that there is a /usr/share/mailman3-web/settings_local.pyc that is as new or newer than the /usr/share/mailman3-web/settings_local.py symlink even though it is older than the target /etc/mailman3/mailman-web.py. Just remove that .pyc, and that should fix it. But I still wonder what python version this is since current Mailman requires python >= 3.6 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: mass invitation

by Mark Sapiro

On 6/20/19 9:07 AM, Abhilash Raj wrote: > > > On Thu, Jun 20, 2019, at 7:17 AM, mailman3(a)malevil.cc wrote: >> in postorius there is just the option to make a mass subscription, in >> mailman2 there was also the possibility to just invite users, so they >> need to click a link when they really want to join the list. Is this >> also available in mailman3/postorius? > > > No, not yet. There is an open issue that I can't dig out right now. The issue is <https://gitlab.com/mailman/mailman/issues/510> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/15/19 3:14 AM, Paul Arenson wrote: > >> Announce only style the list attribute > allow_list_posts is False and for the Discussion style, it's True. > > I guess I should leave it as TRUE if I am keeping as discussion list, but since I am moderating all comments, I am guessing it doesn't matter. Am I right? Yes, leave it True. It only matters for users replying by email with MUAs that provide a "reply-list" function, but for them, it is helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: installation

by Mark Sapiro

On 11/21/20 5:40 PM, Christian Stalberg via Mailman-users wrote: > What do I do now about this? > > (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# > python manage.py collectstatic > > You have requested to collect static files at the destination > location as specified in your settings: > > /opt/mailman/mailman-suite/mailman-suite_project/static > > This will overwrite existing files! > Are you sure you want to do this? > > Type 'yes' to continue, or 'no' to cancel: y > CommandError: Collecting static files cancelled. > (venv) root@localhost:/opt/mailman/mailman-suite/mailman-suite_project# y != yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 4/13/22 05:23, Paul Ssekamatte via Mailman-users wrote: > hi William, > please clarify what you mean by this step > 8. You need to manually set the local virtual host for mailman3 > Thank you He means that if you are going to use the alias domain feature discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… you need to actually set the value you choose for the alias_domain in the Postorius domains view or via REST or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Docker Installation of Mailman -- The Hyperkitty Chronicles

by Mark Sapiro

On 12/22/18 6:08 AM, brian(a)emwd.com wrote: > Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like: ... Check your list's Settings -> Archiving in Postorius and make sure policy is public or private and HyperKitty is active. Also, make sure the cron jobs are running. I'm not sure how this is set up in the Docker container, but see <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/21/19 1:28 AM, Manos Pitsidianakis wrote: > > I cannot discern anything in the qfiles. It'd take some effort to > deanonymise them for posting here. > > I've had new posts in the list and they get stuck as well. It's a stretch, but I suggest you examine the list membership and remove any invalid local addresses. Also, look in the mail server's logs to see if you can see anything about incoming connections being established and then dropped. -- 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

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/27/20 11:47 PM, Shashikanth Komandoor wrote: > I have run the below commands for sure: > > $ cd mailmanclient > $ python setup.py develop > > And as you have suggested, I navigate to mailmanclient directory and ran > the git log to provide you the version output. And I am fairly certain that the running Mailman/Postorius installation is not using those files. I can't tell you why this is the case, but if it weren't, you wouldn't be seeing this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: unwanted chunked delivery

by Mark Sapiro

On 1/7/22 2:12 PM, mm3-omf(a)sh.werbittewas.de wrote: > > I understand, why chunking may have benefits perhaps in most situations, > so it's set as default, but it would be great, to have the possibility > to disable this without patching code, which might get overwritten with > an update. You could submit an issue as a feature request at https://gitlab.com/mailman/mailman/-/issues, but I don't think we'd give it much priority. I think the trend these days is more towards enabling personalization and/or VERP which require one recipient per transaction. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/20/20 6:54 AM, Brian Carpenter wrote: > > On 10/19/20 11:32 PM, Mark Sapiro wrote: >> >> Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman >> 2.1 had no concept of user. All it knew was addresses subscribed to >> lists and an address subscribed to one list had no connection to the >> same address subscribed to another list or being an owner or moderator >> of a list. > > I think this should still be the case for non-registered list members. > List owners/moderators are different. They HAVE to be registered users > of Postorius/Affinity in order to manage/moderate a list. Here's a thought. For Affinity/Empathy at least, how about using Mailman core's user as the Affinity registered user. I.e., if someone's first interaction is to register with Affinity, have that registration create a core user to keep the Affinity registration data. This core user already accommodates a display_name and password and email address(es). If the person already is a core user when registering for Affinity, just update the core user as needed, probably only a password reset or just setting it if it is currently None. Then you don't have the issue of another, separate registration for Affinity. This would be more difficult for Postorius/Hyperkitty because those users are Django users, but that isn't an issue for Affinity. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Search results for query "sapiro"