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

[MM3-users] Re: MM3 on debian - redirect problem

by Mark Sapiro

On 4/27/20 8:17 AM, Gelpi Andrea wrote: > Hi, > on a debian10 I have mm3 installed via apt-get > > apt-get install mailman3-full > dpkg-reconfigure mailman3 > dpkg-reconfigure mailman3-web > > I have this minor issue > > https://webserver/mailman3 redirects to > http://webserver/mailman/postorius/lists/ > > that doesn't exist. > > The same problem form django admin page to return to lists > > https://website/mailman3/admin/sites/site > > In the upper right corner I have a link to https://webserver/mailman3 > that redirects to https://mailman/postorius/lists/ > > I searched for a redirect but without success. The redirection must be a web server issue. There is a urls.py file probably in the same directory as your django settings - probably /usr/share/mailman3-web/urls.py in your case. You can make a URL like http://webserver/mailman/postorius/lists/ work by adding url(r'^mailman/postorius/', include('postorius.urls')), to the urlpatterns list in the urls.py file. -- 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: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 06:48, Odhiambo Washington wrote: > > There is a WARNING on > https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install > which says one must create the config file as /etc/mailman3/mailman.cfg > How to force mailman to read that file is something I haven't understood, > but turns out to be what has taken me days trying to get things right. If you run the `mailman` command without any -C option, it will look for a config in /etc/mailman3/mailman.cfg > Ultimately, when I did the import, there was only one email from the > archives that failed to be imported - which I honestly don't mind, but > maybe there is a solution for this > "'utf-8' codec can't encode character '\udcae' in position 331: surrogates > not allowed" ?? If you provide a copy of that message from the mbox, either on the list or to me directly, I'll investigate. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Change delivery_status of a member by using the rest api

by Mark Sapiro

