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

[MM3-users] Re: installation

by Brian Carpenter

On 11/22/20 6:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I > have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. Mark Sapiro provided some very good suggestions. Is this a new IP address or one that has been used for mail traffic for a white? The only way Gmail and Hotmail will block an IP address is if you have some major outgoing spamming problems or in the case of a new IP address, the IP address has a sordid history which will be reveal if you do a RBL check on it. Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. For Hotmail deliveries, you will want to signed up for Microsoft's Smart Network Data Service (SNDS) program which I find very good. Also sign up for their JMRP program for your IP address. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Re: Hyperkitty

by Onyeibo

Hi Mark, On Mon, 30 Jan 2023 12:24:24 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:58, Onyeibo wrote: > >> 2. Your MM3 log files - do they say anything? > >> > > Nothing! No new errors. It is very strange and frustrating > > > Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/? > YES! A lot of them > Do messages received from the list have an Archived-At: header:? > No > Do messages received from the list have a List-Archive: header:? > No > If the first answer is yes, the mailman_hyperkitty archive_message > method is failing. > > If the second answer is no, the mailman_hyperkitty permalink method > is failing. > > If the second answer is no, the mailman_hyperkitty list_url method is > failing. > That means they are all failing. Wow > All of these failures log errors to the mailman.archiver log which by > default is written to mailman.log. The log doesn't have entries pointing to failures above > > If by chance there is an Archived-At: header, what is it? > The mails don't have that header. I suspect I may have to investigate SELinux.

3 years

[MM3-users] Re: lists.mailman3.org web site.

by Barry Warsaw

On Aug 30, 2016, at 12:01 AM, Mark Sapiro wrote: >Django Allauth is now properly configured and working on >lists.mailman3.org. You can log in by email/password as noted above or via >OAuth2 with a GitHub, GitLab, Google or Facebook identity. > >If you are an existing user, in order to use one of the OAuth2 providers, you >must first log in with email and password and go to the Account Connections >tab in your account settings and add the 3rd party account(s) you wish. This works pretty great. I tried it with my GitHub and GitLab accounts and was easily able to associate those with my Postorius and HK accounts. I didn't try FB or Google, but I guess those would work the same way. I'll miss Persona but I think this is an entirely acceptable alternative, with plenty of choice for folks wanting to control which authority they delegate to. I'd mildly like to see Launchpad support, but I understand 1) it's a minority platform; 2) it only supports OAuth 1. Thanks to the developers for adding this support and to Mark for enabling it. Cheers, -Barry

9 years, 5 months

[MM3-users] Re: no mails to list members

by Thomas Stein

Thanks for the clarification Mark. cheers t. On Friday, 4 January 2019 19:25:20 CET Mark Sapiro wrote: > On 1/4/19 6:49 AM, Thomas Stein wrote: > > > > While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? > > > There are multiple ways to reference templates, but just putting them in > that location should work. > > > > Should > > I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? > > > Your list was created with an older version of import21. That version > named the templates it stored with underscores rather than colons and > set the URI for that template to use the underscore name. Thus, without > changing the URI for the template, you need to continue to use the > underscore name for those templates, but for other templates, you can > use the name with colons and not worry about the URI. > > > > Is there some documentation > > what variables i can put in those templates? > > > See > <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…>. > >

7 years, 1 month

[MM3-users] Re: Module Not Found Error after update

by Abhilash Raj

