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

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

5 months, 1 week

[MM3-users] Re: installation choices for mm3

by Mark Sapiro

On 5/16/19 10:33 AM, John Griessen wrote: > I've been reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > > and see that a virtual is recommended, which is not something I have > done yet, and wonder > if just putting the mm3 on a different server is easier? I am the author of that document. I started with virtualenv because my first Mailman 3 installation used the now obsolete mailman-bundler and it installed things in virtualenvs. It is not at all necessary to use virtualenv. Note that the first paragraph of the "Installation" section in that document says: For these installs, I opted to install the entire Mailman suite in a virtualenv. The biggest motivation for this choice was the fact that there are already production lists on both servers and using a virtualenv allowed me to do a lot of the work in advance without interfering with the production install. Possibly influenced by these experiences, I am now using virtualenv for all installs. There are pros and cons to using a virtualenv. The big plus is it isolates your installation and avoids conflicts due to the installed software requiring versions of dependencies that are different from those that might be installed and required system wide. It also avoids the need to install as root although things like web server and MTA configuration still require root. The downside is a potentially larger footprint in the file system. > I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, > mm2, nsd on it. Another server has just web pages and nsd doing backup > DNS for mail1.cibolo.us DNS server. I could do a straight debian > install of mailman3-full on the 2nd server > and keep it simple, let debian setup a blank database installation, > right? Has anyone seen a good write up on how to do that on a debian > server step by step? I can't speak to the installation of the Debian package. It should be straightforward, but I don't really know. The one potential glitch is if you don't have an MTA on the Mailman server. This is doable. Mailman has it's own LMTP server to receive mail and can be configured to use a remote MTA to deliver mail. Mailman also generates transport mappings to control delivery of mail to Mailman and these get updated when lists are added or deleted. There is a configurable postmap_command which is invoked when the maps are updated to update the .db files. That can point to a shell script to rsync the files to the other server if needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Member Issue Discovered

by Apollinaris Schöll

If this has been implemented already then that’s good. I have not tested with latest. Does this also happen when a user unsubscribes or a list admin unsubscribes? > On Oct 28, 2020, at 1:29 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. > > -- > 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/

4 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I could setup env with python3 and env2 with python 2.7 I visited http://192.168.1.42:8000 in my browser and I could not see the web UI. Should I install WSGI server?? doing: pip3 install uwsgi ??? Thanks El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:44 PM, Rafael Mora wrote: > > I did this: > > > > (env) [mailman@localhost mailman-suite_project]$ pip install Django > > Requirement already satisfied: Django in > > /var/lib/mailman/env/lib/python3.6/site-packages > > Requirement already satisfied: pytz in > > /var/lib/mailman/env/lib/python3.6/site-packages (from Django) > > > > > > Does Django is already installed?? with python3.6 ??? > > > Your 'env' vitrualenv is a Python 3 virtualenv. You need this for > Mailman core, but Django and mailman-suite are Python 2. They need to be > installed and run in a Python 2 virtualenv. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: lmtp runner not starting

by Mark Sapiro

On 4/1/23 12:44, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I get the same error as before: Did you post this traceback before? If so, I missed it. > root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c > "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r > lmtp" > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector > Traceback (most recent call last): > File "/usr/local/bin/runner", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', > 'runner')()) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1128, in __call__ > return self.main(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1053, in main > rv = self.invoke(ctx) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 1395, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/usr/local/lib/python3.9/site-packages/click/core.py", line > 754, in invoke > return __callback(*args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/click/decorators.py", > line 26, in new_func > return f(get_current_context(), *args, **kwargs) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 184, in main > runner = make_runner(*runner_spec, once=once) > File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", > line 70, in make_runner > return runner_class(name, slice) > File > "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line > 295, in __init__ > self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, > port=port) > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 417, in __init__ > self._localhost = get_localhost() > File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", > line 66, in get_localhost > with makesock(AF_INET6, SOCK_STREAM) as sock: > File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ > _socket.socket.__init__(self, family, type, proto, fileno) > OSError: [Errno 43] Protocol not supported > The issue is in aiosmtpd which is trying to determine if it can use IPv6 "::1" for localhost. It does this before it checks if we've provided a hostname which we have. The issue is in aiosmtp/controller.py in the get_localhost() function, but it's even deeper than that in socket which is raising the Protocol not supported error. There is something strange on your server in that IPv6 seems to be only partially supported. I don't know for sure what the underlying issue is, but look at https://github.com/aio-libs/aiosmtpd/blob/master/aiosmtpd/controller.py#L49 Find aiosmtpd /controller.py in your venv/lib/python3.?/site-pacakages directory and change that return has_ipv6 line to return False to work around the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Hyperkitty failure?

