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

[MM3-users] Re: List archives Recent Posts problem

by Mark Dadgar

On Jun 23, 2020, at 3:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 9:01 AM, Mark Dadgar wrote: >> In the last day or so, hitting the Recent page in my list archives results in a spinner and an error message: >> >> Internal Server Error: /mailman3/hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:mailman3/hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> >> AttributeError at /hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> 'NoneType' object has no attribute 'subject' > > > Is this still an issue? > > If so, see the entire thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > for a possible solution. It’s still a problem. I restarted the whole machine and that did not fix it. I also tried to delete any row in the hyperkitty_thread table where starting_email_id was null and that did not return any deleted rows. mailman=> delete from hyperkitty_thread mailman-> where starting_email_id = null; DELETE 0 All of my member functions are still broken as well. :( - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 11 months

[MM3-users] Re: Problems with New MM3 Installation

by Jeff

Thanks Mark and Abhilash (who responded separately). I have worked out all the issues I was having and now the list is running smoothly. The trick for POSTORIUS_TEMPLATE_BASE_URL with uwsgi was "http://[hostname]/mailman3/ <http://[hostname]/mailman3/>“. I appreciate all the help I’ve received from this mailing list. > On May 11, 2021, at 11:43 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/11/21 7:46 PM, Jeff wrote: >> >> I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: >> >> 1) some emails that arrived before I got the archive working are still sitting in: >> >> /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new >> >> Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > >> 2) Some messages that arrived while I was having other problems with the setup have been stored in: >> >> /usr/local/mailman3/mm/var/queue/shunt >> >> What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > >> 3) Similar to above, some messages are in: >> >> /usr/local/mailman3/mm/var/queue/bad >> >> How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > >> 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. > > -- > 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

[MM3-users] Re: Templates

by Odhiambo Washington

On Tue, 17 Nov 2020 at 06:09, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/16/20 4:02 AM, Odhiambo Washington wrote: > > Hello good people, > > > > So today I decided that I should be looking at MM3 to see how far it can > > take me. > > I started from the templates and created one for a footer for non-digest > > messages. > > > How did you create this footer?. If you created it by creating a file in > Mailman's var/templates directiory, can Mailman read it? > > I went into Postorius and selected the list. It's the only one. Selected Templates -> New Template. root@gw:/opt/mailman/mm/var/templates/site/en # ls -al /opt/mailman/mm/var/templates/site total 24 drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 . drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 .. drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:51 en I cannot find anything specific to the particular list in the path. Mailman runs as mailman3, who owns all the files. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 6 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date... All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish). This is not a fight, we want to help, but do not know how. Thanks! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 3 months

[MM3-users] Re: Domain admin

by Johannes Winter

Am Wed, 25 Apr 2018 08:39:58 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 04/24/2018 11:57 PM, Johannes Winter wrote: > > > > We would like to give our users the priviledge to create lists per > > domain. I Haven't found any options for that in the web interface. > > > > Is this possible somehow with mailman3? > > > It is not currently possible. From the point of view of Mailman Core, > anyone who can run the 'mailman' command or access the REST API can > create domains and lists. > > Postorius could support this in some way and could maintain it's own > 'authorized users' data, but it would be better to also add some > concept of domain admin to core. > > These would be significant changes. > A possible workaround could be to create several webhosts to control access rights to the mailing lists. At least I understand the option to create new "web-hosts" in "add domain" in this way. But I haven't found any further information for setting up multiple web-hosts. Is there any yet?

8 years, 1 month

[MM3-users] Re: Caching problem with templates

by Mark

> On 6/28/25 21:50, Mark wrote: > > > > Yes, I thought so too. I also tried 0d -- which wrote the expiry > > date > > the same as the created date (to the second). > > > > # /etc/mailman3/mailman.cfg > > [mailman] > > cache_life: 0d > > > > But, just as with writing in a past date, it didn't solve the > > problem. > > I also spun up a brand new server to thrash it out there, but no > > joy > > there either. > > On Sat, 2025-06-28 at 22:55 -0700, Mark Sapiro wrote: > This is a different issue. See > https://gitlab.com/mailman/mailman/-/issues/1231 > > The template is not removed from the cache until the next run of the > task runner which defaults to running every hour. > Dang! If you know, you know. Thank you for that, and the patch information. I'll leave my hack in place for now (it works) until the next release. My brain is fried from the last couple of days getting to grips with this. Best, Mark

10 months, 4 weeks

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Joel Lord

On 11/23/20 11:15 PM, Mark Sapiro wrote: >> # If the following is set to a non-empty string, that string is the name of a >> # header that will be added to personalized and VERPed deliveries with value >> # equal to the base64 encoding of the recipient's email address. This is >> # intended to enable identification of the recipient otherwise redacted from >> # "spam report" feedback loop messages. For example, if >> # RCPT_BASE64_HEADER_NAME = 'X-Mailman-R-Data' >> # a header like >> # X-Mailman-R-Data: dXNlckBleGFtcGxlLmNvbQo= >> # will be added to messages sent to user@@example.com. >> RCPT_BASE64_HEADER_NAME = '' >> >> >> This hasn't been implemented for Mailman 3 but could be if there's demand. I hadn't spotted that in Mailman 2.1, I will go looking for it there. My 2.1 server has not moved to 3 yet for several reasons, but it's getting close. This feature would get me just a bit closer. -- Joel Lord

5 years, 6 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Sat, Oct 2, 2021 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/2/21 4:26 AM, Odhiambo Washington wrote: > > On Thu, Sep 30, 2021 at 4:09 PM Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > >> > >> Yes, please update it to have SITE_ID = 2 to correspond to the site you > >> want and restart. > > > > > > I did this, but there is still a problem: The hyperkitty URL still shows > > example.com. > > Maybe I need to re-import the database to clear this? > > > The SITE_ID setting affects the domain displayed at the top left of > HyperKitty pages. Is this the correct domain? > No. Mine is showing example.com > > What hyperkitty URL are you talking about? > My url (nothing to hide anyway) is https://lists.fem-international.org/mailman3/hyperkitty/list/members@lists.… . Screenshotted below [image: msapiro.PNG] -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 7 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Stephen J. Turnbull

Mark Sapiro writes: > Presumably that's the 'Recipient address rejected: User unknown in > virtual alias table' message, but I see no virtual_alias_domains in > your posted main.cf. I'm pretty sure that what's going on here is that the message is coming in from outside, Postfix runs down the various relays (including local delivery) available, none matches, the last in line is virtual aliases, and that table is empty so the user is unknown. That's the only way I can see the sender_canonical_maps variable affecting *recipient*-based decisions, by making it look like the sender is local, and so enabling delivery to non-local addresses. Why a Mailman list appears to be non-local is a question I am not sure. My guess is myhostname = localhost because Postfix doc says mydomain "is derived from $myhostname by stripping off the first part (unless the result would be a top-level domain)," so literally "localhost" is the only deliverable domain left, and some-list(a)the.actual.dom doesn't work. Except that the.actual.dom should be in postfix_domains.db, so ... ???? Steve

2 years, 5 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 11 months

Search results for query "sapiro"