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

[MM3-users] Re: MM3 not starting afte an upgrade

by Gelpi Andrea

Il 23/07/20 23:05, Mark Sapiro ha scritto: > On 7/23/20 4:35 AM, Gelpi Andrea wrote: >> Hi, >> to day in a Debian system I upgraded some packages. >> >> After the MM3 doesn't start anymore. . . . >> Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) >> Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] >> Operation not permitted > > > I think you have a stale lock issue and the master is trying to > determine if the process that set it still exists. > > Remove Mailman's var/locks/master.lck* > Thanks Mark, now MM3 star but postorius is not working. The web pagge return: An error occurred while processing your request. I receive an email with: ... Exception Type: KeyError at /postorius/lists/ Exception Value: 'file' Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data Is that related to Django id setting or there is a passphrase mismach some where? How can I check? -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 6 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Alex Schuilenburg

On Fri, 2020-10-02 at 12:00 -0700, Mark Sapiro wrote: > [...]There's much more detail in my reply at< > https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422894486>;, > butyou can fix the ResponseNotReady() issue from the sync_mailman job > byfinding the entries in the hyperkitty_sender table with > invalidaddresses in the address column and deleting them. As per comment https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422958260 , it was not a simple delete, but an insert/update/delete > We can try to address this specific issue in hyperkitty_import, > butthere are in general various mbox defects that we can't detect. > mboxesneed to be checked for unescaped `From ` lines in message > bodies andother defects before importing them. The Mailman 2.1 > bin/cleanarchscript and the new hyperkitty/contrib/check_hk_import > script can helpwith some of this. I ran both on the original archive, cleanarch made no changes and check_hk_import just retported the number of messages. As it turns out, the message was imported, but with the dodgy email as sender which was fixed by the insert/update as per my comment. Hope you have some success with the redacted mbox example. Cheers -- Alex

5 years, 4 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote: > > On 3/13/21 11:14 AM, John Covici wrote: > > > > Now one thing came up while trying to create the database, I got a > > traceback complaining about a revision error because gentoo had a > > slightly different version (3.3.2) instead of 3.3.3 using pip. When I > > upgrade mailman, am I going to have to do something to the database as > > well and why should the database have some kind of reference to the > > mailman version? > > > I don't know why this is an issue. You shouldn't need to do anything > with the database when you upgrade. Please post the full traceback and > error message. Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 11 months

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > > On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >> I've come across mailman-cli docs: > >> > >> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >> This is basically one of our GSoC projects which hasn't yet been merged with MailmanClient. It uses the REST API to to provide a command line client for Mailman, while there hasn't been any in-compatible changes in API since this project was finished, I am not sure about the current status of it. > >> yet I cannot figure out what's the official source for the installation. Official source for MailmanClient is at gitlab.com/mailman/mailmanclient and it doesn't have a CLI, the Github project you linked to says right on the top that it is not official project (Thanks for that Rajeev!). Also, I would say not to use this client to remotely access Mailman, the REST API is not meant to be exposed over internet (unless you have a VPN or other sort of setup to securely access the box remotely). -- Abhilash Raj maxking(a)asynchronous.in

8 years, 4 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 20:21 : > On 6/15/20 9:43 AM, Gilles Filippini wrote: >> Hi, >> >> I'm seeing the above error in mailman-core logs each time an email is >> processed. Is there something I missed in the configuration? I'm using >> dockerized mailman 0.3 from maxking. > > > I'm guessing you have one message in var/archives/hyperkitty/spool/ that > is causing this issue. The message itself will probably have invalid > utf-8 encodings in a message part declared as charset=utf-8. > > Every time a new message is archived, HyperKitty reprocesses this > message and hits the error again. > > You can examine the message with `bin/mailman qfile`. It is a Python > pickle of a message object. There are 4 emails stored into this folder. 3 of them are spam, and the last one is a legitimate email. This is annoying that such emails could accumulate and stay into var/archives/hyperkitty/spool/ forever, causing more and more hyperkitty errors. Any idea how to make their processing more error proof? Thanks, _g.

