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

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Odhiambo Washington

On Mon, Jan 30, 2023 at 12:39 PM Onyeibo Oku <onyeibo(a)schemefusion.com> wrote: > > On Tue, 3 Jan 2023 09:46:00 -0800 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > This is all configured in your web server. It needs to proxy requests > > for lists.website.tld to gunicorn and depending on the web server, > > may need more. E.g. see > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > > for nginx. > > I have fixed this. > > > > > > Set SITE_ID = 0 in your Django settings. Also see > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Actually "SITE_ID = 1" solved that instead. I also had to go into the > database and update the values (django provided 'example.com' by > default and that was problematic). > The common practice I have see is that one creates their domain on the web interface, which then displays the SITE_ID = N. You then take the value into settings.py to replace the one that's there. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Washington Odhiambo

On Sun, Jan 25, 2026 at 12:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/24/26 02:35, Washington Odhiambo via Mailman-users wrote: > > > > I am not trying to export any threads at all. I haven't tried doing it > for > > whatever reason. > > So the fact that there is even an attempt at exporting it is strange. > > > All the errors in your OP result from an attempt to get > > https://lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/ex…<thread-hash>.mbox.gz > > with various thread hashes. > > Check your web server logs and the log at > /opt/mailman/mm/var/logs/access.log. There may be accesses from some bot > or ?? or possibly these are things generated by qcluster. Check things like > > mailman-web qinfo > mailman-web qmemory > mailman-web qmonitor > I have dealt with the bots at the Nginx level for now. -- 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]

3 weeks, 5 days

[MM3-users] converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

I have been instructed by Mark Sapiro to subscribe to this list to post questions related to mailman3. On Mon, 31 Jan 2022, Mark Sapiro wrote: > On 1/31/22 06:20, Lucio Chiappetti wrote: >> One of the lists of which I am a co-moderator has been moved from >> mailman 2 to 3. Actually the migration has been made operative yesterday (and so we got the first problems ...). Basic background. There are a number of lists within my institution (a nationwide research institution with many seats across our country), some are institutional (all staff subscribed ex officio) and managed by staff in one seat, some other are non-institutional (subscription is optional) and are managed by a few volunteers in other cities different from the seat where the mailman server runs. > In particular, the list settings for *_these_nonmembers are at Settings > -> Message Acceptance, but these settings in particular are deprecated > in Mailman 3 except for regexps. In Mailman 3 the preferred way to say > accept a nonmember is to create a nonmember for that user and set it's > Moderation action to Default Processing. If, a nonmember posts, the > nonmember record is automatically created, Let me explain our case, and how it was managed in mailman2. - originally our staff (of the order of 1000) had addresses like user(a)place.inaf.it or user(a)place.astro.it. Some had even two (say place1.inaf.it and place2.inaf.it), so they subscribed with ONE of their work addresses - later we got addresses like name.surname(a)inaf.it. New users subscribe with this address but MANY of the old ones continue to use the PREVIOUS address. - we implemented a spam filtering policy as follows: - staff (and former staff) can SUBSCRIBE with any address or CHANGE their address. Any subscribed address will be recognised. Mail is NOT held in moderation unless too bulky, or has undisclosed recipients - mail from non members with any address in the .it TLD or in the tng.iac.es domain (where some of our staff work) goes into moderation (this is achieved via regexp in hold_these_nonmembers) - anything else is silently discarded as spam (generic_nonmember_action = discard) - when some staff posts from a non-subscribed address (be it the home address, or one of the alternate addresses described above) it therefore goes into moderation because of hold_these_nonmembers - in mailman2 we could let them pass "manually" (if we recognised the person) or (in case they used an alternate address) tick to add them permanently to accept_these_nonmembers (in one tick) - at the end we got somehow fed up of this but we did NOT want to accept any address of the form ^.+@.+\.inaf.it (which could be forged) but found that we could simply put in accept_these_nonmembers two entries like @list1 @list2 where list1 and list2 are two institutional lists on the same server which contain all permanent and temporary staff or assimilated with their official address (these lists are automagically generated each week) (so at least any VALID EXISTING official address is accepted) What I found now (after the migration done by the administrators of the central seat) is that in mailman3: - accept_these_nonmembers is empty - there are 189 entries listed in Non-members (which look those formerly in accept_these_nonmembers) - hold_these_nonmembers was copied identical with the same regexp's as in mailman2 - I have inspected a few of them and found that they have Administration options Moderation set to List default - the effect of this apparently was that a post from some.guy(a)inaf.it (whose subscription address is guy(a)somewhere.inaf.it) was hold for moderation is this due to a loop with the regexp in hold_these_nonmembers ? the default action would be to let it pass Or should we set Administration options Moderation to Accept immediately ? - if so, how can we do it automatically for all 189 entries ? - or move back the 189 addresses to accept_these_nonmembers ? - or for the future have persons posting with alternate addrresses accepted for the future WITH ONE CLICk ? - AND LAST BUT NOT LEAST would the syntax @list1 in accept_these_nonmembers work in mailman3 ? already putting it back will save a lot of work. Many thanks -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ "All that is google does not glitter Nor all who use alpine/procmail are lost"

