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

[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

6 years, 9 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

5 years, 5 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

9 years, 10 months

[MM3-users] Re: hyperkitty_import Unicode Errors

by Mark Sapiro

On 5/6/23 11:27, Dave Hall via Mailman-users wrote: > Hello. > > When running hyperkitty_import to import Mailman 2.1 archives, I frequently > get errors like > > django.db.utils.OperationalError: (1366, "Incorrect string value: > '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column > `mailman3web`.`hyperkitty_email`.`content` at row 1") > > Is there a known cause for this? Is it fixed in some release more recent > than 0+20180916? I'm not sure what's going on here. My first thought is the database is MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database column charset definition is utf8 and not utf8mb4, but '\\xE1\\x90\\xA7\\x0A\\x0A' is the 3-byte UTF-8 encoding for CANADIAN SYLLABICS FINAL MIDDLE DOT ('\\xE1\\x90\\xA7') followed by two newlines. so I'm not sure what the issue is. When you encounter this error, there should also be a message like "Message <Message-ID> failed to import, skipping" or perhaps "Failed adding message <Message-ID>: <error message>". Using that Message-ID value, you should be able to find the original message in the input mbox. I would like to see that mbox message. You can remove any personal info. I only really need the message body and any Content-*: headers. -- 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: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 1:20 PM, eboltz(a)lhtservices.com wrote: > Okay, created a new Mail Host with only 'list.example.com' and no alias domain. I then created a new list and tried subscribe/unsubscribe but got the following error message in mail.log file > > Dec 17 21:14:26 mailman3 postfix/smtpd[6649]: 057E744552: client=localhost[127.0.0.1] > Dec 17 21:14:26 mailman3 postfix/cleanup[6653]: 057E744552: message-id=<170284766462.1144.7361224077829393518(a)ec2-54-172-107-21.compute-1.amazonaws.com> > Dec 17 21:14:26 mailman3 postfix/qmgr[6644]: 057E744552: from=<list_test-bounces(a)lists.example.com>, size=908, nrcpt=1 (queue active) > Dec 17 21:14:26 mailman3 postfix/smtpd[6649]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > Dec 17 21:14:27 mailman3 postfix/smtp[6654]: 057E744552: to=<eboltz(a)lhtservices.com>, relay=mail.smtp2go.com[45.79.114.202]:587, delay=1, delays=0.01/0.01/0.52/0.46, dsn=5.0.0, status=bounced (host mail.smtp2go.com[45.79.114.202] said: 550-From header sender domain not verified (lists.example.com) 550-On your Sending > Verified Senders page 550 verify the sender domain or email to be allowed to send. (in reply to end of DATA command)) Your relay host doesn't like lists.example.com as a sender. You need to fix this on the relay host mail.smtp2go.com. It seems to say that you need to go to the Sending > Verified Senders page on the relay host and add lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/11/24 04:17, Ulf R. wrote: > Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. > So everyone who wants to work as an owner nor moderator must be an AD-User. > In hyperkitty I am able to assign these list rights directly to AD-Loginnames. > With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). You are conflating Postorius, which is simply a web management UI for Mailman core, with Mailman core itself. I suppose it's not really important, but when you think of access rights in Postorius, these are actually in mailman core. > Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? > What would be the best practice for owner/moderator user management? Just ensure that list owners and moderators are using the email address of their AD-Account. This will propagate to HyperKitty. You shouldn't need to manipulate HyperKitty access rights directly at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Getting an error for every post made to any list

by Mark Sapiro

