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

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Odhiambo Washington

On Tue, Oct 1, 2024 at 12:36 PM Chupin Maxime via Mailman-users < mailman-users(a)mailman3.org> wrote: > Mark Sapiro wrote: > > Did you run this as the Mailman user (list in the Debian packages)? > > Thank you, I tried, but the system asked me a Password for this user... I > do not understand. > > ``` > sudo -u list mailman-web makemigrations --merge > Password: > ``` > The user executing `sudo` is yourself so enter your own password. It's not the password for user "list" that is wanted. It's your own login password. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

[MM3-users] Re: Create a mailman-web admin user

by Roland Giesler

On 2024/07/30 19:13, Mark Sapiro wrote: > On 7/30/24 08:55, Roland Giesler via Mailman-users wrote: >> >> I use Linux LXC containers mostly in Proxmox, so adding another layer >> by using docker or something else to mean seems like another layer of >> complication. >> >> The documentation is obviously good enough for people that know how >> already, but need to look up a detail here or, but for a first time >> mailman user it is a bit of a nightmare. Once I have chewed my way >> through all the traps and tunnels, I intend to do something about >> this. I can't contribute to code here, but I can make it easier for >> the next person coming along. > > > Please see https://wiki.list.org/x/12812344 Point taken, Mark.

1 year, 8 months

[MM3-users] Re: Mailman3 breaking DKIM signatures

by Danil Smirnov

Hi Mark, чт, 23 янв. 2025 г., 03:15 Mark Sapiro <mark(a)msapiro.net>: > > You could try a patch like > ``` > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -186,7 +186,8 @@ class LMTPHandler: > listnames = set(getUtility(IListManager).names) > # Parse the message data. If there are any defects in the > # message, reject it right away; it's probably spam. > - msg = email.message_from_bytes(envelope.content, Message) > + msg = email.message_from_bytes(envelope.content, Message, > + policy=email.policy.Compat32(max_line_length=0)) > msg.set_unixfrom(envelope.mail_from) > except Exception: > elog.exception('LMTP message parsing') > ``` > This should prevent folding headers, but this is problematic. It may be > that the incoming message contains a folded header and this change will > not fold it in the outgoing message. Doesn't this parameter fits better? https://docs.python.org/3/library/email.policy.html#email.policy.EmailPolic… Danil

1 year, 2 months

[MM3-users] Re: Separating Lists by Domain

by Abhilash Raj

On Thu, Jan 3, 2019, at 8:19 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > > Is there a way we can get [Postorius updated] where we can > > > separate lists by domain the way Hyperkitty does? Mark Sapiro > > > refers to this in the following post: > > > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > You can file an issue at > > https://gitlab.com/mailman/postorius/issues > > Is this feature GSoC-able, or too small? It could be a good first issue for a GSoC applicant, too small to be the project itself. > > Steve > _______________________________________________ > 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)

7 years, 3 months

[MM3-users] Re: Updated script for checking and fixing mbox files.

by Odhiambo Washington

On Fri, Jan 20, 2023 at 5:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > Mailman 2.1 has a cleanarch script for checking mbox files for unescaped > `From `lines in message bodies and optionally fixing them. For some > time, there has been a stand-alone python3 version of this script at > https://www.msapiro.net/scripts/cleanarch3 (mirrored at > https://fog.ccsf.edu/~msapiro/scripts/cleanarch3) I have just updated > this script to check and optionally fix bad Date: headers. > > I have also added it at > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… > for the next release. > At what point does an MM3 List Admin require this script? I am unable to figure that out :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 months

[MM3-users] Re: Sad news - Brian Carpenter

by Odhiambo Washington

On Wed, May 12, 2021 at 10:45 PM <smorytko(a)gmail.com> wrote: > > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry > from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was > hospitalized with Covid. > I have known Brian for many years mainly from the Mailman lists and he was a great resource. For a while now I have been meaning to check on the HOWTO he was writing for installing Mailm3 on Debian and yesterday I actually wanted to check on it. What a sad turn of events. May his soul rest in peace. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 10 months

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

by Manos Pitsidianakis

Στις 2019-09-19 18:52, Mark Sapiro έγραψε: > No. You referred to "shunted" mails. I assumed that mail was winding up > in the shunt queue, but this is apparently not the case. But they are. Not exactly when or why but they show up in queue/shunt and queue/out at times. (maybe because I used mailman unshunt?) > > This should stop the out runner from "spinning" on these messages. Then > you can examine the files with Mailman's 'bin/mailman qfile' command > and > see if you can identify something in the recipients list or other > metadata that might be causing this. I cannot discern anything in the qfiles. It'd take some effort to deanonymise them for posting here. I've had new posts in the list and they get stuck as well.

6 years, 6 months

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Andreas Barth

Hi Mark, thank you for your help. * Mark Sapiro (mark(a)msapiro.net) [201210 23:26]: > The issue is the code at > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/subscripti…> > appears to not be executed as in my test at least, the workflow continued. Interessting. Here it ended with (current git version) ==> /var/log/mailman3/mailman.log <== Dec 13 23:27:04 2020 (15015) deque: Traceback (most recent call last): File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks MemberRole.member) mailman.interfaces.member.AlreadySubscribedError: t3@$domain is already a MemberRole.member of mailing list t1@$domain This was a "live" run of mailman (however on my testing box). And, however, still no mail. Now I need to think how to continue. Regards, Andi

5 years, 3 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:06 PM, Mark Sapiro wrote: > On 11/11/20 2:11 PM, Brian Carpenter wrote: >> This happened again. Is there a way to get HK to deal with such messages automatically? > > How would you like them dealt with? The issue is in mailman-hyperkitty. > When it's attempt to archive the message returns an error, it queues the > message for retry. It is not clear if any of these errors are actually > retryable - for sure some aren't but maybe others like HyperKitty not > responding are - but even if we think retry won't succeed what would you > like done with the message? > Some sort of auto-discard procedure after a number of retries? Is it possible to detect a message with a null characters and automatically discard them? Do such messages make it into the thread table? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

5 years, 2 months

Search results for query "sapiro"