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

[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, 2 months

[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, 5 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, 3 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Nelson Strother

As you had suggested, the `in` runner/queue was missing in action. Given your insight about the limitations of `mailman restart`, I looked back at the log from the time of the preceding `mailman start`, and found that there was NOT a line such as: in runner started. in that instance! Watching the logs on each subsequent `mailman start`, the good news is that the `in` runner/queue has been started each time; the bad news is that slightly more than half of the time one or two runners are NOT shown as starting. The other runners/queues sometimes missing in action per the log file have been `retry`, `task`, `nntp`, `archive`, and `pipeline`. No errors are being recorded in the mailman log files. This is GNU Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 (2023-05-12) running on a shared system where VMware gives this server enough cycles that `mailman start` and `mailman stop` each consume from 20 minutes to an hour of wall clock time, so I do not issue those commands recreationally, attempting to keep the system available for users. What should I do to help understand the cause for these failures? Would not it be helpful for this limitation of restart to be included in: mailman restart --help with a suggestion to use `mailman stop` and `mailman start` instead? On 6/1/23 11:16, Mark Sapiro wrote: > When you issued a restart and the logs show runners restarting, did > all the runners restart or was one or more missing.

2 years

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Tue, Dec 27, 2022 at 11:57 AM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > The last I looked into using Twitter as an OAuth2 provider, which was > > some time ago, it would not work because Twitter would not provide the > > user's email address via OAuth2. Possibly this could work if the user's > > name was her Twitter handle. > > Yeah, but then I (@yasegumi@twitter) could log in as > yasegumi(a)example.com and every other yasegumi in the world. There > probably aren't any of those that aren't me, but of the 30 kids in my > 6th grade class 5 were named something with the diminuative "Steve", > and we also had one Stephanie. So I could log in as > steve(a)turnbull.sk.tsukuba.ac.jp (that's me) or steve(a)xemacs.org > (that's not me, I'm stephen(a)xemacs.org) or steve(a)any.old.com. Not > good. > > Also, I wouldn't trust Musk's Twitter with no security staff left to > give out only confirmed email addresses. If they give out any address > you gave them, then anybody can spoof anybody. So I would advise not > using Twitter as an idP under any conditions, unless it's to prove you > own a Twitter handle. > Okay. Now I really don't want to add Twitter to my Social Account logins :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

[MM3-users] Re: Archive search failing on one list

by Mark

On Sat, 2023-09-23 at 18:56 -0700, Mark Sapiro wrote: On 9/23/23 17:51, Mark wrote: > > For example, on searching for the word "Derbyshire" (which is > mentioned > in one of the archived messages) the results page displays: > > "Sorry no email could be found for this query." > > The logs show: > > +++++++++++++++++++++++++++++++++++++ > /var/log/mailman3/web/mailman-web.log > +++++++++++++++++++++++++++++++++++++ > > [pid: 1156|app: 0|req: 55/55] > 2001:8004:5310:2405:ce66:5ff:41fc:60db () > {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET > /mailman3/hyperkitty/search?mlist=LISTNAME- > 1%40DOMAIN.COM&q=Derbyshire > => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in > 164 > bytes (1 switches on core 0) ... > mlist = MailingList.objects.get(name=mlist_name) > File "/usr/lib/python3/dist- > packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/usr/lib/python3/dist-packages/django/db/models/query.py", > line > 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.mailinglist.MailingList.DoesNotExist: > MailingList2023-09-21 08:55:36.385239+10 > matching query does not exist. What does this database query return ``` select * from hyperkitty_mailinglist where name like 'LISTNAME-1(a)DOMAIN.COM'; ``` If it returns a row, does case match for the name in the row and the query? Yes, the query returns a result and the case in "name" matches that in the query ... select * from hyperkitty_mailinglist where name like 'listname(a)domain.com' id | 91 name | listname(a)domain.com display_name | Listname description | ... subject_prefix | [Listname] archive_policy | 1 created_at | 2023-09-21 08:55:36.385239+2 list_id | listname(a)domain.com

1 year, 9 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Odhiambo Washington

The links work for me. On Thu, Jan 9, 2025, 20:19 Alain D D Williams <addw(a)phcomp.co.uk> wrote: > On Thu, Jan 09, 2025 at 09:06:56AM -0800, Mark Sapiro wrote: > > On 1/9/25 06:07, Alain D D Williams wrote: > > > > > > For an example see: > > > > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > > > The above URL and also > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give > a 500 > > internal server error response. > > Sigh - try again. > > The 500 error happens several times a day. After 5 minutes it behaves as it > should ... until it happens again some time later. I have not found out > what is > happening; nothing obvious in the logs, not high system load. I can live > with > it for now as I am busy elsewhere. > > -- > Alain Williams > Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT > Lecturer. > +44 (0) 787 668 0256 https://www.phcomp.co.uk/ > Parliament Hill Computers. Registration Information: > https://www.phcomp.co.uk/Contact.html > #include <std_disclaimer.h> > _______________________________________________ > 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 odhiambo(a)gmail.com >

5 months, 3 weeks

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Eggert Ehmke

This makes it even stranger. Removing the trailing / did not help in my case, but replacing the mailman3 for mailman in the ProxyPass line did. Would be really nice to solve this problem at the root. Am Montag, 25. Oktober 2021, 18:09:21 CEST schrieb Mark Sapiro: > On 10/25/21 1:45 AM, Stefan Bauer wrote: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U > SXUYZYB5KIXT37APMCOAUZLKBRPARTL/ > > ... > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > Others have found that removing the trailing slash from > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > to make it > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > fixes the issue.

3 years, 8 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:37 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 00:32, Odhiambo Washington wrote: > > > > Apparently so, because: > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists > > No matching mailing lists found > > mailman@lists:~$ > > > > Which is surprising, given this: https://imgur.com/a/LPrh42K > > > Postfix is talking to a different Mailman core. > There isn't any other. This server has only been running Mailam21. > > root@lists:/home/wash# su - mailman > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create > > skunkworks(a)lists.my.co.ke > > sh: 1: /usr/sbin/postmap: not found > > sh: 1: /usr/sbin/postmap: not found > > Traceback (most recent call last): > ... > > RuntimeError: command failure: /usr/sbin/postmap > > /opt/mailman/var/data/postfix_lmtp, 127, Key has expired > > command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, > > 127, Key has expired > > > > Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. > > > In the [mta] section of mailman.cfg, put > ``` > incoming: mailman.mta.exim4.LMTP > configuration: python:mailman.config.exim4 > ``` > See > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is exactly what I have in my mailman.cfg Installing Postfix suppresses that message though. I installed Postfix and then disabled it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Matthew Blissett

On 13/07/2024 07:17, Mark Sapiro wrote: > On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >> >> Is there a configuration option that does this, or was it a custom >> change made in >> the templates? Was the change made to reduce fake registrations? Did >> it work? > > > It was added in Postorius 1.3.9. See the UI section at > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > > Yes, the change was made in an attempt to reduce fake registrations. > > We haven't really studied it's effectiveness. It seems to help > somewhat, but it also seems that bots may already have a template to > POST so removing it from the UI is not a complete solution. They would be missing the CSRF token (a hidden field on the anonymous signup form) so this ought to fail. > There is also a lot of email to innocent third parties and > non-existent addresses from attempts to register them for an account. There are patches to integrate a Captcha system here: https://gitlab.com/mailman/django-mailman3/-/issues/33 I think it's needed, as less than 24 hours after migrating to Mailman 3 I already see bots retrieving the signup form to get the CSRF token (GET /accounts/signup/?next=/postorius/lists/) then POSTing the request for a new user account (POST /accounts/signup/). There's also the setting ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False, which prevents spam from the "forgot password" address, see https://gitlab.com/mailman/postorius/-/issues/591 -- Matt

11 months, 3 weeks

Search results for query "sapiro"