On Thu, Feb 4, 2021, at 8:52 AM, Brian Carpenter wrote: > > On 2/4/21 11:46 AM, Mark Sapiro wrote: > > You need django-mailman3 1.3.5 > > > > > > While all are not required in this case, when you upgrade like this with > > pip, you should upgrade all of django-mailman3, hyperkitty, mailman, > > mailmanclient, mailman-hyperkitty and postorius. > > Thanks Mark. Perhaps Abhilash can include that in the instructions on > the following page for future releases: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I was hoping pip would actually upgrade django-mailman3 given that P requires ‘django-mailman3>=1.3.5’ [1] but looks like it didn’t :( [1]: https://gitlab.com/mailman/postorius/-/blob/master/setup.py#L56 > I will make a note of this in my own personal documentation and the > Debian 10 How-to guide that I am currently working on. > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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)

5 years

[MM3-users] Re: Moderate mails from owner

by Henrik Rasmussen

Mark Sapiro wrote: > This can happen in a few ways., If this list was originally imported > from Mailman 2.1 by the 'mailman import21' command, there may be a > legacy accept_these_nonmembers attribute for the list. If so, and if a This makes sense. The list was in fact imported from Mailman 2.1. > You need to check the list's accept_these_nonmembers attribute and the > non-member address's moderation action. > > If you have recent Postorius, you can see nonmembers and their options > from the 'users' -> Non-members view. I currently have Postorius 1.2.2 so I don't have it yet. > mailman shell -l list.example.com The sender is in the list of accept_these_nonmembers, however the command memb.moderation_action = m.default_nonmember_action doesn't seem to remove it from accept_these_nonmembers. bash-4.3# mailman shell -l [LISTNAME].lists.example.com Welcome to the GNU Mailman shell The variable 'm' is the [LISTNAME].lists.example.com mailing list >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] >>> memb = m.nonmembers.get_member('listadmin(a)senderdep.example.com') >>> memb.moderation_action <Action.accept: 3> >>> memb.moderation_action = m.default_nonmember_action >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] -- Henrik

6 years, 9 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Johannes Rohr

Am 23.01.23 um 21:08 schrieb Mark Sapiro: > On 1/23/23 02:41, Johannes Rohr wrote: >> >> I don't understand what the cause for the "permission denied" could >> be. The directory "fulltext_index" is owned by mailman:mailman >> >> Does anyone have a hint? I did some googling for the error, but to no >> avail, unfortunately. > > > It's actually trying to create fulltext_index, so clearly it's not > looking at the fulltext_index that you are. If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you > probably need to specify the path in /etc/mailman3/settings.py as in, > e.g. > ``` > HAYSTACK_CONNECTIONS['default']['PATH'] = > '/opt/mailman/mm/var/fulltext_index' Thanks! Indeed. Including this line helps. It makes the error go away. So I guess the instructions should be amended. After that, for some reason, I have to re-index all lists, because initially, empty results were returned for any query, only after re-indexing to I get results. Again, thanks so much for your support! Johannes > ``` >

3 years

[MM3-users] Re: Adding / manipulating users

by Seth Seeger

> On Nov 18, 2019, at 2:28 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/18/19 6:15 AM, Seth Seeger wrote: >> >> My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. > > > ... > > Alternatively, you could create a script that would post the appropriate > transactions to add a member and set moderation and delivery status to > Mailman's REST API and use that to process your members. Great! I can definitely do the REST API route. If I create a script to take a CSV and push it through the API, is there a place I can post it to make it useful for others? Seth

6 years, 3 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 13:11 -0800, Mark Sapiro wrote: > On 2/19/22 12:41 PM, William Oliver wrote: > > > > So, I can just kill the listname user altogether? > > > As far as Mailman is concerned, Yes. > > No joy. I deleted the list as well, and recreated it with the same name -- and the error repeated. I created a list with a different name, and there's no error. I must have really screwed something up in dovecot. Happily, this is a small list, so I'll just migrate everybody to the newly named "listname2". So.. as an aside, it was a bit of a hassle to copy and paste all the usernames from the "Users" list in Postorius to the "Mass subscribe." The only way I could see to do it was copy and paste them one at a time. That worked OK for me, since it's a small list, but that made me wonder if there was a way to select, say, 100 users out of Users and subscribe them all to a list. billo

4 years

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 9:21 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/23 08:11, Quanah Gibson-Mount wrote: >> Hi, >> >> We frequently end up with users who never receive their email to confirm >> their account, leaving them in a netherworld where they cannot become >> list members. If I try to subscribe them via the mass subscribe >> option, it says I can't because their subscription is pending. If I >> go to subscription requests, it says there are 0. If I go to >> "non-members" in the UI, I can find them, but I don't see an option to >> convert them to members. > > > Subscription requests says 0 because it only counts those pending > moderator approval, but if you pull down the menu and select Pending > Confirmation, it should show the request and enable you to delete it, and > then mass subscribe will work. The only elements that have a drop down menu are: Users Mass operations There is no "Pending Confirmation" with either of these. Note: Postorius Version 1.2.4 --Quanah

2 years, 8 months

Search results for query "sapiro"