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

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Mailman 2 made this so easy and Mailman 3 made it impossible. I > will let someone else file the bug report. You don't really think that > this is an issue which means it will be years before it is addressed. So > I will save me some time. I will learn to live with it. I didn't say I didn't think it was a real issue. I mostly questioned whether a new subscription should change an existing display_name. I agree that there should be a way for a user to change the display_name associated with her address. I'm not so sure about a list admin. And in any case, I'm only one person. I'm not the only one deciding what's important and what's not. I only decide what I want to work on, not what anyone else thinks is important or wants to work on, so even if I think something is not worth doing, that doesn't mean it won't get done, and once again for emphasis, I do thing a user should be able to change the display name associated with her address(es). Mailman 3 is totally different from Mailman 2.1 in this respect. Mailman 2.1 had no concept of user. All it knew was addresses subscribed to lists and an address subscribed to one list had no connection to the same address subscribed to another list or being an owner or moderator of a list. Mailman 3 does have a concept of user and addresses belonging to a user. This complicates things in some ways. In Mailman 2.1 we could have "The Boss <user(a)example.com" as a member of one list and "Just a Peon <user(a)example.com>" as a member of another list. In Mailman 3 that is not possible unless the addresses are tweaked in some way to make them different. You don't seem to be concerned about the case where I subscribe to a second list with a different display name and am surprised to find my display name changed on the first list, but it's something that I have to consider. As far as filing or not filing an issue, issues in the GitLab trackers are how we track these things. Threads on mailing lists are appropriate for discussion of issues, but if something is going to get changed or fixed, an issue in the tracker is the way to ensure it doesn't get put aside and forgotten. If this is as important to you as it seems to be, please file the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Stanisław Findeisen

Thank you for your clarification. I am now wildcard (*) DKIM-signing the (arbitrary) From: address domain with the host domain key. However my mailing list is a virtual host (actually there are several of them), which is different than the host domain. Do you know if such a setup is harmful? Or if there is a way to select the VHOST key? This is Postfix + OpenDKIM. With DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = Yes the VHOST key gets selected, which also results in (existing and) valid DMARC. Perhaps this setup makes it easier to pass through the spam filters?... But the cost is the abused From:. Thank you Stanisław On Sat, Mar 12, 2022 at 12:49:38PM -0800, Mark Sapiro wrote: > On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: > > > Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your > > > valid DKIM signature and no prior Authentication-Results:. > > > > Ok, you mean after replacing the From address with the list address, right? > > I can see no way (or sense) to DKIM sign arbitrary From: addresses. > > > Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. > validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. > > If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we > have DMARC mitigations suck as replacing the From: with the list address. > > > > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). > > > And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you > shouldn't need to rewrite From:. If it is because of DMARC, you do. > > > > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? > > > This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. > > We DKIM sign all outgoing mail from lists.mailman3.org. > > -- > 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, 1 month

[MM3-users] Member name management by list owner

by mark＠suburbia.org.au

Bottom line up front: site admins can do some of the things below via https://example.com/mailman3/postorius/users thanks to https://gitlab.com/mailman/postorius/-/issues/403 - I am going to include my original post, in case it helps for visibility should others come up against this in future: -- Continuing in my initiation in the MM2.1 -> MM3 migration. I will say that while the software overall seems good, and the support in here has been excellent. I don't recall a more frustrating experience migrating a service in a long time. One of my list moderators runs a closed list for their non-profit organisation, whose demographic is on the more 'wise' side of life. As such, the organisation's committee pretty much handles all the list management for members, who receive a distribution list newsletter. They don't promote the ability to subscribe/unsubscribe/manage list settings to their membership as for some, replying to emails can seem complicated. It's been seen, (and based on the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… appears to be expected) that once an email address is first associated with mailman3, that whatever that member's name is sticks, including if the name wasn't initially used. And, that if you want to change it, you need to have the member login to/created an account at https://example.com/mailman3/user-profile/. E.g. if I as list owner/admin: 1) Add via mass subscription a new member whose email has never been seen by Mailman3 before `Wrong Name <specificemail(a)example.com>` 2) Search members and see it listed as `"Wrong Name" <email(a)example.com>` 3) Unsubscribe the member from the list 4) Add via mass subscription a same member with a new name `Correct Name <specificemail(a)example.com>` When I look at the members list it still shows `"Wrong Name" <email(a)example.com>` If I'm mistaken about any of the above or that does seem like a bug, feel free to let me know. Otherwise, is there any way, without expecting the members themselves to do it, for a site admin or list admin to change the name associated with an email address? I guess in order of preference, I'd like 1) list owner/admin to be able to modify list member name through web UI 2) site owner/admin to be able to modify list member name through web UI 3) list or site admin to be able to modify list member name through command line 4) direct editing of the mariaDB database. (And if this is the best option for now, if you can tell me the name of the db/table to look at it would be appreciated) -- Back to post BLUF solution - I guess my next ask, since the site admin can modify any user's name - would it be possible for me to grant a list owner/admin the ability to change names of any user without giving them full site admin access, and perhaps add the `Manage` button to the list's members list for them?

