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

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Brian Carpenter

On 1/7/20 2:16 AM, hansen(a)rc.org wrote: > Beats me, Mark. Brian, do you know? Yes sir. Here are the three startup scripts that you will need to know. I should have included that in the communication I sent you and I apologize for that: systemctl start/stop/restart/status mailman (this is for Mailman core) systemctl start/stop/restart/status qcluster (this is for Django) systemctl start/stop/restart/status gunicorn (this is for web access to postorius/hyperkitty) -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 3 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/5/21 2:07 AM, Stephen J. Turnbull wrote: > > Are we guaranteed to get a separate LMTP delivery for each list? That > is, if the MTA receives 2 RCPT TOs to lists for one transaction, won't > it do the same in LMTP when it sends forwards the message to Mailman? It doesn't matter. The LMTP runner makes a separate `in` queue entry for each recipient list, thus these are processed as separate messages regardless of how they arrived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/9/23 14:32, Christian via Mailman-users wrote: > When I ran > > mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org > > I did receive a list of subscribers for the new list I created, not just the > owner or moderator. > > Upon closer examination, another of my longtime working lists is also not > working. Similar behavior as the new list I created in that I see the > message has been archived, but not distributed to the subscribers. What do your MTA logs show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Two trivial questons:

by Bill Oliver

I take that back again. I found the error. I had nothing listed in CSRF_TRUSTED_ORIGINS. I filled that in and it ran like a charm. So, now it's just the SITE_ID thing... billo On Wed, 2024-10-09 at 19:22 -0400, Bill Oliver wrote: > > I take that back. I went back and made another superuser using > mailman-web create superuser. But... I still get bounced with the > error: > > > Forbidden (403) > CSRF verification failed. Request aborted. > > More information is available with DEBUG=True. > > > > my uwsgi.log generates: > > [pid: 1385|app: 0|req: 14/22] 127.0.0.1 () {52 vars in 1078 bytes} > [Wed > Oct 9 23:15:17 2024] GET /accounts/login/?next=/mailman3/lists/ => > generated 8204 bytes in 33 msecs (HTTP/1.0 200) 11 headers in 509 > bytes > (1 switches on core 1) > [pid: 1385|app: 0|req: 15/23] 127.0.0.1 () {62 vars in 1230 bytes} > [Wed > Oct 9 23:15:27 2024] POST /accounts/login/ => generated 1019 bytes > in > 2 msecs (HTTP/1.0 403) 8 headers in 268 bytes (1 switches on core 0) > > So it wasn't that I forgot the superuser name. It's getting denied. > That's all I got. > > Any help would be appreciated... > > billo > > > On Wed, 2024-10-09 at 19:04 -0400, Bill Oliver wrote: > > First: > > > > Last night I got everything installed and, I think, working. > > Unfortunately, I forgot to write down the name and password of the > > superuser I created. I know what I put in as password, but I cant' > > remamber the name of the superuser. > > > > I know I could just create another superuser with "mailmanweb > > createsuperuser" but I was wondering if there was a "mailmanweb" > > command for *listing* superusers. > > > > If not, I'll just make another superuser... > > > > Second: > > > > I have the "example.com" error in the login screen. The > > instructions > > state that this is a problem with making SITE_ID=1. Okay, but I > > don't > > know what to change it to. I tried SITE_ID=2 on a lark and > > everything > > broke, and the instruction say not to do SITE_ID=0. Apparently it > > has > > to be an integer (I also tried putting in site name and got that > > error). So... where do I change it? > > > > Thanks! > > > > billo > > _______________________________________________ > > 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 billo(a)billoblog.com > > _______________________________________________ > 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 billo(a)billoblog.com

6 months, 2 weeks

[MM3-users] Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

I run several MailMan 2.1 mailing lists and some subscribers are frustrated by the way pipermail deals with JPEGs that are embedded in the messages and also with how attachments are handled. Does hyperkitty in Mailman 3.1 do better on these issues. Assuming this message gets archived, I am going to try embedding a small picture right here: Hopefully that shows up in the archive. I won't add an attachment because the list may not allow it but I'm curious how those are handled. Thanks Jason -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

7 years, 9 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/2/21 7:35 PM, Bryan Loniewski wrote: > $ /opt/mailman/mm/bin/mailman version > GNU Mailman 3.3.2 (Tom Sawyer) > > So, I'm running > 3.2. Any other advice on debugging the truncated data? The traceback indicates sqlalchemy is unpickling data whose type is PickleType. The only mailinglist columns which are PickleType are the legacy *these_nonmembers and topics. You could try invoking mysql on Mailman's database and doing SELECT list_name, accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, discard_these_nonmembers, topics FROM mailinglist; and look for the longest values to possibly identify the problem list and attribute. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 04:43 PM, Rafael Mora wrote: > YEEEES! At last!!! I can see the web UI. > > Now I´m getting this message in the web UI: > > Something went wrong > Mailman REST API not available. Please start Mailman core. > > > > Where do I configure the REST API ????? So I guess you figured out that ALLOWED_HOSTS is a Django setting in settings.py or wherever your Django settings are. Now you have to start Mailman Core. In your Python 3 'env' where you installed Mailman Core, run 'bin/mailman start'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Dave McGuire

On 5/25/24 08:47, Jeremy Stanley wrote: > On 2024-05-25 11:33:14 +0300 (+0300), Odhiambo Washington wrote: > [...] >> I last heard of usenet in the late 90's. Do they still exist, even? > [...] > > Yes, and it's surprisingly usable again now that most spammers have > finally forgotten it exists! It's also significantly improved since Google stopped trying to make money off of it. The Usenet spam from the Google users was just unbelievable. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

10 months, 4 weeks

[MM3-users] mailman3-web generating huge amount of error logs

by Stephen J. Turnbull

Helio Loureiro writes: > line 55, in unsign\n raise BadSignature(\'Signature "%s" does not > match\' % sig)\ndjango.core.signing.BadSignature: Signature > "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match\n',) I've never heard of this one. Apparently somewhere there is a secret key that is configured to "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" but should be something else. My best guess is that this is the SECRET_KEY in settings.py, and probably there is some data leftover from before that was signed with the key above but SECRET_KEY in settings.py is still "MyVerrySecretKey". Or it could be the other way around. Don't know what to do about it though.

1 year, 4 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 22 jan 2024, om 17:19 heeft Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> het volgende geschreven: > > Marco van Tol writes: > >> Turns out I was just one `./manage.py rebuild_index` away, so all >> good :-) > > Wonderful news! Thanks for following up, we do love to hear success > stories. Small unfortunate twist, this leads to: --- [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... --- I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? Thanks so much in advance! Marco van Tol

1 year, 3 months

[MM3-users] Re: Mails from Django are not sent

by Simon Hanna

On 10/12/2017 12:27 PM, Bjoern Franke wrote: > Hi, > > I'm using the "mailman-suite" setup for Postorious and Hyperkitty. > > I've set > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' You can just remove the settings to fallback to the defaults (that's what I do) > in settings.py, but no mails are sent. Files with the e-mails are in the > emails folder, but nothing happens, also no errors regarding emails are > logged. What did you have before that? It looks like django isn't using your "new" settings Did you restart django/uwsgi/gunicorn or whatever you are using?

7 years, 6 months

[MM3-users] Apache Conf

by Guiseppin Thomas

