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

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-28 01:32, Mark Sapiro wrote: >> I also note that this timeout only occurs when it is a subscription >> via REST. I.e. subscription via email or `mailman addmembers` sends >> the proper welcome message. >> >> So it has something to do with the retrieval being done by a rest >> runner, but I still don't know what the underlying issue is. I created a text file as a custom welcome message and chowned it to mailman:mailman, then edited the database record (template.uri) from http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… TO file:///home/mark/welcome.txt This delivered the custom welcome message to the user when subscribed via Mass Subscribe. I'm not sure what this tells me other than a call can be made to a file but not the database. > More strangeness. I've now done a test on one of the production > servers I manage, and there is no error. Both the production server > and the development server are running the identical Mailman code > installed in a venv, they both have the same version of urllib3 and > similar Python versions, 3.9.16 on the development server and 3.9.10 > on the production server. Both servers are running under Ubuntu > 20.04.6. The only other difference I see is on the production server > everything runs as user mailman and on the development server > everything runs as user mark. Mine is Debian 12 with Python 3.11.2. Could a newer Python version really cause this amount of grief?

1 year

[MM3-users] Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:58 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 7:17 PM, Timour Bakeev wrote: > > Hi all! > > > > I'm trying to use extended placeholders for the [templated texts]( > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > in the message footer that are sent to the members: > ... > > But my attempts to use REST API to set it fail: > > > This feature is in the not yet released Mailman 3.3.10, see > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… And talking of 3.3.10, I have a feature request, or I might just be making unnecessary noise if this is already documented somewhere: I find the unsubscribe_all button quite scary! I have never used it though, so I am not quite sure about its behavior. What scares me is the possibility of clicking it and then in one fell swoop you've removed ALL the members without a "confirmation". So I was wondering if that button can be modified to have a dropdown selection with No/Yes, so that one has to select the No (backoff) or Yes (blow away!). -- 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]

10 months, 1 week

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Bill Christensen

On 6/23/18 5:01 PM, Mark Sapiro wrote: > On 06/23/2018 02:48 PM, Bill Christensen wrote: >> Our Mailman2 setup uses Fetchmail to retrieve list mail from our >> accounts on Gmail. >> >> Is there a similar setup for Mailman3? > > Delivery to Mailman is different in Mailman 3. What are you currently > doing with Fetchmail? the general syntax we're using is: poll imap.gmail.com protocol IMAP username "<list address>" there with password "<password>" is "mailman" here nofetchall keep ssl sslcertck sslcertpath /path/to/share/ssl/certs mda "/path/to/mail/mailman post <listname>" set daemon 900 > > If you are doing something like getting the mail from google and > delivering it via SMTP to an MTA on the Mailman server, that should > still work for MM 3. I think that's what the above is doing. Right? > > If Fetchmail is piping it to a command like > > "| /path/to/mail/mailman post listname" > > that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP > server (which it calls a runner). Mail is normally delivered to an MTA > which is configured to relay the mail via LMTP to the localhost port > that Mailman is listening on. So Fetchmail can eithr deliver to the MTA > and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. > -- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108 Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo

6 years, 10 months

[MM3-users] Re: Your Dashboard

by Mark Dadgar

On Feb 11, 2020, at 12:26 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. Awesome - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 3 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/23/22 12:37, denis.bitouze(a)univ-littoral.fr wrote: > > > > What is the Postorius version and is it installed from source, pip or as > > package and if as package, what package? - Postorius 1.3.4 - Here are some details: ┌──── │ $ apt-cache show mailman3-full │ Package: mailman3-full │ Source: mailman3 │ Version: 3.3.3-1 │ Installed-Size: 48 │ Maintainer: Debian Mailman Team <pkg-mailman-hackers(a)lists.alioth.debian.org> │ Architecture: all │ Depends: mailman3, mailman3-web, python3-mailman-hyperkitty │ Description-en: Full Mailman3 mailing list management suite (metapackage) │ This is GNU Mailman, a mailing list management system. This metapackage │ depends on all components of the full Mailman3 suite: │ . │ * mailman3: The core Mailman3 delivery engine │ * mailman3-web: Django project integrating Mailman3 postorius and hyperkitty │ * python3-mailman-hyperkitty: Mailman3 server plugin for Hyperkitty archiver └──── > The choices should be Accept, Reject and Discard. There should be no > Ignore choice, but I'm guessing you see them in French where the > translation of Discard is Ignorer. See > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/L.... Indeed, sorry for the misleading translation from French to English. Maybe I'll suggest another word to the French translation team. > The difference between Reject and Discard is Reject notifies the > sender of the rejection whereas Discard just discards the message > without notification. IMHO, even in English, “Reject” and “Discard” are not self-explanatory. BTW, no clue about an automatic banishment of emails from discarded messages?

2 years, 10 months

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Eggert Ehmke