4 years

[MM3-users] Re: Mailman messages are getting a TAG in some email clients.....how????

by Guillermo Hernandez (Oldno7)

El 12/9/23 a las 19:43, Mark Sapiro escribió: > On 9/12/23 8:51 AM, bob B via Mailman-users wrote: >> So I know about the setting "Anonymous list" but regardless of that >> setting some email clients put the list name in [] when it displays >> messages in your inbox. Does anyone know how email clients are doing >> this? I have users who email clients do not do this, and was >> wondering if it is a setting in their client or just not possible. > > > This looks like Mailman adding 'Subject prefix', so all list mail will > have this prefix added to the Subject:. So the question isn't how mail > clients are adding it, but rather why do some mail clients suppress it. I think the simple answer is that some mobile mail clients don't show the subject line by default, you have to click to show it explicitely. That users just don't see that. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 5 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Sebastian Hagedorn

--On 17. Juli 2018 um 22:04:12 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/17/2018 07:27 PM, Joe Steeve wrote: >> >> I have an installation on SQLite. I want to migrate it to PostgreSQL. Is >> that feasible? Any gotchas I need to watch for? > > > It is feasible. > > You would need to stop Mailman core and all Django processes including > cron jobs and WSGI processes to ensure nothing is accessing the SQLite > database, update the database section in mailman.cfg and the DATABASES > settings in your Django settings, use SQLite tools to dump the relevant > database(s) and PostgreSQL tools to create and load them, and finally > restart Mailman core and all Django processes. I have only now started playing around with Mailman 3.2, because I never managed to get the earlier releases to work, and reading through the documentation I thought that such situations could be handled with Alembic, as described here under "Database Migrations": <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> Is that not the case, and if not, in what cases can or should it be used? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

7 years, 7 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 18:37, Mark Sapiro wrote: > On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to remove all non members from a list. I know I can do it via >> Postorius, but it has to be done one at a time. (you can delete ALL >> suscribers but not all non members...) >> >> Anyone has a python recipe to do this? > > $ /opt/mailman/mm/bin/mailman shell -l list.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 list.example.com mailing list > >>> for nonmember in m.members.nonmembers: > ... nonmember.unsubscribe() > ... > >>> commit() > Thanks a lot for the promt response, Mark. It's not functioning. It says: "AttributeError: 'MemberRoster' object has no attribute 'nonmembers'" My system info is: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius 1.3.4

4 years, 6 months

[MM3-users] Re: config incoming email in my domain cpanel

by tlhackque