On 5/4/23 12:30, Michael Schaarschmidt wrote: > Hello, > > I would like to set or change the delivery_status of a list member by > using the rest api. The curl request looks like > > curl \ > -X PATCH \ > -H "Content-Type: application/json“ \ > -H "Accept: application/json“ \ > -u restadmin:secret_password \ > -d "@./foo_patch.json“ \ > "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e“ > > With the json-file: > > { „delivery_status“: „by_user“ } I assume those fancy quotes are an artifact of your mail client. > I get an error message: > > {"title": "400 Bad Request", "description": "Unexpected parameters: > delivery_status“} > > > Is there a way to change the attribute `delivery_status` of an existing > member by using the rest api? You can't set a memnber's delivery status directly. It is an attribute of the member's preferences. The correct endpoint is "http://127.0.0.1:8001/3.1/members/ebcdd09bb8d84758a135c3449023701e/preferen…" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Moderation of held emails vs. spam

by Mark Sapiro

On 3/11/25 7:09 AM, ricola(a)poivron.org wrote: > > The problem is when spam is held for moderation and forwarded to the list owner, the mail provider of the list owner sometimes flags the moderation request as spam because it includes the original spam message. > > Sounds much safer to only forward a summary of the subject line, sender and size to the list owners and not the full message. This is https://gitlab.com/mailman/mailman/-/issues/670. https://gitlab.com/mailman/mailman/-/merge_requests/1332 and https://gitlab.com/mailman/mailman/-/merge_requests/1334 introduce a new admin_notify_held_with_attachment list attribute which if set False will not include the message in the admin notice. This will be in the next release. In the mean time, you can set the list's `Admin immed notify` setting to No to not send the immediate notice and only send the daily summary, but this doesn't completely solve the issue as sometimes the Subject: of the held message contains things that will trigger spam/malware filters. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 12/12/19 6:36 AM, Dieter Leupold via Mailman-users wrote: > Hi, > > I'm new to MM3. I installed version 3.1.1 on Ubuntu 18.04. All looks > fine. But i miss the setting "pass_mime_types" at content filtering. The settings are there in Mailman core but not exposed in Postorius. You can set them via `mailman shell`. MM 2.1 settings map to MM 3 as: filter_mime_types -> filter_types pass_mime_types -> pass_types filter_filename_extensions -> filter_extensions pass_filename_extensions -> pass_extensions collapse_alternatives -> collapse_alternatives * convert_html_to_plaintext -> convert_html_to_plaintext * filter_action -> filter_action * in Postorius Settings -> Alter Messages The mailman import21 command will properly import these settings when importing a Mailman 2.1 list. > Also i don't find the settings for bounce processing. Are these features > no longer supported at version 3.1.1? Bounce processing is not yet implemented in MM 2.1. See <https://gitlab.com/mailman/mailman/issues/343>. There was a recent GSOC project to address this. See <https://gitlab.com/mailman/mailman/merge_requests/538>. I don't know how close this is to being ready. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: HyperKitty failure

by Mark Sapiro

On 12/30/21 1:30 PM, William Oliver wrote: > On Thu, 2021-12-30 at 21:19 +0000, horvath.arpad.szfvar(a)gmail.com > wrote: >> Hi, >> >> I try to connect mailman3 to hyperkitty, but there is no success so >> far. You can see the details below. How can I solve the problem? >> >> As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on >> the same server, so I guess localhost won't work. >> >> In mailman-hyperkitty.cfg there is a line: >> >> base_url: http://lists.xxx.hu/hyperkitty/ As noted in the thread that William references and also the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… the issue is probably that the above http url is being redirected to https and losing POST data. Set the above to base_url: https://lists.xxx.hu/hyperkitty/ > [snip] > > I'm no expert, but here's a previous discussion I found: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Mark Sapiro

On 1/6/22 12:52 PM, Stephen Daniel wrote: > > Sendgrid requires that the "From:" address on any email reference an > authenticated domain. > > In the old mailman2 implementation, emails sent by mailman are listed as > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > Reply-to: <human name> sender(a)senderdomain.com (the original email's sender) > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > validated domain. > > However, in my mailman3 implementation, the From: header lists the original > email's sender. Sendgrid rejects this because the original email's > sender's address is not one of the validated domains. > > How do I configure mailman3 to generate headers in the same style as the > old mailman2 implementation? In the list's Settings -> DMARC mitigations, set DMARC mitigation action to Rrplace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Lost posting in archives

by Mark Sapiro

On 1/21/22 3:06 PM, Axel Rau wrote: > I created a list, did migration from 2.1 and run update_index_one_list. > Then I posted a test mail to the list and it got distributed and was seen in the archive. > Now 2 days later it does no longer show up in the archive. > > What is going on here? > May this have to do with > HYPERKITTY_RENDER_INLINE_IMAGE > which I have turned on meanwhile. It may. Is there anything in Django's log about this? If you have the original message from the list, can you go to the URL in the Archived-At: header? is the message in the hyperkitty_email table in the database? E.g., SELECT * FROM hyperkitty_email WHERE message_id_hash ='xxx'; (xxx is the value of the Message-ID-Hash: header from the message) If the prototype archiver is enabled for the list, the message should be in Mailman's var/archives/prototype/list(a)example.com/new directory and that message will have the Archived-At: and Message-ID-Hash: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > > For the list I am talking about: > - Default action to take when a member posts to the list is set to "Hold for moderation" > - Default action to take when a non-member posts to the list is set to "Hold for moderation" > - When I am viewing all users, the migrated ones are set to Moderation Action: "Hold for moderation". The mass-added ones post-migration are set to Moderation Action: "None" > - When a mass-added post-migration user sent an email to the list it passed through without being held. This should not happen. In the message as delivered to the list what do you see in the X-Mailman-Rule-Misses: header and the X-Mailman-Rule-Hits: header if any? > Happy to check any logs if there might be something to hunt for. What if anything is in the lists Accept these non-members setting? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

Search results for query "sapiro"