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

[MM3-users] Re: Message getting held due to max number of recipients and maximum message size

by Mark Sapiro

On 9/22/23 11:37, Wong, Wesley wrote: > > Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. This is very strange. Are you certain the list's settings are 0? Are there possibly two lists in different domains or otherwise similar names and you are looking at the wrong one? The only place where the defaults are set is in mailman/styles/base.py and this only affects the default settings for a new list. The values in the ``` Message has more than 10 recipients The message is larger than the 40 KB maximum size ``` messages come from the list's settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/29/25 00:17, Alexander Inzinger-Zrock via Mailman-users wrote: > [Status] > > Suggestion: > > It seems, we are wasting to much time with a probably messed up system. > I suggest, that i do as initially suggested [1] and start over with a > reinstall. > > Last idea before that would be to > > 1. delete the files: > > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db > > 2. restart services > > 3. test if programms make new files > > 4. report to mailinglist > > Would that be of interest to someone? Yes. Also, is there anything in Mailman's logs from the time you ran `mailman aliases`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: New releases

by Mark Sapiro

On 6/9/20 1:05 AM, Danil Smirnov wrote: > On Tue, 9 Jun 2020 at 00:05, Mark Sapiro <mark(a)msapiro.net> wrote: > >> After you upgraded did you run these django-admin commands? >> ``` >> django-admin collectstatic --clear --noinput --verbosity 0 >> django-admin compress >> django-admin compilemessages >> django-admin migrate >> ``` >> These 4 commands should be run after every update to Postorius, >> HyperKitty or django_mainlman3. >> > > Hm, interesting... Could you point me to some related docs please? The documentation is weak and should be updated, but see <https://docs.mailman3.org/en/latest/upgrade-3.2.html#migration-steps> > To upgrade, I've just bumped app versions in my Dockerfiles, built and > restarted... > Mailman-core worked right away with no issues. > Mailman-web (Hyperkitty) failed with the error: > > ---------- > ERROR 2020-06-08 19:46:41,942 14 django.request Internal Server Error: > /hyperkitty/ > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/compressor/base.py", line 282, in > precompile > mod = import_module(mod_name) > File "/usr/lib/python3.6/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 994, in _gcd_import > File "<frozen importlib._bootstrap>", line 971, in _find_and_load > File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked > ModuleNotFoundError: No module named 'sassc -t compressed {infile} > {outfile}' ... > I've fixed the error by removing the older file which is > /opt/mailman-web-data/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss > > After that everything seems to be working fine. I'm not sure about the above error. 'sassc -t compressed {infile} {outfile}' is defined in `settings` COMPRESS_PRECOMPILERS, but it is a command to be run as part of `django-admin compress`, not a module to be imported. Possibly running `django-admin compress` before starting Hyperkitty would have avoided this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 1:55 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: >> >> Unless you want to remove the Ubuntu package and install everything >> with >> pip, you need to just stick with what you have that at least partly >> works and we'll try to determine how to fix the utf8mb4 issue. > > Hi Mark, > > You're a very patient soul. Thank you. > > Yes, I'm resigned to exactly that. The archives when folks send emojis > will break, but that's just life. Mail will get sent. Heck, I guess I > could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to > get rid of the emoji in the worst case... You would need to do that, because once one of the `emoji` messages gets into /var/lib/mailman3/archives/hyperkitty/spool, I think no further messages are archived because mailman_hyperkitty tries to process the queued messages first and throws the exception. But, it's still not clear to me whether you have removed the settings_local.pyc and restarted uWSGI or whatever interfaces to Django. > Once I've migrated my 1500 mailing lists (this weekend) to the server, > I'll think about how to get a new server set up that I can shift to and > I'll install that with pip, since that'll clearly give me something > more supportable. > > Is Ubuntu 20.04 a reasonable platform for that? Yes it is. FWIW, this list runs bleeding edge Mailman 3 on an Ubuntu 14.04 server (yes we should upgrade), the only issue being that we needed to install Python 3.6 (the latest at the time) from source because the native Python 3 was 3.4 -- 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: Time Zone Issue in Postorius

