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

[MM3-users] Re: Must every Moderator/Admin be member of a list to be able to use Postorius?

by Mark Sapiro

On 1/31/23 10:25, mm3-omf(a)sh.werbittewas.de wrote: > we're using debian/devuan with distribution-mailman3 and tried to add > admin/mod for a list, but if logging in as this user, there's no item to > manage the list at all. That's strange. If the logged in user is a moderator she should see the Subscription requests and Held messages tabs and with Postorius >= 1.3.9b1 also the Members tab, and if she is an owner she should see the full admin UI without needing to be a member. Are you sure the logged in user is the same user that's an owner/moderator? Log in as a superuser and find the user in the User's view fron the top nav bar in Postorius, click Manage to see all that user's roles and web account. > do we have to add this user as member of this list? > (that wouldn't be nice, because the user doesn't want to get normal > Mails from List, but only admin-Mails) It shouldn't be necessary, but a delivery can always be disabled for a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

by Mark Sapiro

On 9/22/19 2:11 AM, Manos Pitsidianakis wrote: > > mailman3 tries to get the template I've set via the mailman suite > interface but it assumes it is hosted locally: > 'http://localhost:8000/mailman3/api/templates/list/meli-announce.meli.delive…' > In my setup, they are separate machines. I can't find any way to change > this in the configuration. Also, can't the same template be loaded from > the master's localhost:8001 api? See <https://mailman.readthedocs.io/en/latest/build/lib/mailman/rest/docs/templa…>. There are other ways to set the URI for a template which will work in your case. When you set a template via Postorius, it sets the URI for that template to point to itself to return what it set. In your case, this URI points to localhost which is Postorius' localhost, but it is set in core and core's localhost is a different machine so it doesn't work. You could file an issue at <https://gitlab.com/mailman/postorius/issues> about this. > Haven't fiddled with python for some time, why is this exception catched > by "except socket.error"? Is it a subclass of > requests.exceptions.ConnectionError? The other way around. -- 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: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 4:05 PM, Duane Raymond wrote: >> As I said there, Mailman is going through the roster of regular >> (non-digest) list members to find those with delivery enabled and it >> finds a member that has no associated address. Can you view the members >> of this list? > > Yes - the list has three members (test list): me and two others. For my subscription I have gone through the membership options and explicitly set them. For the others their membership options are all unselected and thus I assume defaulting to a fallback value. (not sure if that matters) What matters is at least one of those members doesn't have an associated address record. If you have access to `mailman shell` do the following: 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 mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... And see what that gives you. (At the last ... prompt just type `enter`) -- 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: No digest.mmdf

by Mark Sapiro

On 3/28/21 8:18 AM, Christine wrote: > I have mailman3 running now, more or less. Mailman did not send messages > to my list, giving a permiission error on the digest.mmdf file, which > was not there. I created the file and made list.list the owner, now it > sends messages. > I don't know what should have created the file or what set the > permissions to the directory, I just thought I'd let you know. Mailman core creates and writes the lists/LIST-ID/digest.mmdf file to accumulate messages for the digest. When a digest is sent the file is removed only to be recreated on the next post, and you will probably run into this issue again. The issue is the user that Mailman core is currently running as does not have permission to create that file. This usually results from having run core as root at some point in the past causing some files and directories to have been created by root and not writable by the mailman user now running core. You need to ensure that Mailman processes are always run as the Mailman user, often `mailman` but in the case of Debian/Ubuntu packages, `list`. You probably need to ``` sudo chown xxx:xxx path_to_mailman_var/ ``` where xxx is the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: "autorespond to list owner" setting when importing from mailman2 to mailman3

by Mark Sapiro

On 2/25/22 08:32, bob B via Mailman-users wrote: > In mailman2 a list was moderated, the admin would also get an email to approve the message, our lists mainly have admins and no moderators. The admins did the moderation. > > In mailman3 it looks this is now a setting "autorespond to list owner" was this a setting in mailman 2? Yes, in MM 2.1 this was in the Auto-responder section of the admin UI, but this isn't what you wan. > Anyway, in importing email list from mailman 2 to 3, it appears that this setting is set to "No automatic response", is that right? Probably. It is =correct if that was the MM 2.1 setting. > So does this means if I import all my lists from mailman 2, then the admins will not get moderation notifications until I make that setting change on each list? No. The setting you want was Mailman 2.1's General Options -> admin_immed_notify which should be correctly imported to what Postorius shows as Settings -> Automatic Responses -> Admin immed notify and whether that is Yes or No, they should get periodic notices as long as cron is running `mailman notify`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users]Re: Sass and where to find core rest logs