On 03-Aug-17 17:14, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > You've said you're working with labbrands.com <http://labbrands.com>. > > labbrands.com <http://labbrands.com> has address 192.185.51.89 > mail.labbrands.com <http://mail.labbrands.com> has address > 192.185.51.89 > www.labbrands.com <http://www.labbrands.com> is an alias for > labbrands.com <http://labbrands.com>. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com <http://lists.labbrands.com> has address > 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > image.png > > Is it correct??? > No. And sending images to the mailing list doesn't get you help. You set up lists.labbrands.com as a secondary server, not an independent mail domain. This will cause you serious grief. You need to get some help from a more suitable list. Setting this up is not mailman-specific, and getting it right is more than a quick note. Try the Postfix documentation & mailing lists. > > > And the SPF > records ... and spam and virus filters, and all the other stuff > you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com <http://mail.labbrands.com> > set up as the MX record for > >> labbrands.com <http://labbrands.com>. And it has an A record > with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a > local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers > on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on > your MTA, > >> you would need to relay to your internal server. And make sure > your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > Aug 2017 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport > unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot > easier to > >> manage unless you have a really big operation. Postfix is > probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more > general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if > you want the > >>>>>> web UI (Postorius and HyperKitty) accessible from the > outside, port 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator > hosting, because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, > so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to > the Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > >>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 6 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Per Jessen

Mark Sapiro wrote: >> diff --git a/src/mailman/runners/lmtp.py >> b/src/mailman/runners/lmtp.py index 6a0bdcf5e..eca474089 100644 >> --- a/src/mailman/runners/lmtp.py >> +++ b/src/mailman/runners/lmtp.py >> @@ -217,6 +217,8 @@ class LMTPHandler: >> slog.debug('%s subaddress: %s, queue: %s', >> message_id, canonical_subaddress, >> queue) >> status.append('250 Ok') >> + if queue == 'bounces': >> + config.switchboards['bad'].enqueue(msg, >> msgdata) >> except Exception: >> slog.exception('Queue detection: %s', >> msg['message-id']) config.db.abort() > ``` > will add all received bounces as queue files to var/queue/bad/ where > they can be examined with `mailman qfile`. Thanks. Yep, I'm getting NDRs kept now. "mailman qfile" seems to be a bit slow, 2-3 seconds per go. To look for a specific address that bounced, is there any mailman tool for grepping through a collection of bounces? (I have +1200 after a few days). I'm trying with this: find /var/spool/mailman/bad -type f -name \*pck |\ while read m do (mailman qfile $m | grep -q ad.dr@ess) && echo $m done Is there a better way? -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

4 years, 11 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Tue, 25 Oct 2022 14:46:06 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/22 12:56, Onyeibo Oku wrote: > > > > I must be missing necessary policy modules for mailman or I am > > missing relevant parts of the tutorial that deals with SELinux. > > Where do I go from here? > > > Create the necessary SELinux rules to allow `mailman` to access what > it needs to. Roger that. There is progress beyond the previous report (after setting mailman_lock_t on '/opt/mailman/mm/var/locks'. Systemd fails again on '/opt/mailman/mm/var/logs/mailman.log' I applied mailman_log_t SELinux policy to that folder. Unlike the previous AVC, that didn't fix it. PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/logs/mailman.log' AVC avc: denied { append } for pid=774 comm="mailman" name="mailman.log" dev="sda" ino=2070696 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:mailman_log_t:s0 tclass=file permissive=0 > > I don't know if anyone on this list can help you with that. > > Note that if `mailman` is currently a `normal user` as opposed to a > `system user` making it a system user might help. See `man usermod` > Mailman user is a System User here. Regards Onyeibo

3 years, 3 months

[MM3-users] Re: list of subscribers

by Simon Hanna

On 02/04/2018 01:45 PM, Peter Münster wrote: > On Fri, Feb 02 2018, Mark Sapiro wrote: > >>> Yes, the question is rather: where can *normal* members (or moderators) >>> can see the subscriber list? >> Currently, they can't. If you think they should be able to, you can file >> an issue at <https://gitlab.com/mailman/postorius/issues/new>. > Thanks. Done. > > It seems, that even the owner of the list cannot get the full names of > the subscribers, only the email addresses. Is there any other > possibility for the owner (or the site admin) to get the subscriber list > with full names (perhaps with some Python scripting)? You should be able to use mailmanclient to get a list of subscribers with names. Names are optional though, if people signup without them you won't be able to get them. Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated. IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...

8 years

Search results for query "sapiro"