by Mark Sapiro

On 2/4/22 09:48, Andy Summers wrote: > Hello, > > I'm encountering an error that sounds similar to this previous thread: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I've tried setting my TIME_ZONE to 'UTC' in my settings.py and > settings_local.py files (and restarting Mailman), but when I check the > datetime for a held message in Postorius, the datetime seems to be > pushed +8 hours unexpectedly. > > My Postorius account time zone is set to "US/Pacific". The appropriate setting for Django is always `TIME_ZONE = 'UTC'`because the time passed from Mailman core is a naive datetime.datetime object and is actually UTC. This should then display the time in your account timezone since Postorius 1.3.4. See https://gitlab.com/mailman/postorius/-/merge_requests/531 If this isn't working in Postorius >=1.3.4, it's a Django issue. -- 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: Templates do not work

by Mark Sapiro

On 4/28/22 02:50, Eggert Ehmke wrote: > I created some templates in Postorius to get > personalized notifications when there are > moderator requests. The notifications I get seem to > be the standard texts. When I look into mailman/ > mm/var/templates > the directory is empty. Nevertheless, the templates I > create in Postorius seem to be stored (where?), they > just do not work. As Steve said the templates are stored in the database. I suspect the issue is and incorrect value for `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to construct the URI to retrieve the template. The URI is stored in the `template` table in the database. It is normally just `http(s)://host.name/` If this is the issue, after correcting the setting and restarting the web service, you will need to delete and re-enter the template in Postorius to correct the `template` table entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

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

by 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. -- 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: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/11/24 11:06 AM, Elias Rudberg wrote: > Hello! > > I am using mailman3 (version 3.3.8) and it mostly works fine, but > sometimes (usually several times every day) the error below appears. > > Any suggestions for what could be done about this? ... > Here is what the error message looks like: > ------------------------------------------- > > [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/postorius/lists/ > > Internal Server Error: /mailman3/postorius/lists/ > > ValueError at /postorius/lists/ > Need 2 values to unpack in for loop; got 1. Can you get the page at /mailman3/postorius/lists/ and /mailman3/postorius/lists/?all-lists If those are OK, look in your web server access logs for `GET /mailman3/postorius/lists/` messages with the same timestamp as those errors. Is there some bogus query fragment on those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Django Internal Server Error on held_messages

by Mark Sapiro

On 3/24/22 04:02, Hasan Berkay Çağır via Mailman-users wrote: > Hello, > > We've been running a Mailman3 instance with Debian 10's official package: > > Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version: 3.0 > Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] > > For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: > > """ > Internal Server Error: /postorius/lists/list.example.com/held_messages As Andrew suggests, you will probably find exceptions with tracebacks in Mailman core's mailman.log. This is probably /var/log/mailman/mailman.log in the Debian package. If you find such and you can't determine the problem from them, post one here. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Error while Approving a Post Through Email

by Mark Sapiro

On 12/14/22 01:45, Stephen J. Turnbull wrote: > Alex A.J. writes: > > line 1132, in identify_record > > raise exc.UnknownHashError("hash could not be identified") > > passlib.exc.UnknownHashError: hash could not be identified > > Dec 13 17:01:41 2022 (2677611) SHUNTING: > > 1670931101.6040337+d5806b00b2b9d03f25db396639f66f3a26516178 > > This looks like maybe you have the wrong password? > > Maybe Mark or Abhilash has a more concrete suggestion, I've never used > the Approved header with Mailman 3. I don't have more time to look at this now, but I think it's a bug. This patch ``` --- a/src/mailman/rules/approved.py +++ b/src/mailman/rules/approved.py @@ -140,6 +140,7 @@ class Approved: mpw = mlist.moderator_password else: mpw = mlist.moderator_password.decode('utf-8') + mpw = config.password_context.encrypt(mpw) is_valid, new_hash = config.password_context.verify(password, mpw) if is_valid and new_hash: # Hash algorithm migration. ``` may fix 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, 9 months

Search results for query "sapiro"