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

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by tokyoprogressive＠mailbox.org

Thank you Mark. I will need to find time tomorrow to create two totally new email accounts that I can use in tests so I do not inadvertently sign up again with the same address. Also will double check my settings. Best regards Paul Sent from my iPhone > On Sep 17, 2019, at 14:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/16/19 9:22 PM, Paul Arenson wrote: >> In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? >> >> 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… >> >> 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" >> >> 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org > > > You have to approve it or the user has to confirm her email address? > Maybe you have to approve it because the lists Subscription Policy is > Moderate. > >> 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? > > > No. They will be a member, they just will not have a Django account that > they can log in to. > > >> 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: >> >> "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. >> To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" > > > Because when you create a Django account, you have to confirm your email > address. > > >> 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! >> To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by >> sending a message to....... I then get a notice: >> >> "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" > > > What is Message Acceptance -> Default action to take when a member posts > to the list ? > > You get the notice or the user gets the notice? > > >> 7) While if they send FROM THE interface it goes through. >> >> 8) What I am confused about. >> >> Signing up for an account should make them a member, right? Subscribing should make them a non member, no? > > Signing up for an account is just signing up for a Django account. You > can sign up for an account and log in and then subscribe to the list. > > Subscribing makes one a member whether or not you subscribe from a > logged in account or subscribe without creating an account. > > >> But here it seems that both make them a non member. > > If an address which is not a member posts to the list, that address > becomes a non-member. This is the only way other than being explicitly > added by an admin that an address becomes a non-member. > > >> And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. > > > If by sending from the interface, you mean posting via hyperkitty, the > user must have an account and be logged in to do that. > > Your "same person" may have multiple entities within Mailman, possibly > subtly different email addresses, one of which is a member and one of > which isn't. > > > -- > 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/

7 years, 1 month

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-05-01 13:35, Mark Sapiro wrote: > On 4/30/24 17:54, Mark wrote: >> >> In the new installation, are the template.uri (in the mailman DB) >> records written as http://localhost:8000/... ? > No. In both the installation that worked and the one that didn't, they > were https://msapiro.net/..., but I don't think it would have > mattered. > > When I reinstalled, I kept the same database, I only rebuilt the venv. > > As I have said at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, > this is all strange. My logs from the failure show the web server > getting the request and serving the template with a 200 status and > then after 5 seconds which is the specified timeout a > requests.exceptions.ReadTimeout error is logged in mailman.log. > > The exact same code is executed whether by a rest runner gunicorn > worker or via some other Mailman core runner, but only the rest runner > fails. Further, a reinstalled venv on the failing server has no error, > and another server which has a venv identical to the failing one > except for Python micro version also has no error. > > I can't begin to understand what the underlying cause might be. Thank you Mark. I'll give rebuilding venv a crack. In the meantime I've cobbled together a script -- https://postmark.io/scripts/ -- and it's got things going for the moment. .

2 years, 6 months

[MM3-users] Re: Domain defaults for new lists

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 1/29/26 14:04, Peter Chubb via Mailman-users wrote: >> >> Hi Folks, Is there a simple way to set up the defaults for any >> newly created lists? We've had a few cases recently where in the >> time between creating a mass-populated list and making it private >> it's been inundated with spam. Mark> Actually, I think the 'private-default' list style does almost Mark> all you want except for new members Mark> moderated. https://gitlab.com/mailman/mailman/-/issues/871 asks Mark> for that to be changed, however the 'private-default' list style Mark> sets the subscription policy to confirm then moderate so Mark> spammers can't subscribe and post without their subscriptions Mark> being approved by a moderator. Thanks Mark --- how do I make that the default though? Admins are creating lists without changing the list style because they don't know or understand that they can or should change things. (and searching for 'defaults' in the docs didn't lead me to styles) Mark> You can implement a new list style to do exactly what you Mark> want. See https://gitlab.com/mailman/example-mailman-plugin for Mark> information about implementing a plugin to do that. Also see Mark> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… Mark> for general information on list styles. Thanks for the pointers. I'll try ... Peter C

9 months

[MM3-users] Re: MTA setup

by Arte Chambers