Hi, Currently, I use a nginx configuration for mailman. It's work perfectly. I tried to do the same with Apache, but the statics files are not delivered (404). Basically, it's the same configuration: /server { listen 80; server_name mailing.ddd.fr; access_log /var/log/nginx/mailing.access.log; error_log /var/log/nginx/mailing.error.log; location /static/ { alias /opt/mailman/static/; expires 30d; } proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { proxy_pass http://localhost:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } } <VirtualHost *:80> ServerName mailing.ddd.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined <Location /static/> Alias "/opt/mailman/static/" </Location> <Location /> ProxyPass http://localhost:8000/ ProxyPassReverse http://localhost:8000/ ProxyPreserveHost On </Location> </VirtualHost>/ I missed something ? Thanks.

6 years, 6 months

[MM3-users] Re: Broken web UI after upgrade

by Jörg Schulz

I had this issue (using the dockerized version) when - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static has been set to the wrong path. Maybe it's just the same: that your web server doesn't find the location for the static files. Am 14.12.22 um 17:15 schrieb Odhiambo Washington: > After upgrading MM3 and running all the post-update tasks and even > re-indexing all the posts, I have ended up with a somehow "broken" > hyperkitty. > The archives display on a browser six, to say the least. > The site is public, so I can share the link: https://list.rc.org/archives/ > > What should I do in order to fix this? >

2 years, 4 months

[MM3-users] mailman break DKIM signature by modifying body

by Peter Münster

Hi, I'm using mailman 3.3.8. Some messages with attachments from Google users get rejected by spam filters because of invalid DKIM signatures. It seems, that mailman alters some lines in the body. Here an example: Original message: --8<---------------cut here---------------start------------->8--- Lines: 2031 --000000000000f846c505fc494b7a-- --000000000000f846c705fc494b7c Content-Type: application/pdf; [...] Content-Disposition: attachment; [...] --8<---------------cut here---------------end--------------->8--- Altered message: --8<---------------cut here---------------start------------->8--- Lines: 2032 --000000000000f846c505fc494b7a-- --000000000000f846c705fc494b7c Content-Type: application/pdf; [...] Content-Disposition: attachment; [...] --8<---------------cut here---------------end--------------->8--- An empty line is added, and the spaces after the semicolons are removed. Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. What could I do please, to prevent such modifications of the body? TIA for any help, -- Peter

1 year, 10 months

[MM3-users] Question about message bounce stats

by Ruth Ivimey-Cook

When I used Mailgun some time back, it had a feature of, for any specific outgoing mailing, being able to show you stats and other details of which mails were received ok, which bounced, and which were undeliverable, which I found helpful to check every so often. Their system also kept track of long-term trends, eg for addresses that frequently failed. Does Mailman3 keep such stats, and if so is there any way to get access to them, even if only API? I would think it useful to do so (and yes, for individual outgoing messages at least for a period). Regards, Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 7 months

[MM3-users] Re: Errors while importing mm2 list archives

by Odhiambo Washington

On Tue, Dec 20, 2022 at 3:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/17/22 23:22, Odhiambo Washington wrote: > > > > I have dropped the DB, recreated, ... > > When you created the DB did you specify `CHARACTER SET utf8mb4`, e.g. > > CREATE DATABASE mailmansuite CHARACTER SET utf8mb4 > Yes. That is what I do at the minimum for my databases unless specific instructions exist against it. So it seems like I have done everything that is commonly expected, but the import still fails on several messages. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Where is postorius.wsgi?

by Peter Münster

On Fri, Jan 26 2018, Peter Münster wrote: > ImportError: cannot import name EmailMessage > > What should I do please? Ok, found it. This patch is needed: --8<---------------cut here---------------start------------->8--- --- /usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py~ 2018-01-26 08:43:30.027617074 +0100 +++ /usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py 2018-01-26 11:37:08.737066069 +0100 @@ -23,7 +23,7 @@ from mimetypes import guess_all_extensions from email.errors import HeaderParseError from email.header import make_header, decode_header -from email.message import EmailMessage +from email.message import Message # Path characters for common platforms PRE = re.compile(r'[/\\:]') @@ -63,7 +63,7 @@ sanitize = Sanitize.SANITIZE_HTML def __init__(self, msg): - assert isinstance(msg, EmailMessage) + assert isinstance(msg, Message) self.msg = msg def scrub(self): --8<---------------cut here---------------end--------------->8--- -- Peter

7 years, 2 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by Torge Riedel

Am 17.10.20 um 20:31 schrieb Mark Sapiro: > Please do file a bug. It won't be fixed until after the upcoming 3.3.2 > final release because we not making i18n changes between the candidate > and final releases. Also, if you don't like my suggestion, feel free to > suggest something else. Hi Mark, thanks for your answer. Filed as https://gitlab.com/mailman/mailman/-/issues/785 I also added a suggestion similar to the ones you did. And also the idea of a comment field for each rule to give additional information to the moderator. Kind regards Torge

4 years, 6 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/28/20 12:08 AM, Shashikanth Komandoor wrote: > I tried this way but in this method I don't find any files to edit for my > customizations like > 1. Removal of social accounts, > 2. Addition of SMS integration and so. > > If I can do my required customizations through pip installation I am fine > with that. If you follow the instructions for installing in a virtualenv, in say /opt/mailman/venv, all the component files will be in /opt/mailman/venv/lib/python3.x/site-packages -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: more about spanish translations

by Mark Sapiro

On 2/19/21 5:09 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I would like to translate it all, but as said, I cannot find where to do > it. I wonder if it's comes from another package as allauth or something > like this. Yes, it does come from allauth, specifically allauth/templates/account/email/email_confirmation_message.txt. The Spanish allauth message catalog is at <https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC…>. I suppose you could submit a pull request to update it. Or you could just update your local file in your installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: accept mails from several Users, not list members beside members, howto

by Mark Sapiro

On 7/12/21 11:56 PM, Lars Schimmer wrote: > > Thank you. > I would have hoped for a extra input box to enter a list of ~100 email > addresses, but ok, lets do it this way. There is the legacy accept_these_nonmembers setting (exposed in Postorius since 1.3.3). This is designed to support the MM 2.1 setting which accepted regexps, but it also supports non-regexp addresses. Note that a match in one of *_these_nonmembers will override the moderation action for a non-member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 12:32 PM, Morris Jones wrote: > > It appears that my installation predates the mailman-web package, as I > don't have it installed. > > But if I understand the docs correctly, it serves to take care of the > django-admin commands for migration, static files, js/css compression, etc. > > So I think I don't need to do anything special (like add mailman-web), > except a database migration after the upgrades. That's correct. I recommend running these Django commands after upgrading collectstatic --clear compress compilemessages migrate -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Problems with shunted Mails

by Mark Sapiro

On 4/20/22 02:00, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> You might be able to fix this with something like >> >>> for mbr in m.regular_members.members: >> ... if mbr.address is None: >> ... mbr.address = mbr.user.preferred_address or >> member.user.addresses[0] >> ... >> >>> commit() > > This fix didn't worked. It returned a "Index out of bounds" exception. Apparently these Users have no associated Addresses at all. Do you have any idea how these Users got created/subscribed to the list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

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

by Mark Sapiro

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. 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` -- 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: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Andy Macheta

Hi Odhiambo, Well; looks like I'm much further on thanks to your tips - thanks!! So now I can get my local web browser pointing at http://localhost:8000/mailman3/lists/ and I can see my test list. But, the webpage does not seem right, i.e. the text has loaded but not the images and wondering if anyone has any tips on how to resolve. I've checked ownership/group ownership of the /opt/mailman/web/ directory and sub-directories and all is owned by mailman:mailman which I ?think it should be. Not sure what else to check/do as definitely not a web developer. Thanks, Andy

11 months

[MM3-users] redirecting -bounces replies

by Hirayama, Pat

Greetings, Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? In Mailman2, I know that I could do that by modifying the aliases table. I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856 phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org>

5 months, 3 weeks

[MM3-users] Re: Programmatically modify Thread-Topic *before* message is sent out the door?

by Thomas Ward

Well, I discovered some chaos, and indeed this is a Microsoft MAPI added component. Thread-Topic and Thread-Index are Microsoft's crap for their handling of threading, and they add it to *any* origin message going out the door for Microsoft's conversation handling. Which is annoying. I'm going to be exploring some things on my clients' end to see if we can strip those headers *before* they end up at our mailing list system. Painful systems are painful, and Microsoft is one of the worst offenders in this case. And I've informed Microsoft through our deep diving on their end and mine that they're breaking things. FORTUNATELY, I have administrative access on the MS365 side for the clients involved, so I can do some tweaking on mail ingress to strip certain headers. And hopefully that'll work. Going to be doing more testing on that, but I might need to set up some rules to strip messages of those headers programmatically. Thomas -----Original Message----- From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Wednesday, January 3, 2024 3:06 AM To: Thomas Ward <teward(a)thomas-ward.net> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Programmatically modify Thread-Topic *before* message is sent out the door? Thomas Ward via Mailman-users writes: > Any chance Thread-Topic or such is spawned by the msgdata object > instead of directly in the message? No, the string "thread-topic" does not appear *anywhere* in the Mailman core sources. Mailman itself has no concept of threads. HyperKitty uses References, Reply-To, and Subject to algorithmically identify threads. Mailman does have an independent concept called "topic", which can best be thought of as "sub-list". But it uses the X-Topics header, and as far as I know doesn't pay attention to threading. AFAIK, Thread-Topic is a Microsoft-specific device. If you use Exchange or Outlook, you have to negotiate with that software about the use of Thread-Topic. My guess is that it is generated by Exchange because somebody at Microsoft decided that threading should be enforced by the server, not inferred by the MUA. > Unfortunately there's very little documentation on msgdata in the > handlers and what it is/contains so I'm asking again. I guess the relevant documentation is RFC 5321. ;-) msgdata's original purpose is to contain envelope and delivery information. That is, any data about the message that the LMTP runner knows that is not in the message header itself. HELO hostname, sender, recipients, IP address of SMTP client, timestamp of receipt is what I can think of offhand. There may be other stuff in there that is parsed out of the message and copied to msgdata for convenience but I don't know of any offhand. I'd have to read source to confirm. > Due to the holidays I didn't get around to testing/poking this so... You're welcome to ask even if you haven't. Of course we prefer that you investigate as much as possible, but we're all grownups. Everybody has their limits, and we cover for each other as we can. Steve

1 year, 3 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Abhilash Raj

On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: > On 07/08/2019 17:04, Abhilash Raj wrote: > > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > >> On 06/08/2019 09:48, Phil Thompson wrote: > >> > On 06/08/2019 03:38, Abhilash Raj wrote: > >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >> >>> I'm in the process of setting up mailman3. The only problem I seem to > >> >>> be > >> >>> having is getting Hyperkitty to archive messages. Rather than the > >> >>> authorisation problems people have previously asked about on the > >> >>> list, I > >> >>> am getting a 403 error... > >> >>> > >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> > >> >>> Any suggestions would be appreciated. > >> >> > >> >> How did you install Hyperkitty? > >> > > >> > On Ubuntu... > >> > > >> > apt-get install mailman3-full > >> > > >> >> You probably need to the set the API key correctly in both Core and > >> >> Hyperkitty. > >> >> > >> >> Have you looked at documentation here[1]? > >> >> > >> >> [1]: > >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… > >> >> > >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in > >> >> quotes, single or double, doesn't matter) in your settings.py for Web > >> >> (Django) should be same as the `api_key : value` (without quotes here > >> >> in hyperkitty.cfg config file). > >> > > >> > That's all correct. I'm familiar with the authorisation issues that > >> > other people have had. > >> > > >> > The only thing I'm doing differently (as far as I am aware) is that > >> > I'm using a URL prefixed with /mailman3 which is stripped off in my > >> > nginx configuration... > >> > > >> > # mailman3. > >> > location /mailman3/ { > >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > >> > include uwsgi_params; > >> > uwsgi_param SERVER_ADDR $server_addr; > >> > uwsgi_modifier1 30; > >> > uwsgi_param SCRIPT_NAME /mailman3; > >> > } > >> > > >> > location /mailman3/static { > >> > alias /var/lib/mailman3/web/static; > >> > } > >> > > >> > location /mailman3/static/favicon.ico { > >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > >> > } > >> > > >> > ...but I don't see this affecting the mailman to Hyperkitty > >> > communication. Posting to lists and the Postorius and Hyperkitty > >> > frontends seem to work fine. > >> > >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my > >> public IP address). However I now get a 400 Bad Request error. > >> > >> I have traced this to the archive() function in > >> hyperkitty/views/mailman.py which is expect a POST but is actually > >> getting a GET, specifically... > >> > >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' > >> > >> ...which seems to be a fairly fundamental problem. > >> > >> Again, any suggestions would be welcome. > > > > It should be sending POST request to archive emails[1]. How did you > > grab the above request? Was it from logs? > > Yes, I added DEBUG=True in mailman-web.py and captured the HTML from > mailman.log. DEBUG=True doesn't print anything more useful around the 400 error response? > > > Do you have anything else in the logs? There should be something in > > the Mailman Core or web logs should have something. > > There's nothing useful in the core log. > > There are 3 preceding entries in the web log... > > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > > There is one item in the spool directory. > > These were all (apparently) successful. It seems odd that the last two > entries were identical. The only other thing that I can think of is, ALLOWED_HOSTS. What settings do you have in your ALLOWED_HOSTS in settings.py for Django? You need to have 'localhost' or whatever is the value of the "Host" in the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not sure what is the default value in Ubuntu system. If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS and see if the problem goes away, this will bypass the Host header check. -- thanks, Abhilash Raj (maxking)

5 years, 8 months

[MM3-users] Settings: No templates are visible in settings

by paul＠arenson.org

I am struggling to find out why I do not see TEMPLATES in the Settings. When I first logged they were there. Many of them. Then, toying with the settings, they disappeared. I cannot find them now. Originally i thought I would not list the mailing list but changed my mind. Likewise, archives are now listed as public. I am still thinking about that. In any case, I want to see if there are templates to allow me to change headers or footers in messages, such as give the address of the list. Thank you for your advice. P.S> Sorry i asked too many questions the other day. Trying to keep this brief.

5 years, 7 months

[MM3-users] Re: Hyperkitty

by Onyeibo

On Mon, 30 Jan 2023 16:01:16 +0300 Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > So an array?? > These are defaults. I have also added my IPs. Nothing is happening. > > > Perhaps I did something wrong here. Any documentation on this? > > > > https://mailman-web.readthedocs.io/en/latest/settings.ht > > > > My instance is not archiving. > > Things to check: > 1. Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!) > the same as api_key in mailman-hyperkitty.cf (unquoted here!)? I have double-checked this. Yes ... I got it right > 2. Your MM3 log files - do they say anything? > Nothing! No new errors. It is very strange and frustrating Onyeibo

2 years, 2 months

[MM3-users] Re: Unknown attribute: max_message_size

by Simon Hanna

On 12/06/2017 11:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. It is. https://gitlab.com/mailman/mailman/merge_requests/329 > > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. Are you sure you have up to date images?

7 years, 4 months

[MM3-users] Re: Dealing with recipients' servers spam filtering

by Brian Carpenter

On 2/12/21 10:59 AM, Gilles Filippini wrote: > It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected > (in reply to end of DATA command) I don't have any SPF record setup. > DMARC mitigation is configured to 'Replace From: with list address' > and 'DMARC mitigate unconditionally' set to 'No'. Well make sure you set up SPF records for your list domains. They do help in mail delivery. I personally set DMARC mitigate unconditionally to yes for my lists. Unfortunately the 550 spam detected message is too generalized to be helpful. If you have more informative information from your logs then please share them. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 16:59 GMT+01:00 Terri Oda <terri(a)toybox.ca>: > > > On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad < > thor.rustad(a)gmail.com> wrote: > >2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > > > >> On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> > >>> Imagine an installation with 500+ mailing lists and almost as many > >local > >>> admins that are supposed to maintain their own local lists with a > >few > >>> local > >>> members. As site admin, I see all 500+ lists, but I was expecting > >*local* > >>> admins to see only the lists they maintain. I have set all lists to > >>> "advertised = False", so they are hidden from ordinary view. Is > >there a > >>> way > >>> to show only relevant lists to local admins? > >I believe I wrote Postorius in the subject line, but it may not be so > >obvious. So yes, in Posterius I would like to hide the lists from email > >harvesters, while relatively "untrusted" admins should have access to > >basic > >operations on the one list he/she "owns" (and without having to browse > >through 50 pages of mailing lists). Somehow I don't think 500 > >superusers in > >our system is a good idea! > > What do you mean by local admins? > > Is this > 1. Giantsite.example.com hosts lists for a bunch of domains, and you want > the logged in admins of mydomain.com to see their list admin pages but > not otherdomain.org's lists > > 2. You want each logged in admin to have their own personal dashboard of > list admin pages for lists they administrate, even though they're all under > one big domain. > > (Neither of those scenarios talks about archives, since you say you're > only talking about postorious) > > I think #2 is something we should be doing, and the old "todo" section of > the interface kind of was made with that in mind. Probably worth mocking > up some screenshots and opening a feature request to keep the idea in mind, > but it should be more a matter of prioritizing how things are displayed > than any huge change. > > I'm not sure if we have a "local admin" concept in the system that lines > up with #1, though. > > Ok, this would more like number 2. It's National.dogclub.com with its various mailing lists like poodle.dogclub.com, which expands to poodle-regionA.dogclub.com, poodle-regionB.dogclub.com, poodle-regiionC.dogclub.com and so on. So with dozens of different dog breeds and geographic chapters, the number of mailing lists are between 500 and 1000, but all are under the same dogclub.com domain. The members of each list should be maintained by a person with some elevated rights, but not enough to mess up the system. What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.

7 years, 3 months

[MM3-users] Re: Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Mark Sapiro

On 8/8/21 4:41 AM, Thomas Möhle via Mailman-users wrote: > Hey Mark, > > thanks for your reply!> In what way? Do list posts get delivered? What > works and what doesn't? > > What are the observable symptoms for things that don't work? > Yes, mails are not delivered. You can send a mail to the mailinglist > without getting a bounce, but you will not receive the mail back through > mailman. > In addition to that, I'm unable to edit mailing lists in the web > interface. After clicking on a list, I'll get a 404. > Plus, I noticed that mailman is constantly writing files to > /var/lib/mailman3/queue/out/ but they seem to get deleted right away > again. I'm getting alot of IO there though. So messages are being queued for the outgoing runner and then something is done with them. If there are no errors in mailman.log about this and nothing in the shunt queue, they are being delivered to the MTA. What's in the MTAs logs? > > What do you get for example if you go in a web browser with hyperkitty > > running to > > > > > https://mail.bitkomplex.de/mailman3/hyperkitty/api/mailman/urls?mlist=landw… > > I get a small gziped json file back. Key is "url", value is a link to a > message. OK. That's correct and it seems that Mailman core can communicate with the HyperKitty API, at least when HyperKitty is running. > > And please don't post secret keys and change the value of api_key: in > > mailman-hyperkitty.cfg and the corresponding value in > > MAILMAN_ARCHIVER_KEY in your Django settings. > I actually tried to redact the logs and config files, but I must have > failed to save my edits on that one file. I'll change it right away. The key was in the mailman-hyperkitty.cfg file you posted and was in multiple entries in mailman-web.log. There is some strangeness in the logs you posted. Mailman.log contains many of these: Aug 07 12:49:55 2021 (2343598) HyperKitty failure on https://mail.example.com/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html> (503) and mailman-web log contains many of these [pid: 2343625|app: 0|req: 1/1] 10.133.3.2 () {60 vars in 1350 bytes} [Sat Aug 7 12:49:58 2021] GET /mailman3/hyperkitty/api/mailman/urls?mlist=aussen%40lists.example2.com&msgid=002601d777e2%244c34c540%24e49e4fc0%24%40example2.com&key=g8nOyDVbCNsi18L%2FjgTj%2BWDVKUQ2XeQM => generated 131 bytes in 279 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) which actually seem normal except for the quantity, but the time stamps don't correlate. There's nothing in mailman-web.log for the times of the 'HyperKitty failure' messages in mailman.log. Was the web service even up during those times. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] MIME Digests with posts and index inline likewise Plain Text Digests

by Henrik Rasmussen

Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. Would it be possible for Mailman to send both posts and index inline in the MIME digest? I am pretty sure it's not a feature yet, but if Mailman would be able to, I will submit an issue in core (I presume). /Henrik Rasmussen

6 years, 3 months

[MM3-users] Error after HyperKitty 1.3.x upgrade

by Florian Schulze

Hi! After upgrading to HyperKitty 1.3.x I get the following error for qcluster: File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300, in pusher task = SignedPackage.loads(task[1]) File ".../lib/python3.7/site-packages/django_q/signing.py", line 31, in loads serializer=PickleSerializer) File ".../lib/python3.7/site-packages/django_q/core_signing.py", line 38, in loads return serializer().loads(data) File ".../lib/python3.7/site-packages/django_q/signing.py", line 44, in loads return pickle.loads(data) AttributeError: Can't get attribute 'process_task_result' on <module 'hyperkitty.tasks' from '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> How do I recover from that? It seems like there are still persisted tasks in the qcluster queue using the old code from 1.2.x with the old locking implementation. Regards, Florian Schulze

4 years, 9 months

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

by Mark Sapiro

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

4 years, 2 months

[MM3-users] Re: "Unsubscribe all" failed with large lists

by Alan So

Alan So wrote: > Thanks. > We are still using Postorius 1.2.4 and Mailman core 3.2.0. However, there is no such > issue. Is this specific to Postorius 1.3.x or a result of using together with Mailman > core 3.3.2? Postorius 1.2.4 is probably not using mass-unsubscribe API. > We are planning to upgrade Mailman core first to solve another issue and upgrade > Postorius a bit later. Just figure out that our production environment with Mailman core 3.2.0 do reply with the API call /3.1/lists/listname.domain/roster/member even for long lists though it takes long time to complete. However, Mailman core 3.3.2 simply give empty reply with long lists after around a minute.

4 years, 3 months

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

by Andrew Hodgson

Abhilash Raj wrote: > On Aug 24, 2021, at 1:00 PM, Andrew Hodgson <andrew(a)hodgson.io> wrote: >> >> 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? >I have just updated the mailman-suite gitlab project with this change. Thanks for doing this all working this end. Andrew.

3 years, 7 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark@msapiro.netmailto:mark@msapiro.net> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab… > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs

3 years, 5 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 9/27/23 16:29, paulrubin37(a)gmail.com wrote: > I went through the install process in the provided link when I tried to start the service I keep getting errors about: > > Sep 27 19:17:15 mail mailman[1771]: ImportError: cannot import name 'path' from 'importlib_resources' (/opt/mailman/venv/lib64/python3.8/site-packages/importlib_resources/__init__.py) > > I verified the python version: > > (venv) mailman@mail:~> python -V > Python 3.8.10 See https://gitlab.com/mailman/mailman/-/issues/1093 The easiest fix is in your venv do ``` pip install importlib_resources\<6.0 ``` Mailman core <=3.3.8 is incompatible with importlib_resources>=6.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Add rule to auto-discard "AutoReply" messages from list members

by Stephen J. Turnbull

Abhilash Raj writes: > You can implement a custom rule and a custom chain to do this, but you'd > need to set that as the default chain on every existing list. Setting > the default chain can be scripted using `mailman shell` pretty easily > though. I'd just from mailman.config import config config.chains['default-posting-chain'].insert( right_place, vacation_program_considered_harmful_rule) TBQH. If I was feeling really paranoid I'd search for the preceding and following rules expected, and if found insert there. There really should be a default-posting-chain option (and default-posting-pipeline option for that matter) in schema.cfg.

1 year, 5 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/28/20 2:34 AM, Odhiambo Washington wrote: > > So, now I remember why I had to chown -R mailman3 /opt/mailman > Then now it seems like I have been doing things incorrectly, because I have > been doing > a lot of operations as root by simply: > cd /opt/mailman/mm > virtualenv venv > source venv/bin/activate > Looks like the correct way is to start with su - mailman3 Yes. All those things should be done as the Mailman user. >>> PS: There is the issue with qcluster, which doesn't seem to have been ... > I have run it from supervisord. It has forked 30 processes and refuses to > kill them when I stop supervisord. > I will look for options around it. I know nothing about supervisord, but there should be a parent process. E.g., here > msapiro@mail:~$ ps -fwwu mailman|grep qcluster > mailman 2885 1 0 Jul18 ? 00:00:00 /bin/bash /opt/mailman/mm/bin/mailman-web-django-admin qcluster > mailman 2889 2885 0 Jul18 ? 00:01:57 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2930 2889 0 Jul18 ? 01:21:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2944 2930 0 Jul18 ? 00:04:17 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 2945 2930 3 Jul18 ? 07:11:14 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 6467 2930 0 15:39 ? 00:00:03 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12337 2930 0 15:00 ? 00:00:07 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 12639 2930 0 11:08 ? 00:00:11 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 14658 2930 0 Jul27 ? 00:00:22 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 15860 2930 0 01:41 ? 00:00:21 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > mailman 19205 2930 0 Jul27 ? 00:00:29 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin qcluster > msapiro@mail:~$ pid 2885 is the parent which forked 2889 which in turn forked 2930 which forked all the others. stopping (sigterm) 2885 in this case will stop them all. I have seen an issue on one server where some of the qcluster workers become orphaned and their parent pid is 1. These are left when I stop the upstart service so I have this script. #! /bin/bash if echo `status qcluster` | grep -q 'running' ; then echo qcluster is running exit fi ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill to kill them. > PS: Did you by any chance find time to look into the issue about wsgi.py > that you had mentioned - the one that has me > stuck using it?? If you're referring to the issue at the end of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, I think that was caused by your not having the __init__.py file in /opt/mailman/mm/. If not, I probably need more information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: LMTP on unix socket

by Stephen J. Turnbull

Mark Sapiro writes: > You would have to modify mailman/runners/lmtp.py to listen on a unix > socket. The docs imply the aiosmtpd.controller.Controller class has a > make_socket() method which "allows subclasses to customize the creation > of the socket before binding" which I suppose could be used to create a > unix socket, but mailman/runners/lmtp.py currently doesn't make use > of that. If someone is thinking about doing this, I suggest comparing the asyncio event loop's create_server method with create_unix_server, which will probably give ueful hints about implementation. BTW, I object to the smtpd package's lmtp_host=UNIX_SOCKET_PATH style of configuration. There should be a separate parameter for this. Steve

5 years, 6 months

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

by Onyeibo

On Mon, 2 Jan 2023 09:57:45 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' I've not had any occasion to set these while following the documentation. > > match > > $ mailman info > ... > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Note the 3.1/ in REST root url is not included in > MAILMAN_REST_API_URL. > > What do you get from, e.g. > > curl -urestadmin:restpass http://localhost:8001/3.1/lists > > It should return JSON with information about your lists. > I get the following: {"start": 0, "total_size": 0, "http_etag": "\"678678567346533573674563786538\""}

2 years, 3 months

[MM3-users] Re: Can't start mailman after reboot.

by Mark Sapiro

On 8/24/23 11:22 AM, mrl(a)psfc.mit.edu wrote: > Hi - I couldn't find the locks. So I rebooted the computer and it told me to force start it using: > > mailman -C /etc/mailman3/mailman.cfg start --force > > I recall someone asking using bugzilla (?) a few months ago, if this could be in the startup file. > > What do you think about that? It is a bad idea because it allows using the normal startup to start a second instance of Mailman core when core is already running. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 02:23, Danil Smirnov wrote: > > I observe occasional error messages in MariaDB log even with NNTP runner > disabled via > ``` > [runner.nntp] > start: no > ``` > They look like this: > ``` > 2024-01-31 0:23:03 231666 [Warning] Aborted connection 231666 to db: > 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading > communication packets) ... > ``` > However, no harm caused by them was detected. Can you correlate these with mailmanweb.log entries that might indicate what Django was doing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 9/24/18 4:52 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> On 9/21/18 6:21 AM, Henrik Rasmussen wrote: >>> 2) How do I change the default for existing lists >> >> Postorius -> Settings -> Digest > > Sorry, I was unclear here. I was aware of changing the size in the web interface, but what I meant was changing the Digest Size Threshold value for all lists using REST API. > > Is that possible? Probably not in a single REST interaction, but you could iterate over all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 16/9/21 16:40, Mark Sapiro wrote: >> >> Are you asking what the equivalent MM 3 scripts would be? >> > More or less: I'm asking for a general direction here. I think I cannot > use tthe "withlist" method as before, inside a python script, and I'm > not sure how to do it. You can run scripts via withlist in Mailman 3 similarly to Mailman 2. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Shorted Subjects in Mailman

by Victoriano Giralt

On mar, 2022-07-26 at 09:50 +0000, Stephan Krinetzki wrote: > And again: The Mail from the beginning https://pastebin.com/gsVtvKm1 I'm not sure if Mailman does the transformation of the subject to Quoted Printable, but, I think that whatever is doing that is the most likely culprit, as "it" has added the QP terminator (?=) where the subject line breaks: Subject: =?utf-8?q?=5Bedv-support=5D=5BSAV- LINUX=5D_Notice_from_Sophos_Anti-Virus_on?= -- 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 ?

2 years, 8 months

[MM3-users] Re: RemoteUserBackend for Mailman3?

by Mark Sapiro

On 3/27/23 06:00, Markus Ludwig Grandpré wrote: > Dear MM§-users, > > is there a good documentation and example how I can learn to enable > > django.contrib.auth.backends.RemoteUserBackend > > for Mailman3? I've already found a detailed documentation (see [1]), but > I do not manage to implement this AuthN mechanism for Mailman3. Can you > help me? Have you configured your web server. If using Apache mod_wsgi, see https://modwsgi.readthedocs.io/en/master/user-guides/access-control-mechani… If proxying to a wsgi server, e.g. uWSGI or gunicorn, see the respective documentation for passing environment variables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] How to see the admin password reset in docker with mailman3

by bob B

I am setting up a new environment of Mailman3 in docker. I understand I have to reset the password to set the password for admin. I go to forget the password, in the GUI and I put in the address I have listed in the docker-compose.yaml and I never get the email. I look at the mail log on the host and I do not see the smtp connections. I assume Django is not using the docker host but sending the mail directly?? Basically, where can I see the password email rest mail logs to make sure an email was sent out and where it is going?

2 years

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/27/23 1:15 PM, Lars Bjørndal wrote: > [Mark] > >> This appears to be an issue with psycopg2 itself. >> >> What happens if you activate your venv and do >> >> python -c 'import psycopg2' > > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "/opt/mailman3/venv/lib64/python3.11/site-packages/psycopg2/__init__.py", > line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception Your psycopg2 installation is broken. Try to `pip uninstall` it and then install again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Message is received but is not sent out. Another, similar message, is processed fine.

by Mark Sapiro

On 6/27/23 12:30 AM, Stephen J. Turnbull wrote: > > That said, if the users are unable or unwilling to use UTF-8, it would > be possible to create a codec for "iso-8859-8-i", I don't know how to > do that, and I doubt Mark does. You could ask on > python-list(a)python.org, or file an RFE on Python's GitHub tracker. See https://github.com/python/cpython/issues/90079 filed by me in Nov 2021. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/22/24 17:51, Mark Sapiro wrote: > > If the Enable Digests setting is Yes, then the lack of digests needs > more investigation. OTOH, do you know digests are not being sent? With digests enabled and the threshhold set to 0, on each post a digest.mmdf will be created and then immediately moved to digest.<vol>.<num>.mmdf and an entry queued for digest runner to create the digest(s) from that file and remove it, so within probably a few seconds /opt/mailman/mm/var/lists/<LISTID>/ will be empty again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

[MM3-users] Re: Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty

by Tim Cutts

Thanks Mark. The migration seems to have done the trick for the archive - thanks for the pointer. Given that I have mailman-web running as www-data in Debian-style, I had to use: sudo -u www-data /opt/mailman/venv/bin/mailman-web migrate But that did the trick, and my archives have reappeared, so thank you. > On 7 Jul 2022, at 19:35, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/7/22 8:12 AM, tim(a)thecutts.org wrote: >> Hi everyone, >> As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. >> With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. >> However, there do seem to be two problems, which might be linked: >> 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory > > > Look in mailman.log. There will be exceptions and tracebacks associated with the shunted messages. What are these? Right, thanks for the pointer (there are so many separate log files, I’d been looking in the wrong one!) Jul 07 17:17:44 2022 (117110) SHUNTING: 1657210664.44771+e859f37833c541df3582ea334ab4b7b016557f77 Jul 07 17:23:39 2022 (117110) Uncaught runner exception: no nameservers Jul 07 17:23:39 2022 (117110) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 176, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 269, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 316, in check if maybe_mitigate(mlist, address): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 288, in maybe_mitigate answer = is_reject_or_quarantine( File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 177, in is_reject_or_quarantine resolver = dns.resolver.Resolver() File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 758, in __init__ self.read_resolv_conf(filename) File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 850, in read_resolv_conf raise NoResolverConfiguration('no nameservers') dns.resolver.NoResolverConfiguration: no nameservers Jul 07 17:23:39 2022 (117110) SHUNTING: 1657211019.9355967+2e5a440ca577e112e092e03072660a4314f012eb Purging the resolvconf package and configuring resolv.conf manually fixed that little issue. Thanks again for the help Tim > >> Are these issues likely to be related, or do I have two things going on here? > > > The shunted messages are not related to the Django migration issues. > > -- > 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/

2 years, 9 months

[MM3-users] How to get Mailman core to provide more debug info in a running environment

by Henrik Rasmussen

Docker-mailman 0.1.1 I am using Mailman 3.1 in production and I am trying to debug a problem[1] so I tried to setting Mailman to provide more debug info in the smtp.log file[2]. I might have been doing it wrong, but in the mailman-extra.cfg I set [logging.smtp-failure] path: smtp.log and restarted Mailman, which stopped incoming mails until removing the added section. What is the correct way to get Mailman to provide more debug info in the smtp.log 1) https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… 2) http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html… Henrik Rasmussen

7 years, 6 months

[MM3-users] Mailman Core: REST API: Member Subscription Invitation

by Peter Knowles

Product: Mailman Core Version: 3.3.10 When I post an "invite" to the REST API: http://localhost:8001/3.1/members Params: list_id = list.domain.tld subscriber = some(a)email.address display_name = Some Name invitation = true Should Mailman Core be attempting to send an "invitation" email to the "subscriber" address, or is this the job of the "client" calling the API? I understand the API does return "token", and "token_owner" on success, which I assume the "token" would be used for a subsequent "verification" process. I'm developing my own "frontend" for "subscribers", "moderators", "list admins", and "system admins" respectively. Sort of working through understanding what Core does and does not do itself.

2 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Dmitry Makovey

On 10/18/2017 12:28 PM, Mark Sapiro wrote: > On 10/18/2017 09:00 AM, Dmitry Makovey wrote: >> >> It seems like mailman-core is still operating properly, but for some >> reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? > > > I'm not very well versed in the docker images, but I think mailman-web > uses uWsgi and sending the uwsgi process a SIGHUP should do it. I think I didn't express myself clearly - I want to reset any saved state for mailman-web - not just in-memory stuff. I've restarted my setup several times with mailman-web having exact same problem every time. -- Sr System and DevOps Engineer SoM IRT

7 years, 6 months

[MM3-users] Re: Converting non-members to members

by Alan So

I manage to use the following code to catch the http error code 409 so that the script won't exit. I hope that it is the appropriate way to handle. So, the remaining question is whether a non-member can be removed as we do not want the remaining non-member setting affect member setting if such a member is removed using the web UI. try: imported = my_list.subscribe(nonmember.email, 'Import from nonmember', pre_verified=True, pre_confirmed=True, pre_approved=True) importedmember = my_list.get_member(nonmember.email) print ("Importing " + nonmember.email) importedmember.moderation_action = nonmember.moderation_action importedmember.save() prefs = importedmember.preferences prefs['delivery_status'] = 'by_user' prefs.save() except HTTPError as e: if (e.code == 409): print ("Already imported " + nonmember.email) else: raise

6 years, 3 months

[MM3-users] Showing sender as ... via ... list

by Wolfgang Bock

Hello, after correcting little discrepancies within the mm3 configuration proposals in the debian buster package and the help of Mark I am very pleased with it now. BTW: There is a very helpfull instruction for installing other mail components like dovecot/postfix/etc on https://workaround.org/ispmail/buster/ actually not yet for bullseye, but my experience is: it will come soon. So I dont understand the discussions like: "hands off debian mm3 packages". Here is my question: What do I have to configure to get my lists to show the sender like in this list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> I tried several combinations but failed upto now. Can someone help?? Regards Wolfgang

3 years, 5 months

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

by Mark Sapiro

On 2/2/23 04:26, Odhiambo Washington wrote: > > Okay. This is a bit off from my understanding. > > What is the cause and how do I mitigate it? The cause is the monthly hyperkitty update_and_clean_index job runs for a long time, i.e. hours, because it is rebuilding the entire search index so during the time it's running multiple hourly hyperkitty update_index jobs are started and they are competing for the same lock. See https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… for mitigation. -- 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: [Mailman-Developers] Re: SSL error while connecting to hyperkitty

by Mark Sapiro

On 11/28/23 20:50, Odhiambo Washington wrote: > On Wed, Nov 29, 2023 at 4:56 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > >> Do you have new link for this >> http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server >> currently not accessible. >> > > https://docs.list.org/en/latest/install/virtualenv.html#setting-up-a-wsgi-s… Where did you find the link to <http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server>? If it's somewhere in our docs or wiki, I want to fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Enable Notifications on Mailman3 Threads

by Mark Sapiro

On 12/14/23 11:15, jdamos(a)iu12.org wrote: > In my environment, I am trying to enable notifications on a thread just like this one. When someone responds, I want the list to get a notification and or the person that is getting responded to. I don't understand. I am responding to your post. My response should go to you and all the other list members with delivery enabled. What are you asking for beyond that. If someone responds off list to you, Mailman never sees that response so there's nothing Mailman can do about it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 14:34, jkoral(a)luc.edu wrote: > Mark, thank you for the quick reply. We will most likely need to migrate the lists over a period of time. So the DNS cannot be changed at the moment. Both servers have different FQDNs. Any suggestions on what we can do? If lists on the old and new servers have the same posting address domain you have to configure the incoming MTA on the old (MM 2.1) server to relay mail for the migrated lists to the new server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 3:35 PM, Mark Sapiro wrote: > On 7/7/22 3:09 PM, David Newman wrote: >> >> I *think* the command runs if I escape the hyphen: >> >> root@somehost:/opt/mailman/venv/lib/python3.9/site-packages# grep -r >> '\-jango' /opt/mailman/venv/lib/python3.9/site-packages/ >> >> But then that doesn't return anything. > > Yes, escaping the hyphen is the correct thing to do. You could also try > something like > ``` > grep -r '.-jango' /opt/mailman/venv/lib/python3.9/site-packages/ > ``` > but that will also return nothing. > > See > https://stackoverflow.com/questions/67613777/pip-ignoring-invalid-distribut… > https://stackoverflow.com/questions/68880743/why-do-i-get-this-when-using-p… > and perhaps other hits from > https://www.google.com/search?q=pip+warning+ignoring+invalid+distribution > > Look for > ``` > ls -la /opt/mailman/venv/lib/python3.9/site-packages/~jango* > ``` > i.e. `~jango` rather than `-jango` Interesting -- that does produce two directories with names starting with a tilde: /opt/mailman/venv/lib/python3.9/site-packages/~jango: total 100 drwxr-xr-x 19 root root 4096 Jul 7 10:56 . drwxr-xr-x 188 mailman mailman 12288 Jul 7 12:38 .. drwxr-xr-x 3 root root 4096 Jul 7 10:56 apps drwxr-xr-x 3 root root 4096 Jul 7 10:56 bin drwxr-xr-x 7 root root 4096 Jul 7 10:56 conf drwxr-xr-x 18 root root 4096 Jul 7 10:56 contrib drwxr-xr-x 11 root root 4096 Jul 7 10:56 core drwxr-xr-x 6 root root 4096 Jul 7 10:56 db drwxr-xr-x 3 root root 4096 Jul 7 10:56 dispatch drwxr-xr-x 5 root root 4096 Jul 7 10:56 forms drwxr-xr-x 3 root root 4096 Jul 7 10:56 http -rw-r--r-- 1 root root 800 Jul 7 10:56 __init__.py -rw-r--r-- 1 root root 211 Jul 7 10:56 __main__.py drwxr-xr-x 3 root root 4096 Jul 7 10:56 middleware drwxr-xr-x 2 root root 4096 Jul 7 10:56 __pycache__ -rw-r--r-- 1 root root 4896 Jul 7 10:56 shortcuts.py drwxr-xr-x 5 root root 4096 Jul 7 10:56 template drwxr-xr-x 3 root root 4096 Jul 7 10:56 templatetags drwxr-xr-x 3 root root 4096 Jul 7 10:56 test drwxr-xr-x 3 root root 4096 Jul 7 10:56 urls drwxr-xr-x 4 root root 4096 Jul 7 10:56 utils drwxr-xr-x 6 root root 4096 Jul 7 10:56 views /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: total 500 drwxr-xr-x 2 root root 4096 Jul 7 10:56 . drwxr-xr-x 188 mailman mailman 12288 Jul 7 12:38 .. -rw-r--r-- 1 root root 36843 Jul 7 10:56 AUTHORS -rw-r--r-- 1 root root 83 Jul 7 10:56 entry_points.txt -rw-r--r-- 1 root root 4 Jul 7 10:56 INSTALLER -rw-r--r-- 1 root root 1552 Jul 7 10:56 LICENSE -rw-r--r-- 1 root root 13231 Jul 7 10:56 LICENSE.python -rw-r--r-- 1 root root 3625 Jul 7 10:56 METADATA -rw-r--r-- 1 root root 415583 Jul 7 10:56 RECORD -rw-r--r-- 1 root root 7 Jul 7 10:56 top_level.txt -rw-r--r-- 1 root root 92 Jul 7 10:56 WHEEL Going back to the original warning: (venv) mailman@somehost:/home/dnewman$ pip show mailman-web WARNING: Ignoring invalid distribution -jango (/opt/mailman/venv/lib/python3.9/site-packages) Name: mailman-web .. The warning goes away after moving those two tilde directories out of the way. Is it safe to delete them? Thanks again. dn

2 years, 9 months

[MM3-users] Re: no mails to list members

by Abhijith PA

On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: > On 04.01.19 09:40, Thomas Stein wrote: >> >> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >> i missed something else but after adjusting the permissions of that template everything worked as expected. > > While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should > I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation > what variables i can put in those templates? If you are using 3.2.0, you can do that from webapp itself. [ I haven't tried though] --a

6 years, 3 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/30/20 1:57 PM, Mark Sapiro wrote: > > Setting > > local_recipient_maps = > > disables all local recipient checks. If you don't want to do that, you > need to specify whatever the current or default setting is in addition, e.g. > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/var/data/postfix_lmtp > > > See <http://www.postfix.org/LOCAL_RECIPIENT_README.html> > > We need to update the docs for that setting. And we have. <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#transpor…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Dadgar

On Jun 18, 2020, at 10:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > The grizz.org domain was recently migrated from from a larger server in > a colo that supported multiple domains to a DigitalOcean droplet which > initially had only 4 GB RAM, but that seemed marginally enough at best, > so I upgraded it to 8 GB. My 4GB DO droplet runs a couple of mm3 lists, including one that does ~4000 posts/month times ~400 recipients, running postgres, with no signs of the OOM killer. In fact, the only time I’ve ever seen it is when I was using the mailman3 shell to search for bad characters in the archives the other day. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Re: Recently active discussions - Hyperkitty

by Mark Sapiro

On 5/31/24 12:22, Sam Darwin wrote: > > Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. > > What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? It's based on the Date: headers of the messages. Are there messages with Date: headers in the last month? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Removing a moderator via the REST API

by Mark Sapiro

On 11/14/24 13:44, Andy Matthews wrote: > > However it doesn't appear that you can remove a person as moderator via the API, per a comment made by Mark on 8/12/24 in this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I'm not sure what I said there to make you think that, but first you have to be able to do this via the API because Postorius does it via mailmanclient which uses the API. See https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: ARC

by Marvin Gülker

Am 14. August 2019 um 20:44 Uhr -0000 schrieb brian(a)emwd.com: > Did you keep an eye on the reputation on the IP addresses you were > sending from? Sometimes an IP address just doesn't send enough volume > of mail to build one up. This mail server ever only sent my personal and my family's e-mail -- no public mailing lists. The volume was very low. Maybe about ten e-mails a week in average, sometimes no e-mail a week at all. If low e-mail volume is indeed a criterion, then it could be the cause. But low volume as a spam criterion strikes me as doubtful, because a spammer specifically wants to issue mass e-mail. The server was online since I think 2013 and always had the same IP. It wasn't a shared IP, i.e. this mail server was the only one sending from that IP. The spam classification problem was there from the very beginning. > We did get that fixed. The key to Microsoft is to sign up for > their Hotmail Feedback Loop. They also provide a nice interface (SNDS) > that shows you what they think of your IP addresses so you can > mitigate any potential delivery issues ahead of time. I'm leaving that to my SMTP relay provider now. I find it too much hassle to sign up for such services just for my private e-mail. I'm not getting paid for sinking my time into this; keeping the server running and clean is enough of time investment into my hobby (I use it for other things than e-mail, too). Microsoft is not the only e-mail provider, so if all e-mail providers did it like that, you'd have to create dozens and hundreds of accounts. Microsoft's pure size is what allows them to pose such a restriction successfully. The real problem is the centralisation of services at only a few providers. > Yahoo is the worst. Luckily, Yahoo e-mail addresses are so rare in Germany that I can ignore them. I don't have anyone with a Yahoo address in my address book currently. outlook.com is much more common, but from my experience most German e-mail addresses are hosted by the United Internet group (GMX et al.), which I never had problems delivering to. They do a decent job. As for GMail, after a few attempts with followup questions my contacts started looking into their spam folder. That's why I was fine without the SMTP relay provider for years. But since recently, more and more people use outlook.com, which outright rejected. > The majority reason why messages ends up in Spam folders has nothing > to do with the mail server at all. It is because the content of the > message comes across as spammy, i.e. a message that contains several > URLs, using exclamation points, etc. Normal private 1-1 correspondence usually does not fulfill these criteria, and I've still been filed/rejected as spam (and likewise other family members). I felt like Don Quixote fighting the windmills. Today's e-mail infrastructure makes things difficult for private individuals who want to self-host. Anyway, I think this subthread has grown large enough. My questions were answered. Thanks to everybody who commented! -- Blog: https://mg.guelker.eu

5 years, 8 months

[MM3-users] Re: Can't remove footer(s)

by Henrik Rasmussen

Mark Sapiro wrote: > The templates named list_member_digest_footer.txt and > list_member_regular_footer.txt (with underscores) were created by > import21 and set as the URIs for those templates. Had you just copied > /dev/null (or otherwise made empty) those files and done nothing else, > that would have done what you wanted, but since you deleted the template > URIs for the list, the template names are now the default How do I make these not default? > list:member:digest:footer.txt and list:member:regular:footer.txt names > (with colons) and those are the empty files you need to create. Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? Henrik

6 years, 6 months

[MM3-users] Re: Adding list via web form

by Mark Sapiro

On 11/2/22 15:25, fstltna--- via Mailman-users wrote: > Trying to add a list using the web form but I get this: "Error: You are not authorized to create new mailing lists". Do I need to log in somewhere? I thought I was logged in as admin but maybe not? You need to be logged in as a Django superuser. See the Django admin command createsuperuser. Although if you are not logged in as a superuser, the Create New List button should not appear on the index page. Did you go to https://example.com/mailman3/lists/new/ directly? -- 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] Authenticating against Hyperkitty's DB

by Marvin Gülker

Hi, inspired by the question about LDAP, I want to ask a related question. We're currently thinking about adding a wiki to our small OSS project, and requiring users to have multiple accounts for the same project is nonsense. We don't have LDAP set up yet, but we do have a running Mailman 3 installation, including Hyperkitty. Thus I thought about whether it's possible to just write some glue script that authenticates against the user information in Hyperkitty's database. Creating an account for Hyperkitty would then be sufficient to get access to the wiki. Could someone give me a hint where and in what format Hyperkitty stores the user information into its database? Marvin -- Blog: https://mg.guelker.eu

5 years, 8 months

[MM3-users] Re: django-mailman3 update causing errors

by Mark Sapiro

On 05/02/2018 07:12 AM, Darren Smith wrote: > So we have pulled all fresh versions of these projects from gitlab as of > last Friday: > > postorius > hyperkitty > django-mailman3 > mailmanclient > > Django is version 1.11 > > When we installed, each of these were placed in a conda virtual > environment. Postorius, Hyperkitty, and django-mailman3 are all still under > a python 2.7 environment. Is that our problem here? Do they need to be in > python 3 now? Yes, that is exactly the issue. The current GitLab branches all require Python >= 3.5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Moderate mails from owner

by Henrik Rasmussen

Do I have to make a commit or something? Even m.accept_these_nonmembers.remove removes the member from the list, it is right back when I return to the Mailman shell: > bash-4.3# mailman shell -l [LISTNAME].lists.example.com > Welcome to the GNU Mailman shell > The variable 'm' is the [LISTNAME].lists.example.com mailing list > >>> m.accept_these_nonmembers > ['listadmin(a)senderdep.example.com'] > >>> m.accept_these_nonmembers.remove('listadmin(a)senderdep.example.com') > >>> m.accept_these_nonmembers > [] > quit() > # bash-4.3# mailman shell -l [LISTNAME].lists.example.com > Welcome to the GNU Mailman shell > The variable 'm' is the [LISTNAME].lists.example.com mailing list > >>> m.accept_these_nonmembers > ['listadmin(a)senderdep.example.com']

5 years, 11 months

[MM3-users] Re: How to remove a nonmember from a list

by skenny＠scss.tcd.ie

Thanks for that Abhilash. I've since figured out how to add and remove nonmembers using the REST API. Regarding the web interface, I wonder could you comment on the following: I've created a test list and I have added a large number - 1,800 - of nonmembers to it. I find that if I try to delete a nonmember via the web interface, it seems to hang, and then the following message appears: Something went wrong Mailman REST API not available. Please start Mailman core. The same operation succeeds on other lists, where the number of nonmembers is not large. Do you think this could be an issue of scale? Thanks Stephen

5 years

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Brian Carpenter writes: > Well I am having the same difficulty. *With your statement here, > let me ask you this:* Evidently you haven't understood how I propose to address the issue. My answer to each of your suite of questions is, "it doesn't matter because I'll ask the member what to do when the time comes." This approach is - explicit, - effective in addressing the original issue, - almost no burden on users, - little burden on administrators, and - no burden on Mailman developers for analyzing scenarios. Are you tired of all the winning yet? ;-) If somebody wants more automation, patch for optional automation welcome. Or they can pay for Harmony. Can we please stop this now? Steve

4 years, 5 months

[MM3-users] Re: mailman-full question

by Mark Sapiro

On 9/25/22 05:44, flatley wrote: > - to configure the db in venv i would use mailman-web migrate - this > works fine - but mailman-full install does not seem to include mailman-web > or mailman3-web - the mailman info cmd works fine - do i need to > also install mailman-web? i had thought the mailman-full included all > components I'm not sure what it's called in the Debian/Ubuntu mailman-full package, but the `mailman-web` command installed by `pip install mailman-web` is the Django admin command, possibly called `django-admin` or `manage.py` in the mailman-full package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 01:19 PM, Rafael Mora wrote: > What should I do to tell Postfix to use my domain?? for example send emails > using the email account mailing(a)labbrands.com If what you're asking is how to configure Postfix to relay all outbound mail via some other email server, that is a Postfix configuration question. If I thought I could give you a simple answer and that would be the end of it, I'd try, but in your case every answer leads to another question, so I suggest you start here to learn about configuring Postfix <http://www.postfix.org/documentation.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

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

4 years, 5 months

[MM3-users] Re: Twitter OAuth2

by Mark Sapiro

On 12/27/22 21:46, Odhiambo Washington wrote: > On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> I see from another post that you've decided against using Twitter, but >> to answer the question, Twitter does not require adding anything to >> SOCIALACCOUNT_PROVIDERS. >> > > I tried it and ended up with: > > ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: > /accounts/twitter/login/ > Traceback (most recent call last): ... > allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > query does not exist. Do you have 'allauth.socialaccount.providers.twitter', in INSTALLED_APPS? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Message does not appear in archive

by Simon Hanna

On 8/30/18 6:40 AM, paul(a)arenson.org wrote: > Well, I have looked here to see my previous post (and to check how the archives look), but i do not see the below. post. > > Am I missing something. > > ARCHIVE I SEARCHED > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> > > The thread: Re: [MM3-users] Using as a forum > > Can someone advise? It is being archived. You can find it here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You can see it listed here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2018/8/ Hyperkitty has a "little" problem with caching and cache-invalidation...

6 years, 7 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Stefan Tatschner

On Mon, 2018-12-03 at 10:01 -0800, Abhilash Raj wrote: > So, if you are using Django's ORM to keep the task states in Django Q, this > is bound to happen depending on how frequently do you run tasks. In Hyperkitty, > we have some minutely tasks, which means the polling is going to be high. > > You can however, configure Django Q to store the tasks outside of database > in a better high-speed in-memory database like Redis for example[1] for queuing > the tasks. Other options like MongoDB, Amazon SQS is also available. Is it really necessary to have these high complexity? Reducing database load by introducing another database seems wrong to me. Stefan

6 years, 4 months

[MM3-users] Re: /bin/sh: sassc: command not found

by Ralf Wiegand

Thank you Mark, where do I find this section of code? On 4/22/20 2:56 PM, Mark Sapiro wrote: > On 4/22/20 11:38 AM, Ralf Wiegand wrote: >> /bin/sh: sassc: command not found - Not sure on what I am missing? > > You currently have something like: > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > in your settings. > > Either install sassc or you can install ruby-sass and change the settings to > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > >

5 years

[MM3-users] Re: xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??

by Mark Sapiro

On 7/29/24 03:27, Odhiambo Washington via Mailman-users wrote: > Today, my hourly cron job has generated an error and continues to do so > every hour: > > ``` > Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs hourly > ``` > > Not sure what caused this. Perhaps a reboot when the cronjob hadn't > completed? And a possible manual remedy would be to wipe the indexed db and > let the cron run again? Or maybe just run `/opt/mailman/mm/bin/django-admin rebuild_index` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Read mailing list config via CLI

by Andy Matthews

I'm working on a feature to allow configuration of mailing lists using the REST API. The docs show how to do this: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… But I'd like to be able to verify settings using the mailman command or Python shell; and surprisingly I can't find where in the docs it shows how you can read settings on a per-list basis. I'm fine with either option, but I've spent about an hour digging through source code and docs and I'm not finding it. Would someonebe so kind as to point out how I can inspect configuration on a list by list basis? TIA.

7 months

[MM3-users] Re: Mailman 3 Installation

by Mark Sapiro

On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: > I am trying to set up Mailman 3 on a new server. So far I have run: > > pip3 install Django==3.1.5 This will be a minor issue. django-mailman3 requires Django>=2.0,<3.2; HyperKitty requires Django>=2.2,<3.2, but postorius requires Django>=1.11,<3.1. We really should be more consistent with these requirements, but what this means is > pip3 install postorius will install Django 3.0.11 alongside Django 3.1.5. > pip3 install Hyperkitty > pip3 install mailman > pip3 install uwsgi > > All that went well. I've been struggling with the configuration though. I am using /etc/mailman.cfg and that seems to be explained in the documentation OK. From there I am confused. > > I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? You can use sqlite, but if you don't already have a mysql/mariadb database on the server, we recommend postgresql for performance and robustness. I personally have had issues with mysql and use postgresql on one production server that uses mysql for other applications. > I think I can follow the instructions to set up postfix. > > In the section 'Configure Web Frontend', it discusses setting up the administrator. As I want to put Mailman on /srv/mailman I can create that, but what should the owner/permissions be? Later the docs discuss editing Django's settings.py. Where do I find that file? I'll note here that my experience with python is quite limited and my knowledge of Django is nil. There should be a 'mailman' user that is the user under which you run things. Don't run things as root. sudo chown -R mailman:mailman /srv/mailman For settings.py and some others, see <https://gitlab.com/mailman/mailman-suite/-/tree/master/mailman-suite_project>. The end of settings.py imports from settings_local so you put your local overrides in settings_local.py in the same directory as settings.py > Later in the section 'Set up HyperKitty', it sends me to a page that discusses installing it. I did that with pip3. Then it says to 'Setup your django project'. What django project is that. Postorius and HyperKitty. See settings.py. These files, settings.py and settings_local.py need to be in a directory that also includes an empty __init__.py so python can import from it and this directory needs to be in the path that Django runs with. This is a shell script I use to run django. It uses a virtualenv, but that isn't necessary. Also my stuff is in /opt/mailman/mm/, but it could just as well be /srv/mailman. #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ > I would appreciate advice or a pointer to where I can figure this out. Thanks. There is a work in progress you may find more helpful. See <https://gitlab.com/mailman/mailman-suite-doc/-/merge_requests/55#note_48712…> and the 'Rendered documentation' linked therefrom. You might also find <https://wiki.list.org/x/17891998> and/or the docs linked from its first paragraph to be helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: confirm-email: error NoReverseMatc

by Simon Hanna

On 01/31/2018 11:59 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Simon Hanna wrote: > >> It's complaining about an empty url used for reversing. Do you mind sharing >> your settings.py file? we don't need the secret key and logins for stuff, so >> you can mask those. the rest should be ok to make public. > Ok, here are the settings (mainly from mailman-suite): > > SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' > LOGIN_URL = 'account_login' > LOGIN_REDIRECT_URL = '' > LOGOUT_URL = 'account_logout' I guess that's the issue. Try using something else for LOGIN_REDIRECT_URL It should either be a valid path so "/postorius/" for instance or a valid view name like "list_index"

7 years, 2 months

[MM3-users] Re: Open List

by Mark Sapiro

On 5/13/20 12:22 PM, Samir Faci wrote: > So, > > I found a setting to allow me to create an Open List. I assume this is > still doable in MM3 though I can't find the equivalent option. > > https://mail.python.org/pipermail/mailman-users/2009-March/065479.html Settings -> Message Acceptance -> Default action to take when a non-member posts to the list. > 2nd question is how do I create a new List Style. I'd like Open- Archived > and Open-NonArchived to be options when creating a new list. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Installation Questions [Installation}

by Ron / BCLUG

Arte Chambers via Mailman-users wrote on 2024-11-03 17:58: >> For other things like the systemd service and the postfix and web >> server configs, you need to do them as root (via sudo). > > Does this mean i need to add the mailman user as a sudoer? No, user mailman can talk to postfix without being in any other groups than mailman. It just means that to edit the postfix config files or start / stop mailman via systemctl, one needs root privileges. Those are generally only needed when initially setting everything up. Once setup is complete and you run `systemctl enable --now mailman3 mailman3-web`, mailman will start after every reboot and there's no need to touch it any further.

5 months, 2 weeks

[MM3-users] Re: MM2 to MM3 on different server. Process to move everything at once.

by Mark Sapiro

On 12/12/24 10:37, Jeremy Stanley wrote: > > Not long ago I did this for many lists on quite a few different > domains, the tools will still be the same either way, but you can > run the commands over and over in a loop. Plan thoroughly, check > carefully, log everything. One thing to be aware of when doing multiple lists is to run hyperkitty_import with the --no-sync-mailman option for all but the last run. This will save some time and computing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: settings sanity check

by David Brown

[mostly ninja'd by Jeremy, but I 'd already typed this, and you might find PyCharm a useful editor.] I'm not a Django expert, but from https://docs.djangoproject.com/en/4.1/topics/settings/ it sounds like they just import the settings.py as a module. This means it is run by the python language itself as a python program. It's not merely a data file describing the settings -- it's code that is run as a program. The name Q_CLUSTER refers to a variable and the = operator assigns the value on its right hand side to that variable/name on the left. (The curly braces enclose an object literal: a comma-separated list of name: value pairs.) So, it will go with the second set of properties for Q_CLUSTER. There is no error; it's perfectly okay to store one value to the name/variable Q_CLUSTER and then later in your program assign a different value to the same name/variable. The code runs from top to bottom, so the second value assigned to Q_CLUSTER is what remains in memory after these settings have been processed. If you would like a tool that *would* complain, take a look at PyCharm Community Edition (no cost... not sure it's free-libre, though) from JetBrains: https://www.jetbrains.com/pycharm/download/#section=windows When I paste your snippet into an PyCharm editor window, it puts a warning highlight behind the second instance of Q_CLUSTER. When I hover over that, a pop-up tooltip cautions that I "Redeclared 'Q_CLUSTER' defined above without usage' and I can click on it for an extended explanation. (It also caught that you have three spaces before 'retry' and then four before 'timeout'... in some places in python syntax, inconsistent indentation is an error, but not here) Hope that's helpful. -- David Brown, IT Specialist dave(a)aasv.org This message contains confidential information belonging to the American Association of Swine Veterinarians (AASV) and is intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by email if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the AASV. -----Original Message----- From: Odhiambo Washington <odhiambo(a)gmail.com> Sent: Wednesday, February 8, 2023 2:50 AM To: Mailman users <mailman-users(a)mailman3.org> Subject: [MM3-users] settings sanity check Does mailman-web do sanity checks in settings.py? Suppose I have the following: Q_CLUSTER = { 'name': 'mailman3-web', 'workers': 8, 'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default', } Q_CLUSTER = { 'retry': 320, 'timeout': 300, 'save_limit': 100, 'orm': 'default', } Which setting will it go with? And why doesn't it complain about a setting being made 2x? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) _______________________________________________ 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 dave(a)aasv.org

2 years, 2 months

[MM3-users] Re: Bounce processing

by Barry Warsaw

On Aug 11, 2017, at 06:02, Mark Ziranski <Wal3(a)gmx.net> wrote: > I read that mailman3 supports 'bounce processing' but I do not know how > to configure it. I want to delete members automatically from a mailing > list if the delivery has failed after a certain time of attempts > because his mailbox has been removed or his mail server has been > shutdown etc. There is also the case that an users mailbox is full > (mailbox limit exceeded). Is possible to deal with this case too? Bounce processing is currently incomplete in Mailman 3.1. We will fix that in Mailman 3.2. (I was going to include a link to the issue, but GL is giving me a 500 error right now.) -Barry

7 years, 8 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Mark Sapiro

On 5/3/20 10:04 PM, Samir Faci wrote: > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead of > # localhost for Postfix integration, because Postfix only consults DNS > # (e.g. not /etc/hosts). > lmtp_host: lists.domain.org > lmtp_port: 8024 Why, in spite of the comment, do you have lmtp_host: lists.domain.org and not lmtp_host: 127.0.0.1 Note that lmtp_host: 127.0.0.1 lmtp_port: 8024 are the defaults. > So, now it's finally working but here's a question. Does 8024 need to be > publically accessible from the outside? No. Port 8024 is only for LMTP delivery from Postfix to Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: migration plan and auto responder

by Mark Sapiro

On 7/21/20 12:02 PM, Mohsen Masoudfar wrote: > Hi, > > The short version of this question is: > > How May I setup on Mailman2 to send an auto response to the member who sent an email to the list, but do not send the original email to any list member? In the web admin UI, go to Auto-responder, set autorespond_postings to Yes and set your message in autoresponse_postings_text. You probably also want to set Privacy options... -> Sender filters -> member_moderation_action to Discard and on Membership Management... -> Membership List under Additional Member Tasks, set everyone moderated. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark London

Has anybody attempted to change the format of the emails that are sent to the owner of a mailing list, to include a URL, instead of stating "visit your dashboard"? The former is the behavior of Mailman 2. Is there any reason why this can't be done? If nobody has tried to do so yet, I'll give it a try myself, as I'm familiar with django. Thanks. - Mark At your convenience, visit: https://.../mailman/admindb/... to approve or deny the request. The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request.

1 year, 11 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Ralph Seichter

* Mark Sapiro: > It's still a work in progress. Of course. I did not mean to criticise, just point out what settings I was surprised not to find in the UI. > To not add headers and or footers, you need empty templates for them. > These could be created via the list's Templates form except until [1] > is fixed, you can't make empty templates. I actually found a workaround in the meantime: update template set uri='file:///dev/null' where id=123; Not that I like to modify the underlying database manually, but it seems to do the trick for now. -Ralph

6 years, 1 month

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/8/22 8:28 AM, David Newman wrote: > > This system runs Debian 11, with everything installed in a venv. I'm > unclear on the relationship between the usual apt* tools and pip, and > just do everything Mailman-related using pip. apt will not install into a virtualenv, even if the virtualenv is active when running apt-get. It only installs system wide. Further, apt doesn't know about packages installed by pip (either system wide or in a virtualenv) and vice versa. See https://askubuntu.com/questions/581648/install-package-into-virtualenv-usin… for more. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 4 Nov 2021, at 11:57 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914<https://gitlab.com/mailman/mailman/-/issues/914> and this was a fix for that. Yeah I’m seriously amazed we’ve not had complaints in the year we’ve been running mailman3 that people have lost emails to multiple lists. Only now that you fixed the exception have people seen missing emails :) Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. -- 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> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 5 months

[MM3-users] Re: 'str' object has no attribute 'token_type'

by Mark Sapiro

On 11/15/21 6:06 AM, Marco Marinello wrote: > Hi everybody, > > I'm sorry for being always the strange guy with strange errors here but for some reason... I am. > On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: > > > Traceback (most recent call last): > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner > response = get_response(request) > File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator > return func(request, *args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view > return view_func(*args, **kwargs) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive > add_to_list(mlist_fqdn, msg) > File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list > from_str = header_to_unicode(message['From']) > File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ > the values matching a header field name. > File "/usr/lib/python3.9/email/message.py", line 471, in get > for k, v in self._headers: > File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse > return self.header_factory(name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ > return self[name](name, value) > File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ > cls.parse(value, kwds) > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in parse > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> > [Address(mb.display_name or '', > File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name > return self[0].display_name > File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name > if res[-1][-1].token_type == 'cfws': > > Exception Type: AttributeError at /hyperkitty/api/mailman/archive > Exception Value: 'str' object has no attribute 'token_type' > Request information: > USER: AnonymousUser > > > I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. > Any clue of what could have happened, why and how to fix it? The exception is thrown in the Python email package on HyperKitty's attempt to get the From: header of the message. This looks like https://bugs.python.org/issue43501 and/or https://bugs.python.org/issue30988. These issues refer to display names beginning or ending with a dot. Is that the case with the From: header of the problem messages? Note that display names containing dot should be quoted. It appears that at least one of the people posting posts with the problem From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: footer message

by Mark Sapiro

Sorry for not rep[lying sooner. This got misplaced. On 9/20/18 6:14 AM, Henrik Rasmussen wrote: >>From lists imported by import21, the colon in the files are substituted with underscores. Instead of list:member:regular:footer.txt the file are called list_member_regular_footer.txt The latest import21 doesn't do that any more. > And I wonder why having a footer text makes the mail contain the original HTML message sent to the list as attachment both in .txt and .html and the footer-text from list_member_regular_footer.txt as inline message. See <https://wiki.list.org/x/4030707>. While aimed at Mailman 2.1, much of this is relevant to Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Hyperkitty Authorization Required

by Mark Sapiro

On 6/6/19 5:52 AM, andrew.bernard(a)gmail.com wrote: > Nearly there configuring my first Mailman 3 installation with Postorius and Hyperkiity. This issue eludes me: > > When trying to start a new thread in the archive, we have: > > HyperKitty failure on https://list.jackrail.org/hyperkitty/api/mailman/archive: <html><title>Auth required</title><body> > <h1>Authorization Required</h1></body></html> (401) > > I can access this URL just fine" > > https://list.jackrail.org/hyperkitty/api/ > > Where do we look to solve this issue? You have to be logged in to post from HyperKitty. You can't post anonymously. -- 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: Subscription issue with ghost confirmations

by Stephen J. Turnbull

Brian Carpenter writes: > So the question now is: Is this a bug? Or an intentional design? I consider it a bug. The intent behind having independent options for moderation and confirmation is to provide for moderated lists in close-knit communities. There are many reasons the list owner might want to configure the list "opt-in", but they do know everybody and moderation is "enough security" for them. I don't have a guess why it's happening. I may be able to look at it in a few days, but this is my busiest quarter and COVID and election jitters are making it worse, so we'll see. Maybe Abhilash or Mark can get to it sooner. Steve

4 years, 5 months

[MM3-users] Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/15/21 9:32 AM, Mark Dadgar wrote: > > That’s actually why I paid someone to do in the initial install. While I have 3+ decades of UNIX-like admin experience, I am not even remotely well-versed in Python and its ecosystem and/or Docker. > > Unfortunately, the person I hired, who did a great job and has contributed mightily to this community, is no longer with us. He did however post a writeup at <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10>. There is also <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> from another user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Another set of new releases

by Abhilash Raj

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

5 years, 3 months

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

by Mark Sapiro

On 3/14/22 04:07, Stanisław Findeisen via Mailman-users wrote: > 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. In your opendkim.conf set SenderHeaders List-Post,Sender,From See the MAILING LISTS section in http://www.opendkim.org/opendkim-README -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: MM3 List Templates

by Odhiambo Washington

On Wed, Dec 21, 2022 at 1:50 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > I am reading > https://wiki.list.org/DOC/Mailman%203%20installation%20experience > regarding templates and I am confused about > whether to treat the path /opt/mailman/mm/var/templates/*site*/en/ > literally or even if that information is still relevant. > I created the exact path and put those templates in there, but they do not > show up on Postorius. > Responding to myself and apologizing for the noise. I have read https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… as regards templates. There is still a lot to learn about MM3. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Sendgrid experiences

by Andrew Hodgson

Hi. I am temporarily using Sendgrid now on my Mailman instance. Initial observations have been positive. A list with 100 users is racking up email delivers though, I am on the basic paid account which gives me 50k emails per month. I was hoping to use a cheaper provider and pay overage costs per email on the assumption that I'm seeing a spike in traffic today because people have started getting the messages again. Sendgrid is maintaining the Message-Id header which is good for archiving. It is re-writing the Return-Path header though which means that bounce handling in Mailman won't work, but I think all the services do this in some way so I am happy to live with that for the moment. Hope this helps. Andrew.

1 year, 11 months

[MM3-users] Re: Mailman 3 Privacy Policies, GDPR, etc and social logins

by Mark Sapiro

On 9/19/23 6:22 AM, Jered Floyd wrote: > > This is a bit of a headache. Do we have a draft of a community Privacy Policy for a vanilla Mailman 3 install that meets Facebook's requirements? Is this going to be a constantly unraveling thread of future GDPR and Right to Be Forgotten troubles, since there doesn't seem to be an easy way to scrub a subscriber from Hyperkitty archives if they request so? How have others addressed this situation? I use https://www.list.org/privacy.html which appears to satisfy Facebook. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: So, why are css & js files only served with "DEBUG = yes" ?

by Simon Liebold

Am 07.05.2017 um 16:12 schrieb Simon HANNA: > js and css files are static and should be served by your web server of choice. In a development environment you usually don't have a web server running, so django serves the files itself. > > Your webserver can serve these static files much faster than django can, so django doesn't serve them in production by default. You can find instructions on how to do so online (Google is your friend) but since that's not incouraged there is no point in including these in the repos. Thanks, this answers my question. > Simon Good name. Simon

7 years, 11 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 4:25 PM, Mark Sapiro wrote: >> I am not at all fluent in django interactions (I'm still not entirely >> sure of what django actually *is*) so I have some reading to do. Any >> pointers on "django wrangling for n00bs" would be great. As I >> mentioned, I've not been hacking on mm3, just using it. I'm an >> accomplished programmer, but embedded C and assembler are a few >> galaxies away from python and web services! > > > Django is a Python based web framework. It is the framework used to > support HyperKitty and Postorius. To learn more, start at > https://www.djangoproject.com/ I'll get to reading. Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

3 years, 8 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 14:06, William Oliver wrote: > > So.. as an aside, it was a bit of a hassle to copy and paste all the > usernames from the "Users" list in Postorius to the "Mass subscribe." > The only way I could see to do it was copy and paste them one at a > time. Postorius Users -> Members view has a CSV Export button. That exports a CSV with all the member addresses. It's actually just a flat list as it only has one column. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Loops back to myself

by Odhiambo Washington

On Thu, Jan 11, 2024 at 7:30 AM <simonjwiles(a)gmail.com> wrote: > Were you ever able to solve this problem? I'm having exactly the same > issue with GNU Mailman 3.3.9 (Tom Sawyer), and I can't work out what I > should be doing. Thanks! > The standard configuration is detailed at: https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta For *unusual* configurations, you can look at this page: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…, especially https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Re: Moving mm2 mail archives to mm3

by Henrik Rasmussen

> See 'django-admin hyperkitty_import --help' for more info. Is this also valid using Docker-mailman? I don't have a hyperkitty_import django command. How do I import MM2 archives in Docker-MM3? # docker exec -it mailman-web bash bash-4.3# django-admin help Type 'django-admin help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). -- Henrik Rasmussen

7 years, 7 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by Mark Sapiro

On 2/13/19 3:37 PM, worik wrote: > When a outbound email bounces where is the carcass? Gone. > Google is asking me for all the headers, and since this email bounced I > do not have a handy copy. Presumably this is list mail so your list copy should be the same except for the few headers related to delivery from Mailman to you. Also, if you have the 'prototype' archiver enabled, you will find the message with all headers up to the point,it was sent from Mailman in mailman's var/archives/prototype/LIST_ADDRESS/new/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: migration

by Mark Sapiro

On 7/30/21 1:10 PM, Dave McGuire wrote: > > I am not at all fluent in django interactions (I'm still > not entirely sure of what django actually *is*) so I have some reading > to do. Any pointers on "django wrangling for n00bs" would be great. As > I mentioned, I've not been hacking on mm3, just using it. I'm an > accomplished programmer, but embedded C and assembler are a few galaxies > away from python and web services! Django is a Python based web framework. It is the framework used to support HyperKitty and Postorius. To learn more, start at https://www.djangoproject.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Mailman issues after re-boot

by Stephen J. Turnbull

paulrubin37(a)gmail.com writes: > | python3-virtualenvwrapper | Enhancements to virtualenv | package I suspect this is part of the problem, it's probably blocking any other Debian virtualenv packages as "conflicts". > mail:~ # python3 -m venv --help > usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear] [--upgrade] [--without-pip] [--prompt PROMPT] [--upgrade-deps] ENV_DIR [ENV_DIR ...] You should be able to use "python3 -m venv $ENV_DIR" to create an appropriate virtual environment, and then . /path/to/venv/bin/activate python -m pip --upgrade install pip # NOTE: using the venv python3! python -m pip install build wheel followed by installing `mailman` and friends in the same way. If there are complaints about pip itself, I believe "python -m ensure_pip" should do the trick.

1 year, 6 months

[MM3-users] Re: Whitelist non subscriber

by Barry Warsaw

On Aug 10, 2017, at 13:05, Mark Sapiro <mark(a)msapiro.net> wrote: > > Mailman 3 defines the list attribute accept_these_nonmembers, but it is > not currently implemented to actually have any effect, nor is it exposed > in Postorius. Yes, that attribute is deprecated and (almost) completely removed. > At the present, I think you would have to create a user record with the > address and add that user to all lists with role nonmember and > moderation_action 'defer' to apply subsequent tests or 'accept' to > unconditionally accept posts from that address. That’s the way it should be done. Those actions may not be exposed yet in Postorius or the CLI, so you might have to do it with a `wishlist` script. -Barry

7 years, 8 months

[MM3-users] Re: Moderated Signup with "info" box?

by Mark Sapiro

On 12/7/20 8:01 AM, Brian Carpenter wrote: > > Keep in mind that Mailman 3's REST API is only accessible locally. So to > access Mailman 3's REST API from another server is not remotely > possible. (see what I did there?) The REST API is only accessible locally by default. It is certainly possible to configure the webservice section of mailman.cfg to be able to access it remotely - if you do this, be sure not to use the default admin_pass. There is also an authenticating REST proxy project called lemme (possibly abandoned) at <https://gitlab.com/mailman/lemme>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Mailman 3 Core user assistance

by Stephen J. Turnbull

Tony Deshields writes: > I currently have a docker mailman stack that utilizes Django LDAP > backend for authentication. I have my users attributes mapped as > you see below in my settings.py file. Whenever a user logs into > postorius with their 'uid', mailman-core uses their 'uid' as their > email address instead of the 'email' attribute. I don't think Mailman core is doing that, Mailman core just takes the token passed by Postorius verbatim. It's the Django LDAP auth module. You need to have that module pass the email value as the user identity token to Postorius rather than uid. There may be a way to configure that in settings.py. Check the module docs.

1 year, 3 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Marc SCHAEFER

Hello, On Wed, Oct 02, 2024 at 08:05:44AM -0000, Chupin Maxime via Mailman-users wrote: > Thank you. So, using `mailman-web makemigrations --merge` as `root` is the right way to do it (as it call user `www-data`). Unfortunately, I get the error wrote in my first message: > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/django_q/migrations/0015_merge_0010_auto_20220618_2315_0014_schedule_cluster.py' I did not use makemigrations so far. It is well possible that files that were prepared were on the wrong UID, check ls -la /usr/lib/python3/dist-packages/django_q/ (especially since debian separates mailman3 and mailman3-web users) You could change the owner manually (chown www-data '/usr/lib/python3/dist-packages/django_q/*), but I prefer you get advice from others on the list.

6 months, 3 weeks

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Stephen J. Turnbull

Mark Sapiro writes: > Thanks for filing the issue. I'll work on a solution. My current > thinking is to add a `count` column to the message table, set the count > to 1 when initially adding a message-id, increment the count when adding > an existing message-id, decrement the count when deleting a message-id > and only delete the entry and message when the count reaches 0. Are we guaranteed to get a separate LMTP delivery for each list? That is, if the MTA receives 2 RCPT TOs to lists for one transaction, won't it do the same in LMTP when it sends forwards the message to Mailman? Steve

3 years, 5 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Ron / BCLUG

Mark Sapiro wrote on 2025-02-05 12:48: > As of Mailman 3.3.10 (not yet released) the nntp runner is not started > by default. This is a welcome change, thank you. > For older releases you can add > ``` > [runner.nntp] > start: no > ``` > to mailman.cfg I've been digging into MM3 resource usage vs MM2 and have been wondering: are there any other runners that can be disabled, or invoked via cron job to run every $interval then exit again? Second question, similar topic but MM2: how to disable NNTP? (if that's what this is doing): /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Thanks again.

2 months, 2 weeks

[MM3-users] Re: Verification Failed Error

by brian＠emwd.com

Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > Exim experts would be able to help you better with this. > I'm the one who set up the original sample Exim .conf, because (a) I > didn't want to migrate all my bots to Postfix, and (b) the one-real- > host .conf turned out to be trivial. I'm an Exim expert only for my > own configuration, which is a (pre-global-warming) glacially-moving > target. I've never seen anything like the problems described here, > sorry. Can't help. > > Since it's looking like we don't have any real Exim experts hanging > around here, perhaps we should move the sample containers and other > default configs to assume Postfix and document "Exim should work but > you're kinda on your own, we'll do what we can but it's limited." At > least Mark is maintaining such systems, and they're probably better > documented than Exim for the single-real-host configuration, though > they would probably run into similar problems with the containerized > setup. WDOT? Hi Steve, I think it really is not that complicated in getting exim setup, at least with a Centos system. The macros, router, and transport files that maxking provided were a big help and probably the hardest part of setting it up. The problems I had with setting exim up were: 1. Not realizing exim is setup differently depending on the flavor of Linux. For Debian systems, there is a conf.d folder to place the 3 above mention files into. Not for Centos 7. Evidently some of the syntax is different as well. 2. I also did not realize I had some syntax errors in exim.conf that caused exim not to restart. For some reason, the OS did not tell me Exim failed to restart when I used "systemctl restart exim.service". I happen to run "systemctl status exim.service" and that told me exim was dead in the water. I quickly found out why and fixed the errors. 3. I did not know how to include the 3 above mention files in the exim.conf nor did I know that I needed to. It is easy to do and Odhiambo WASHINGTON helped me with that. (Thank you!) What I would change in the documentation is to let exim users know to use a valid mail account for posterious to send out messages. Perhaps it is there but it was not apparent to me. I would also mention some more Exim specific settings to modify For example: "To use Exim4, it should be setup to relay emails from 172.19.199.3 and 172.19.199.2." I would change the above line to include the actual setting to change in the exim.conf file: hostlist relay_from_hosts = localhost : 172.19.199.3 : 172.19.199.2 : 172.19.199.1 However the challenge in that is the above setting is for Centos 7. I am not sure if the setting is different for Debian or other Linux variants. I would also mention that the macros, router, and transport files need to be included via exim.conf. Not knowing Exim very well, I did not know that. I know we don't want to make the documentation too large or unwieldy but I think the above suggestions won't add too much to the weight of the documentation. Brian

6 years, 4 months

[MM3-users] Re: Python is updated

by Lars Bjørndal

[Mark] > On 4/27/23 11:13 PM, Lars Bjørndal wrote: > > > > When running `django-admin migrate`, I get the following: > > > > Traceback (most recent call last): > ... > > django.core.exceptions.ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. > > > > How could that be fixed? > > Your django-admin command is not finding your settings.py file. Do you mean /etc/mailman3/ where settings.py lives? > Either run > it with a --pythonpath argument naming the directory that contains > settings.py or set the environment PYTHONPATH to that directory. I tried `django-admin migrate --pythonpath /etc/mailman3`, and got the same result. Thanks, Lars

1 year, 11 months

[MM3-users] Re: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Mark Sapiro

On 5/22/24 11:16 AM, Andy Macheta wrote: > Hi Odhiambo, > Well; looks like I'm much further on thanks to your tips - thanks!! > > So now I can get my local web browser pointing at http://localhost:8000/mailman3/lists/ and I can see my test list. > But, the webpage does not seem right, i.e. the text has loaded but not the images and wondering if anyone has any tips on how to resolve. Did you do the 4 steps beginning at https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Postfix + MariaDB + Mailman 3 Core

by Stephen J. Turnbull

Peter Knowles via Mailman-users writes: > In particular, with regards to Mailman 3 Core generated content. So > instead of referencing a postmap generated file which MM3 presently > generates, but have MM3 add and/or remove those records to/from a > MariaDB table. All that is already in the 'mailman' database. I don't do MySQL, but there must be a cli where you can examine the tables etc. There are about 50 tables altogether in a fully populated mailman database IIRC. Information about lists from which you can construct posting addresses and list-id is in the 'list_name' and 'mail_host' columns of the 'mailinglist' table, and the domains themselves have a separate table 'domain'. Steve

1 month, 3 weeks

[MM3-users] Re: Trying to set up mailman3 on my mail server

by Mark Sapiro

On 10/14/21 7:51 PM, Shawn Heisey wrote: > I'm having a lot of trouble with trying to set up mailman3 on my mail > server. > > It's on an AWS instance, running Ubuntu 20.04 LTS. All software is > installed from Ubuntu packages. Mailman version is 3.2.2. Please see <https://wiki.list.org/x/12812344>[1] > The problem I am trying to troubleshoot first is how this can be happening: > > Oct 14 11:27:26 2021 (2341) ACCEPT: > <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> > Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on > port 25 > > From the shell, I can "telnet localhost 25" successfully, even as the > "list" user. Apparmor is disabled. The UFW firewall is enabled, which > allows all traffic on the loopback interface. I disabled ipv6 at the > kernel level, but had the same problem with ipv6 enabled, so I don't > think ipv6 is related at all. I do not see any connections in the > postfix log that correspond to the mailman connection error. There's a long thread on this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. Your issue may not be the same, but that one had to do with templates, perhaps created in Postorius, that couldn't be accessed. > From a fresh install of mailman, I created two mailing lists. Once upon > a time I had those lists active on a Debian 6 machine running mailman > 2.1.13 ... I copied the mailing list config from that machine over and > used the "import21" facility to import the configuration into the new > mailman3 install. That worked without error and I can see the lists and > their members with the "mailman" command. I found instructions for > integration with postfix, and added the required three config lines to > the postfix config. > > When I try to send a message to the list, I get what I pasted above in > the mailman log. I think that means the postfix integration is working, > and is forwarding to mailman. Yes, and the message should be archived in whatever archivers are enabled. If the prototype archiver is enabled you should see the message in Mailman's var/archives/prototype/<list-id>/new/ directory and if HyperKitty is enabled, in mailman's database in the hyperkitty_email table. > I'm hoping somebody can give me some pointers, and if more information > is needed for troubleshooting, let me know what is needed. If your web UI isn't working, you probably haven't created any templates in Postorius, but import21 will create templates and if you ran import21 as root, you may have created templates and perhaps other things that can't be accessed by the Mailman user (`list` in your case). All Mailman related commands should be run only by the Mailman user. [1] This FAQ says you should be going to Debian/Ubuntu for support. If you've tried that and are not getting help there, I respectfully submit that you should purge the Debian/Ubuntu package and start over from here <https://docs.mailman3.org/en/latest/install/virtualenv.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Mailman backend maintenance task

by Stephen J. Turnbull

Eugenio Jordan (external) writes: > The idea we were considering was more or less stopping all of the > components, then starting up only PostGRESQL, and then performing each > one of the mentioned tasks. In that case, your Mailman installation will basically be down (no web presence, no deliveries) for the duration of the database maintenance. > You mention that regardless the connectivity that > Mailman's core processes might have with the database, the emails will > be received by and queued until the connection is back again and they > can be delivered to the distribution lists' members. Could you please > confirm whether this task would be actually delegated to Postfix (or > any MTA integrated with Mailman)? If Mailman core is running, it will accept the mail and store it in its own queue. If not, the MTA will store it in its deferred queue until Mailman comes back up. The big problem with delegating this to the MTA is that after two days the MTA probably won't retry for whole days, but if you do an MTA queue flush, it will probably stop other mail delivery for quite a while, since it will be occupied with processing the Mailman backlog. The way Mailman works is that there is a master process, which manages a suite of runners. Each runner is responsible for a particular stage. The LMTP runner does nothing except accept messages from the MTA, and store each one in a file for the next runner in the chain. Each one does various things, then moves the file into the next runner's queue, until the message ends up in the outgoing queue, and Mailman's outgoing runner then picks it up and sends it to the MTA along with the list of RCPT TO addresses. When the MTA accepts the message, Mailman deletes it from its own queue. This is very much like the way that the MTA itself handles mail -- Mailman doesn't accept responsibility until the message is safe on disk, and it doesn't delete its copy until the outgoing MTA accepts responsibility. Then, at some point in the chain of runners, the current runner will need to access the database, it will fail, and block. Messages will pile up in this runner's incoming queue until the database comes back up, at which point it will continue as if nothing happened. The advantage to having Mailman accept and store the message is that the MTA doesn't have a backlog of its own that it keeps retrying, which can slow other mail, especially once Mailman comes back up, and the MTA gets tied up sending deferred mail to Mailman. Most MTAs can be configured to limit the rate at which they accept mail from individual users, which balances the load better. Mailman, on the other hand, just passes the deliveries to the MTA as fast as it can, which is normally what you want, and the MTA is in a better position to impose rate limits when needed. > If so, this is actually what we need: we could afford delaying > the reception a couple of days, whilst we are sure that no mail > will be lost. Mailman doesn't lose mail, because it operates on the same principle of read, store, acknowledge that MTAs do. Steve

3 years, 7 months

[MM3-users] Re: File Attachments

by Stephen J. Turnbull

brian(a)emwd.com writes: > Thanks Mark. I went ahead and [submitted an RFE to implement file > attachments in Hyperkitty posting]. This one is not GSoC'able by itself, right, Abhilash? But it seems a little bigger than a minimal "can you submit a PR" test. Anybody know if there are some other "buttons" we should put into the "post from HyperKitty" UI that we could bundle up as a GSoC task? Maybe this weekend I'll go through the tracker and start tagging in preparation for a GSoC application. Of course we'll decide later if we have enough mentors etc, but I think this is worth doing anyway (updating the "easy" bugs, etc) even if we don't apply for GSoC this year. Steve

6 years, 3 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 2:41 PM, maszap(a)tin.it wrote: > I can create a list, add members to the list, but when I create a new thread, I only get it on the email from the same domain as the list. While all the other members of the list, they do not receive the thread. > I tried to check the logs, but I don't see anything significant. > What can I check? This is most likely because the outgoing MTA can't deliver/relay to external domains. Check the MTA configuration and logs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Running Mailman3 under supervisord

by Abhilash Raj

On Sun, Jul 26, 2020, at 6:08 AM, Odhiambo Washington wrote: > Hello world, > > Is it possible to run MM3 under supervisord? > What would I use for command= ?? If you want something that doesn't fork into the background, then you can run "master start" command. It will stay in the front and supervisord can monitor the pid. I do the same for the container images. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", grep ^[^#] :-) > _______________________________________________ > 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)

4 years, 8 months

[MM3-users] Re: About the path forward [was: ... regarding message acceptance]

by kaos＠tecnologiaconsciente.es

Stephen J. Turnbull wrote: > > Any plans to implement message acceptance based on another list? > > I think that most Mailman 2.1 features are plausible proposals for > Mailman 3. While we don't make decisions based on user voting, we do > care about user requests. If you want to make a formal request, post > a request for enhancement (ie, issue) on our GitLab issue tracker, and > post a link here so other interested people can follow it. I am also quite interested in sibling lists feature for mailman 3 (regular_include_lists in mailman 2). Pawel, did you ever posted a request for enhancement in gitlab, as Stephen suggested? Thanks a lot for your answer!

3 years, 3 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Mark Sapiro

On 09/21/2017 01:29 PM, Andrew Hodder wrote: > > I keep getting around this by creating symlinks to the pid file and then > the stop works, but it's getting silly. It seems like mailman just assumes > CWD + /var/ + master.pid must be the location. Once I realized this, I > found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since > it'd then add /var/master.pid). But that seems a little nonsensical. That is the normal expected behavior if devmode is enabled. Check your configs for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] bounces with empty message-id

by Peter Münster

Hi, It seems, that mailman bounces the bounces, so that the list-owner never sees them: --8<---------------cut here---------------start------------->8--- postfix/smtpd[12002]: connect from out04.smtpout.orange.fr[193.252.22.213] postfix/smtpd[12002]: 879D6F12E8: client=out04.smtpout.orange.fr[193.252.22.213] postfix/cleanup[11841]: 879D6F12E8: message-id=<> postfix/qmgr[10092]: 879D6F12E8: from=<>, size=4048, nrcpt=1 (queue active) postfix/smtpd[12002]: disconnect from out04.smtpout.orange.fr[193.252.22.213] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/lmtp[11846]: 879D6F12E8: to=<test-bounces(a)my-domain.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.05, delays=0.04/0/0/0.01, dsn=5.0.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 550 No Message-ID header provided (in reply to end of DATA command)) postfix/qmgr[10092]: 879D6F12E8: removed --8<---------------cut here---------------end--------------->8--- What could I do please, to get the bounces? I would like to use VERP to identify wrong addresses... TIA for any hints, -- Peter

7 years, 2 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by brian＠emwd.com

Hi Kevin, I have been following this thread. You won't be able to use the mailman shell due to this being a shared mailman 3 server. Just let me know what the email address is of the user that has an outstanding pending request and I should be able to clear that out via Mark's instructions. You can do that via our support ticket system. I also wasn't aware of a setting for expiring pending requests. I will wait for Mark's response to look into that further. I can tell you from experiencing that making your subscription policy open will not allow those with pending requests to be added. I just tried that myself. Brian

6 years

[MM3-users] New Mailman Core Release

by Mark Sapiro

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies (aiosmtpd) not supporting 3.10 yet. -- 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: list footer questions

by Mohsen Masoudfar

Hi, Thanks again for your help. When I check the postorius version, it says 1.1.2-3: [509]# apt list | grep postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] It is on Ubuntu18.04 and has been installed with Ubuntu package Mailman-full. There is no update available yet. So it looks like I cannot use the easy way of modifying the templates. Question: Is there a way to achieve the same by updating the code? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 8, 2020 4:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list footer questions [EXTERNAL EMAIL] On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - > listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.list…> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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…

4 years, 11 months

[MM3-users] Re: list of subscribers

by Simon Hanna

>> Displaying the names stored in django probably won't happen. >> Matching the names in django with the members in lists >> would require lots of code > Really? I don't know Python, but wouldn't it be possible (just as an > option) to do something like this: > > user = User.objects.get(email = ...) > if user is found then > print next to email address: user.first_name + user.last_name > Yeah, that way you make quite a lot of database queries. to make it perform better, you'd need to get all user accounts and match them to the subscribers. Since users can have multiple addresses you need to check all their addresses. Making this quite expensive for a very small use case.

7 years, 2 months

[MM3-users] Re: Suspend a list temporarily

by Mark Sapiro

On 8/31/19 7:20 PM, Andrew Bernard wrote: > I need a bit of handholding here. What settings do I have to make to reject with a message, and how to make or modify a template with my message containing the reason for temporary list processing suspension? The template to modify is list:user:notice:rejected. This does not seem to be one that can be customized via Postorius so you would need to make a templates/lists/<list.id>/en/list:user:notice:rejected.txt file in Mailman's var/ directory or set a URL for the template as in <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- 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] apache2 security for mailman3 admin

by Lars Schimmer

Hi, I know it is not the perfect place to ask, but if onyone has a good idea, example, I would be happy. I do run mailman3 with apache ProxyPass in front. I did set: <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> as given as example to set it up. Now I want to limit the mailman3/admin area to a defined IP range. Anyone has a working example to limit only the /admin area to a IP range in Apache2, but everything else as it is now? Thank you, MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 years, 4 months

[MM3-users] ANNOUNCE: Mailman 3.1.0 final!

by Barry Warsaw

Hello Mailpeople! On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line! Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out. Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two. Feedback is welcome: https://github.com/maxking/docker-mailman What is GNU Mailman? GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3. The best places to start for all things related to this release: http://docs.mailman3.org/ http://www.list.org/ https://gitlab.com/mailman (Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.) Happy Mailman Day, -Your friendly neighborhood cabal An overview of what's new in Mailman 3.1 ======================================== Feature parity with Mailman 2.1 ------------------------------- * You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists. Core ---- * Added support for Python 3.5 and 3.6 * MySQL is now an officially supported database * Many improvements with importing Mailman 2.1 lists * DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1 * The REST API requires HTTP/1.1 * A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries * Many new REST resources and methods have been added * Individual mailing lists can augment the system's header matching rules * `mailman create` now creates missing domains by default * `mailman digests` now has `--verbose` and `--dry-run` options * `mailman shell` now supports readline history * `mailman members` can filter members based on their subscription roles * A new template system has been added for all messages originating from inside Mailman. * The Message-ID-Hash header replaces X-Message-ID-Hash * New placeholders have been added for headers and footers * Unsubscriptions can now be confirmed and/or moderated Postorius/HyperKitty -------------------- * General U/I and U/X improvements * Many more features from the Core's have been plumbed through * We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab. Backward incompatibilities -------------------------- * Core/REST: Held message resources now have an `original_subject` key that is not RFC 2047 decoded. `subject` is now RFC 2047 decoded. * Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.

7 years, 10 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 8/5/22 10:13, Kimmo L wrote: > Okay. Maybe i should to the same and replace my existing configuration with gunicorn. > Is it complicated to do that change ? I ask because this gunicorn term is quite new for me. You already have gunicorn installed because Mailman core uses it to support the REST interface. For configuration see https://wiki.list.org/DOC/Mailman%203%20installation%20experience. In particular, see the `Recommended Configuration` section items labeled `if using Gunicorn:` for sample gunicorn.conf and Script to start Gunicorn. Also, the `Web Server` and `Running Things` sections. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Mailman-web showing "An error occurred while processing your request."

by Mark Sapiro

On 2/9/23 07:57, C. Souza wrote: > > Just for curiosity, does anyone know the reasons for this kind of problem > and how to avoid it? Cause: Something in the specific email message. Avoidance: Possibly if we knew what the specific issue was or could see the held messages as displayed by the mailman shell script I provided, we could detect the issue and do something about it. Possibly Postorius could catch this and be more graceful about it, but again we'd probably need a message that triggers this 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, 2 months

[MM3-users] Hiding an ML from a site

by Odhiambo Washington

I host two MLs on the same server/same MM3 instance. Under the Django Admin interface, I created two sites. I expected that each ML will belong to its own site and should not be visible on another site. On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two lists. How do I stop the "Users" list from showing up on this site ( https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own site - https://exim4u.org/mm/lists/ ? -- 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]

1 year, 2 months

[MM3-users] Re: Auth question

by Barry Warsaw

On Mar 30, 2017, at 12:34 AM, David Krantz wrote: >When starting this as the recipe seems reasonable I find that I have >no reliable source for git links for the parts. Some of the git links >I find are marked with "do not use" so it is a bit hard having >confidence in selecting one of the others. All the Mailman 3 suite subprojects are listed here: https://gitlab.com/mailman Those project links will take you to the active git repositories. The only one you should not use is mailman-bundler. Releasing 3.1 and a better deployment story are top priorities for the Pycon sprints. I wish we'd been able to release 3.1 before Pycon, but it just seems unlikely. Plus we have a fine tradition to uphold. :) -Barry

8 years

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Just checked again and saw: - in the setup it works perfectly in Hyperkitty, that's nice - for the first web host I have 2 mail domains registered, so it also matches (unfortunately) with what you said :-( Anyway, I dceleted one of it, still both lists are shown on either web host, so it's generally not working. If I can do something on this issue, please advise me. Thanks. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host.

4 years, 1 month

[MM3-users] Re: See list of subscribers

by Mark Sapiro

On 3/27/24 00:38, Tom Yates wrote: > > I have a list, as admin under "Settings" -> "List Identity" -> "Members > List Visibility" I have it set to "Only Mailinglist Members". > > But a random subscriber, who's signed up and authenticated, when she > visits the list page she sees her subscription, but no option to list > the other subscribers. > > Is she looking in the wrong place? Do I need to open up more settings? > Am I just being an idiot? This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Abhilash Raj

On Thu, Feb 25, 2021, at 6:38 PM, Brian Carpenter wrote: > On 2/25/21 8:28 PM, Abhilash Raj wrote: > > Thanks Brian, this looks quite comprehensive in the details. The only > > thing I am a bit concerned about is granting sudo privileges to the > > Mailman user. It really shouldn't have sudo given that Mailman and > > Django are supposed to run as mailman user. Any compromise of > > the Django application will provide the attacker root on the machine. > > Thanks for pointing that out. I have removed that step. It really wasn't > needed. Great, thanks! > > > Is there a specific reason that you chose to go with an entirely new doc > > Yes. Just from observing the communications on this list, there are > multiple ways to install Mailman 3 which produces installation issues, > database problems, outdated apps, etc. My document produces a VERY > stable installation of Mailman 3 and one that is easy to maintain and > update. It is also very comprehensive covering not just Mailman Suite, > but the configuration of an entire server environment. Personally I > think the choice of Debian, NGINX, Postfix, and PostgreSQL makes for a > long and loving relationship with Mailman 3 but I do understand everyone > has their own environment that they want to work with. My guide > represents a very stable and easily maintained environment for me and > hopefully others. I think it is okay to be pick up a specific configuration and provide a guide to installation keeping that as the target technology. As it happens to be, the official doc uses the same set, Nginx, Postfix and PostgSQL. https://docs.mailman3.org/en/latest/install/virtualenv.html I don't see anything very specific to Debian in the doc except the package names and I think they are similar enough in Debian derivative distros that we can write up that assumption up front in the top. Given that most of the installation is based off on pip, I don't think there is going to be a *lot* of deviation for even RHEL/Fedora based distros when it comes to Mailman itself. Some minute deviations could occur with the behavior of certain commands, like `nano` doesn't exist, but I still expect 95% of the doc to be the same, except obviously the package names. > > > rather than helping to improve the existing one? Several parts of it (at > > least the ones that official guide covers) seems similar to me and is > > duplicate information that at least two people are going to spend time > > writing and maintaining in future. > > Is there an official guide? See that is the problem. I did not know > there was an official guide. Because every time I tried finding > documentation in the past using Google searches, I got fed outdated > information. So for me the guide that I came up with, works great for me > and if no one else uses it, I certainly will. I am not that well versed in SEO, but the official website https://list.org does point to it. Maybe not prominently enough for new users to discover? I'll see if we can make the discovery of docs.mailman3.org better. > > Your guide, by nature has to be minimalistic to accommodate all the > various server environments out there. My is meant to be narrow but > comprehensive. I guess it is fine to be opinionated about choosing the technologies but yet provide pointers to help people using other technologies. Right now, I do that using "Hints" and "Notes" and "See also" banners through out the documentation to point to different pages where they can lookup setup for other technologies. For example, how to setup MySQL if official doc recommends Postgres. > > > Is it something about the contribution process to the official documentation > > that makes it hard for people to contribute? Most of the pages at > > docs.mailman3.org or come from this[1] repo and use Sphinx to build and > > REsT formatting (.rst). > > > > [1]:https://gitlab.com/mailman/mailman-suite-doc > > Well I don't know much about any of the above approach to documentation. > So I would say that is a hindrance. Gitlab has a fairly good experience editing REsT files and you don't necessarily have to do much outside of a Web Browser actually. It lets you preview before saving like wiki.list.org and you can submit it for review and merging into main repo. Would you be more willing to contribute to official documentation if we documented the Gitlab contribution process better? > > I am just trying to understand how can we lower the barrier for community > > members to help contribute to existing docs instead of them having to create > > new ones. Specifically around installation, since that tends to get stale often > > when depedent packages change or a new dependency is added that > > breaks the installation. > > I had to update my guide twice due to recent changes made to the > installation process such as the addition of the Dart Sass section and > the problem with the cryptography module when installing Hyperkitty. > While my guide covers these new hurdles to a new installation, I don't > think yours says anything about them. The Dart Sass section came from > Mark's comments on this list. Because we haven't yet gotten to updating those in the official docs, unfortunately. And there are more things missing like Fulltext search (Xapian recommended) and more of the Email setup like SPF and DKIM. Very much aligned with your plans, which is why I suggested contributing updates to docs.mailman3.org instead :) -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 13:34 -0800, Mark Sapiro wrote: > On 12/25/21 12:42 PM, William Oliver wrote: > > > > Is there a "make-the-freaking-virtual- map-database" command in > > mailman3, or is this postfix thing? Should I just touch the thing > > and > > create an empty file? I'm a little scared to... The error message > > makes me think that it should be populated with something... > > > Did you add an Alias Domain (different from the Mail Host domain) to > the > entry for your domain? This is what triggers the creation of > postfix_vmap. > Well, I hope youi had/have/will have a great holiday. I just finished our dinner and I am now amusing myself by pretending to enjoy the Hallmark movies my wife is watching and debugging my mailman3 installation when she's not looking. It was either "The twelve cats of Christmas" or "Die Hard." I put my foot down and said we were watching Die Hard. So of course we are watching a movie about 12 kittens in a fire truck. In any case, I added a line for "virtual_alias_domains" in my main.cf for postfix. But it doesn't do anything, apparently, except generate another error line (see the syslog output below). So, just for a lark, I created an empty /opt/mailman/mm/var/data/postfix_vmap file and ran postmap on it to create a postfix_vmap.db file. Now, it no longer complains about there not being a postfix_vmap.db file. Instead it complains about it being empty. Here's what my mailmanweb.log has to say: smtplib.SMTPRecipientsRefused: {'redacted(a)libertyfp.org': (550, b'5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table')} I redacted the name because this is supposed to be the admin account -- and it fails on login. So, here's syslog: Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 where "redacted2" is the name in settings.py for EMAIL_HOST_USER and DEFAULT_FROM_EMAIL and "redacted" is the address for "Mailman Suite Admin" I don't know where "root(a)localhost.local" comes from. OK, it didn't work when I just had virtual_mailbox_domains defined, and it didn't work when I had both defined, so I commented out virtual_mailbox_domains and just left virtual_alias_domains. That didn't help, either, though it got rid of the warnings in syslog: Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: connect from localhost[::1] Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: connect from localhost[::1] Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<reacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 Here's my postfix configuration: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases always_add_missing_headers = yes command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/lib/postfix/sbin data_directory = /var/lib/postfix debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 default_destination_concurrency_limit = 15 default_destination_recipient_limit = 30 header_checks = regexp:/etc/postfix/header_checks home_mailbox = Maildir/ inet_interfaces = all inet_protocols = all local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq mydomain = libertyfp.org myhostname = mail.libertyfp.org mynetworks = 127.0.0.0/8 10.0.0.0/24 mynetworks_style = host myorigin = $mydomain newaliases_path = /usr/bin/newaliases owner_request_special = no relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains sendmail_path = /usr/sbin/postfix smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_banner = $myhostname ESMTP smtpd_recipient_restrictions = permit_mynetworks, permit_auth_destination, permit_sasl_authenticated, reject smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 virtual_alias_domains = libertyfp.org virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap virtual_gid_maps = static:20000 virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 Here's my settings.py: # Mailman Web configuration file. # /etc/mailman3/settings.py from mailman_web.settings.base import * from mailman_web.settings.mailman import * #: Default list of admins who receive the emails from error logging. ADMINS = ( ('Mailman Suite Admin', 'redacted2(a)libertyfp.org'), ) # Postgresql database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } # 'collectstatic' command will copy all the static files here. # Alias this location from your webserver to `/static` STATIC_ROOT = '/opt/mailman/web/static' # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' #: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "www.libertyfp.org", "libertyfp.org", "mail.libertyfp.org", "list.libertyfp.org", "127.0.0.1", "2.56.57.28" # "lists.your-domain.org", # Add here all production domains you have. ] #: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 1 # Set this to a new secret value. SECRET_KEY = 'passwd' # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'passwd' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } # To be added to Django's settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'redacted(a)libertyfp.org' EMAIL_HOST_PASSWORD = 'passwd' DEFAULT_FROM_EMAIL = 'redacted2(a)libertyfp.org' SITE_ID = 2 Here's my mailman.cfg: /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: redacted(a)libertyfp.org [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://redacted2:passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg # And, create the /opt/mailman/mm/mailman-hyperkitty.cfg file containing # these settings uncommented #[general] #base_url: http://127.0.0.1:8000/archives/ #api_key: Secret_Hyperkitty_API_Key [shell] history_file: $var_dir/history.py [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.libertyfp.org lmtp_port: 8024 smtp_host: mail.libertyfp.org smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no Here's uwsgi.ini # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. #http-socket = 127.0.0.1:8000 http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log And, last but not least here's mailman-hyperkitty.cfg: [general] base_url: http://127.0.0.1:8000/archives/ api_key: passwd

3 years, 3 months

[MM3-users] How to store additional information about lists?

by Andreas Barth

Hi together, I need to add custom attributes to the mailing lists: "responsible department": Free text field who is responsible from an organisational pov (not a person but an entity) Enhance the boolean public to a tri-state: public, restricted audience and private (restricted audience means: some people could subscribe themself - how that works is a different topic but w/o the information this can't be achived) - of course this could also be implemented as a second boolean that e.g. splits "not public" into "restricted audience" and "private" (means: nothing goes wrong for code that doesn't know this difference). Any hints how to do that best? Is it possible to store custom attributes, or should that be stored elsewhere? Andi

3 years, 11 months

[MM3-users] Re: username

by Jörg Schulz

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth. While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)?

1 year, 6 months

[MM3-users] GDPR - save subscriptions confirmation emails

by contact＠maadix.net

Hi, I am new in the list. I have been looking for this topic in the archives in order to avoid duplicate, but I could not find any thread. According to the new GDPR rules, lists owners need to have a confirmation from subscribers, and this is easy to do with Mailman 3. What I can't figure out is how to save all the confirmation emails received from users. I only see the confirmations commands emails in the logs, Is there another place/way to store them? For GDPR compliance it is important to be able to demonstrate that you received the confirmation, in case you may need it in the future. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

6 years, 10 months

[MM3-users] Re: Equivalent of listadmin Perl script for Mailman 3?

by Mark Sapiro

On 11/16/21 11:48 PM, Philip Colmer wrote: > Hi > > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > (Petter Reinholdtsen: listadmin, the quick way to moderate mailman lists - > nice free software (skolelinux.org) > <http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate…> > ) > > Does anyone know if there is an equivalent tool that works with Mailman 3? I'm not aware of any, but others might be (I wasn't aware of `listadmin` before reading this post). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Importing mbox files into archive defect with lines with From

by andrew.bernard＠gmail.com

A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. Is this a known bug? If not, how do I report it?

5 years, 10 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:19 PM, Mark Sapiro wrote: > > Otherwise, you can do this in mailman shell, e.g. > ``` > $ mailman shell > > 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. > > >>> dm = getUtility(IDomainManager) > >>> d = dm.get('example.com') > >>> d.alias_domain = x.example.com > >>> commit() > ``` Ooops. That should be d.alias_domain = 'x.example.com' I.e., quoted -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: per domain SITE_ID views?

by Mark Sapiro

On 12/28/21 1:14 PM, David Newman wrote: > Using FILTER_VHOST, I have two domains set up and working with MM3, > Postorius and Hyperkitty. However, because SITE_ID in settings.py points > to one of the domains, that domain name always appears on Postorius and > Hyperkitty pages. ... > How to get the correct domain to appear on that domain's Postorius and > Hyperkitty pages? I don't think the domain is actually displayed on Postorius pages. If I'm wrong, on what Postorius view do you see it? As far as HyperKitty is concerned, please file an issue for this at https://gitlab.com/mailman/hyperkitty/-/issues/new -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 9/16/22 14:42, Dan Caballero wrote: > Thanks Mark. We're using an external host(s) for the outgoing MTA. See settings below. I can advise those sysadmins about your recommendations. Your settings seem fine. [mta] smtp_host: smtp.caltech.edu [mta] smtp_port: 25 sets your outgoing MTA, and [mta] verp_delivery_interval: 1 says VERP every message which impacts performance in that each recipient's message is delivered to the MTA in a separate transaction, but this is what I do as it makes bounce processing more reliable. You might find some of the hits from https://wiki.list.org/FrontPage?action=fullsearch&context=180&value=perform… to be useful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: localtime() cannot be applied to a naive datetime

by Mark Sapiro

On 3/1/24 3:09 AM, Freerk Bosscha via Mailman-users wrote: > Since yesterday I get the following error-message when I go to the webinterface: And what in your installation changed since yesterday? > ValueError at /admin/login/ > localtime() cannot be applied to a naive datetime > Request Method: GET > Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ > Django Version: 2.2.28 This Django version is quite old. > ... > mailman info > GNU Mailman 3.3.3 (Tom Sawyer) and so is this Mailman version. Do you have USE_TZ = True and a setting for TIME_ZONE in your Django settings? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Deleting A List

by Mark Sapiro

Mark Sapiro wrote: > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > mailinglist_id = 13; > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > mailinglist_id = 13; > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = 13; > delete from hyperkitty_mailinglist where id = 13; > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; Or instead of that you could just go to the new list(a)lists.nog.ke archive in HyperKitty and delete it and then just do the ``` update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = 'list.lists.nog.ke' where id = 2; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] ARC

