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

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Cameron Smith

Mark, My apologies for not investigating more thoroughly before opening my mouth (so to speak). You are, of course, correct in your analysis of what happened to my emails, and this is not the first time that my email setup has caused me problems. I’ve added my alternate email address to my lists.mailman3.org user profile, so hopefully it won’t happen again. > On 2017.11.29, at 18:09 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/29/2017 05:05 PM, Cameron Smith wrote: >> >> On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. > > > Your post was received: > > Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: > message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: > from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) > > delivered to Mailman core: > > Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: > to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > and immediately discarded: > > Nov 21 14:31:21 2017 (19106) DISCARD: > <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > > >> Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. > > > Possibly you never received a list copy of his message because you were > directly addressed and your list option "Receive list copies (possible > duplicates)" is set to No. > > >> So, what’s going on? > > > As to why your post was discarded, unfortunately, the logs don't give > more info. There are a couple of possibilities. If your post contained > an attachment with Content=Type: application/subtype where sub-type > doesn't contain 'signature' it would have been discarded by a header > filter rule. Also it looks like you sent the message From: > <ccsmith(a)mail2.cetsi.com>. If that is not an address on your > <ccsmith(a)cetsi.com> account, it would have been discarded as a > non-member post. > > >> What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. > > > I see nothing so far to indicate anything at lists.mailman3.org is > broken in this respect. The only "unusual" thing is this is now a new > thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, > but presumably that is because your post was in reply to your earlier > post which wasn't archived. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Cameron Smith Nanaimo, BC tel:1.604.803.0051

8 years

[MM3-users] Re: Problem replying via Hyperkitty

by Jeff

I am finally getting around to revisiting the problems I have been having with replying or posting through the web of my Mailman 3 installation. Posts or replies simply disappear. Here is the Django log section from when I did a test post today: [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b/addresses HTTP/1.1" 200 824 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 1195 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org HTTP/1.1" 200 480 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname(a)lists.domain.org/config HTTP/1.1" 200 3878 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org/member/address%40domain.com HTTP/1.1" 200 544 "-" "GNU Mailman REST client v3.3.3" Nothing at all appeared in the Mailman log or the MTA log. Does anyone have any idea what is happening to the posts or what I can do to troubleshoot? Thanks much! > On Jun 30, 2022, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/30/22 10:07 AM, Jeff wrote: >> Hello Everyone, >> A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: >> [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) > > > This looks like the post of the reply to HyperKitty. What does the user see in response to that? > > There should be a brief alert popup indicating the message was sent. > > >> A couple of basic questions: >> 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? > > To the list. > > >> 2) what log files could I check to see what — if anything — happens to these emails? > > Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > > >> 3) Are there any settings that need to be set to make this work? > > There shouldn't be as long as the list and archiving work. > > Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto the list. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 4 months

[MM3-users] Re: Migrating Mailman 3 lists

by Andrew Hodgson

Mark Sapiro wrote: >On 5/19/20 7:25 PM, Mark Dadgar wrote: >> >> I get a bunch of these errors because identifiers in postgres are limited to 63 characters and mm3 creates some in sqlite that are longer than that: >> >> 2020-05-20T02:16:20.574000Z WARNING PostgreSQL warning: identifier "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6b632_uniq" will be truncated to "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6" [...] >> For reference my pgloader script looks like: >> >> load database >> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db >> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman >> >> with include drop, create tables, create indexes, reset sequences, no >> truncate Have you tried this without indexes and then run the migrate script? It may re-create them as part of the schema upgrade check. Andrew.

5 years, 6 months

[MM3-users] Re: Installation Wooes

by Samir Faci

@Marc disregard the direct email I sent you. Okay, so just to clarify both postfix and mailman are running on the same host. In theory, everything should be able to connect to localhost on port 25 to be able to send any emails it needs. 198.199.98.177 resolves is already added to my networks, but I added it explicitly. mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, lists.domain.org, 198.199.98.177 I tried setting the values to the dns name which resolves to the public IP and the 127.0.0.1 and right now I keep on seeing these errors: connect to lists.geekbeacon.org[198.199.98.177]:8024: Connection refused So, I ended up having to tweak my /etc/hosts file a bit as well as ``` smtp_host: lists.domain.org smtp_port: 25 smtp_user: smtp_pass: # 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 ``` So, now it's finally working but here's a question. Does 8024 need to be publically accessible from the outside? On Sun, May 3, 2020 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 8:13 PM, Samir Faci wrote: > > > > Postfix Failed Logs. > > > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > > unknown[198.199.98.177] > > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > > client=unknown[198.199.98.177] > > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > > message-id=<158856165549.136760.840427238489827082@lists> > > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > > from=<booh-bounces(a)lists.domain.org > > So mailman and Postfix are on different machines. That may complicate > things, but > > > > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue > active) > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > This was a successful delivery. > > > > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > > unknown[198.199.98.177] > > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > > <mailto:csgeek@domain.com>>: Relay access denied; > > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com so relay access is denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 7 months

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

