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

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/16/23 20:04, Mike Wertheim wrote: > Thanks for the response. > > A while back I experimented with enabling verp-probes. The users on the > list were confused by the probe emails and sent me a lot of messages asking > about them, so I disabled it. But at least their delivery wasn't being disabled because the probes weren't being bounced. Further, the first sentence in the body of the probe is "This is a probe message. You can ignore this message." If you think the probe could be more explanatory, you can always set a list:user:notice:probe template to say what you want. > There is zero spam on the list. Ill try reducing "bounce info stale after" > to "2d". (Actually, would "1d" be even better?) Suppose you set it to 1d. This means that in order for a true bouncing user to have delivery disabled with threshold = 5 There have to be posts every day for 5 consecutive days. If it's set to 2d, there can only be one day out of 6 with no posts for a true bouncing user's delivery to be disabled. If you can't guarantee that condition, you might as well just set Process Bounces to No. I would ensure Notify owner on bounce increment and Notify owner on disable are set to Yes. Then, assuming Mailman core >= 3.3.5, when users scores are incremented the owner will get a notice containing the bounce DSN. With that information, you can figure out why these valid addresses are bouncing the mail. Or, if the bounces occur during your outgoing SMTP, your MTA logs will have the reason. Given that information, you may be able to fix whatever is causing the delivery issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Mailman stopping message distribution because of SMTP errors

by Mark Sapiro

On 2/11/20 10:28 PM, Victoriano Giralt wrote: > > I have recently migrated some lists from Mailman 2 to Mailman 3. Users have > been added using the mailman client as pre-verified addresses so the > migration happened "silently". Thus, there was a dozen "bad" addresses > (domains that did not exist anymore). It seems you rolled your own instead of using `mailman import21`. Is there a reason for this? > Unfortunately, Mailman got some of the "bad" addresses in the first message > batch for sending out, so, Postfix closed the connection because of "too > many errors" and this stopped the process completely, i.e. Mailman did not > continue sending messages to the rest of the list over 600 addresses. Is the message shunted? Is there a traceback and a shunting message in mailman.log? Normally, I would expect the message to be queued in Mailman's retry queue and retried by Mailman > There was no more information in the logs than the Postfix error messages > in smtp.log. What was in the smtp.log? Nothing in mailman.log? Nothing in var/queue/shunt? > Once the "bad" addresses were removed, the list started working as > expected. > > I consider this a bug. The bouncing addresses should have been marked as > "non deliverable" and the subscriptions "paused" and the rest should have > been delivered. Or, the list owner should have been notified that there was > a problem with message distribution. None of these happened. The HEAD of the https://gitlab.com/mailman/mailman master branch implements bounce processing. This will be in 3.3.1 which is not yet released. The place for a bug report is <https://gitlab.com/mailman/mailman/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/25/21 9:38 AM, dancab(a)caltech.edu wrote: > Mark, > > Is it only this list that has an issue? > > Yes, this is the only list that is having the issue. > > Can you visit other pages for this list? > > Yes, I'm able to view the members list, list settings, templates, etc. > > I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. > > > ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen > chunked=chunked, > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib64/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response This is from Django's log. What's in Mailman core's mailman.log? Since everything else is accessing the REST API with no problem, I think core must be stuck on something and timing out. Is there a time delay between trying to get the held messages view and the "Mailman REST API not available. Please start Mailman core." response? Also is there a non-zero count in the badge on the Held messages tab? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: update_index_one_list in parallel?

by Mark Sapiro

On 5/28/19 3:44 AM, Szymon Sokół wrote: > > Now, however, I have noticed that indexing my archives in hyperkitty (using "manage.py update_index_one_list" for each list in sequence) takes quite a lot of time while using only one CPU (out of 4). Hence my question - is it safe to run several such processes in parallel, and if so, will it have any benefits? I have no idea how locking on the database is done in this code, maybe I'll end up running the jobs in sequence anyway due to exclusive locks… Any informed answers will be appreciated. As Abhilash says, we really haven't tried. You could try running more than one "manage.py update_index_one_list" for different lists in parallel and see how it goes. I suspect it depends on the Haystack backend. Whoosh tends to be used because it's pure Python and installable with pip, but again as Abhilash says, we have recently converted to elasticsearch. There are some issues with that both due to the fact that elasticsearch runs as a separate service on the host, and we are using elasticsearch 5, the Haystack support for which is still developmental (and the current elasticsearch version is 7), but for example, indexing 180,000+ messages on mail.python.org takes 15 minutes elapsed time (about 14 minutes CPU) with elasticsearch which is an order of magnitude faster than the multiple hours it took with Whoosh. On the other hand, this only affects search in HyperKitty, and you didn't have archive search in Mailman 2.1, so if it takes an extra day to get it working in HyperKitty, it's probably not a big deal. You could just migrate all your lists and when done, run manage.py rebuild_index & and just let it run in the background until it's done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: non-member moderation: list default vs default processing