by David Krantz

Hi all, Is the documentation correct that ARC should be as simple to configure in mailman 3 as to add the private DKIM key and restarting mailman? (https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign…) I've tried that without finding any effect in my so far limited tests. I have not found anything in logs although I might have missed looking in one. Are there any known limitations? I have previously a working DKIM signature on outgoing mail as well as correctly set up SPF in DNS and SPF-checking on received mail. The verification on incoming mail adds a few headers but I do not think that that should be an issue, neither would the DKIM signing change anything should mailman add new headers. I now run Mailman 3.2.3 (La Villa Strangiato) on Python 3.7.4. Cheers // David

5 years, 8 months

[MM3-users] Re: Docker or virtualenv?

by Stephen J. Turnbull

Tim Cutts writes: > Has anyone considered whether it’s feasible to turn it into a bunch > of Lambda functions with a serverless database behind it? ... you just did. I'm not sure if "patches welcome" is appropriate for what looks to me to be a pretty radical idea, but someone could give it a try. :-) I don't think anybody in Mailman core has thought about it though. I don't really see the advantage for most sites. Hosts, especially VMs, are cheap, and unless you're running the lists for a major university or the like, lowest tier hosts will do. As for "serverless databases", that depends on whether Django and SQLAlchemy support them. Mailman has a lot of code invested in those ORMs. Steve

