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

[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"

3 years, 10 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, 8 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, 1 month

[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...

7 years, 10 months

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:06 AM, Mark Sapiro wrote: > On 10/11/20 7:41 AM, Brian Carpenter wrote: >> Does the import21 script also import custom templates? > No. > > >> Are these custom >> templates contained in the config.pck file? > No. They are in the same MM 2.1 directory as the config.pck, but in a > sub-directory for the language code, i.e. lists/LISTNAME/LC/ > > >> Are there any known issues >> with the importing of mm2 templates into a mm3 environment? > > The replacements are different. i.e., things like %(email)s and > %(listname)s become $user_email and $short_listname. > > Also, there are some MM 2.1 templates that have no MM 3 equivalent. > Also, things like message and digest headers and footers that are MM 2.1 > list attributes that are templates in MM 3, although import21 tries to > handle those. So are how these templates showing up on my Mailman 3 servers? They show up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client whose old footer template from Mailman 2 still showing up in list messages. He then created a custom footer template via Affinity (same thing happen in Postorius) and both custom footers were being included in list messages. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 14/2/21 2:42, Abhilash Raj wrote: > You can actually translate the templates in Weblate too. That is > actually the whole > reason to go with monolingual template format in Mailman Core. > > Mailman uses the template file's name as the msgid for translations > and all in-tree > templates are copied into English's .po file when we re-generate them. > > For example in here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > The english .po file is considered as reference in Weblate and used > for source string. I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something. Can you, please, point me in the right direction on how to do it?

4 years, 9 months

[MM3-users] Re: Setting up From: field as list address

by Steven Maddox

Hey, Thanks Mark... found that about 2 minutes after I sent this in :) If you ever get a 'moderator waiting approval' reply when sending into a mailman list... don't suppose there is some magic command you can send into the list to cancel off a pending e-mail? :D Steven Maddox Lantizia On 25/11/2019 15:30, Mark Sapiro wrote: > On 11/24/19 11:54 PM, Steven Maddox wrote: >> Hi folks, >> >> I'm trying to configure our mailman3 lists (via postorious) in a way >> that'll mean they'll behave in the way way that I've witnessed on >> another 3rd party list (one running mailman2). >> >> This is where (when receiving a message from the list) the From: is the >> list itself, and the person who actually sent it bizarrely appears as a >> CC:, for example... >> >> From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> >> Subject: [Shropshire LUG] Whatever >> To: shropshire(a)mailman.lug.org.uk >> CC: s.maddox(a)lantizia.me.uk > > > Go to Settings -> DMARC Mitigations and set DMARC mitigation action to > "Replace From: with list address" and DMARC Mitigate unconditionally to Yes. >

6 years

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:21, Mark Sapiro ha scritto: > On 2/28/21 10:17 AM, blackout69 wrote: > It looks to me like a race condition of some kind or possibly an > incompletely deleted thread. Have you deleted any threads? I have not deleted threads > I'm curious as to how you happen to be going to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> > as opposed to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. > I know that ULS and similar ones are in HyperKitty's urls.py, but I > don't see them exposed on any pages. > > Anyway, when you say "from that moment the maiilan3 has stopped > working." (sic) exactly what stopped working. Did core stop delivering > messages? Did Postorius stop working. If so, this all may be related to > some underlying database issue or something like that that was fixed by > the restarts. I don't see how this HyperKitty error could affect > Postorius or Mailman core. When I say that it stops working, I mean that all members of the lists no longer receive messages. Postorius and Hyperkitty continue to work blackout69

4 years, 9 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, 4 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 11:06 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 2/16/21 9:59 PM, Mark Dadgar wrote: >>> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >>> >>> Error messages below. >>> >>> rebuild_index fails with the same error. >>> >>> This is with django version 3.0.12. >> >> >> django.utils.six was removed in Django 3.0. See >> <https://pypi.org/project/django-utils-six/> for a work around >> replacement. I.e. in your venv do >> >> pip install django-utils-six > > > OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. One last note on this for the next person who searches the list archives: I also ran into the “Key too long” error while re-indexing. Applying the patch linked here fixed it: https://gitlab.com/mailman/hyperkitty/-/issues/322 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

Search results for query "sapiro"