4 months, 3 weeks

[MM3-users] [Mailman-Users] Mailman 3 Ready?

by Stephen J. Turnbull

Reply-To set to mailman-users(a)mailman3.org. Allan Hansen writes: > I need to upgrade from Mailman 2.1 - my hardware needs upgrading > (badly) and the address mangling is having my subscribers rip their > hair out. That's not going to go away. We have ARC support in Mailman 3, but (a) like most envelope manipulation, that should be done in boundary MTAs, not in Mailman, and (b) ARC implementation is not universal. *Very likely* some of your subscribers are going to lose mail if you depend on ARC, rather than munge from. > I need to get this done before they start on my already thinning > hair! I sympathize. I tell the little kids I meet that my hair grows out of the bottom of my face, not the top (it's very alliterative in Japanese[1], the kids frequently don't get it but the accompanying adults usually laugh). > I’m ready and eager to move on to MM3 on a Linux box. The obvious "turn-key" installation is to use the Docker containers, which Abhilash keeps fairly up-to-date. But see comment below about universal working solutions. Which distro do you have? Are you using the distro's packages of Mailman 3 (not yet a good idea, unfortunately), or installing from source? > I have looked into it a few times now and I keep running into the > same blocks. I don't see much moving either. I was hoping someone > (Mailman developing community) would come up with a better working > solution. It's email. There are no universal working solutions. > [Some third party wrote:] My concern is that the Mailman3 is not > ready. There are too many dead ends and undocumented stuff. Who is this guy and has he consulted us? I'd like to do an archive search if he's done so to see what the issues are. > For Mailman2 I have a working integration with iRedMail, that does > not seem to work with 3. What's iRedMail? How does it fit into the community your lists serve? > So, is MM3 ready for the big screen? Works for us, for values of us including python.org. > If so, is there some way/how/where/when that my friend can get help > helping me with the installation other than the published > installation docs, which did not work for us? mailman-users(a)mailman3.org is the Mailman 3 version of this list. If your friend is the type to get his hands dirty with code, and has the time for development activity, mailman-developers(a)python.org would also be useful. You might be better off getting bids from consultants. There's a page listing them on wiki.list.org. > I have looked for both free and commercial alternatives to MM, There are sites that support MM commercially. I think the prices are reasonable, of course YMMV on that. Again, there's a page for those services on wiki.list.org. Footnotes: [1] "hage dakara hige o" -- the vowels are pronounced as Spanish or Italian, the consonants as in English.

5 years, 4 months

[MM3-users] Re: Error on timeout vs retry values

by Andrew Hodgson

