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

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/22/21 5:47 PM, dancab(a)caltech.edu wrote: > I've imported a list from Mailman2 and had the owner send a message for testing purposes. > > His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. > > However if we attempt to view the message in Postorius web UI then an error is thrown. Can you see the message in the held messages view and only get the error when you click the message, or can you not see the held messages view at all? Is it only this list that has an issue? Can you visit other pages for this list? > In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." > > But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. > > [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages > > Does "Service Unavailable" mean I'm missing something in the configuration? Possibly, but I don't think so. What is the Traceback from the message Django sends to the server admin? -- 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: mailman 2.1 or 3.0 (or another MLM)

by Mark Sapiro

On 1/26/22 08:49, nate wrote: > (In case the list admin/moderator sees this message I sent this email > again from the wrong FROM: address a few minutes ago, re-sending with > the right one now, please discard that bad message(have not > gotten confirmation it was held for moderation) Posts to this list from non-members are discarded without notice. > -- side note with > MM2 it gave the user the option to discard their own message if it > was held for moderation if I recall right. My very first post to > this list was held for moderation (sent from correct FROM: address), > not sure why it was held(it got through eventually), was assuming > that perhaps I triggered a bug in that the fact I am using the > text mailman in my email address maybe tripped something I don't know, > but I was seemingly unable to view the status/discard that message.) Your initial post was held because all new members are moderated by default. This is an anti-spam measure. If you post on topic, we clear your moderation. And yes, Mailman 3 doesn't (yet?) have a way for ordinary users to delete their own held posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: MASS mailing list import - 900 ezmlm lists to Mailman

by Mark Sapiro

On 4/18/23 17:41, grant(a)horizonsunlimited.com wrote: > Hi, > I hope someone can help. > I have 900-ish, mostly small lists, basically all locations round the globe where people have volunteered to help particular people passing though. Those lists have 2 to 200 people. There are about 50 lists of up to 1000 people each we use for announcements. So two different setups, and a whole lot of manual work. > I am moving from an old, now unreliable, host to a new one. Hopefully reliable, certainly cheaper, and better for privacy GDPR etc regs. > Mailman is already installed, appears to be version 82?? on cPanel 108.0.15. Ezmlm, no surprise, is not. Installing and configuring it is not something trivial, also have to install gmail etc. Yuck. First of all, cPanel Mailman is most likely 2.1.38. This list is for Mailman 3. The appropriate list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. This search <https://mail.python.org/archives/search?mlist=mailman-users%40python.org&q=…> finds 169 posts mentioning ezmlm. Some of those might be relevant to importing lists from ezmlm. Also see <https://wiki.list.org/DOC/Mailman%20and%20CPanel> and be aware that Mailman 2.1 is end of life. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/16/25 13:43, via Mailman-users wrote: > HI Mark, > > I simply tested by unsubsribing to the mailing list and then re-subscribing to receive the welcome message. > > How do you test using the mailman command with user list? sudo -u list mailman addmembers -h or in your case, you may not have that subcommand in which case see sudo -u list mailman members -h However, that is all irrelevant. I only thought you might be testing by using `mailman` commands to add a member and if so and if the command is not run as user `list`, it might not have access to read the template. If you are (un)subscribing via Postorius or via email these are handled by Mailman runner processes which should all be running as user `list` and should have access to the template. So, as I said, I don't know what the issue is unless it is something with your Debian package which is ancient. Even Debian buster has mailman core 3.2.1. Does your empty list:member:generic:footer.txt work to not add any footer to list messages? If so, I can't think of any reason why your list:user:notice:welcome.txt wouldn't be used. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 4 weeks

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 12:53 PM, Marco Marinello wrote: > Dear Mark, > > had > # pip freeze > ... > HyperKitty==1.3.5 > ... > mailman-hyperkitty==1.2.0 > ... > > and got the described behaviour. > Downgraded to > > HyperKitty @ https://gitlab.com/mailman/hyperkitty/-/archive/1.3.4/hyperkitty-1.3.4.zip > mailman-hyperkitty @ https://gitlab.com/mailman/mailman-hyperkitty/-/archive/v1.1.0/mailman-hype… > > and now archiving works. Actually, with HyperKitty==1.3.5 and mailman-hyperkitty <1.2.0, the message is not exactly as in this message's Subject:. It is 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer. Perhaps you paraphrased the message. If not, that exact message was not in any version of HyperKitty leading up to 1.3.5. And with mailman-hyperkitty==1.2.0, it should work. I see what pip freeze reported, but something was wrong somewhere because that combination should work and the 'The MAILMAN_ARCHIVER_KEY ...' message would only be logged with a version of mailman-hyperkitty <1.2.0. Perhaps you did not realize you had to restart Mailman core and skipped that step. The mailman-hyperkitty module is imported by Mailman core, thus core needs to be restarted if it is changed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Threads by month dropdown

by Mark Sapiro

On 6/5/25 10:22, Sam Darwin via Mailman-users wrote: > > Deleting all archives and importing the older messages first... that worked correctly. It is a large destructive actions though, should that count as the official solution? No, that shouldn't be the "official" solution. It may be too late now, but did you restart mailman-web? See the thread (started by you) at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Detour: > > While debugging it seemed to be an interesting question whether the mailman3-web periodic cron tasks had been running, and if those tasks affected the hyperkitty import. Referring to "Cron Jobs for Mailman Web" https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… Those instructions are not dumping stdout/stderr to a log file, nor rotating the log files. What is your opinion if I sent a pull request that adds "Method 2 - Advanced", and include logging for the crons. Or maybe I am missing something. Is the output of the cron tasks getting logged in your environment? Any output to stdout or stderr from any of the crons will be emailed to the owner of the crontab or the address in a MAILTO= in the crontab. You should ensure that mail to `mailman` is deliverable -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Mark Sapiro

On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > I have had this working before, so I guess it's a simple setup error. > > When I send a message from the Postorius interface, it is neither sent out > or stored. I briefly see this message: "Your reply has been sent and is > being processed.", and then nothing happens. I assume you mean HyperKitty. Postorius has no facility for posting messages to a list. > I have installed maxking's docker-mailman and copied my old setup with > basic stuff like passwords and such. The only new thing is that I'm now > running in userspace by putting in /etc/subuid and subguid: When you post from HyperKitty, HyperKitty creates a django.core.mail.EmailMessage() instance and calls it's send() method which causes Django to send the message to the list address. It then has to be received and processed by Mailman the same as any email post before it will appear in the archive. Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. If DEBUG = False and normal posting is working, perhaps there is some Postfix issue in delivery of the message from Django to Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Mailman runners missing - nothing in logs

by Mark Sapiro

On 1/18/20 6:13 AM, Torge Riedel wrote: > > So now back to good. I checked all the logs prior to restarting the > service in directory /opt/mailman/var/log, but I do not see any errors. > And the master was still running, I would expect that the master will > start / restart a runner in case it died? What's in /opt/mailman/var/log/mailman.log? There should be entries like Jan 18 13:51:11 2020 (11700) xxxx runner started. for each runner every time it starts and like Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. Jan 18 13:47:31 2020 (10096) xxxx runner exiting. for each runner every time it stops, but with perhaps a reason other than `caught SIGTERM` That should at least tell you when they stopped. Also, if they stopped for some reason. The master will only restart runners that exit if they exit because of SIGUSR1 or some internal error and even then, only the configured max_restarts number of times. Do you have a logrotate script for the logs in /opt/mailman/var/log, and if so, does it have a postrotate script that signals Mailman to reopen logs other than by a `mailman reopen` command, perhaps by signaling the master with other than SIGHUP? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Bounce counter visibility for List Admins

by Mark Sapiro

On 5/19/21 4:10 AM, smorytko(a)gmail.com wrote: > As you may know, we use MM3 but the Affinity/Empathy flavor and we only have List Administrator using the Postorious/Affinity. Unlike many here, we have no access to any server-based files. > > Can someone tell me if Postorious gives list administrators visibility into the bounce counters? User's bounce scores are not available in REST so neither Affinity nor Postorius has access to them. > While List Admins get to set various bounce counters we have no visibility of those counters until, all of a sudden, an entire source of subscribers hits the bounce threshold and gets bounced off the list. It would be really nice to be able to see the bounce counters and possibly head off trouble before users/subscriber mail hosts. It can serve as an effective early warning system that something is wrong. > > Assuming Postorious cannot, is there another way List Admins can inspect bounce counters? Email command? In the next release of Mailman core (3.3.5), lists will have a `bounce_notify_owner_on_bounce_increment` setting which if True, will send to the list admins a notice including the triggering DSN when a user's bounce score is incremented. This setting will also be exposed in Postorius 1.3.5. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

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

by Mark Sapiro

On 12/02/2016 08:07 AM, Barry Warsaw wrote: > Hello Mailman 3 users and developers! > > It's been a long slog but I think we are finally ready to begin the release > process for Mailman 3.1. I am pretty happy about the state of the Core, and > Florian is going to do some more integration testing with HyperKitty and > Postorius. We still have a few issues and a merge proposal or two to address, > but I am planning to spin a beta of Core this weekend to facilitate testing. Barry, 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. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

Search results for query "sapiro"