by Mark Sapiro

On 5/24/21 10:46 AM, dancab(a)caltech.edu wrote: > Sorry for any confusion. I'm specifically referring to addresses configured as "accept_these_nonmembers" in Mailman2. Upon importing to Mailman3 I see the moderation setting for most of those non-members as "Default Processing -- run additional checks and accept the message." This is the correct result for an imported address from accept_these_nonmembers. > However, I've seen a few others set with the moderation option as "List default -- follow the list's default member action." after migrating to Mailman3. In our case that means "Hold for moderation". So we've had a couple of incidents where a user that was able to email the list just fine via Mailman2 is unable to message the list once migrated to Mailman3. > > I'll try importing more lists to look for some kind of pattern now that I'm aware of this happening. Yes. importing an address from accept_these_nonmembers should not result in a non-member with moderation_action = List Default. If you send me a config.pck that you imported that resulted in this, I'll investigate further, or perhaps you can identify the conditions that cause this. One thing you might look at is whether the affected addresses were previously imported as members or non-members of another list. Also, I don't know if this is possible given your list create/import scenario, but if there is a window between list creation and the import, if the non-member posts during that window, a non-member record will be created with moderation_action = List Default and the import won't change that. If this is the case, the import will print <address> is already imported with role MemberRole.nonmember for each such address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Dealing with spam from Web users

by Mark Sapiro

