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

[MM3-users] Re: Moderation not working?

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: >> >> Hi Folks, Running a shiny new instance of mailman3, as per the >> Debian package (version 3.2.2) but the moderation doesn't seem to >> work. WE got hit by a heap of spammers overnight, even though the >> 'hold for moderation' bit is set for non-members (and now for >> members too). Mark> If the action for member posts was accept ot default processing Mark> at the time, perhaps the spam spoofed a member address in one of Mark> From:, Reply-To:, Sender: or the envelope sender, Nope ... >> Emails seem just to get straight through. Mark> Even now with both member and non-member actions set to hold? Haven't seen any emails since setting that bit, so can't tell yet. The only think I noticed after trawling through all the configs is there was no moderator address set up. In Mailman 2.1 that meant the list owner would be asked to moderate. I've added a couple of addresses to see what happens next For other lists on the same mailman instance I *am* seeing moderation requests for non-member postings --- but they had explicit moderator addresses configured. Peter C

4 years, 5 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by David Newman

On 12/29/21 4:11 PM, Mark Sapiro wrote: > On 12/29/21 3:58 PM, William Oliver wrote: >> >> I'd like to delete all my archives that are more than a certain age, >> e.g. more than a week old. I can easily do that with a cron job, >> deleting old files in >> >> >> /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* >> >> which is, as far as I can see the only place archive emails live. > > > Those are emails archived in the prototype archiver. That's all the > prototype archiver does - store the mail there. The HyperKitty archived > emails are stored in the mailmanweb database in the hyperkitty_email > table. Attachments are in the hyperkitty_attachment table and other > tables are also involved. As a followup: Is there any need or advantage to running both the prototype and hyperkitty archivers? I did an installation following the venv directions, and it looks as though the system now uses both archivers. If this is a duplication of effort and storage, is it safe to disable the prototype archiver like this: # /etc/mailman3/mailman.cfg .. [archiver.prototype] enable: no and then delete anything under here? /opt/mailman/mm/var/archives/prototype/ Thanks dn

3 years, 4 months

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

4 years, 8 months

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Bill Oliver

On Sun, 2024-10-27 at 10:01 -0700, Mark Sapiro wrote: > On 10/27/24 05:13, Bill Oliver wrote: > > > > (venv) mailman@mail:~$ pip freeze | grep readme > > readme-renderer==17.4 > > > Which is over 6 years old. Howat did that get installed? Current > version > is 44.0. There may or may not be an issue with the current version as > it > imports cmarkgfm which is in the venv of all the MM 3 installations I > support, but I don't know how it gets there as even though > readme_renderer imports it, it is not listed as required by > readme_renderer or anything else. > > In any case, in your venv, do > ``` > pip install --update readme_renderer cmarkgfm > ``` > That did the trick, though I had to use --upgrade instead of --update. Thanks... Now on to the next step. I don't know about the libraries. Here's my mailman info. It seems like the right version of python. (venv) mailman@mail:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:qazASD%401cko@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Thanks for your help! billo

6 months, 3 weeks

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by ulf.rapphahn＠offis.de

Mark Sapiro wrote: > Lists, not Mailman lists. When you create a list in Postorius or Mailman > core, this is a Mailman list. A corresponding HyperKitty list will also > be created if hyperkitty is one of the active archivers for the list so > you see it in Django. > When you create a list in Django, it is only a HyperKitty list and will > be visible in HyperKitty, but no Mailman list is created so the list is > not in Mailman/Postorius. Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

6 months, 1 week

[MM3-users] Re: Error: 451 Requested action aborted

by Hagen Bauer

On 16.11.18 00:41, Mark Sapiro wrote: > On 11/15/18 8:23 AM, Hagen Bauer wrote: >> Hi >> I am running mailman in docker and I start to receive this error when my >> postfix tries to deliver a mail >> >> said: 451 Requested action aborted: error in processing (in reply to end >> of DATA command)) >> >> Any idea what is going wrong and where to look for problems? > > > Is there more information in the Postfix mail.log? > > no, in postfix this is the only entry. But I believe I solved one problem and now have to work on the next one. First I saw this error in in a log file ERROR could not translate host name "database" to address: Name does not resolve Based on this hint https://github.com/moby/moby/issues/8425 adding external dns server made this message go away. Now I find this error in my logs. : ERROR: xlog flush request 0/1FA5640 is not satisfied --- flushed only to 0/1E9C7A0 CONTEXT: writing block 0 of relation base/16384/16525 I believe this is related to some sort of database corruption but since I have no idea about postgres I am not sure (I chose the docker images because I didnt want to care about the Internals) any suggestions are welcome