2 years, 3 months

[MM3-users] Re: 120 gmail users removed from lists !

by Yvan ♞

I add an SPF entry on my web hosting, domain name: "v=spf1 mx ptr include:_spf.google.com -all" and it seems to fix the problem. Le 24/10/2023 à 12:51, Stephen J. Turnbull a écrit : > Yvan ? writes: > > > Any "handmaid" solution should be great. > > That *was* the handmade solution. The commit IDs are in my message. > You can get the corresponding patches from GitLab. There's a reason > why I wrote that I don't recommend this -- you're asking for a lot of > work. > > If you can't do it yourself, and you're in a hurry, there is a list of > consultants athttps://wiki.list.org/COM/Mailman%20consulting%20services. > > Steve >

1 year, 5 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 9:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > This is definitely an issue with django_allauth 0.58. See > https://github.com/pennersr/django-allauth/issues/3503 and > https://github.com/pennersr/django-allauth/pull/3504 Thank you for following up on the fix. Consequent upon this django-allauth issue and the previous issue with psycopg2, how likely is it that new MM3 installations will suffer the effects? I am asking because I am doing my tests on a relatively vanilla system and just following the official documentation sin any deviations. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 5 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/26/19 5:22 AM, brunol(a)agro.uba.ar wrote: > > No errors/tracebacks in mailman.log. This is the output of debug.log configured as shown in my first post: > > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> to: lispruebas(a)mailman3.agro.uba.ar, list: lispruebas, sub: None, dom: mailman3.agro.uba.ar > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> subaddress: None, queue: in > Dec 26 10:02:37 2019 (696) b'250 Ok\r\n' > Dec 26 10:02:37 2019 (696) _handle_client readline: b'QUIT\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) Data: b'QUIT' > Dec 26 10:02:37 2019 (696) b'221 Bye\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) connection lost > Dec 26 10:02:37 2019 (696) Connection lost during _handle_client() > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbbb70> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f83fd0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483e0b8> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d8079438> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f70f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4a60f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981860> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483eda0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e2f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d80792b0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981e10> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e9780> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4d02c50> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbb550> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49cf048> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4983fd0> > > Those "Using agent: <mailman.mta.bulk.BulkDelivery object at " are constantly appearing, is this behavior normal due to the verbosity of the level? What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? On 12/26/19 10:24 AM, brunol(a)agro.uba.ar wrote: > I've also noticed that the messages are stuck in the "message" table (postgresql) and the corresponding files exists under /var/lib/mailman3/messages/ This indicates the held message has not been removed from the held message queue. You previously posted that you saw a log message > Dec 23 12:35:47 2019 (701) held message approved, message-id: CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com This message comes from mailman.app.moderator.handle_message() (in mailman/app/moderator.py). After logging that message, it requeues it in the 'pipeline' queue for further processing and deletes it from the message table and /var/lib/mailman3/messages/. This indicates that possibly subsequent processing is holding the message again. > Is there any relevant logger i should look on debug too besides the ones i already configured? set [logging.debug] level: debug in mailman.cfg to get more in debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: import21: A string literal cannot contain NUL (0x00) characters.

