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

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Mark Sapiro writes: > Actually, there's more involved in the pipeline between the > to_archive and to_outgoing handlers. The to-digest, to-usenet, > after-delivery, acknowledge and dmarc handlers are all invoked > between to_archive and to_outgoing IIRC all of the shunted messages that Stephen looked at with qfiles were those special digest messages (ie, message component empty, pointer to lists/$LIST/something.mmdf in the msg_data component). So something is going wrong in the to-digest handler. I don't understand why the original .pck would disappear without either leaving an error log or delivering. (Hmm, @Stephan, have you looked at your "vette" log? it is a separate log in your mailman.cfg I think.) The number of .tmp files lying around bothers me. AFA grep CS, the only place that can happen is in switchboard.py:136 in .enqueue: with open(tmpfile, 'wb') as fp: fp.write(msgsave) pickle.dump(data, fp, protocol) fp.flush() os.fsync(fp.fileno()) os.rename(tmpfile, filename) where `msgsave` is already a pickled object. So either pickle.dump is choking on something in data (the metadata, which I believe is all primitive Python data types), or something (OOM kill?) is happening at the OS level. A crash in pickle.dump should leave an exception log and backtrace in the logs. AFAIK, Mailman does not clean up .tmp files at startup, right? -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 2 weeks

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 00:51, Mark Sapiro wrote: >> Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> > > Probably because (in Postorius) Settings->Digest->Enable Digests is No Double checked that Enabled Digest s= Yes >> Then, as "mailman", I ran "mailman digests --periodic" manually and >> got the same error (as expected since there is nothing there) ... > This error should not occur if there is no digests.mmdf. It only does > occur because you have set Digest size threshold to 0 under the > assumption that 0 means unlimited which it doesn't. If you don't want > digests sent on size, you need to set Digest size threshold to a very > large number. > > I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid > throwing the exception, but setting the threshold to 0 is still wrong Oh? I was indeed assuming that 0 meant unlimited. The threshold was set at 0. My thinking was that meant the file size was not a factor in determining when the digest was sent and that the sending would be triggered by the daily cron. When I set the threshold very low - 10kB - it sends a digest on every post. So my understanding of what you are saying is: if the threshold is set very large, say 100,000 kB - then a digest will be be sent by the daily cron even if it is smaller than 100,000 kB. Am I understanding correctly?

1 year, 10 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Ken Alker

--On Monday, June 26, 2023 5:26 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 4:19 PM, Ken Alker wrote: >> >> What else is stored in /var/messages, if not archives? I see 4711 >> messages in that directory (which I presume would be as many messages >> are in the archive database). If there is a write-up on this, feel >> free to point me to it. I found >> <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/ >> model/docs/messagestore.html> but this isn't really answering my >> question. > > > These are probably artifacts from your old Debian package. There have > been issues in the past with handled messages not being removed from the > message store. See https://gitlab.com/mailman/mailman/-/issues/257 > > This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes > orphaned messages from the message store, but if they are still > referenced in pendings they won't be deleted. So is the only thing stored in var/messages/ the held messages, and nothing more? Is there an outline as to how to clean up the var/messages hierarchy? (I assume one has to be careful not to remove current held messages and maybe old ones that have not been processed; or maybe "old ones" can all be assumed orphaned, and thus, removed w/o concern?)

2 years, 10 months

[MM3-users] Re: Setting up on ubuntu server 22.04

by Odhiambo Washington

On Wed, Oct 4, 2023 at 3:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > > > However, I cannot find the mailman/setup.py anywhere in order to patch > it, > > since the installation was done through pip from here: > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install > > > Upgrading Python won't help. There is currently an incompatibility issue > when following > https://docs.mailman3.org/en/latest/install/virtualenv.html because that > doc is based on the head of the GitLab branch, but `pip install > mailman3` installs the 3.3.8 released version of core and the latest > 6.1.0 version of importlib_resources and these are incompatible. > > There are two ways to fix this. > > The easy way is to downgrade importlib_resources in your venv with > ``` > pip install importlib_resources\<6.0 > ``` > The slightly more complex way is to upgrade mailman core to 3.3.9b1 from > GitLab with > ``` > pip install -U git+https://gitlab.com/mailman/mailman.git And I think the 'slightly more complex way' is a better choice as it lets one not get stuck with old software versions :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 7 months

[MM3-users] Re: Default moderation for new members

by Seth Seeger

On Thu, Nov 14, 2019, at 9:33 PM, Mark Sapiro wrote: > > > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. > > > In Postorius set Settings -> Message Acceptance -> "Default action to > take when a member posts to the list" to Hold for moderation. > > This is the action which will be taken for a post from a member whose > individual Moderation is List Default as it is for all new members. > > Then when a post from that member is held, if you click the subject in > the held messages view, a dialog opens showing the message content with > Accept, Reject and Discard buttons and a dropdown list you can use to > set that member's Moderation to Default processing. > > Default processing is generally what you want as it bypasses the > moderation hold but still applies other tests such as header filters, > administrivia, implicit-dest, max-recipients, max-size, etc. So I've set my "Default action to take when a member posts to the list" to "hold". I'm just unclear on what I want to set each member's moderation action to... defer or accept? (I've been reading the docs, but I'm not clear on the difference.) Thanks, Seth