Looks like the from header is the email address I am using for testing: From: Arte Chambers <paul.m.robey(a)gmail.com> ``` $mailman qfile /opt/mailman/mm/var/archives/hyperkitty/spool/1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck [----- start pickle -----] <----- start object 1 -----> Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) by list.louisvillecommunitygrocery.com (Postfix) with ESMTPS id 3E36381ED2 for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 17:02:48 +0000 (UTC) Received: by mail-lj1-f182.google.com with SMTP id 38308e7fff4ca-3003e203acaso44323081fa.1 for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 09:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734973367; x=1735578167; darn= list.louisvillecommunitygrocery.com; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; b=SFr5MsvE4S5GUIy9pEuqDHdEW5nW16briFnXG6ARqjLiFgAX12TU5ozUgw5NCJobcx RQWkL64TyXv2C2CTKHjcBH26jiLo1p7h2edLXSBCmd374QbRYQPbv5yZb4jmwX5kfMzr fc/I3pSk6ruN/j+JPGLVxBJBreyLRDV+YL0rDJts83a8hcPHghGMkRTmi2Z1vLYgqThA 2fV/IYwrOe/q4c2+/AwlKQFUuClaxFN4AniNi++Hk7eql7q4ceDtURp1pHW/h4+8UXgJ 2DQ+zwPapOiU5POtfka1fAHTJgykuOoMCmO0YiwfP9p51lXmr4GmdFjFgDOiQwzhx8dH vAEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734973367; x=1735578167; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; b=IwucO1D8XfIbWVT6dQ/LdKNsesrSsiekzj0khFI38CLd6WryQGJOQftxOLR5AvneNs 9gUbVvFAe0VENzTbMrelFr4H5DTI9HrKbNVYEbleeMrbuPypsTdtqWTrjizGhMQROhvs vOxl3T+UfRjDywLj9OuYBiWKTDIIaTpeQ7rR4u1lT8iMGTUre0V8kikm1BsFXwRRzl+U e0ghdIaZYN5kfu/bfR5veCCQhU0l0IF+DvoZzdJCgLkYgImIPhB/X7Zv0wQiUnKoebJo h1UFAEQIrVx2iMFHzLsHiqBhKHvJqG72PAa1bMiG0K3EsYvSJHu5zjrkTjoHXazAci4c trXg== X-Gm-Message-State: AOJu0Yz8oZOnap/9jvXAOcFZnjYoReVHBQrfUnC9u6Mi6M2Ea7dkofrs 4mAlHtOuQYGEyFxJZIOdFybTI20qdBoQBJAPF7FHL6d4mAGrLbPMgTZy3/hWFtmXfOo93a74CSu YsRCZKH5ixK5jPHn4Vye0i/h0oilWXQ== X-Gm-Gg: ASbGncsYG3zr9300F+iwV6VLqHlMKoLuiS2mnT5tGiid8o6Ojd4JIrOBQI0BVNx1aeO FVisNFC7AKewms0adY+Ug4HLKEtg8GwSIz0i32IOtPNA+tNxEAac47wHBGkcv+H2EfTOMsD/p X-Google-Smtp-Source: AGHT+IFNyfqXALTZ0zcO0GJZfpIf/4WT9IZ2EG3oThjt5aoZP3sdPhxjN2UOMTqwI2axiu9io1WSiFszsjxPLHtLIs8= X-Received: by 2002:a05:6512:1190:b0:53e:37e4:1457 with SMTP id 2adb3069b0e04-54229550e25mr4737922e87.33.1734973365282; Mon, 23 Dec 2024 09:02:45 -0800 (PST) MIME-Version: 1.0 References: <77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> In-Reply-To: <77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com > From: Arte Chambers <paul.m.robey(a)gmail.com> Date: Mon, 23 Dec 2024 12:02:08 -0500 Message-ID: <CAM05vAepJnJQengX825dZ4E1PVVxeEgv4ogUcmifP9tqh1i= mg(a)mail.gmail.com> To: Arte Chambers <paul.m.robey(a)gmail.com> Content-Type: multipart/alternative; boundary="00000000000021f3da0629f2f7aa" Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG X-Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG X-MailFrom: paul.m.robey(a)gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: testing(a)list.louisvillecommunitygrocery.com X-Mailman-Version: 3.3.10 Precedence: list Subject: [Testing] Re: test 12.23.24 11.57 List-Id: For testing mailing list software < testing.list.louisvillecommunitygrocery.com> Archived-At: <> List-Archive: <> List-Help: <mailto:testing-request@list.louisvillecommunitygrocery.com ?subject=help> List-Owner: <mailto:testing-owner@list.louisvillecommunitygrocery.com> List-Post: <mailto:testing@list.louisvillecommunitygrocery.com> List-Subscribe: <mailto:testing-join@list.louisvillecommunitygrocery.com> List-Unsubscribe: <mailto:testing-leave@list.louisvillecommunitygrocery.com> --00000000000021f3da0629f2f7aa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Dec 23, 2024 at 2:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: > > Output from mailman log after sending a test message to the list: > > > > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): > > File > > > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > > line 158, in _archive_message > > url = self._send_message(mlist, msg) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File > > > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > > line 228, in _send_message > > raise ValueError(result.text) > > ValueError: > > <!doctype html> > > <html lang="en"> > > <head> > > <title>Bad Request (400)</title> > > </head> > > <body> > > <h1>Bad Request (400)</h1><p></p> > > </body> > > </html> > > mailman_hyperkitty is sending the message to hyperkitty to be archived > and receiving the 400 response. Presumably it has previously requested > and received the list_url and the permalink to put in the message > headers. This can be confirmed by the presence of List-Archive: and > Archived-At: headers with values in the messages from the list. So the > configuration seems to be correct to allow mailman_hyperkitty to > communicate with hyperkitty. It is not clear why, but this code > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… > is getting the ValueError. That can come from one of three places in > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. > > The lack of a Message-ID: is not it because Mailman's lmtp runner will > add one. Most likely it is the non-ascii sender address from > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… > > What do you get from > ``` > mailman qfile var/archives/hyperkitty/spool/xxx.pck > ``` > where xxx.pck is one of the (hopefully smaller) files. In particular, > what is the From: header in that? > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

1 year, 10 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Gilles Filippini a écrit le 15/06/2020 à 22:05 : > Mark Sapiro a écrit le 15/06/2020 à 21:58 : >> On 6/15/20 12:37 PM, Gilles Filippini wrote: >>> >>> There are 4 emails stored into this folder. 3 of them are spam, and the >>> last one is a legitimate email. This is annoying that such emails could >>> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >>> more and more hyperkitty errors. >>> >>> Any idea how to make their processing more error proof? >> >> >> Change the offending .encode() method to add errors='replace'. >> >> The traceback from the error should tell you where it is. >> >> You could also open an issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If >> you do that, please include an error traceback if possible. If there is >> not a traceback in mailman.log associated with the error, there might be >> one in HyperKitty's log (configured in Django's settings). Also, >> including enough of a message to duplicate the issue is very helpful. > > I've now deleted the offending messages. Will open an issue with related > details the next time this error occurs. I've experienced this error again today. Filed issue #301. Thanks, _g.

6 years, 4 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Jim Popovitch

On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > Comments received directly from one of the people who developed the > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > established that AWS Mailman is *not* intended to interact with AWS > > > SES when receiving email messages > > > > I don't think there is a Mailman 4 and the person who is marketing his > > services under that name is sending a confusing message to the public. > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > In response to our request, the following is included at the bottom of > <https://mailman3.com/>;: > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > used to coordinate development of the Mailman 3 free software suite. The > Mailman 3 core developers are not involved with Mailman3.com, and cannot > answer any questions or provide any support related to its operations. > If you are looking for resources for development of the Mailman 3 free > software suite, please see mailman3.org. > > Yes, this is all ripe for confusion ... Just to add, Danil also owns mailman2.com, and I own (and parked) mailman2.org. -Jim P.

5 years, 7 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 18:55, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > > > If I could run MM3 using the apt-get install method, perhaps that would > > have made my life a bit easier, hoping that MM3 can actually be run in > > parallel with MM2.1 on the same host. Is anyone doing that already?? > > > Yes. I am on two production and one development machines. See, e.g. > <https://mail.python.org/mailman/listinfo/> and > <https://mail.python.org/mailman3/> > > One caveat here is I install both Mailman 2.1 and Mailman 3 from source > on all these machines. I don't know for example if the Debian/Ubuntu > packages play well together. > On my Ubuntu machine, I decided to install MM21 from source so I am willing to install MM3 either from source, package or docker. The sparse documentation is my undoing. > > See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > for more on how I install MM 3. > I have seen that link, but it's missing a ton of details within the process. As I mentioned before, these virtualenv stuff are new to me too, so I thought dockernization would simplify things. If you could include the missing steps that you left out then I could possibly be able to follow the steps :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 9 months

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Mark Sapiro writes: > Actually, there's more involved in the pipeline between the > to_archive and to_outgoing handlers. The to-digest, to-usenet, > after-delivery, acknowledge and dmarc handlers are all invoked > between to_archive and to_outgoing IIRC all of the shunted messages that Stephen looked at with qfiles were those special digest messages (ie, message component empty, pointer to lists/$LIST/something.mmdf in the msg_data component). So something is going wrong in the to-digest handler. I don't understand why the original .pck would disappear without either leaving an error log or delivering. (Hmm, @Stephan, have you looked at your "vette" log? it is a separate log in your mailman.cfg I think.) The number of .tmp files lying around bothers me. AFA grep CS, the only place that can happen is in switchboard.py:136 in .enqueue: with open(tmpfile, 'wb') as fp: fp.write(msgsave) pickle.dump(data, fp, protocol) fp.flush() os.fsync(fp.fileno()) os.rename(tmpfile, filename) where `msgsave` is already a pickled object. So either pickle.dump is choking on something in data (the metadata, which I believe is all primitive Python data types), or something (OOM kill?) is happening at the OS level. A crash in pickle.dump should leave an exception log and backtrace in the logs. AFAIK, Mailman does not clean up .tmp files at startup, right? -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 year, 3 months

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

by Mark

On 2024-06-23 00:51, Mark Sapiro wrote: >> Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> > > Probably because (in Postorius) Settings->Digest->Enable Digests is No Double checked that Enabled Digest s= Yes >> Then, as "mailman", I ran "mailman digests --periodic" manually and >> got the same error (as expected since there is nothing there) ... > This error should not occur if there is no digests.mmdf. It only does > occur because you have set Digest size threshold to 0 under the > assumption that 0 means unlimited which it doesn't. If you don't want > digests sent on size, you need to set Digest size threshold to a very > large number. > > I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid > throwing the exception, but setting the threshold to 0 is still wrong Oh? I was indeed assuming that 0 meant unlimited. The threshold was set at 0. My thinking was that meant the file size was not a factor in determining when the digest was sent and that the sending would be triggered by the daily cron. When I set the threshold very low - 10kB - it sends a digest on every post. So my understanding of what you are saying is: if the threshold is set very large, say 100,000 kB - then a digest will be be sent by the daily cron even if it is smaller than 100,000 kB. Am I understanding correctly?

2 years, 4 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Ken Alker

--On Monday, June 26, 2023 5:26 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 4:19 PM, Ken Alker wrote: >> >> What else is stored in /var/messages, if not archives? I see 4711 >> messages in that directory (which I presume would be as many messages >> are in the archive database). If there is a write-up on this, feel >> free to point me to it. I found >> <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/ >> model/docs/messagestore.html> but this isn't really answering my >> question. > > > These are probably artifacts from your old Debian package. There have > been issues in the past with handled messages not being removed from the > message store. See https://gitlab.com/mailman/mailman/-/issues/257 > > This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes > orphaned messages from the message store, but if they are still > referenced in pendings they won't be deleted. So is the only thing stored in var/messages/ the held messages, and nothing more? Is there an outline as to how to clean up the var/messages hierarchy? (I assume one has to be careful not to remove current held messages and maybe old ones that have not been processed; or maybe "old ones" can all be assumed orphaned, and thus, removed w/o concern?)

3 years, 4 months

Search results for query "sapiro"