by Henrik Rasmussen

Stephen J. Turnbull writes: >> It seems that this issue is still unsolved. Is there any estimated >> date for a fix? https://gitlab.com/mailman/hyperkitty/issues/155 . >Why do you think this is a problem that Mailman should solve? >What is your desired treatment of this data? I was originally just asking for help and was asked by Berry Warsaw to submit the issue: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I tried to clean up the files as told by Simon Hannah. When that didn't work, I was simply just reporting that, thinking that there might be a problem somewhere else. I am sorry if I did anything wrong by asking for help. -- Henrik Rasmussen

7 years, 2 months

[MM3-users] Scheduled tasks

by Darren Smith

All, I am looking more through the documentation of the Mailman Suite here: https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf In section 3.2.5 it talks about the scheduled tasks that need to be run to do "specific routine functions" in hyperkitty. I installed through the easy install script found here: https://github.com/iomarmochtar/mailman3_ei/ However, I can't find anything in THAT documentation that talks about these cron jobs, and in fact the Mailman Suite isn't installed through that script. Can someone point me to any other documentation about the tasks that need to be run on a continual basis? Our hyperkitty installation seems to be bogging down more and more, and I am hoping that it will be as simple as just running some jobs that haven't been on our radar. Thoughts? -Darren

6 years, 10 months