6 years, 6 months

[MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3?

by Phil Stracchino

On 2020-01-30 12:01, Mark Sapiro wrote: > On 1/30/20 1:50 AM, Gila Halpern wrote: >> I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? > > > This feature in MM 2.1 is not very effective. On mail.python.org, this > feature as well as reCAPTCHA is enabled (e.g. > <https://mail.python.org/mailman/listinfo/mailman-users>) and we still > get periodic attacks of robotic subscribes that get around these measures. Human verification vs. verification-defeating countermeasures is an ongoing arms race which, frankly, humans have been losing for a long time. I have more than once commented, not entirely joking, that we're reaching a point where *FAILURE* to complete the CAPTCHA is evidence that you're a human. We need to come up with a better verification paradigm than presenting increasingly difficult puzzles which AI agents are better overall at solving than humans are. -- Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958

5 years, 3 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Hello every body I have progress to try to reinstall mailman3 on yunohost server but I still have an error, if somebody can help me as I don't understand the log https://paste.yunohost.org/raw/ugijepuyuv Sincerely. Yvan Le 14/03/2022 à 16:31, Yvan ♞ a écrit : > Ok thanks, I'll try on debian forum as I already unsuccessfully tried > on yunohost since 6 months. > > Le 14/03/2022 à 16:23, Mark Sapiro a écrit : >> On 3/14/22 08:12, Yvan ♞ wrote: >>> Maybe an idea of my problem as I have pgadmin app installed, it >>> could be in conflict to create a postgresql db? >> >> Your original dbug logs seem to show no issue with postgresql. >> >> I don't think people on this list can be much help for installing the >> Debian package on YunoHost. As I said earlier, I would go first to >> YunoHost for help and then to Debian if necessary. >> >> If you want help from us, I recommend installing as documented at >> https://docs.mailman3.org/en/latest/install/virtualenv.html >> > _______________________________________________ > 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/

3 years, 1 month

[MM3-users] Re: combine postorius and hyperkitty into one Apache vhost

by Eggert Ehmke

So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ... ´ never change a running system Am Donnerstag, 29. Dezember 2022, 21:48:54 CET schrieb Mark Sapiro: > On 12/29/22 05:51, Wolfgang Rosenauer wrote: > > Hi, > > > > I'm in the process to set up a new mailman3 site. > > (Migrating from mailman2) > > > > There are RPMs for my distribution which integrate postorius and > > hyperkitty with uwsgi. > > I think you'll be much happier if you don't use the distro's RPMs which > are probably out of date and instead follow > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those > instructions use uWSGI as a WSGI interface, but Gunicorn > <https://gunicorn.org/> is what is used on the site supporting this > list. The advantages of Gunicorn are it's already installed as a > dependency of Mailman core, and it's what the Mailman developers are > more familiar with. > > I'll work on updating > <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include > Gunicorn as an alternative.

2 years, 4 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Joel Lord

On 12/26/2020 3:07 PM, Mark Sapiro wrote: > As far as utf8mb4 vs. utf8 is concerned. There will be issues with the > hyperkitty_email table subject and content columns in particular and > maybe others if email messages contain 4-byte utf-8 unicodes. However, > as I read the MySQL docs, for columns like VARCHAR(255) and > VARCHAR(510), the difference affects only the number of characters that > can be stored in the column and not the actual column width. I.e., a > VARCHAR(255) column is actually up to 256 bytes wide (1 byte for length > and up to 255 butes of data) and can thus hold up to 85 3-byte utf-8 > encodings or up to 63 4-byte utf-8 encodings, but since any string > normally contains only a few if any (probably none in the case of the > mailinglist table) the actual limit is much closer to 85. > Earlier I had attempted changing the encoding and collation and manually adding the new column, and it failed with the same error. This fits with Mark's explanation of how the column size and encoding go together. I just ran an "optimize table mailinglist;" and then the update ran clean. Thanks for the eyeballs today, no idea why that would have worked but now we're up and running. -- Joel Lord

4 years, 4 months

Search results for query "sapiro"