5 years, 8 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Mark Sapiro wrote: > The senders are defined as addresses in the headers listed in > the configuration setting sender_headers, default = from, from_ > meaning envelope sender, reply-to and sender. See > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> This was very useful in explaining why MM3 (3.3.9) accepted the problem post and attributed it to my address, even when seeing the bounce+ address as a different sender. Thank you for taking the time to reply. > Are you saying that the bounce+... address ends up as a nonmember of > the list you are sending to. I don't think that should happen. Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Steve

1 year, 5 months

[MM3-users] Re: Deleting moderation requests in database

by Joachim Schrod

Mark Sapiro writes: > On 12/2/24 6:40 PM, Joachim Schrod wrote: > > > > First: I assume that all information about moderation is in the > > database mailman3. If that's not the case, please tell me. > > > It is the case, but it's easier to use mailman shell. Something like > ``` > $ mailman shell -l test.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 test.example.com mailing list > >>> pendingsdb = getUtility(IPendings) > >>> for token, data in pendingsdb.find(m): > ... if data.get('token_owner') == 'moderator': > ... if data['type'] == 'unsubscription': > ... pendingsdb.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks a lot, worked like a charm! Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

1 year, 2 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 1:04 PM, Mark Sapiro wrote: > On 10/23/20 9:37 AM, Brian Carpenter wrote: >> How would a person already be a core user outside of a registration with >> Affinity? Via a list subscription or the import21 script? > > Yes, or even just by sending a post to a list as a nonmember. > > Everyone who is or has been a member, non-member, owner or moderator of > a list has a user and one or more address records in Mailman core. And those records are kept in the database? Is that correct? >> I do want to apologize for my tone Mark. I was wrong in the way I communicated. > > Apology accepted. I understand that it can be frustrating to be > dependent on something you don't control and that this can sometimes > lead to "anomalous" behavior. > > Here's a take on this that is intended to be humorous, but is actually > quite frightening. https://xkcd.com/2347/ I actually came across that cartoon months ago and that one person reminded me of you. So the fact that you are sharing that cartoon is ironic and very funny! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[MM3-users] Re: Extracting mailing list users

by Eggert Ehmke

Am Montag, 2. Januar 2023, 02:40:58 CET schrieb Mark Sapiro: > Understood, but there are a couple of things at work here. One is that > this particular task is a one-off the correct the result of a bug, but > perhaps more significantly, mailman developers (at least me) are > comfortable with `withlist` (it's been around since MM 2.1) and if I can > do it that way, it reduces the motivation to make something more > friendly for the normal admin. Unfortunately doing things easily that > way requires a lot of specialized knowledge of Mailman internals, so > most admins need help with it. Mark, I completely understand your situation as a core developer with limited time and lots of requests from all directions. Being a Python programmer myself, I would be happy with a consistent documentation of the relevant Python classes to be able to develop own applications. The isolated code snippets in the mm3 documentation are not too helpful. Such a documentation would possibly remove some of the workload you feel by constantly answering admin questions.´ When you look at the documentation of the Qt library you know what I mean. Thank you again for this great project! Cheers, Eggert

3 years, 1 month

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 1:14 PM, Mark Sapiro wrote: > On 10/21/20 8:53 AM, Brian Carpenter wrote: >> If you set the unsubscription policy to confirm then moderate for a list >> and someone unsubscribes, they receive a confirmation request. That is >> good. They respond to it. That is also working fine. However the list >> owner/moderator than gets a request to approve the unsubscribe request >> and well, unless I am missing something, I don't see an interface to >> handles such requests via Postorius. > > This is <https://gitlab.com/mailman/postorius/-/issues/332>. > > >> How does one handle an unsubscribe request that requires moderator >> approval? > > I'm not sure at this point, I can look further later, but if the notice > to the admin has a token, it might work to send a `confirm <token>` > command to the list-request address. > > Otherwise, don't moderate unsubscription requests. Well I can't dictate that to my list owners and there is no confirm token sent with the moderation notice. Why include this option in Postorius when it can't be properly handled? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

Search results for query "sapiro"