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

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/31/2017 01:06 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna <simon.hanna(a)serve-me.info> wrote: >> On 03/31/2017 08:10 AM, David Krantz wrote: >>> I think that would correspond to this line in urls.py >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >> Yes, that's the culprit. Replace it with the following: >> >> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >> You can also update whatever guide you were using... > > Great, will try that! I don't know whether I can update the guide. > It's the one referenced earlier in this thread named something like > setup experience of mailman 3 in production. Yes, that comes from "https://wiki.list.org/DOC/Mailman%203%20installation%20experience", specifically the attachment urls.py. The interesting thing is that works for me both at <https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/18/20 10:26 AM, Milan P. Stanić wrote: > > Sending mail by mail clients works and mails are sent to subscribers > properly. > Most other 'things' works but we have problem with reply to posts and > creating new threads using web ui. When replying to post with web ui it > says that the everything is ok and post is sent but post doesn't arrive > to mailing list. Same happens with creating new thread. > > Our debug says "KeyError: 'display_fixed'" but we are not sure what > should be changed/fixed/set for this problem. > Attached is excerpt from debug log. I don't think that exception is the problem. See <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/posting.…> for whit I think might be the issue. I.e., Hyperkitty won't send the mail if DEBUG = True -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Bounce Problems

by Mark Sapiro

On 2/23/21 2:25 AM, M4tze wrote: > If I understand the settings correctly, bounce_info_stale_after = 7d > means that any bounce received > 7d ago are not counted (which would be > intuitive). But it doesn't work that way. It means that the user's bounce info is ignored/discarded if the user hasn't received a bounce within the last bounce_info_stale_after days. I.e it is bounce_info_stale_after and not bounces_stale_after. > It seems, that there must be a 7d gap between the last > bounce received and a new bounce to get the score reset to 1. Is my > interpretation right? Is this intentional? Can this be changed? Yes, this behavior is intentional and no, it won't be changed. Consider a list that gets fewer than five posts per week. While default settings probably aren't appropriate for this list, with default settings, if we discarded bounces older than 7 days, an address that bounced every post would never be disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/6/21 6:26 AM, bob B wrote: > > But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024 > > > ************************************ > 2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1(a)sender.com> > 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER(a)sender.com>, size=8308, nrcpt=1 (queue active) > 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused > 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) The Connection refused is from trying to connect to localhost at IPv6 ::1. Then Postfix tries 127.0.0.1, gets connected and then Mailman's LMTP runner closes the connection. There may be more info from aiosmtpd in Mailman's smtp.log. -- 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: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: High IO for 8+ hours

by Mark Sapiro

On 3/1/26 05:10, Paul Tomblin via Mailman-users wrote: > > I did a "update_index_one_list" on each archive after I brought it into hyperkitty. I was impressed with the full text search. The HyperKitty update_and_clean_index job runs monthly and does the same thing as the hourly update_index job plus removing index entries for messages that have been deleted from HyperKitty. It is very long running and there are lock contention issues between it and the hourly update_index job. It's purpose is to drop entries for messages that have been removed. It's not critical that it runs at all. If you don't want to run it, you can apply a patch like: ``` --- a/hyperkitty/jobs/update_and_clean_index.py +++ b/hyperkitty/jobs/update_and_clean_index.py @@ -31,7 +31,7 @@ from hyperkitty.search_indexes import update_index class Job(BaseJob): help = "Update the full-text index and clean old entries" - when = "monthly" + when = "never" def execute(self): run_with_lock(update_index, remove=True) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

[MM3-users] Re: Button unsubscribe

by Mark Sapiro

On 12/7/18 7:22 AM, erlonmz(a)hotmail.com wrote: > how to put a button unsubscribe in the message together with the part > > " LIST mailing list -- LIST@domain > To unsubscribe send an email to LIST-leave@domain' > > I want to put this button in the emails to the users unsubscribe. it would already send the confirmation tolkien. > > my question is, has some place where generated tolkien is saved in mailman files? No. The confirmation token is not generated until the unsubscribe request is received so there's no way to know it in advance. Further, a button requires HTML and the list's footer is plain text. Finally, one-click unsubscribe without confirmation is dangerous. People forward list messages to others and even reply to the list without removing the one-click unsubscribe link and then wonder why they get removed from the list. At least with confirmation, they only wonder why they got a confirmation request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/14/24 13:57, Mark wrote: > > I have a list and user account set with French as the preferred language. > > Most message emails (such as the Welcome email) all arrive in French, > but not the Password Reset email (shown below) - it arrives in English. > > I'm guessing that there may not be an .mo file for it. This message comes from django-allauth. there is a French message catalog for it. These are in site-packages/allauth/locale/fr/LC_MESSAGES and should be good. You can always run `django-admin compilemessages` to update all the .mo files for all the projects. However, the issue is probably that Django doesn't get the language context from the list's preferred language. In fact, the password reset is not in a list context at all. See https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… for how it determines the language to serve. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 11:01, Arte Chambers via Mailman-users wrote: > Thanks, this was helpful. It was a message I sent to the list that was just > an image attachment with no body text. I noticed this other thread > about messages > with attachments, without text discarded silently > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I am attaching the pickle file hoping that it helps anyone researching this > issue. I think the underlying issue is the same as in that thread. While your message has mime structure multipart/mixed multipart/alternative text/plain <- empty text/html image/jpeg If you have content filtering Collapse alternatives = yes, it will become multipart/mixed text/plain <- empty image/jpeg after collapsing alternatives and that will trigger the error. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for a patch (not yet tested) that I think will fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/11/25 08:45, dap1--- via Mailman-users wrote: > Not sure what that means. I would expect to allow any domain to access mailman-web since members can come from anywhere. Isn't that what the '*' means?. > > ALLOWED_HOSTS = ["*", > "localhost", # Archiving API from Mailman, keep it. > "127.0.0.1", > # "lists.your-domain.org", > # Add here all production domains you have. > ] You should not have the "*". The remote host accessing mailman-web does not need to be in ALLOWED_HOSTS. The host that needs to be allowed is the host that is receiving the request. You should remove the "*" as it's too permissive, and as it says, add any and all host names that external users use to access the system. That's why it's called ALLOWED_HOSTS rather that CLIENTS. And have you tried logging in using one of those host names rather than localhost? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

Search results for query "sapiro"