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

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Kelly Close

Thanks for those clarifications Mark. -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 Direct: 303-867-7665 Kelly.Close(a)LREwater.com LREWATER.COM 1221 Auraria Parkway Denver, CO 80204 **CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you. On Tue, Jun 16, 2020, 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > > I resolved this myself with a search that turned up a 2018 post from > Mark that suggested typing "mailman aliases" to create the > hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where > they are on Ubuntu 18.04). I looked in that folder and sure enough it was > empty so I typed "sudo mailman aliases" which did indeed create the 4 > things that needed to be there: > > postfix_domans > > postfix_domains.db > > postfix_lmtp > > postfix_lmtp.db > > > > But, they were owned by root:root and everything else under that > /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the > ownership on the 4 files to list:list. > > Because that's how you ran it. Run > > sudo -u list mailman aliases. > > > > Seems to have worked! I was perplexed about why I had to do this though > because these were created automatically last time I did this, but I > figured that out too. > > > Current `mailman start` should create the aliases. > > -- > 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, 11 months

[MM3-users] Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/15/20 9:24 PM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> >>>> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >>>> >>>> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >> >>> This is not relevant. >> >> Does it need resetting back to http://localhost:8000? Not if it works. Most likely either one is OK, but localhost:8000 avoids a DNS lookup an proxying through the web server. Ok I have reset this value now. >>>> However emails are still coming through with the wrong URL. >> >>> I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. >> >> I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. >What's in `sites` and what's in `Mail domains` in the django admin UI https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/: <Mailman domain lists.hodgsonfamily.org> https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/1/change/ Site: lists.hodgsonfamily.org Mail domain: lists.hodgsonfamily.org https://lists.hodgsonfamily.org/admin/sites/site/1/change/ Domain name and display name: lists.hodgsonfamily.org >and what's in Web Host in the Postorius domains view - in particular, if you have Postorius 1.3.3, what's the SITE_ID, and what's SITE_ID in settings(_local).py. https://lists.hodgsonfamily.org/postorius/domains/ Mail Host Description Alias Domain Web Host lists.hodgsonfamily.org lists.hodgsonfamily.org (lists.hodgsonfamily.org) SITE_ID = 1 Site ID is 1 in settings.py (not overridden in settings_local.py) > Also, when you go to the archive UI, whats the domain at the top left of the pages. Lists.hodgsonfamily.org I have overridden the following settings relating to this in settings_local.py: USE_X_FORWARDED_HOST = True ALLOWED_HOSTS = [ 'localhost', 'lists.hodgsonfamily.org' ] Settings.py is from the latest commit from the Mailman Suite Gitlab project. Thanks for helping me with this. Andrew.

5 years, 7 months

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. I've been playing with wget, and no matter what I put, I keep getting a 404 error. So: this works: wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/lists/list.example.com' but this does not (404 error): wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… ' Is there a way to list all templates? Or all templates for a list? On Thu, Feb 17, 2022 at 12:34 PM Stephen Daniel <swd(a)pobox.com> wrote: > That pulls a 404 error. Thanks for the hint. I will investigate. > > On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/17/22 08:04, Stephen Daniel wrote: >> > Mailman3 people -- >> > >> > I created a new list, and used postorius to create a template for " >> > list:user:notice:welcome". I then used the mass subscription feature to >> > add myself to the list, having checked "pre-confirmed", "pre-approved", >> and >> > "pre-verified". >> > >> > I received a welcome message that appears to be the default welcome >> > message. It certainly wasn't what I put into my template. >> > >> > Any suggestions on how I get mailman to use my template? Things I >> might be >> > doing wrong? >> >> >> What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a >> full URL by appending >> `/api/templates/list/list.example.com/list:user:notice:welcome` >> <http://list.example.com/list:user:notice:welcome> to that >> where `list.example.com` is the actual list_id of your list, and go to >> that URL, what do you get? >> >> -- >> 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/ >> >