6 years, 5 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Odhiambo Washington

On Tue, 28 Jul 2020 at 07:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 6:48 AM, Odhiambo Washington wrote: > > > So now I have tried to see if there is such option from django-admin, > but: > > > > (venv) [root@gw /opt/mailman/mm]# django-admin --help > > > You must run /opt/mailman/mm/bin/django-admin. If you run these commands > in your venv, you run the ones in /opt/mailman/mm/venv/bin which dont > have all the pointers to configuration and settings. It's OK to run > /opt/mailman/mm/bin/* with your venv active, but if you just give the > command name, you get the wring one. > So, I should run /opt/mailman/mm/bin/django-admin with a valid argument, right? Like /opt/mailman/mm/bin/django-admin createsuperuser ... How do I get all the available arguments for django-admin? That is what I was attempting to do by passing --help to it. > You also must have the empty /opt/mailman/mm/__init__py so that imports > of /opt/mailman/mm*.py modules will work as I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > This is quite clear now. Thank you. It wasn't clear at what point in the installation process this file needs to be created. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 9 months

[MM3-users] Re: using SSH/TLS with external MTA

by Odhiambo Washington

On Sat, Jul 27, 2024 at 11:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/24 13:05, Odhiambo Washington via Mailman-users wrote: > > > > ASMTP works on the premise of "we can relay mail for you if we can > > authenticate you with certain credentials" > > Adding the IP to "hosts we can relay mail for" negates the need to > > authenticate, IMHO. > > So I am still waiting for how MM3 does ASMTP. Does it? > > > If by ASMTP, you mean SMTP AUTH, Mailman does it if smtp_user: and > smtp_pass: are provided in mailman.cfg. > > > I agree that an authenticated user should be able to submit mail to be > relayed. Just guessing here, but perhaps the issue is the OP is > submitting to the deprecated port 465 instead of 587. > Port 465 is not quite depreciated. It's the decision of the Admin to decide to listen on/and accept SMTP AUTH on which port. On the servers I run, and based on Exim as the MTA, I accept SMTP AUTH On ports 465, 587 and 2525 (this is meant to subvert some ISPs!). But let's await Roland's response. -- 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, 9 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:53:23 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ > Greetings Mark, I gave up on setting up mailman using option #2 while following https://docs.mailman3.org/en/latest/install/install.html (there are lots of unknowns on that route. Certainly, the packagers are considering a lot of things that are not immediately apparent to users). Perhaps, we will see elaborate guides/docs soon. In the meantime, I moved to option #3 (recommended for production). I hit a grey area when setting up the virtual environment. At https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, I see: $ cd /opt/mailman $ python3 -m venv venv The documentation imply that a 'user' creates the virtual environment but is not explicit about that 'user'. OUTPUT: Error: [Errno 13] Permission denied: '/opt/mailman/venv' This is expected. Which makes me wonder ... hmm, how did you do it? (1) Is it better to have a dedicated user (say 'mailman') then use that while following the docs? I see a lot of docs referring to a 'mailman' user. Installing mailman3 from distribution repository introduced a 'mailman' user to my box (with special UID). There has to be reasons for that. (2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?) (3) How about using an already existing local user? What are the implications? Regards Onyeibo

5 years, 7 months

[MM3-users] Re: How to delete non-users

by Allan Hansen

Sure: >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... >>> Nothing here, either. Yours, Allan On 9/17/22, 10:30 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/

3 years, 8 months

[MM3-users] Re: Footer variables

by Washington Odhiambo

On Mon, Mar 2, 2026 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/2/26 05:03, Washington Odhiambo via Mailman-users wrote: > > On Mon, Mar 2, 2026 at 3:41 PM Stephen J. Turnbull <steve(a)turnbull.jp> > > wrote: >> > >> Have you tried using "$hyperkitty_url" instead of "${hyperkitty_url}"? > >> > > > > I have now removed the curly braces. Let me see what follows. > > > That shouldn't matter. It should work with or without the curly braces. > > Is there anything relevant in mailman.log? Does Mailman have permission > to access > /opt/mailman/mm/var/templates/lists/ > kictanet.lists.kictanet.or.ke/en/list:member:regular:footer.txt? > I will have to check the mailman.log. What should I look for? Right now it looks so clean - without anything to worry about. Yes. all files in /optmailman/ are owned by mailman:mailman In the OP you said "in my posts, it's blank". Do you mean the entire > footer is blank or is it just that ${hyperkitty_url} is replaced with > nothing and the rest of the footer is OK? > Only the ${hyperkitty_url} is replaced with nothing. I suppose there may be another way to get the end result, no? -- 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]

2 months, 2 weeks

Search results for query "sapiro"