by Odhiambo Washington

On Sat, Dec 10, 2022 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/10/22 01:13, Odhiambo Washington wrote: > > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> In the DATABASES['default'] definition, you need to set `'OPTIONS': > >> {'charset': 'utf8mb4'}` > >> > > > > I added that: > > > > [database] > > class: mailman.database.mysql.MySQLDatabase > > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > > /mailmansuite?charset=utf8mb4&use_unicode=1 > > > The above is for Mailman core. It doesn't affect HyperKitty. For that > you need to look at the DATABASES definition in > /etc/mailman3/settings.py > < > https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> > > and ensure that in addition to the other settings under `default {` you > have > ``` > 'OPTIONS': {'charset': 'utf8mb4'}, > ``` > > ... > >> You might also need to modify the tables, particularly hyperkitty_email > >> with something like > >> ``` > >> ALTER TABLE hyperkitty_email > >> DEFAULT CHARACTER SET utf8mb4, > >> MODIFY subject varchar(512) > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, > >> MODIFY content > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; > >> > > > > > > So I removed my list, dropped the database, and proceeded as follows: > > > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > > utf8mb4_0900_ai_ci; > > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET > utf8mb4 > > COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > > > I did all those (although looks overzealous) just to be on the safe > side. I > > have seen people putting emojis in their names. > > > None of that should be necessary. `mailman-web migrate` should create > the database and tables as needed. > > > > After that, I did the mailman-web migrate, created the list, imported the > > config from MM2 and then proceeded to import the archives. > > However, the errors still are there, and several messages were not > imported > > Do you have the OPTIONS setting in your DATABASES definition in > settings.py? > Here is what I have tested lately in settings.py: # MySQL Database setup DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmansuite', 'USER': 'mm3', 'PASSWORD': 'XXXXXXXXX', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } I have dropped the DB, recreated, run the 'migrate', created the list, imported config from MM2. However, nothing seems to be able to address the errors with importing the archives. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Odhiambo Washington

On Sun, Apr 3, 2022 at 12:06 PM Yvan ♞ <elemac(a)free.fr> wrote: > Hello every body > I have progress to try to reinstall mailman3 on yunohost server but I > still have an error, if somebody can help me as I don't understand the log > https://paste.yunohost.org/raw/ugijepuyuv > Sincerely. > Yvan > Hi Yvan, As previously advised by Mark Sapiro, you are better off taking to the YunoHost support people for help. They will most likely help you with the failing dependencies issue. But I also wonder - why don't you follow the virtualenv method to install? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 8 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 10:13 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This was added in Postorius 1.3.0 which was released almost 4 years ago. > If you can't upgrade, see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/messa > ge/6GKWYT3ZMXPHMGSXUW6OI6J2222AR7OV/ for a mailman shell script. That shell script seems to have errors: >>> pendings = getUtility(IPendings) >>> for token, data in pendings.find( ... token_owner=TokenOwner.subscriber, ... pend_type='subscription'): ... print("hello") ... Traceback (most recent call last): File "<console>", line 3, in <module> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) TypeError: find() got an unexpected keyword argument 'token_owner' --Quanah

2 years, 6 months

[MM3-users] Re: Hyperkitty is not archiving due to 405 error - GET instead of POST

by Matthias

Hi Mark, Mark Sapiro wrote: ... > You could always try adding additional logging to > mailman_hyperkitty/__init__.py to log the entire result, but I suspect > the issue is that there is a redirect somewhere in the path from the > configured HyperKitty base_url (see mailman_hyperkitty.cfg) and the > actual HyperKitty API that is redirecting the POST to a GET and also > dropping the POST data. Thanks a lot...I assumed already the same, but your sentence was giving me again some hint...and I found the base_url...there it wasn't httpS but http, which then was redirected and lost the POST... Now it is working as intended! Great, Thanks, Matthias

1 year, 9 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Andrew Hodgson

Mark Sapiro wrote: >On 4/17/20 4:51 PM, Abhilash Raj wrote: >> >> If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. >I created <https://gitlab.com/mailman/mailman/-/issues/699> for this. In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. Thanks. Andrew.

5 years, 7 months

[MM3-users] Re: The dread "relay access denied" error

by Bill Oliver

On Sat, 2024-11-02 at 16:48 -0700, Mark Sapiro wrote: > On 11/1/24 19:07, Bill Oliver wrote: > > > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mail.bill- > > oliver.com bill-oliver.com lists.bill-oliver.com > > I suspect this is the issue. mynetworks is a list of network > addresses > or network/netmask patterns. Domain names don't work. set > > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > 162.144.108.19 > Doh. That was exactly it. Thanks. There's another 20 hours of my life I'll never get back again... I ended up having to add my explicit IP address, but I dropped the names and it worked. Now it's running like a charm. Thank you so much. billo

1 year, 1 month

Search results for query "sapiro"