On 4/1/23 08:09, Jeremy Stanley wrote: > We recently migrated a bunch of lists from 2.1 to 3.3.7 and have > started to get spammers posting via HyperKitty (because I guess > that's easier for them than SMTP). It looks like I should be able to > set posts from HyperKitty to be automatically moderated by creating > a header filter on "User-Agent" matching "HyperKitty" but is there a > better/easier way? Typically, these would be non-members posting from HyperKitty and then being automatically subscribed. Set `Default action to take when a member posts to the list` to `Hold for moderation` so that all posts from members you haven't seen before are held. Then when handling a held post, if it is spam set the posters moderation action to discard and discard the message; if it is on topic, set the posters moderation action to default processing and accept the message. > Also, for things which already went out to the list, obviously I can > ban the spammer but what's the cleanest solution for removing > their posts from list archives so that we don't further their goals > by continuing to publish their handiwork? List owners should be able to delete messages and threads from HyperKitty, but they can't. See <https://gitlab.com/mailman/hyperkitty/-/issues/261>. You need to be a superuser to do this. If you are logged in as a user with Superuser status there will be a `Delete this thread` link in the thread view and a `Delete this message` link in the message view. You can use the `django-admin createsuperuser` command to create superusers. Also, anyone who is a superuser can set this for any user via the Django admin web UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Change base mailman URL path

by Mark Sapiro

On 4/6/23 20:07, chad.hays86(a)gmail.com wrote: > Hi, I recently completed the a Mailman3 install using these[1] instructions. I'm able to access the web interface, the Django admin app, etc off the root domain URL. For example: https://mydomain.org/mailman3, https://mydomain.org/admin, https://mydomain.org/archives > > What's the most straightforward way to put all of these URL paths behind a different context? For example: https://mydomain.org/lists/mailman3, https://mydomain.org/lists/admin, https://mydomain.org/lists/archives > > I'm running Apache2 as my web server and am using mod_proxy to proxy requests to uwsgi. There are two pieces to this: For the Django side, copy /opt/mailman/venv/lib/python3.x/site-packages/mailman_web/urls.py to /etc/mailman3/urls.py where python3.x is the python version in your venv and edit that file as in ``` 30,34c30,34 < path('mailman3/', include('postorius.urls')), < path('archives/', include('hyperkitty.urls')), < path('', include('django_mailman3.urls')), < path('accounts/', include('allauth.urls')), < path('admin/', admin.site.urls), --- > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), ``` and add the following to /etc/mailman3/settings.py ROOT_URLCONF = 'urls' Then for the apache side, it depends what you have for your ProxyPass directives are. If you have several like ``` ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ... ``` change those to ``` ProxyPass "/lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" ProxyPass "/lists/archives" "http://127.0.0.1:8000/lists/archives" ``` If you have just one like ``` ProxyPass "/" "http://127.0.0.1:8000/" ``` change it to ``` ProxyPass "/lists" "http://127.0.0.1:8000/lists" ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: No e-mail distribution after import of archive

by Markus Grandpré

Dear Mr Sapiro, thank you so much for your advice: > Check ownership and permissions on everything in var/templates/ fixed the issue. All pending email has been delivered immediately after i changed ownership on our Debian12 server: # chown list:list /var/lib/mailman3/templates -R Best regards, Markus Grandpré Am 11/12/24 um 22:45 schrieb Mark Sapiro: > On 11/11/24 23:33, Markus Grandpré wrote: >> Dear Mr. Sapiro, >> >> on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into >> a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list >> find their way into the archive, but they are not sent to any member of the list. >> >> Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a >> problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please >> help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive >> mailman system v3.3.8 during the next months. > > Nothing in HyperKitty should affect Mail delivery from the list. The symptom you see could result in a file in Mailman's > mailman/templates/lists/<THIS.LISTS.ID>/<LC>/ directory not being readable by the Mailman user. Check ownership and > permissions on everything in var/templates/ > > See the latter part of the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/ > KGYZXN2QP3RWRZOQKLHD2MKUSI7H2W6B/ > > Note that if this is the issue, something other than hyperkitty_import did it. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

10 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 6/12/19 1:46 AM, Henrik Rasmussen wrote: > > The difference was that list(m.pass_types) is [] > > Now, setting > > m.pass_types = ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword'] > > on the new testlist and resending the mail again, the mail still came out intact. > > So I guess the problem must be something complete different. > > Also I wonder why a newly created list accepts the PDF in question, when list(m.pass_types) is []. You need to look at all of pass_types, filter_types, pass_extensions and filter_extensions for both lists. For a newly created list, these are all empty. They work as in Mailmam 2.1 and are imported from the similarly named 2.1 attributes by `mailman import21`. In brief if filter_content is True, processing is: 1. If a part's MIME type is in filter_types it is removed. 2. If pass_types is not empty and a part's MIME type is not in pass_types it is removed. 3. If a part has a file name and the file name extension is in filter_extensions it is removed. 4. If a part has a file name and pass_extensions is not empty and the part's file name extension is not in pass_extensions it is removed. So in your case of the list that doesn't work, possibilities are: 1. The PDF part's MIME type is in filter_types, or 2. The PDF part has a file name whose extension is in filter_extensions, or 3. pass_extensions is non-empty and The PDF part has a file name whose extension is not in pass_extensions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Help with fresh debian install

by Mark Sapiro

On 10/5/19 11:30 AM, Mark Dadgar wrote: > > Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. You could just run, e.g., `sudo -u list bin/mailman import21 ...` which will work even if 'list' can't log in. > I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: ... > Any thoughts on how I can re-run the full import to make sure that all the archives are present? As far as reimporting the entire archive, you need the --since option. As it says in hyperkitty_import --help > --since SINCE only import emails later than this date. Defaults to > the date of the newest message in the existing archive > if any. If you run hyperkitty_import --since=1990-01-01, that should do it. As far as "the archives for many months consist of just a single identical thread", were there error messages when you ran the initial import? Were there issues in the imported mbox that you have corrected? Mailman 2.1's bin/cleanarch can help identify unescaped 'From ' lines that cause problems. If unescaped 'From ' lines is the issue and you have fixed them, rerunning the import should import the messages correctly, but it won't delete the bogus threads. You can delete these threads manually in HyperKitty if you are logged in as a Django superuser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Search results for query "sapiro"