[MM3-users] Re: Postorius no connection to REST API

by Mark Sapiro

On 8/9/21 10:14 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I have the apache24 and uwsgi working together. I did this way: > > For the apache24 part I decided to use the mod-wsgi (and uswgi binary). > did a > > pip install mod-wsgi > (with "mod_wsgi-express module-config" it shows the conf needed.) > > after that a > > pip install uwsgi mod_wsgi and uwsgi are two different, incompatible ways of doing the same thing. It appears from the rest of your post(s) that you are actually using mod_wsgi and (hopefully) not running uwsgi at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Williams, Peter B

Hi Mark, Thanks for the help with this! Other list members will also see the e-mail as coming from user(a)invalid.domain<mailto:user@invalid.domain>. I will continue testing the other scenarios and will reply back as soon as possible. Thanks again for the help with this and have a nice day! Peter On Mon, Sep 21, 2020 at 9:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: On 9/21/20 10:49 AM, peterbw(a)gmail.com<mailto:peterbw@gmail.com> wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, "Williams, Peter" <peters_real_address(a)example.com<mailto:peters_real_address@example.com>> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org<mailto:listserv@lists.test.org>. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org<mailto:listserv@lists.test.org>; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com<mailto:test_user@gmail.com> cc: other_user(a)gmail.com<mailto:other_user@gmail.com>; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> and other_user(a)gmail.com<mailto:other_user@gmail.com> receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- 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> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 1:02 PM, Mark Dadgar wrote: > > The downside to this is that you lose automated bounce processing, of course. You don't lose bounce processing. It just becomes a bit less reliable. The VERPed envelope sender says exactly what address the message was sent to. Without this information, Mailman (actually flufl.bounce <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse the returned bounce message to determine the bouncing address. There are many MTAs that do not send RFC 1894 compliant DSNs and we have several heuristic recognizers to try to parse these, but they can fail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] [Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