by Stephen Daniel

Thanks! The thread pointed to at the end of your email, specifically replacing the base URL with http://127.0.0.1:8000/archives did the trick. On Thu, Feb 24, 2022 at 1:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/24/22 09:24, Stephen Daniel wrote: > > > > In the log I see messages that look like this: > > > > Feb 24 11:43:44 2022 (28621) HyperKitty failure on > > https://lists.example.com/archives/api/mailman/archive: <html> > > <head><title>401 Authorization Required</title> > > > What are the exact versions of HyperKitty and mailman-hyperkitty > HyperKitty >=1.3.5 requires mailman-hyperkitty >=1.2.0. Earlier versions > of HyperKitty require earlier versions of mailman-hyperkitty. > > If you have HyperKitty >=1.3.5 and > mailman-hyperkitty >=1.2.0 there is a thread on this at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > See the last two posts in that thread. > > -- > 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, 6 months

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 11:00 AM, Mark Dadgar wrote: > On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >> everytime I receive a mail for moderation it says: >> >> At your convenience, visit your dashboard to approve or deny the >> request. >> >> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. There's no overall dashboard per se. The message actually refers to whatever web UI you use to manage the list. The default template for this message is non-specific because it comes from Mailman core, and core doesn't know if you are using Postorius or some other web management system or non at all, and even if it were to assume Postorius, it doesn't know the URL. >> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >> >> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? As I said, there is no overall dashboard in Postorius, just the individual list management pages. > This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. I explained above why this is the case, but you can fix it. You do so by making a sitewide template for this message. In the case of this list, we have a template in Mailman's var/templates/site/en/ directory (the default directory for sitewide english templates. This template is named list:admin:action:post.txt and its content on this site is: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: $listname > From: $sender_email > Subject: $subject > > The message is being held because: > > $reasons > > At your convenience, visit > https://lists.mailman3.org/mailman3/lists/$list_id/held_messages Of course, in your case the <https://lists.mailman3.org/mailman3/> part of the URL will be different. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> for the other templates I also install. You can also put domain specific templates in var/templates/domains/$domain/$lc/ which override site templates for the domain and list specific templates in var/templates/lists/$list_id/$lc/ which override site and domain templates for the list, and you can also set list templates via Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: why owner mails rerouted to list

by Mark Sapiro

On 10/22/19 2:20 AM, Tamas HOLCZER via Mailman-users wrote: > Hi All, > > we have moved to Mailman3 from Mailman2 recently, and have a quite > strange problem: > > Every message sent to owners is forwarded to the lists instead of the > owner's mail address. ... > We are using GNU Mailman 3.2.1 (La Villa Strangiato) from the Debian > Buster repo. As MTA we use exim4 (running on the same machine as > Mailman), and have Amavisd on a separate machine for spam filtering. This may be an exim configuration issue. You can stop the mail from being delivered to the list by ensuring the Postorius Settings - Message Acceptance -> Acceptable aliases is empty and Settings - Message Acceptance -> Require Explicit Destination is Yes. This will cause the messages to -owner, etc to be held. First ensure exim, particularly the router for list messages is configured as in <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim4-co…>. > From MYLIST-bounces(a)MYDOMAIN.COM Mon Oct 21 21:13:59 2019 > Return-path: <MYLIST-bounces(a)MYDOMAIN.COM> > Envelope-to: MYADDRESS(a)MYDOMAIN.COM > Delivery-date: Mon, 21 Oct 2019 21:13:59 +0200 > Received: from [SPAMFILTER] (helo=localhost) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7u-0007pv-VR; Mon, 21 Oct 2019 21:13:59 +0200 > X-Virus-Scanned: by amavis-dc > Received: from MAILSERVER.MYDOMAIN.COM ([MAILSERVER-LOCAL-IP]) > by localhost (spamfilter.MYDOMAIN.COM [SPAMFILTER]) (amavisd-new, port 10023) > with ESMTP id Pe6CPG7d_0VR; Mon, 21 Oct 2019 21:13:57 +0200 (CEST) > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7t-0007pn-Mu; Mon, 21 Oct 2019 21:13:57 +0200 It seems the issue occurs here. The Received: header below is the receipt of the message from Mailman to MYLIST-owner. That header clearly says the envelope recipient is MYLIST-owner(a)MYDOMAIN.COM. Then the header above looks like the delivery of the message from the Mailman list to one or more list members. What we don't see is the intermediate step of LMTP delivery of the message to Mailman's LMTP server. That delivery must have had envelope recipient MYLIST(a)MYDOMAIN.COM rather than MYLIST-owner(a)MYDOMAIN.COM I think what's missing is `rcpt_include_affixes = true` in the exim transport for Mailman. > Received: from MAILSERVER2.MYDOMAIN.COM ([MAILSERVER-PUBLIC-IP] helo=MAILSERVER.MYDOMAIN.COM) > by MAILSERVER.MYDOMAIN.COM with esmtp (Exim 4.92) > (envelope-from <MYLIST-bounces(a)MYDOMAIN.COM>) > id 1iMd7r-0007pR-JZ > for MYLIST-owner(a)MYDOMAIN.COM; Mon, 21 Oct 2019 21:13:55 +0200 > From: MYLIST-owner(a)MYDOMAIN.COM > To: MYLIST-owner(a)MYDOMAIN.COM -- 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

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/24/23 9:54 PM, Ken Alker wrote: > I am working on a mail server that was migrated from mailman V2 to > mailman V3 in February. I just noticed that there are over 1000 > messages in the bad queue. All of the messages in the bad queue are > dated 2/2/23 and all have a timestamp within a one-hour window of each > other. > > I used mailman qfile to inspect five random emails in the bad queue and > so far they are all "successfully subscribed" emails, This is a bit strange. See below. > but I presume > there are no guarantees there aren't others mixed in there that might be > legitimate emails (ie. I just unshunted 140 emails in the shunt queue > and they were all good emails and all got processed). Presumably these were shunted due to some issue that was subsequently fixed. > I figure that the easiest way to inspect these 1000 emails is just to > have them re-delivered. I tried moving one from the bad queue to the > shunt queue and I ran "mailman unshunt" but nothing happened. What does nothing happened mean? "mailman unshunt" should move the message to the original queue which was stored in the 'whichq' attribute in the msgdata when the message was shunted. Since this wasn't a shunted message, there's no 'whichq' attribute so it goes to the 'in' queue. I.e., "mailman unshunt" would have moved the message from the 'shunt' queue to the 'in' queue. If the message wound up back in the shunt queue, there should be messages in mailman.log indicating why. > Is there a way to reprocess the bad queue? You could just move the messages to the 'in' queue. > Also, what exactly is the bad queue? If Mailman's content filtering is enabled and Filter Action is Preserve, messages which have no remaining content after content filtering are put in the 'bad' queue. These are the only messages put there. When this happens there should a log message like <message-id> preserved in file base <queue_file> It is unclear to me how these 1000+ messages wound up in the 'bad' queue. If you have logs from Feb 2, they might help. My guess is there was some MTA misrouting that caused these list welcome messages (from some mass subscribe?) to be rerouted to the list posting address combined with some bad content filtering settings that removed all the content, but that seems pretty far fetched. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Stefan Bauer

Mother: Anonymous list: No First strip reply to: No Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Daughter: Anonymous list: No First strip reply to: Yes Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Am Mi., 24. Nov. 2021 um 21:53 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/24/21 2:05 AM, Stefan Bauer wrote: > > That is already set. No change. > > This completely removes the reply-to: header and sets the iu-all > > list-address as new and only reply-to. > > > What are your current settings on both the mother and daughter lists for > Anonymous list, First strip reply to, Reply goes to list and under DMARC > Mitigations for DMARC mitigation action and DMARC Mitigate unconditionally? > > > -- > 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, 9 months

Search results for query "sapiro"