4 years, 3 months

[MM3-users] Re: hyperkitty failed to create a thread

by Abhilash Raj

On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > Thank you very much for the quick fix, Mark and Abhilash! > > Abhilash, could you include the fix into the "latest" version of > mailman-web container please? They are nightly builds, if the fix was merged and the CI went through, they should already be in there. > > Btw I wasn't able to find a changelog of Mailman docker images anywhere and > 'Releases' page in Github is quite outdated too... Is there any other > place I should check? I have admittedly been too busy to write release notes, but the recent releases have seen not too much changes other than version bumps for the included Mailman packages. > > Danil > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > chained emails? > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > instead > > > of only one... > > > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > > > > Thanks for the report. > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > will fix 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/ > > > _______________________________________________ > 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)

7 years, 3 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Perry Kollmorgen

Thanks Mark. So, I have python scripts which do the adding of nonmembers and moderators. For the nonmember script I needed to add something so that the nonmembers can send, i.e the moderaction_action = 'defer' This is my code for nonmembers: mailing_list.add_role('nonmember', nonmember.email, display_name=nonmember.display_name) list_member = mailing_list.get_nonmember(nonmember.email) list_member.moderation_action = 'defer' list_member.save() For the code for moderators it currently only adds them: mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) Would I need to add something similar which sets a delivery_status for the moderator added ? Cheers, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 27 November 2024 2:16 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Notifying owners of membership changes but not moderators On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- 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, 6 months

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Thu, Feb 16, 2023 at 9:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 23:42, Odhiambo Washington wrote: > > On Thu, Feb 16, 2023 at 10:26 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > In my case, I had the exact same files in the two paths and the > > list:user:action:subscribe.txt was still not used in my tests. > > Why? > > > I don't know why? What's the content of the template table in the database? > ``` > SELECT * FROM template; > ``` > root@localhost [mailmansuite]> SELECT * FROM template; Empty set (0.03 sec) > I have now created the directory: > > mkdir -p /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ > > And I have placed the same files in there. Gearing up for a test to see > if > > the template will be used this time around. > > > That's just wasting space. If you're putting the exact same templates in > site/, domains/ and lists/, you might just as well delete the ones in > domains/ and lists/ and Mailman will use the ones from site/. > Well, space is cheap these days. > >> A template from import21 of the kictanet(a)lists.kictanet.or.ke list will > >> be stored in the > >> /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > >> directory. > >> > > > > It wasn't a template per se. It was the regular nondigest msg_footer from > > MM2. > > > import21 imports the nondigest msg_footer, makes certain adjustments for > Mailman3 compatibility and stores it as a template in the > var/templates/lists/<list-id>/<lc>/ directory, however if it was the MM > 2.1 default msg_footer, it won't be stored as a template and the MM3 > default list:member:generic:footer template will be used. > And what I am seeing is that the default list:member:generic:footer template is what is showing up in all posts. To my chagrin though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> 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/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 9 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

8 years, 9 months

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Wolfgang Bock

Dear Mark, I am running mailman3 (version 3.2.1) on debian buster. Created yesterday a Test mailinglist and faced the same problem in postmapping postfix_vmap again. Is the debian buster version of mailman3 not uptodate?? Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 00:43 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: > /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe(a)lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscri > be@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no > whitespace.ce in the last line and I made a new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- 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, 8 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Perry Kollmorgen

Oh great, that will be very useful when it is ready. It is easy for standard users to maintain a list which can be used also for sending access to other lists, particularly when nested. This along with the extra URL variables for use in templates look handy also. I already have added some URLs to our templates manually however if we expand to other domains it would save on some updating of templates. Usually, I would look to merge in useful PRs to my own branch of the source code used in production however with the use of docker this time around it isn't quite as easy. Likely not too difficult, but it might be good to wait too. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 8, 2024 3:59:46 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- 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, 11 months

Search results for query "sapiro"