Hi. I just received the same error this evening when rebuilding Mailman3 on a new Debian 11 instal. There is a later version of Django on the new install. I got the original settings from the Mailman-Suite Gitlab project. I have made the modification but does this need to be made in that Gitlab project as well as that is where a lot of folks are getting their base Settings.py from? Thanks. Andrew. -----Original Message----- From: Robert Moody <robert(a)kneedrag.org> Sent: 18 July 2021 22:35 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Error on timeout vs retry values Thank you, that's fixed it. On 19/07/21 7:28 am, Abhilash Raj wrote: > > On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >> Hi everyone, >> >> I have recently setup a new mailman3 service using the venv method. >> Everything is functionally working however I keep getting an error >> sent to the mailman email every min which I can not seem to figure out why. >> >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >> UserWarning: Retry and timeout are misconfigured. Set retry larger >> than timeout, >> failure to do so will cause the tasks to be retriggered >> before completion. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry for details. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry >> for details.""" >> >> I have edited the timeout and retry values in the >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file >> and restarted both mailman and mailman-web however this still keeps repeating. > You shouldn't edit files in `site-packages` directory as they are part > of the package itself and could cause issues. > > What you want to do is override it in your settings.py (or > settings_local.py) file for Django. I am not sure which guide you > followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). > > It should look something like this > > > https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web > .settings.mailman.Q_CLUSTER > > Just the value of retry should be just > than timeout as the error > says, so not necessarily same values, but so far 300 and 360 has been > working good for us and I haven't seen any report to increase them. > > >> Any ideas? >> >> Regards, >> >> Robert >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> _______________________________________________ >> 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/ >> > _______________________________________________ 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, 7 months

[MM3-users] Re: OperationalError: database is locked

by Sten Aus

Hi I've had this problem when mailman was importing new lists (I had script running) and I wanted to access those lists. I am using sqlite as well. Sten On 11/01/2018 11:21, cyp(a)trojina.si wrote: > On our installation, we are often gettting Internal Server Error (500). The logs look like this: > > ERROR 2018-01-09 13:52:57,640 1604 django.request Internal Server Error: /hyperkitty/list/test(a)seznami.cjvt.si/ > Traceback (most recent call last): > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/exception.py", line 42, in inner > response = get_response(request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response > response = self._get_response(request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/HyperKitty-1.1.0-py2.7.egg/hyperkitty/lib/view_helpers.py", line 133, in inner > mlist = MailingList.objects.get(name=mlist_fqdn) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/manager.py", line 85, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 379, in get > num = len(clone) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 238, in __len__ > self._fetch_all() > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 1087, in _fetch_all > self._result_cache = list(self.iterator()) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 54, in __iter__ > results = compiler.execute_sql() > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/sql/compiler.py", line 835, in execute_sql > cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute > return self.cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/utils.py", line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute > return self.cursor.execute(sql, params) > File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 337, in execute > return Database.Cursor.execute(self, query, params) > OperationalError: database is locked > > Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…) but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? > > Thanks in advance! > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 3 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > On 13/2/21 20:00, Mark Sapiro wrote: > > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > But... here is a thing that I can not understand: If the source (the > > > .po > > > file) is from november 7th, it doesn't matter how many times you > > > recompile it: the result will be the same. > > Correct, but the point is if you download the latest > > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 > > file > > in the distribution, you will find they are identical, so it it appears > > that the weblate translation hasn't changed since that time. > > > > If there are issues in this mailman.po, they exist in weblate too and > > need to be fixed there. > > That clarifies all. Thanks. As I said in my previous message, I'll wait > for the next upgrade and hopingly the translations done after 7h of > november (by others and me) will be there. I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version. Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-) > > Also note that the translations on weblate only affect strings in the > > core code. The Mailman core templates are not currently translated in > > weblate and there are currently no Spanish language templates. One > > would > > need to create Spanish translations of all the templates in > > < > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en > > > > > and submit a merge request to add them to a mailman/templates/es/ > > directory. > > > I will make the template translations locally, test them, and then, if > they are yet lacking in the main repo, follow your suggestion. I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ... -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 2 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Thanks Stephen and Mark for your replies. I have been able to identify a file in the shunt queue that threw a matching error when I performed mailman qfile on it. I moved this file out of the queue in the hope that I would then be able to load the held_messages page successfully. Unfortunately I am still seeing a 500 error on loading the page. I temporarily reenabled debug logging to confirm that the same error was being thrown. I have run a loop over all remaining files in the shunt queue and all the remaining files can be accessed by mailman qfile without error. Assuming that file was the cause are there other steps I need to perform in addition to removing the file from the shunt queue directory? Thank you, Simon. ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Sunday, 30 August 2020 12:52 To: Simon Handfield <simon.handfield(a)sl.nsw.gov.au> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius Simon Handfield via Mailman-users writes: > I have been working through other threads that indicate the same > symptom (500 error when loading held_messages for a list). You want threads that deal with Unicode: > Error reported in log with debug enabled: > > Traceback (most recent call last): And that last call is:: > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) It appears that the message is improperly constructed, and either a Content-Type field has a omitted or inappropriate charset parameter, or perhaps the Content-Type field is omitted entirely (ASCII is the default charset). This is frequently a problem created by spam messages. The message should be in the shunt queue. You can examine it with the command "mailman qfile /path/to/message_file.pck". Unfortunately it's not clear from the backtrace where in the message this is: it's at the beginning of a part ("position 8-9") or maybe line, but the part could be late in the message. If it's spam, you can just delete the file (and do whatever else you do about spam, of course). If it's not spam, it would help if you can guess what language and charset are being used in the message, and we can go from there. If this is unclear, feel free to ask more. _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 7 months

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

