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

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/9/24 3:39 PM, Mark Sapiro wrote: > See this post and maybe more of that thread which may help. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Thanks Mike, I've been looking into this, and I don't think it's that. What I did find is that our mbox from the mailman2 list is actually a amalgamation of mailman2, and majordomo archives. The mbox is not in order, but the start of the mbox starts in 2007 (coinciding with the last displayed month). Later on in the mbox file, the archives going back to 1992 from majordomo are present. There is no errors in the check_hk_import for this, and the messages are present in the index when I search for them and there are no errors during import. mailman 2.1 archives works just fine with this mbox file. Here's a link to the server in question, it's just a text box as we work through this. There's about 14k people on this list, so we want to get it right before cut over. https://nanog-mm3.keekles.org/archives/list/mm2-mm3@nanog-mm3.keekles.org/ Any ideas? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

10 months

[MM3-users] Re: Username being set to givenname for socialaccount login

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210922 20:46]: > On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > >I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > > >We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > >ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” > > > >Any direction would be welcome. > > This is an issue for Django allauth > <https://django-allauth.readthedocs.io/en/latest/index.html>. > Mailman has no control over this. The username is part of Django's > login and is not used by Mailman at all. Does that mean, not having an user name would work for mailman? I always thought having an user name was required Regards, Andi

3 years, 8 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

8 years, 5 months

[MM3-users] Re: Time Zone Issue in Postorius

by Stephen J. Turnbull

Henrik Rasmussen writes: > > Fra: Mark Sapiro <mark(a)msapiro.net> > > It should be TIME_ZONE = 'UTC' > > > > Times passed from Mailman core are naive times, I.e. they don't have > > time zone info, but they are in UTC. Mark is saying that Mailman core converts to UTC. All times that come out of Mailman core in the relevant API are UTC. > As stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-django > seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), > to make sure, am I right to understand it as for Mailman, Danish time > should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? No, USE_TZ=True means "hey Django, you need to add a time zone to this datetime." And you use TIME_ZONE=UTC (exactly), because this variable is *not* the local time zone, it's the time zone that Postorius tells Django to add to datetime objects that don't carry their timezone with them. There is a setting somewhere else that tells Django what time zone should be used for I/O. Steve

3 years, 3 months

[MM3-users] Custom Archiver

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/1/23 16:33, Peter Knowles wrote: > > That all being said, on a slight segway... Aside from using the > > REST API, is it practical or possible to manipulate the database > > directly? That is, in doing so would it just work or are there > > extra moving parts when an API request is issued? > > It probably is possible, but I would definitely discourage it. The > REST API should provide everything you need without your having to > reimplement everything it does. I think it would probably be a really heavy lift, because Mailman internally uses an object-relational manager, SQAlchemy. We occasionally change the schema, and SQAalchemy will automatically upgrade the database schema. You would have to handle that by hand in your code. I would recommend you get the sources for mailmanclient (https://gitlab.com/mailman/mailmanclient, iirc). They're quite repetitive, you wouldn't want to literally port them, but once you're familiar with the scaffolding and a couple of the commands you should be able to write a lot of PHP really fast to cover the REST endpioints you most need in a library with an API to your taste. Steve

2 years, 1 month

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

by Shashikanth Komandoor

Can I go back to any previous version which is felt as working fine ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 11:43 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Mark Sapiro writes: > > > I think the issue is your mailmanclient is too old. The version of > > Postorius you are running requires mailmanclient >3.3.1 which is only > > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > > > What version of Postorius is this? It appears to be >1.3.3. If you > > install Postorius from unreleased code on GitLab, you have to install > > all of mailman, mailmanclient and django-mailman3 as well. > > Shouldn't Postorius's setup.py be checking for this? > > Steve > _______________________________________________ > 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 & Regards, Shashi Kanth.K 9052671936

4 years, 6 months

[MM3-users] Re: Mailman 3 Installation

by Mark Dadgar

On Jan 16, 2021, at 7:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: >> I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? > > You can use sqlite, but if you don't already have a mysql/mariadb > database on the server, we recommend postgresql for performance and > robustness. I personally have had issues with mysql and use postgresql > on one production server that uses mysql for other applications. I’ll word this a little more strongly: do not use sqlite for a production server. Do not "just start with sqlite to get it running and then I’ll migrate it to something else down the road.” There is currently no validated way to migrate a mailman3 instance from sqlite to something else, and by “no validated way” what I actually mean is “no one has managed to get this to work, me included.” Put in the extra effort to start with posgresql or mysql/mariadb up front. You’ll regret it if you don’t. Ask me how I know. 😁 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

3 years, 2 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Hi Mark, Mark Sapiro 於 2019/10/26 上午2:08 寫道: > The issue is the list welcome message is sent in the character set of > the new member's preferred language and if that is not set in the > subscription request, and it's not possible to do that in Postorius, it > defaults to the installation's preferred language. > > It should probably default to the list's preferred language. See > <https://gitlab.com/mailman/mailman/issues/608> > > You have two choices: > > You can set the installation's default language by putting > > [mailman] > default_language: zh_TW > > in your mailman.cfg, or you can leave the default language English and > set the character set for English to utf-8 by putting > > [language.en] > charset: utf-8 > > in your mailman.cfg. Thanks for your help. After trying I found that it only worked when I set the [language.en] charset to utf-8. If I didn't set this but only set default_language in [mailman] section to zh_TW it still sent ? in the welcome messages. I commented in the issue. Thanks, Franklin

5 years, 6 months

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Ruth Ivimey-Cook

On 03/06/2021 15:09, Mark Sapiro wrote: > On 6/3/21 1:06 AM, Kimmo L wrote: >> Thanks for the quick replay! >> If its not a big trouble, could you kindly give me some advice/guide >> how upgrade my Hyperkitty/Postorius/Django from python2 to python3. >> I would be very grateful. > > > It depends heavily on how Mailman was installed to begin with, but > essentially you just upgrade the various components to the latest > versions using pip. Some things you need to be aware of are at > https://docs.mailman3.org/en/latest/upgrade-3.2.html If you start with python libs installed using a package manager (apt, yum, etc) and later upgrade them using pip, make sure you lock the packages at their current version so they cannot be changed by package updates, or you'll eventually have the package manager do an unintended downgrade. It is usually best to start with a distinct installation from pip, into a python venv to avoid changing system libs. You can of course seed that install with the current setup first! Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 11 months

Search results for query "sapiro"