I've imported a list from Mailman2 and had the owner send a message for testing purposes. His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. However if we attempt to view the message in Postorius web UI then an error is thrown. In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages Does "Service Unavailable" mean I'm missing something in the configuration? Thanks for your help. ---- Dan Caballero

4 years, 2 months

[MM3-users] EMWD Mailing Lists Down

by Sherry Xie

Hi all, I am an EMWD Mailman 3 customer, and I recently realized my mailing lists are no longer working (the last email that went through was sent on December 25, 2021). Emails I send to the lists do not show up in archives or reach subscribers. It seems like others have had this issue before since ownership of the company was transferred following Brian Carpenter's passing – has anyone been able to get in touch with support or get their issues resolved? I've submitted a support ticket but have no idea if this is being monitored. I also have no way to contact the current management team, as only their names were announced in the November 5, 2021 email from Barbara Carpenter. Any help would be greatly appreciated – thanks in advance! Sherry

3 years, 3 months

[MM3-users] Re: Upgrade Mailmam Core from

by Mark Sapiro

On 9/27/22 05:42, sascha.rissel(a)gmail.com wrote: > For the moment, I ignored this error > error: invalid command 'bdist_wheel' > ---------------------------------------- > ERROR: Failed building wheel for mailman > > and carried on, with creating a configuration file at /etc/mailman3/mailman.cfg for Mailman Core. > I notice that directory /etc/mailman3 has not been creating during mailman setup from with venv. > > Is this correct? > Shall I manually create this directory or persist mailman.cfg at some other location where system user mailman has permissions to? I suggest you remove the venv and start over ensuring you do `sudo su mailman` before creating the venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/26/24 13:55, Mark Sapiro wrote: > > Yes, presumably because no one sets `XAPIAN_LONG_TERM_METHOD=hash` in > the environment. Do you have a reason for this? Actually, it's not an enviroment setting. It's a django setting XAPIAN_LONG_TERM_METHOD = 'hash' but in any case, I don't know why anyone would want that. What it does is rather than truncate a long term in the index, it replaces that term with a sha224 hash of the term, but that raises the question of how/why one would be searching for the hash rather than the term. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

On 10/18/23 20:25, Mark Sapiro wrote: > On 10/18/23 15:06, Thomas Ward via Mailman-users wrote: >> Is there a way to oerhaps custom-plugin my way through to set this up >> as an integration into Core? And specify the custom handler process >> or such to allow that integration? I see that there are ways to code >> plugins into existence so it may be a custom-processor plugin or such >> for this purpose. > > > The issue is Mailman core would have to keep track of the message-ids > and thread number of all prior posts to know whether the current post > is a reply to some other post or not. > > You would need a new database table or some other mechanism to keep > track of this and then you may need to keep everything forever because > you can't know that there won't be a future post in reply to some very > old post. > I think this is doable in our (read: Employer) use case, but without needing to modify Mailman Core much beyond a custom plugin and some fussing around. This is a side effect of a custom implementation of "Tagging" data by thread ID in a separate data / intel tagging system that reads from received emails in a custom intel processing mailbox. That has zero care as to how Mailman or Hyperkitty index items, and actually is pretty trivially implemented with `PREFIX` format being [ListName-NNNNNNN]: 1. If subject does not match `PREFIX` format: * Get next thread number from DB (In postgres, this is a serial matched to {list_id}_thread we call with nextval()) * Add subject prefix as [ListName-{ZeroPaddedThreadNumFromDB}] 2. If subject matches `PREFIX` form: * Do nothing As for how HyperKitty handles this, it replies entirely on RFC 5322 fields (see section 3.6.4 in that RFC) for identifying reply to, etc. to identify replies to things, which in turn it seems is fully capable of handling that. We simply need the message to be sent *with* a thread ID that members can hit reply to and keep the prefix in the subject line. We don't care how that's done in the Hyperkitty side of things, we only care about it being sent in the subject line. I noticed that Mailman3 has the capacity for external / custom plugins, and with some work I believe I can achieve this with a customized pipeline with a custom handler of `thread-prefix` instead of `subject-prefix`, otherwise calling the other handlers done by the traditional system, and just handle prefix differently in the thread-prefix handler in the custom pipeline. I'm following this attempt currently, but will keep it internal to employer. It'll also be kept internal to our use-case because it isn't easily exportable to other Mailman3 implementations. But yes, you're right it needs additional DB table to map list_id <--> thread_id and then would need some kind of "Subject prefix uses thread IDs instead of Post IDs config option", or only handle based on a custom pipeline. I"m going to deep dive into this on my end and see if I can come up with a solution that relies direct on the DB calls. Which hopefully should be safe to do, but we'll see in testing. Thomas