/ I saw output like:/ <User "Real Name1" (250400693957149667060114911620088407125) at 0x7f9435096640> deleted from Mailman <User "Real Name2" (52978839424924170731978420609240089133) at 0x7f9435096760> deleted from Mailman So your users had no real names configured? Cheers, Eggert Am Dienstag, 25. April 2023, 23:14:27 CEST schrieb Andrew Hodgson: > Mark Sapiro wrote: > >The script at https://www.msapiro.net/scripts/clean_users.py has been > >updated. As before, it has settings to control whether Django users are > >deleted if there is a corresponding Mailman user with no memberships or > >only if there is no corresponding Mailman user, and whether or not Mailman > >users with no >memberships are deleted. > Thanks, I ran this script and it did delete a load of Mailman users, I got > output similar to this: <User "" (47600399411039288509336192576257642185) > at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? > > Thanks. > Andrew. > _______________________________________________ > 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 > /BTJUT6FGNGK5ARADPD6VW37VMHQG2GWJ/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years

[MM3-users] Re: hyperkitty failed to create a thread

by Marvin Gülker

Hi, Am 11. Februar 2019 um 13:20 Uhr -0800 schrieb Mark Sapiro: > I downloaded the February mbox from > <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> > and imported it to a test list with 'django-admin hyperkitty_import and > see the same issue. Here's the Hyperkitty Mbox for my affected mailinglist: <https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch…> Maildir from my local machine as received from Mailman via e-mail: <https://files.guelker.eu/misc/tsc-devel.tar.gz> > Examination of the mbox shows for the first message [...] > Note the folding of the header and the double angle brackets. I can confirm that I see this behaviour for my affected mailinglist as well. The Message-ID header is broken over two lines with double angle brackets in the Hyperkitty MBox linked above: Message-ID: < <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org>> However, the original message as it was delivered by Mailman to me does not have such a weird message-id header: Message-ID: <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org> In this message, the header is broken exactly as shown above after the colon of "Message-ID:". Maybe some problem with parsing long Message-ID headers, or ones folded over multiple lines? With regard to bug reporting on gitlab.com: I already have accounts on a ton of sites, and at some point I'd actually like to stop creating new ones all the time... Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

6 years, 3 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > That combination at least produces multipart/signed messages with > multipart/* parts containing a Content-Transfer-Encoding: header. > > The Python 3 email library considers this to be a > InvalidMultipartContentTransferEncodingDefect() message defect. Merely containing C-T-E is not an error per RFC 2045, although it seems to consider it a stupid thing to do. If present, it may be "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening that restriction been published since? (I don't know why it would, though.) Even with a non-cleartext C-T-E, it seems reasonable for Mailman to treat it as application/octet-stream and pass it through, unless the list is configured to do something like strip application/octet-stream or that requires decoding like spam-filtering (Postel principle, although one could argue it shouldn't be sent on on the same principle -- ah, the joys of being an e-mail Mediator). That would be especially true it if were quoted-printable, since any relevant MIME headers would (presumably) be pure ASCII and therefore unencoded. > multipart/signed > multipart/mixed * > text/plain > message/rfc822 (the attached message) * > multipart/signed * > text/plain > application/pgp-signature > text/plain (an empty plain text part) > text/plain (a quote of my message to you) > application/pgp-signature It's true that Apple Mail is horked if it produces that structure with C-T-E in the indicated places (but we already knew that :-( ). Steve

3 years, 1 month

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > Any suggestion on how to migrate mailing list and archirve with diffirent > server and domain. For the mailing list from sample.domain1.example.com > to sample.domain2.example.com > > Old Mailing list > Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] > Domain Domain1.example.com > > New Mailing list > Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC > 8.5.0 20210514 (Red Hat 8.5.0-20)] > Domain domain2.example.com How many lists? How big are the archives? Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, it seems like it's not a trivial exercise. However, I am wondering about the consequences of: 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then re-importing 2. editing settings.py and webserver config to reflect the DOMAIN2 3. reconfiguring your MTA to handle list mails using the DOMAIN2 I am imagining a virtualenv type of installation. Is there somewhere in the data where the DOMAIN1 is hardcoded in a way that it cannot be replaced by a text editor? @Mark Sapiro <mark(a)msapiro.net> ? -- 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, 4 months

[MM3-users] Re: Dealing with email bounces from web signups

by Hans-Martin Mosner

Am 17.03.22 um 03:40 schrieb Mark Sapiro: > > > The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address > receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which > affects my server's reputation. But, so far, I don't do anything about that either. > As I'm a mail admin for a server whose users get lots of those misguided mails I'd say that the vast majority of them are not from mailing list signups but from web contact forms which automatically respond to entered contact requests with "Dear Polly liked your profile https://bit.ly/crap". I regularly report these as spam and expect website owners to disable automatic mails from such forms (I also advise our users who have their own websites to disable that, and strictly filter it on outgoing mail). I would probably also report these as spam when coming from mailing lists subscription requests, and I would likewise advise you to send subscription responses only after a moderator checks and releases the subscription request. It can still happen that you send out somethin to someone who didn't subscribe, but you should be able to reduce the numbers significantly. I know this causes extra moderator work because you don't get the automated pre-filtering for deliverable addresses, so this is something where you need to weigh pros and cons for your particular situation. Cheers, Hans-Martin

3 years, 2 months

Search results for query "sapiro"