On 4/22/25 1:35 PM, sun zi via Mailman-users wrote: > As mentioned in the subject, I am getting the following error after every post. Any assistance would be much appreciated: The error is from an attempt to archive a message. Since it fails, the problem message is queued in Mailman's var/archives/hyperkitty/spool/ directory and is retried with each post. The message is in a Python pickle, *.pck, file in that directory. Yoy can examine the message by giving it to `mailman qfile`. From the tracebacks you posted, it appears that the issue is that the sender's address is longer than 255 bytes. Move the .pck file out of the var/archives/hyperkitty/spool/ directory and that will stop the recurring error. If the message is spam you can ignore it. If you want to archive it you need to edit the message's sender, but you can't edit the *.pck directly. You can use `mailman shell` and do something like ``` import pickle with open('path/to/the/pickle', 'rb') as fp: msg = pickle.load(fp) # code here to edit the sender with open('path/to/the/pickle', 'wb') as fp: msg = pickle.dump(msg, fp) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/18/21 1:41 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I've been trying to "translate" the python script that I made for > mailman2 to new mailman3, but obviously, I'm missing something. It seems > that mailman cannot locate the "module" needed. > > The script is named "moderar.py": > > *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) > > /usr/local/mailman3 # cat moderar.py > #! /usr/local/bin/python3 > # > # script via withlist para moderar a pelo en mailman3 > # > > import os > import sys > > sys.path.insert(0, '/usr/local/mailman3') If /usr/local/mailman3 is not already in the path, this is too late. The rest of your script is not relevant. Here's what you need: ---------------------------------------------------- from mailman.interfaces.action import Action def moderar(mlist, member): memb = mlist.members.get_member(member) if not memb: print('{} is not a list member.'.format(member)) return memb.moderation_action = Action.hold print('{} moderation_action set to hold.'.format(member)) ---------------------------------------------------- That should be put in a moderar.py file somewhere in Mailman's path. The same directory that contains the `mailman` command is for sure good. Possibly that's /usr/local/mailman3/bin/. Then mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Internal Server Error: Reattach this thread

by Mark Sapiro

On 10/18/22 21:38, hasimoto(a)designet.co.jp wrote: > Hi, > > In the archive, clicking "Reconnect this thread" causes an internal server error. > I received the following email, but I don't know how to solve it, please help me. How big is the archive in which you are doing this? Are you running the periodic django-admin jobs via cron? See https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/crontab I ask because I've now seen this issue in a test installation, but only with an archive containing only one message. The particular steps I followed somewhat by accident were: Start with an archive containing only two messages in separate threads. Open one thread and `Delete this thread` leaving only one thread. Open that thread and click `Reattach this thread` - this produces the error. Restore the deleted message/thread with `hyperkitty_import` Clicking `Reattach this thread` in either thread produces the error. After running the hourly and daily django-admin jobs, clicking `Reattach this thread` in either thread works as expected. That scenario with deleting and restoring a thread was somewhat accidental, but did produce the error. in other list archives on the same server, even one containing only one message, clicking `Reattach this thread` in either thread works as expected. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: certain msgs not archived

by Mark Sapiro

On 2/17/22 10:49, Sandor Dibuz wrote: > > Great! So valuable info. Thank you, Mark. "earlier that the oldest > message" you sure mean earlier then the oldest of already archived. Or > since= any date of the mbox messages to be imported. Will check the > hyperkitty_import for since= option format. That was a typo. I meant "earlier than". I tend to use `since=1970-1-1`. It doesn't matter how early as long as it's earlier than the oldest message to be imported. > Yet another question. Is it supposed to stop minutely/hourly/etc. > mailman3-web cron jobs during import to avoid any collisions? Or even > mailman3-web completely but probably it needs to be running. I only ask > because my last import attempt on a test maillist failed with > > [ERROR/MainProcess] Failed indexing 1 - 2 (retry 5/5): (1712, 'Index > hyperkitty_attachment is corrupted') (pid 5841): (1712, 'Index > hyperkitty_attachment is corrupted') > > Optimizing cured the hyperkitty_attachment InnoDB index corruption > problem but scared the sh.. out of me for a moment... I don't know what may have caused the index corruption. I don't bother to stop any crons or services while hyperkitty_import is running and I've never had an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Search results for query "sapiro"