1 year, 6 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > It has nothing to do with the ssl certificate. In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-) > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs. Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it. -Ralph

6 years, 1 month

[MM3-users] Re: Receiving 8bit-clean mail

by Stephen J. Turnbull

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. Based on the symptoms, I'm guessing this means the SMTPUTF8 extension. Mailman is not prepared for this as far as I know. That is, Mailman expects that the headers will be ASCII, possibly MIME-encoded. I'm guessing the problem is that either the host MTA or Mailman's LMTP server doesn't handle SMTPUTF8 negotiation correctly, but I do not have time to analyze for some days. Mark Sapiro writes: > It works for me. I created this message Your message doesn't have UTF-8 in the *header* as far as I can see. Steve

5 years, 6 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

> IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed >hosts to get the right connectivity, too. >> I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? > I agree with this, we need a setting for which interface for Gunicorn to listen on, and what Mailman Core sends out in the self_link attribute when responding to REST requests. > Exactly! :-) Ruth

4 years, 10 months

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

The concept of a Django user sounds like the big thing I was missing. Thank you; I believe I have resolved the immediate need. I'm thinking, then, that if I want to be able to programmatically create the Django users in parallel with our Mailman users (I don't want to have registration open to the world), I'm going to have to do some coding... either create some sort of Postorius API or perhaps better would be to make a social / OAuth plug-in that will use our existing membership site. (Once I get stuck on that, I'll switch to the developer list.) Thanks again.

3 years, 2 months

[MM3-users] Re: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

2 years, 1 month

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 26, 2017 9:39:06 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > >> >> But in my testing, I replied to a subscription confirmation message >and received back an undeliverable looping email error message from >postfix. Any clues there you can offer? I can post to the list from any >email added via the admin console. The test subscriber address was >local to my server. From an outside address, same error. > > >This usually means that postfic is trying to deliver to an address and >the message already has a Delivered-To: header with that address. > >What are the headers of the "looping" message in the report? What are >the Postfix log messages related to that message? > > >> Once I registered the new email domain, I reverted my postfix config >back to the default suggested by maxking's docker instructions. >> >> https://github.com/maxking/docker-mailman > > >I have essentially no knowledge of the docker container images, so I >can't be much help with issues specific to them. Return-Path: <MAILER-DAEMON> Delivered-To: turtl(a)deviltracks.net Received: by mail.garden-life.org (Postfix) id 39F6C2055; Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Date: Thu, 26 Oct 2017 21:02:17 -0400 (EDT) From: MAILER-DAEMON(a)mail.garden-life.org (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: turtl(a)deviltracks.net Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="2D7231948.1509066137/mail.garden-life.org" Content-Transfer-Encoding: 7bit Message-Id: <20171027010217.39F6C2055(a)mail.garden-life.org> This is a MIME-encapsulated message. --2D7231948.1509066137/mail.garden-life.org Content-Description: Notification Content-Type: text/plain; charset=us-ascii This is the mail system at host mail.garden-life.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>: mail for gjb-online.com loops back to myself --2D7231948.1509066137/mail.garden-life.org Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mail.garden-life.org X-Postfix-Queue-ID: 2D7231948 X-Postfix-Sender: rfc822; turtl(a)deviltracks.net Arrival-Date: Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Final-Recipient: rfc822; test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com Original-Recipient: rfc822;test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com Action: failed Status: 5.4.6 Diagnostic-Code: X-Postfix; mail for gjb-online.com loops back to myself --2D7231948.1509066137/mail.garden-life.org Content-Description: Undelivered Message Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Return-Path: <turtl(a)deviltracks.net> Received: from mail.garden-life.org (localhost [127.0.0.1]) by mail.garden-life.org (Postfix) with ESMTP id 2D7231948 for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:17 -0400 (EDT) Authentication-Results: mail.garden-life.org (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=garden-life.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=garden-life.org; h=references:in-reply-to:to:subject:subject:message-id:from :from:x-mailer:content-transfer-encoding:content-type :content-type:date:date:mime-version; s=dkim; t=1509066135; x= 1509930136; bh=k85upIKMt3yA1zcaSrQxE349DcmKTq86MMRdi7hh2yw=; b=X 2phB5a1/LGy0J5YIHZTnbXOeoJ55wkcBrFax3cTvvXAAbfZEBsV3BLZ9Z25GdncT CK7b3FU8He/70UAKZtcjreE1AP/hB89yX63xNSqFu2iULKIYMOhWaE/eWl897VhN NIR1mONlrQxOUf5+o16As9WPdbAiEO/TKNMUpuyk+A= X-Virus-Scanned: amavisd-new at mail.garden-life.org X-Spam-Flag: NO X-Spam-Score: 6.117 X-Spam-Level: ****** X-Spam-Status: No, score=6.117 tagged_above=2 required=6.2 tests=[RCVD_IN_PBL=3.558, RCVD_IN_RP_RNBL=1.284, RCVD_IN_SORBS_DUL=0.001, RDNS_NONE=1.274] autolearn=no autolearn_force=no Received: from mail.garden-life.org ([127.0.0.1]) by mail.garden-life.org (mail.garden-life.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3zCxRxppUkZt for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:15 -0400 (EDT) Received: from rainmail.deviltracks.net (keys.fspproductions.biz [IPv6:2600:3c03::f03c:91ff:fe24:1eeb]) by mail.garden-life.org (Postfix) with ESMTPSA id 1116A2F1 for <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>; Thu, 26 Oct 2017 21:02:15 -0400 (EDT) Mime-Version: 1.0 Date: Fri, 27 Oct 2017 01:02:14 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.11.3 From: turtl(a)deviltracks.net Message-ID: <4e5829300419cfb7bf13d5a0d9ebebd1(a)deviltracks.net> Subject: Re: confirm b7322edad83ae7ec99cfc5100161c7062d2c7685 To: test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com In-Reply-To: <150906420646.31.12186705534373041145@mailman-core> References: <150906420646.31.12186705534373041145@mailman-core> X-Originating-IP: 108.53.239.102 October 26, 2017 8:30 PM, test123-confirm+b7322edad83ae7ec99cfc5100161c70= 62d2c7685@gjb-online.com=0Awrote:=0A=0A> Email Address Registration Confi= rmation=0A> =0A> Hello, this is the GNU Mailman server at gjb-online.com.= =0A> =0A> We have received a registration request for the email address= =0A> =0A> turtl(a)deviltracks.net=0A> =0A> Before you can start using GNU M= ailman at this site, you must first confirm=0A> that this is your email a= ddress. You can do this by replying to this message,=0A> keeping the Subj= ect header intact.=0A> =0A> If you do not wish to register this email add= ress, simply disregard this=0A> message. If you think you are being malic= iously subscribed to the list, or=0A> have any other questions, you may c= ontact=0A> =0A> test123-owner(a)gjb-online.com --2D7231948.1509066137/mail.garden-life.org-- Logs: mail amavis[1576]: (01576-09) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [2600:3c03::f03c:91ff:fe24:1eeb]:33512 [2600:3c03::f03c:91ff:fe24:1eeb] <turtl(a)deviltracks.net> -> <test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, Queue-ID: 15BD218EE, Message-ID: <09b6ea7c3203e7357e4e996c352223d0(a)deviltracks.net>, mail_id: UgTlYoHupO-Z, Hits: 6.117, size: 1663, queued_as: 928292055, dkim_new=dkim:garden-life.org, 451 ms, Tests: [RCVD_IN_PBL=3.558,RCVD_IN_RP_RNBL=1.284,RCVD_IN_SORBS_DUL=0.001,RDNS_NONE=1.274] Oct 26 21:47:44 mail postfix/smtp-amavis/smtp[19971]: 15BD218EE: to=<test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.64, delays=0.18/0/0/0.46, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 928292055) Oct 26 21:47:44 mail postfix/qmgr[1240]: 15BD218EE: removed Oct 26 21:47:44 mail postfix/smtp[20025]: 928292055: to=<test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com>, relay=none, delay=0.04, delays=0.01/0.02/0/0, dsn=5.4.6, status=bounced (mail for gjb-online.com loops back to myself) Oct 26 21:47:44 mail postfix/cleanup[19953]: 9E63E18EE: message-id=<20171027014744.9E63E18EE(a)mail.garden-life.org> Oct 26 21:47:44 mail postfix/qmgr[1240]: 9E63E18EE: from=<>, size=5273, nrcpt=1 (queue active) Oct 26 21:47:44 mail postfix/bounce[20027]: 928292055: sender non-delivery notification: 9E63E18EE Oct 26 21:47:44 mail postfix/qmgr[1240]: 928292055: removed Oct 26 21:47:44 mail postfix/pipe[19986]: 9E63E18EE: to=<turtl(a)deviltracks.net>, relay=dovecot, delay=0.03, delays=0/0/0/0.03, dsn=2.0.0, status=sent (delivered via dovecot service) Oct 26 21:47:44 mail postfix/qmgr[1240]: 9E63E18EE: removed [root@mail ~]# -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 5 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 17:07 schrieb Sebastian Hagedorn: > Am 27.08.20 um 16:41 schrieb Brian Carpenter: >> On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: >>> In case it matters, I'm trying to moderate the list using the "root" >>> account. Discarding works, but when I try to either accept or reject a >>> message, there is a timeout. >> Is there an error message displaying in Postorius or do you receive an >> Apache timeout error? > Neither. The browser times out. > ... and when I realized that, I tried a different browser, where it works. Sorry for the noise. FWIW, Firefox isn't working (at least right now), Safari is.

4 years, 7 months

[MM3-users] Re: Importing archive from mm21

by Mark Sapiro

On 11/28/23 11:32, Lars Bjørndal wrote: > On Mon, Nov 27, 2023 at 01:26:03PM -0800, Mark Sapiro wrote: >> >> The messages are there. I went to >> https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages >> from 2023, but then I went to >> https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 >> and started seeing all the messages even at >> https://hodr.no/archives/list/annonsering@hodr.no/. >> >> What do you see now? > > Now, all messages are visible. I suspect this was fixed by one of the daily hyperkitty jobs which just coincidentally ran when I was looking. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: scheduled tasks in docker-based deployments

by Abhilash Raj

On Thu, Oct 26, 2017, at 02:42 PM, Dmitry Makovey wrote: > > I came across the section > http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > that claims that crontab entries are *required* for normal MM3 > operations, but I do not see anything like that in docker-based > implementation. Should I add similar cron jobs manually to the host box? No, the container takes care of it. uwsgi process running inside the `mailman-web` container handles both cron and django_q processes within the container. See [1] for the configuration. [1]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… > -- > Sr System and DevOps Engineer SoM IRT > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

[MM3-users] Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, When I was seeing this, new lists weren't showing in HyperKitty. I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now. Was this working for you in the past? If so, did you do any updates recently? Derek Lambert On 2/6/19, 1:50 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Mark Sapiro wrote: > This looks like <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_mailman_hyp…> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

6 years, 2 months

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Peter Adebahr

On 7/18/20 7:46 PM, Mark Sapiro wrote: > On 7/18/20 9:30 AM, Dave Clements wrote: >> Hi all, >> >> I have just noticed a big jump in the number of emails going out with >> "***UNCHECKED***" added to the subject line. > > > This does not come from Mailman. Some milter or other process in your > MTA or elsewhere in the delivery chain is adding this to the Subject: > Hi Dave, I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf: # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; # Hope it helps :) Best regards, Peter

4 years, 9 months

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Mark Sapiro

On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: > I am trying to change email "To" field to user's email instead of > mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: > <mailman-users(a)mailman3.org>" In Postorius set Settings -> Alter Messages -> Personalize to Full. > I looked around old mailman configs they mentioned about adding > > OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py > > is this feature still available in mailman3 ? Can I do it via Postorius > or REST API? There is no setting in Mailman 3 to control the ability to set personalization. It is always available. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] hyperkitty url not found

by Eggert Ehmke

I installed mailman3 in a virtualenv following this guide: https://docs.mailman3.org/en/latest/install/virtualenv.html[1] The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, but it is empty. In my /opt/mailman/mm/var/logs/mailman.log file I find error messages like: HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: The requested URL was not found on this server. Indeed I cannot access that url using curl. Do I have to set up a separate apache vhost? The documentation is not clear about this, or I missed it. My external visible url is https://lists.[2]<tld>_/mailman3/mailman3/lists/_ -------- [1] https://docs.mailman3.org/en/latest/install/virtualenv.html [2] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

3 years, 1 month

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 17:06, Mark wrote: > > There was no line POSTORIUS_TEMPLATE_BASE_URL in /etc/mailman3/settings.py So presumably you were getting the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' from mailman-web/settings/mailman.py because of from mailman_web.settings.mailman import * in your settings.py. > Then, as site-owner, creating a new custom Welcome template (again via > the WebUI) I can see it correctly added to the database in > mailman.template.uri > > - > https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… And what happens if you go to that URL in a web browser? Also what do you get when going to https://lists.mydomain.com/mailman3? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Remove footer link

by Mark Sapiro

On 04/21/2017 02:14 AM, David Terni wrote: > Hi, > I need to remove footer message like "to unsubscribe etc etc" from all > lists. How i can do it or edit text? Assuming this is recent MM 3 with the "new" templating system implemented per commit dbde6231ec897379ed38ed4cd015b8ab20ed5fa1 Author: Barry Warsaw <barry(a)python.org> Date: Sat Jul 16 15:44:07 2016 -0400 New template system. Closes #249 The new template system is introduced for API 3.1. See ``src/mailman/rest/docs/templates.rst`` for details. and using English as an example, you can put a sitewide footer template in var/templates/site/en/list:member:generic:footer.txt. If this file is empty, the footer wont be added. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Running Mailman3 under supervisord

by Odhiambo Washington

On Mon, 27 Jul 2020 at 18:38, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Sun, Jul 26, 2020, at 6:08 AM, Odhiambo Washington wrote: > > Hello world, > > > > Is it possible to run MM3 under supervisord? > > What would I use for command= ?? > > > If you want something that doesn't fork into the background, then you can > run "master start" command. It will stay in the front and supervisord can > monitor the pid. > > I do the same for the container images. > Hi Abilash, Might you be able to share your how you have configured that all that in supervisord.conf? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 8 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Torge Riedel

Am 03.02.21 um 02:59 schrieb Abhilash Raj: > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Dear MM3 releasers, after successful update to latest versions I realized that Mailman Core change log links are stable (I requested this some time ago and it was changed - thanks for that), but Postorius and Hyperkitty change logs do not have stable header ids. Can this be changed too? It makes it easier for me (and hopefully for others) when communicating changes to the users. At the moment they see the upcoming changes for Postorius first, which always introduces confusion for some of them. Thanks in advance and kind regards Torge

3 years, 11 months

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/3/22 20:23, chucka(a)blackforest-co.com wrote: > I send out a monthly newsletter via MM. To keep traffic smaller the email has a link to the PDF of the newsletter. > I need to somehow include a variable (the To: email) as part of the link. > ie href = thewebsite/nl.pdf?tomjones(a)email.com That way I can tell A) who is reading the NL and B) popup a notice: Your membership dues have been paid through 2023. You can do this with a custom template for list:member:regular:header or list:member:regular:footer. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 05:02, Wikinaut wrote: > > (venv) mailman-web migrate > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.11/site-packages/django/contrib/postgres/search.py", line 1, in <module> > import psycopg2 > File "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> > from psycopg2._psycopg import ( # noqa > SystemError: initialization of _psycopg raised unreported exception Since you are using MySql and not PostgreSQL, in your venv do ``` pip uninstall psycopg2_binary ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Abhilash Raj

> On Mar 19, 2021, at 4:10 PM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > I did have the first setting, yes. > > The second one no, but activated it now, no change. Can you also share your uwsgi configuration? > > Am 20.03.21 um 00:00 schrieb Mark Sapiro: >> I don't use uwsgi so I can't advise on its configuration, but do you have >> USE_X_FORWARDED_HOST = True >> SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') >> in your Django settings? > _______________________________________________ > 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)

4 years, 1 month

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 17:01 -0800, Mark Sapiro wrote: > On 2/19/22 14:06, William Oliver wrote: > > > > So.. as an aside, it was a bit of a hassle to copy and paste all > > the > > usernames from the "Users" list in Postorius to the "Mass > > subscribe." > > The only way I could see to do it was copy and paste them one at a > > time. > > > Postorius Users -> Members view has a CSV Export button. That exports > a > CSV with all the member addresses. It's actually just a flat list as > it > only has one column. > Thanks! billo

3 years, 2 months

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

by Mark Sapiro

On 2/2/23 21:25, Odhiambo Washington wrote: > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> See >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… >> for mitigation. > > > What is the danger of replacing my settings.py with this one, seeing as it > differs in a number of ways with mine? If your's works, don't do it. The danger is the differences might be significant and break things. Also, that one is for HyperKitty only and doesn't include Postorius settings. -- 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: spf/dkim/dmarc

by Jeremy Stanley

On 2023-05-17 07:07:53 -0700 (-0700), Christian via Mailman-users wrote: > Thank you for your reply. I'm being driven mad by Gmail rejecting > my SPF record, this while I get SPF record approvals everywhere > else. > > I read that having two SPF records for the same server will > generate errors. Is this true? [...] I'm not an SPF expert (I don't even use it for my domains), but I do know how to query standards documents. IETF RFC 7208 "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1" states in §3.2: "A domain name MUST NOT have multiple records that would cause an authorization check to select more than one record." https://www.rfc-editor.org/rfc/rfc7208#section-3.2 Hope that helps! -- Jeremy Stanley

1 year, 11 months

Search results for query "dO"