by tlhackque

I think you're confused. You already have mail.labbrands.com set up as the MX record for labbrands.com. And it has an A record with the same address as your webserver. 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 25 Trying 192.185.51.89... Connected to mail.labbrands.com (192.185.51.89). Escape character is '^]'. help 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 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>) 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>) >> 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> 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/ >> -- This communication may not represent my employer's views, if any, on the matters discussed.

7 years, 8 months

[MM3-users] Re: Dmarc settings and

by Abhilash Raj

On Sat, Sep 7, 2019, at 7:36 PM, paul(a)arenson.org wrote: > Can ANYONE help? I guess it is bad form to create more threads. But I > am losing confidence. > > - - - - - - - - - - - - -- - - - - - - - - - - - - > MAILMAN 2.1.27 (CPANEL > - - - - - - - - - - - - -- - - - - - - - - - - - -) > 1) I checked our old list. (I no longer manage it but I have access > to the settings) > > 2) Those settings are: > -->Should the Sender header be rewritten for this mailing list to avoid > stray bounces? > Yes is recommended., Details for include_sender_header > > -->Privacy Options Sender rules > > -->Action to take when anyone posts to the list from a domain with a > DMARC Reject/Quarantine Policy. Munge > > --->Shall the above dmarc_moderation_action apply to messages From: > domains with DMARC p=quarantine as well as p=reject > > Yes > > > Shall the above dmarc_moderation_action apply to messages From: domains > with DMARC p=none as well as p=quarantine and p=reject > No > > - - - - - - - - - - - - -- - - - - - - - - - - - - > 3) MAILMAN 3 ( Hyperkitty 1.2.2) > - - - - - - - - - - - - -- - - - - - - - - - - - - > Now i want to make sure that my new list does not encounter problems > My settings are > > -->Alter > > REPLY GOES TO THE LIST is selected This option controls if the `Reply-To` header is always changed to the list, instead of letting it be whatever the email came with. This list is configured with "No Munging". "Reply goes to the list" basically means that if I send an email to the list with "Reply-To" set to my own address ( so that replies are directed to me instead of the MalingList because I don't want people to send replies the list), Mailman will unconditionally change the "Reply-To" header to list's address. "Reply-To" header is used when for some reason "From" address can't be used by mail clients. Unless you have a strong reason to change this, the default value is "No Munging". > > -->DMARC Mitigations > > a) Dmarc mitigation Action replace From: With list address > > b) Dmarc Mitigate unconditionally > > Now NO. SHOULD I CHANGE THIS TO "Yes" Let this be the default option, which is "No", unless you have strong reason to do so. DMARC policies are published per domain, so, some of your senders will have DMARC policy that will cause emails from Mailman to be rejected by receivers. For those senders, Mailman will replace the "From" header to list's address so that DMARC doesn't fail for the receiver. Doing it unconditionally means that you replace "From" header of every email to the list address. > > > Can anyone approve or disapprove? Please. I need to make sure this is > right BEFORE going live. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 7 months

[MM3-users] Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:46 PM, Jeff wrote: > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > 1) some emails that arrived before I got the archive working are still sitting in: > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a collection of messages in maildir format. This is how the prototype archiver stores messages. This has nothing to do with HyperKitty. It is a separate archiver. If you don't want messages to be stored there, you can disable the prototype archiver for the list by unchecking prototype in Postorius -> Settings -> Archiving -> Active archivers or disable it entirely for the installation by setting ``` [archiver.prototype] enable: no ``` in mailman.cfg > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > /usr/local/mailman3/mm/var/queue/shunt > > What should I do to get these messages processed? Assuming the issues that caused them to be shunted have been fixed, just run the command ``` mailman unshunt ``` > 3) Similar to above, some messages are in: > > /usr/local/mailman3/mm/var/queue/bad > > How can I get these messages processed? First examine the messages with ``` mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> ``` To be sure you want them. Also examine mailman.log for the times they were stored in the `bad` queue. You are looking for 'Skipping and preserving unparseable message: <file>' and/or 'SHUNTING FAILED, preserving original entry: <file> messages and you want to determine which runner preserved the message. There may be a 'whichq' entry in the message's metadata in which case, that's the answer. Once you have determined the queue, you can just move the .psv file from the bad queue to the appropriate queue, renaming it from .psv to .pck in the process. > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? I know little about uwsgi. setting it to `uwsgi://localhost:8000` might work. You could also set it to the base URL that a user would use to access the web UI, e.g. `https://example.com` and that would presumably be proxied to uwsgi. For example, on the server for this list we have ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` which gets proxied to gunicorn, but the idea is the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

I created a new list with this setting. This new created list can send to Gmail addresses, this is very strange, because I have changed the problem list (The list that cannot send to @gmail addresses) settings to match the new one, but still the issue is there. The only difference is that the problem list has been imported from mailman2. Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? Thanks Mohsen ________________________________ From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, September 6, 2023 1:32 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Issues with @gmail.com addresses Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 7 months

[MM3-users] Re: Upgrade path

by David Krantz

Hi. Getting back to this... Some log of what I'm doing. * First git fetch; git pull on all parts. Started new envs to simplify rollback etc. * activate the new 3.5 venv. ( I run the commands one at a time, but this is more compact in text form:) > cd git/mailman; python setup.py build; python setup.py install > cd ../mailman-hyperkitty; python setup.py build; python setup.py install > deactivate activate 2.7 venv, then > cd ../mailmanclient; python setup.py build; python setup.py install > cd ../django-mailman3; python setup.py build; python setup.py install > cd ../postorius; python setup.py build; python setup.py install > cd ../hyperkitty; python setup.py build; python setup.py install So far no errors. Just warnings. Backups: * deployment directory (as user with rw in directory) > tar -cvzf backup.tgz deployment_directory * postgres databases (as user with postgres-priv) > pg_dump maiman | gzip -9 > mailman.bak.gz > pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service. I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run. So the line with ^$ in urls.py now is url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))), instead, and the line "hyperkitty," is commented in the django application list. cheers. // David On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/08/2017 04:42 AM, David Krantz wrote: >> >> What is the rekommended way to upgrade to the newest version? (newest >> _usable_ version, of course)? Is it docker-only with a migration from >> the current solution to a docker based? If so, any ideas or pointers >> on how to go about this? > > > You may find this wiki article helpful <https://wiki.list.org/x/17891998>. > > I started with bundler on both this (lists.mailman3.org) and the > mail.python.org installs, but have been updating from the heads of the > various gitlab branches since very early on. > > At the moment, these installations are somewhat ahead of the 3.1 > release, but I am not updating as the latest core has dropped Python 3.4 > support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu > 14.04) servers. (I will probably install 3.6 from source at some point.) > > Please feel free to ask here if you have more specific questions. > > -- > 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/

7 years, 7 months

[Test] Re: setting up the mailman-users@mailman3.org list

by Mark Sapiro

On 03/26/2016 06:34 PM, Mark Sapiro wrote: >> I think we are very close to going live with a >> mailman-users(a)mailman3.org list. Very,very close. One question. I don't think we have any DMARC mitigations available yet. Given that, I think I should disable Yahoo OpenID login for the web UI, I.e., at least not encourage people to use Yahoo addresses. We could also use header filter rules to stop posts from Yahoo. What do people think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[Test] Re: Delete test* lists

by Barry Warsaw

On Apr 05, 2016, at 10:39 PM, Simon Hanna wrote: >I guess the lists can be removed or at least not be advertised now :-) If Mark wants to delete them (which would be fine with me), please do keep the archives. -Barry

9 years

[MM3-users]Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Hello World! Very nice to meet you all this afternoon! In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler.

8 years, 10 months

[MM3-users] Re: Mailman3 in AWS

by Barry Warsaw

On Aug 19, 2016, at 05:02 PM, Andrew Hodgson wrote: >-Any issues with runner processes being ran on more than one machine talking >-to the same DB backend? There shouldn't be, especially with PostgreSQL or MySQL (MM3.1), although we're pretty much relying on SQLAlchemy to do the right thing. Cheers, -Barry

8 years, 8 months

[MM3-users] Find a smtp server to send out emails

by Leon

Hi, This problem is not caused by mailman, but I still want to give it a shot here. I'm hosting a mailing list on top of mailman3. Emails are supposed to be sent out by AWS ses. However, ses requires that sender address must be verified, which leads to a problem that emails sent by subscribers to mailing list cannot be sent to other subcirbers, since their addresses are not verified. And it is impossible to verified every subscriber. Are there smtp service providers allowing unverified email address to send out emails, or do I have other solutions? Thanks. -- Best wishes, Leon

8 years, 4 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 03, 2016, at 09:22 PM, Florian Fuchs wrote: >I think it's OK to put out a separate beta of the core, because the >version pulled from pypi will still be 3.0 if I'm not terribly mistaken. BTW, I did upload a beta of Core to PyPI before I started my travel. >For the real 3.1 we should probably do a coordinated release of all >components, once everything's tested a little more thoroughly. For sure. Cheers, -Barry

8 years, 4 months

[MM3-users] Re: Domain in welcome message

by Maadix

Hi, I'm having problems with customizing welcome message It's working fine for var/templates/site/en/welcome.txt but not for domains or lists , so maybe I'm doing something worng I'm using a subdomain as mail_host which is different from the URL Host. I've been trying all these combination, with no success: var/templates/domains/sub.example.com/en/welcome.txt var/templates/lists/listname.sub.example.com/en/welcome.txt var/templates/lists/listname(a)sub.example.com/en/welcome.txt I'm running mailman-bundler version 3.0.0 Thank you

8 years, 2 months

[MM3-users] Mailman 3 api php

by david.terni＠gmail.com

Hi, I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Someone can help me? Thank's a lot

8 years, 1 month

[MM3-users] Auth question

by David Krantz

Hi, I have of course activated password login as it was not possible to get the provider based logins to work (might be but not worth the time for me right now). Is there any way for an user to request a new password when it is forgotten? I presume that the Persona login is removed now. I cannot hide it in my version or at least I do not know how. cheers // David

8 years

[MM3-users] Remove footer link

by David Terni

Hi, I need to remove footer message like "to unsubscribe etc etc" from all lists. How i can do it or edit text? Thanks alot for any suggestion. David

8 years

[MM3-users] Re: "Private archives" aren't private

by Simon Hanna

>> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it. I couldn't get the command to run, will investigate later...

7 years, 10 months

[MM3-users] Confirm on mass subscription

by David Krantz

Hi, Is there a way of requiring all mass subscribed users to confirm their email adress? I have an use case where we have a current mail list but when moving it to mailman I for different reasons would like to confirm all subscribers. Some very shallow testing suggests that if I just add them using mass subscribe, they will not have to confirm at all. I have yet to upgrade to 3.1 but I will do so in due time. cheers // David

7 years, 9 months