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

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Mark Sapiro

On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > I have put the following in /etc/mailman.cfg and restart mailman. An empty file can be created but nothing can be logged when admin or non-member subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in mailman.log and smtp.log. Thanks. > > [logging.subscribe] > path: subscribe.log > level: debug The above is correct. As far as not seeing things in the log, very little is logged in the subscribe log. Only (un)subscription requests held for moderator approval and moderator approval of held unsubscribes but not subscribes. In other words, unless your list's subscription police includes 'moderate' nothing will be logged in subscribe.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: mailman shell

by Mark Sapiro

On 1/2/19 7:12 PM, Alan So wrote: > Sorry for my ignorance. May I know what should be imported before using mailman shell within Python? > > $ python3.6 > Python 3.6.6 (default, Aug 13 2018, 18:24:23) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] on linux > Type "help", "copyright", "credits" or "license" for more information. >>>> command = cli('mailman.commands.cli_withlist.shell') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > NameError: name 'cli' is not defined > > Link to documentation: https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht… That's too complicated. Just run mailman shell as a command. If you want to operate on a single list, run mailman shell -l <list_id> Also see mailman shell --details -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/18/20 2:23 PM, Mark Dadgar wrote: > > There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. > ... > Could this somehow be related to my recent migration from sqlite3 to postgres? I think it's quite likely that that migration is involved and your database is now corrupted in some way. Exactly how or in what way, I don't know, but it seems likely to me that that's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 2/5/23 01:13, Odhiambo Washington wrote: > > So in my case, I should at least increase the value of > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? It probably isn't even set in your case and defaults to 900 if it isn't set. Yes, you can set it to a larger value. If your archive search engine is woosh and your archive is even moderately large, 1800 probably isn't nearly enough. There was no indication of timing in your OP, but you should determine when that cron job started and when the error was reported. The difference is the absolute minimum you should set for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin to that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

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

by Mark Sapiro

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 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Help Setting Up Mailman 3 on an Ubuntu Server

by Mark Sapiro

On 9/26/24 12:43, Jeremy Stanley wrote: > > Wow, that one was pretty sneaky. I've been seeing a lot of similar > linkspam attempts on mailing lists I moderate, recreating posts > similar to ones found in archives or in some cases replying to very > old threads, in an attempt to get past moderators. All seem to come > with a whiff of having been composed by a chatbot too. I've resorted > to closely inspecting links in every moderated post lately. Thank you. Usually they are more obvious than that, but that one got by me. I have redacted the link for the digest and in the archive and reset the poster's moderation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: adding personalized email header/content in mailman 3

by Mark Sapiro

On 10/17/24 12:47, Alex I wrote: > Thanks, but no luck. Trying option 1, added custom_header.py file: The below is incomplete. Additions inline. import logging > from mailman.interfaces.handler import IHandler from public import public > from zope.interface import implementer > logger = logging.getLogger('mailman.smtp') # or some other @public > @implementer(IHandler) > class AddCustomHeader: """A doc string is nice" name = 'custom-header' description = 'Some description' > def process(self, mlist, message, msgdata): > """Add a custom email header.""" > message['X-Custom-Header-1'] = 'ABCD' > logger.info('Custom header added to message for list: %s', mlist.fqdn_listname) > > to /opt/mailman/venv/lib/python3.9/site-packages/mailman/handlers/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Cannot issue commands through email

by Mark Sapiro

On 11/9/25 07:38, stonehold(a)thedagora.social wrote: > Thank you so much, Mark. That pointed me exactly where I needed to go. Everything's running nice and smooth. You're welcome. I'm glad you got it working. > Now, you wouldn't happen to know where to look for a halfway decent elist management primer, would you? I'm only half-joking -- I've never run something like this before, so am naturally a bit nervous. There are links to Mailman 2.1 docs that might be helpful. Some settings names are different in Mailman 3, and the GUI is different, but the high level guidance is the same. There is also https://docs.mailman3.org/en/latest/userguide.html, but that is for list members, not admins. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Mark Sapiro

On 2/5/26 06:30, Chihurumnaya Ibiam via Mailman-users wrote: > > Yes, postfix_lmtp table is set in transport_maps, virtual_mailbox_maps, > relay_domains, local_recipient_maps. I'm coming in late here so I may have missed things, but ... If you actually have virtual_mailbox_domains and virtual_mailbox_maps, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > No, I'm not running mailman as root, it's run as mailman. > Seeing as that's the case, would I still need to change lmtp_port? The lmtp_port setting determines what port mailman listens on and what port is in the lmtp: entries in postfix_lmtp. Id should absolutely NOT be the same port dovecot listens on and the default 8024 is a good value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/29/20 3:48 PM, Massimo Zappalà wrote: > Hi Mark, > I sent the IT templates as your requested to your email address. Thank you very much for your contribution. It is much appreciated. See <https://gitlab.com/mailman/mailman/-/merge_requests/677> >>> Is this perhaps a permissions issue. The Mailmanuser needs to be able to >> read them. See https://gitlab.com/mailman/mailman/-/issues/745 > > you could clarify this point better? Where did you put your templates? What does `ls -la /path/to/templates/it` show? I may need more information about messages that are and aren't delivered. I.e. what's different between them and the way they are submitted, or is this one message only delivered to some users? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Search results for query "sapiro"