by Mark Sapiro

On 05/04/2016 09:45 AM, Andrew Hodgson wrote: > Anyway, I have compiled Mailman3, and the web interface is coming up. Bringing up the list of lists initially gave me an exception, and I saw a 5xx error in the mailman.log file in /opt/mailman/var/logs. I read up on this and as a result downgraded Falcon<1.0 in the Python 3.4 venv. > > I am still unable to browse the list of lists with a 500 error, only this time I am not getting an entry in the mailman.log indicating there is an issue, and I am wondering if there are more detailed logs that can be switched on? There are the web server logs and there is the mailman-web configured in LOGGING:handlers:file in (using bundler) mailman-bundler/mailman-web/production.py (or testing.py). The production default is /var/log/mailman-web/mailman-web.log; the testing default is /opt/mailman/var/mailman-web/hyperkitty.log. > The other question I have is on Sassc. I believe the default Mailman web interface has now switched to the Ruby implementation of Sass, but is this correct? The documentation on the Mailman-Bundler site seems to suggest that Sassc is still the default. I think the bundler doc is out of date on this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 4 months

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

by Mark Sapiro

On 3/17/22 12:25, Quanah Gibson-Mount wrote: > > I've done nothing in regard to this user. Neither command returns > anything. Well, something has deleted the user, but ... >> If the user is gone, you should be able to replace >> ``` >> ... sub_mgr.confirm(token) >> ``` >> in the above with >> ``` >> ... wfm = getUtility(IWorkflowStateManager) >> ... pendings.confirm(token, expunge=True) >> ... wfm.discard(token) >> ``` >> to clear the pending subscription and workflow and then be able to mass >> subscribe the user. > > I did this, and can confirm that they no longer show up in the list of > pending subscriptions via the mailman shell interface for that list. > > However, if I go to mass subscribe them via the interface, I get: > > HTTP Error 409: b'Subscription request already pending' I don't understand. If there is no entry for that address when you do ``` >>> for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['email'] != 'user(a)example.com': ... continue ... print(data['email']) ... ``` You should not be getting that 'Subscription request already pending' response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Moderation request email from a non existing user

by Mark Sapiro

On 5/31/22 02:15, David Lopez via Mailman-users wrote: > Every day mailman (MM 3.3.3 (Tom Sawyer)) sends me an email with a held unsubcription request from X user. This user is not subcribed to that list anymore but every day an email is sending to the list owner. On the web interface there's nothing pending for approval or similar. Is there anyway to avoid receiving this anoyning email every day? Thanks in advance. Postorius >=1.3.5 has an `Unsubscription Requests` choice in the `Subscription requests` pull down. This choice will list the request with and allow you to delete it. For earlier Postorius this needs to be done via the REST API or via mailman shell. For example: ``` $ bin/mailman shell -l list(a)example.com 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(a)example.com mailing list >>> pendingsdb = getUtility(IPendings) >>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): ... if data['token_owner'] == 'moderator': ... pendingsdb.confirm(token) ... data about the request will be displayed here >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Performance issues with Mailman 3

by Mark Sapiro

On 10/6/22 15:08, Wong, Wesley wrote: > Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I suspect the difference is your Mailman 3 instance has full VERP enabled and your Mailman 2.1 instance did not. I.e., In MM 2.1, you did not override the default `VERP_DELIVERY_INTERVAL = 0` in mm_cfg.py, but in MM 3 you have `verp_delivery_interval: 1` in the `mta` section of mailman.cfg. > I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: Search the Titles for `performance` at https://wiki.list.org/. The articles you find are all written for MM 2.1, but you're really dealing with the MTA and the issues are the same for MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Search results for query "sapiro"