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

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: > >Hi Mark, > > > >Actually all this stuff happens inside the container after it's started > >and > >initialized without errors. I didn't amend the image anyhow. > > > >Also I have the configuration based on docker-compose.yaml provided in > >the > >repository which works just fine for mailman-web image. > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > >fails > >with 500 error... > > > >Now answering your questions: > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > >what > >> is set for Q_CLUSTER? > >> > > > >I've checked settings.py inside the container and I haven't found any > >of > >the mentioned configurations there. > > > >Does the manage.py that's being run here point to the right > >settings.py? > >> > > > >No clue. > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > >configured image? > > > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > Because I am a dum dum ;-) > > Will work on removing those crons and stuff. Would be nice if you > opened an issue on Github so that I don't forget. Should now be fixed in the latest image. > > >Danil > > > > > > > >> -- > >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > >> San Francisco Bay Area, California better use your sense - B. > >Dylan > >> _______________________________________________ > >> 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/ > >> > >_______________________________________________ > >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/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- thanks, Abhilash Raj (maxking)

7 years, 1 month

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, Actually, this is saying cache_life under mailman: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… There is a cache_lifetime under ‘dmarc’. I used your clue about the database to concoct my own solution… 😊. I edited the ‘expires_on’ values in the file_cache table in the database so the files were expired. It looks like the times in that table are UTC. I’m going to ratchet down my cache_life so anyone that is playing with templates doesn’t go bonkers (like me) with why their changes aren’t honored. I have a small site, so not much performance impact. Thank you for your help. Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Monday, February 10, 2025 at 12:46 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/10/25 12:09, Lieuallen, Thomas Otis via Mailman-users wrote: > > I haven’t figured out how to work with these cache files. I found some mention that a runner would clean up cache files after a week (default) and that one could use ‘cache_life’ to change that default. So, I set the following and restarted mailman. The cache files hadn’t been removed after > 4 hours, so I unset it and restarted again. > > Cache_life: 1d The setting is actually `cache_lifetime` in the `[mailman]` section of mailman.cfg, however when a file is cached, it's lifetime is saved in the database and won't be changed by changing that setting. > Without further information or direction, I’m tempted to just remove those cache files and move on with life. Removing them is OK, but a database entry will still exist pointing to them and attempt to retrieve them will return `Cache content lost`. The way to properly remove them is in Mailman shell ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> cm = getUtility(ICacheManager) >>> cm.clear() >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

1 year, 1 month

[MM3-users] Re: statistics monitoring for Mailman3

by Mohsen Masoudfar

Hi Mark, Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) Data: b'QUIT' Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) connection lost Mar 14 12:53:19 2021 (11696) Connection lost during _handle_client() Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> post to testlist3(a)newlistserv.aaas.org from testlist3(a)newlistserv.aaas.org, 7940 bytes LOGRETS = ('^(?P<time_stamp>[^(]*) $\d+$ (?:\n|\r\n)') LOGREMI = (' (?P<msgid><[^>]*>) smtp to (?P<listname>[^ ]*) for (?P<count>\d+) recips, completed ') def get_log_data(log): data = [] with open(log) as fp: for line in fp.readlines(): mo = re.match(LOGRE, line) if not mo: mts = re.match(LOGRETS, line) if mts: dt = datetime.datetime.strptime(mts.group('time_stamp'), '%b %d %H:%M:%S %Y') if not mts: mmi = re.match(LOGREMI, line) if mmi: mid = mmi.group('msgid') lname = mmi.group('listname') count = int(mmi.group('count')) data.append([dt, mid, lname, count]) continue continue dt = datetime.datetime.strptime(mo.group('time_stamp'), '%b %d %H:%M:%S %Y') mid = mo.group('msgid') lname = mo.group('listname') count = int(mo.group('count')) data.append([dt, mid, lname, count]) return data Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, March 12, 2021 2:42 PM To: MM3 Users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: statistics monitoring for Mailman3 [EXTERNAL EMAIL] On 3/12/21 11:22 AM, Mohsen Masoudfar wrote: > I was checking on log rotating on smtp.log. On my server it does not rotate. I could use log-rotator to rotate that, but could not find any information how to inform the mailman process of the rotation, e.g. which signal to send him? The `mailman reopen` command is the recommended way, or you can send the `master` a SIGUSR1. The master's PID is in the file var/master.pid or /var/run/mailman/master.pid if you've configured `layout: fhs`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years

[MM3-users] Re: Mailman3 stopped sending out mail

by Mark Sapiro

On 12/31/18 2:14 AM, Abhijith PA via Mailman-users wrote: > > Recently my mailman3 instance stopped distributing mail. But mailman's > own mail (notification, digest etc) and archiving are working OK. I > couldn't figure what is going wrong > >>From mail.log > > --- > Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection > established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher > ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) > Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection > established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher > ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) > Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass > (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; > envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> > Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass > (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; > envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> > Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: > client=mail.xxxx.xx[5.79.72.163] > Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: > client=mail.xxxx.xx[5.79.72.163] > Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: > message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> > Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: > message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> > Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx > SSL > Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx > SSL > Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from > mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from > mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: > from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: > from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) > Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: > to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, > delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) > Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: > to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, > delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed Aside from the fact that every log message seems to appear twice, this is a normal interaction for an incoming message to test3(a)lists.yyyy.yy and delivered via lmtp to Mailman. Is there anything later in the Postfix log for an outgoing message? > I am not sure why 'postfix/qmgr[13211]: 04C2412038F: removed' is happening. Because Postfix has finished processing the message, has delivered it and has now removed it from the Postfix queue. > from /var/log/mailman3/smtp.log: > > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) handling connection > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'LHLO lists.xxxx.xx' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'MAIL > FROM:<abhijith(a)xxxx.xx>' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) sender: abhijith(a)xxxx.xx > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'RCPT > TO:<test3(a)xxxx.xx>' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) recip: test3(a)xxxx.xx > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'DATA' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'QUIT' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) connection lost > Dec 31 10:03:21 2018 (6323) Connection lost during _handle_client() This again looks normal other than the fact that the recipient in the Postfix log is test3(a)lists.yyyy.yy and the recipient here is test3(a)xxxx.xx. Presumably this is just because you chose to mung the address differently in the two cases. > Here again I am doubtful about 'Connection lost during _handle_client()'. That's a red herring. Postfix has sent QUIT and one side or the other has disconnected before the response to QUIT was delivered. That's not a problem. This 'Connection lost during _handle_client()' message is a normal occurrence. It appears that Mailman has received the post. You say above "...archiving are working OK". Does this mean the received post was archived? If so, and it wasn't delivered, either there were no eligible recipients or something went wrong in the pipeline between to-archive and to-outgoing. Are there messages like Dec 31 10:03:xx 2018 (6323) <message-id> smtp to test3(a)xxxx.xx for n recips, completed in n.nn seconds Dec 31 10:03:xx 2018 (6323) <message-id> post to test3(a)xxxx.xx from test3-bounces(a)xxxx.xx, nnn bytes in /var/log/mailman3/smtp.log What's in /var/log/mailman3/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Can login at /admin, but cannot login at the account/login page.

by Abhilash Raj

> On Aug 15, 2021, at 11:33 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 8/14/21 9:34 PM, Stephen J. Turnbull wrote: >> I'm sorry, I'm in a "second vaccination" fog at the moment (mending >> but concentration lasts only about 10 minutes), so I'll answer what I >> know offhand since Abhilash is busy and Mark is probably offline for >> vacation by now. > > > Not quite, but very soon. > > >> pabsta(a)gmail.com writes: >> > However, if logout and attempt to login from the postorius website, >> > I get a « 502 bad gateway » error after roughly 30 seconds. The >> > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech >> > free" error message > > >> I would guess this is also just a connection drop because it doesn't >> receive the expected response within timeout. > > > I'm sure that's right. > > >> > and the nginx error logs just show a connection drop: >> > >> > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: >> > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" >> a > > > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" > > > I suspect you may be getting a redirect from http to https which is losing POST data and you need to change > > proxy_pass http://127.0.0.1:8006; > > in your nginx configuration to > > proxy_pass https://127.0.0.1:8006; > > or set > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" > This configuration actually doesn’t really dictate connection related configs, but mostly, the protocol to use in the emails generated by django-allauth to verify email and such. It shouldn’t have affect on the problem IMO. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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, 7 months

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Willie Castillo

I saw them. OK, I must be missing several steps. I'll have to start from scratch. Let me carefully follow the link you send me, it should work for Almalinux 9.4 right? We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… [cid:92ffd146-5b65-4e46-a2f8-021ea40371e9] Willie Castillo Linux Systems Administrator, IT Department - Defense & Security CAE USA T. +1-813-885-7481 E. Willie.Castillo(a)caemilusa.com A. 4908 Tampa West Blvd, Tampa, Fl. 33634 cae.com CONFIDENTIALITY NOTICE This e-mail message is intended only for the above named recipient(s) and may contain information that is confidential. If you have received this message in error or are not the named recipient(s), please immediately notify the sender, delete this e-mail message without making a copy and do not disclose or relay this e-mail message to anyone. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, July 18, 2024 2:55 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/18/24 11:12 AM, willie.castillo(a)caemilusa.com wrote: > Mark first let me thank you for your assistance with this. I don't believe I mentioned that this is a fresh/new installation I'm performing on an AlmaLinux 9.4 VM. I have searched everywhere for a solid Mailman installation on AlmaLinux document/process but, I haven't had any luck. I tried following documentation on this site and I only found this https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/dist… . Did you see my post at https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Outlook-2rvyqd2h.png Replaced multipart/alternative part with first alternative.

1 year, 8 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by David Krantz

Hi, I tried psycopg2-binary and a few other rehashes of that. Now I got it working by downloading the source for psycopg2 manually and building it myself, then I installed it into my venv like any other self-built package. https://pypi.org/project/psycopg2/#files I run mod_wsgi in Apache so I thought it should be enough to restart Apache. I am quite convinced that I did that (and for that matter restart the machine at a few points). But I might have been sloppy and reversed the order in the end when I got it running, this process is a bit to manual. I will use another solution when I rebuild the server one day. The problem with rebuilding the server is that I'd have to install a MTA with all its modules, milters, setups and what not, and mailman. To just reinstall on a fresh machine would be easy, the trick is that I want to rebuild some things in a better way which will take me some time. E.g. using a separate wsgi service and a more modern spam filter than Spamassassin. Otherwise it is easy. But my situation now is a bit short on time so if I can postpone that a bit I will. Thanks. // David // David On Tue, Mar 3, 2020 at 10:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/3/20 12:33 PM, David Krantz wrote: > > > > I think that this might be due to some kind of python misfeature where > > compiled code behaves slightly differently to interpreted code, that > > might explain the delay in it working initially before breaking. I > > have no idea of how to solve this. I have tried to uninstall and > > reinstlall psycopg2 in different versions without any luck. > > You need to activate your virtualenv and do > > pip install psycopg2-binary > > it must be psycopg2-binary, not just psycopg2. It's probably best to do > > pip uninstall psycopg2 > > first. > > As far as it working for a while, did you restart your wsgi service > (gunicorn, uwsgi, ??) after upgrading? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/

6 years, 1 month

[MM3-users] Re: How to fix lists with characters errors?

by Helio Loureiro

Hi, Thanks a lot! Nice catch. It was indeed loading as latin-1. Not sure why, but that's a matter to discuss on the Ubuntu mailing list. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 24 Mar 2024 at 01:07, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/23/24 11:56, Helio Loureiro wrote: > > Hi, > > it is python 3.10. Problem is... some mailing lists were created long > ago, > > with python2 something. Most probably 2.5. And the tables on mysql were > > set to latin1. > > > This has nothing to do with the data or the charsets/collation in the > database. The issue is the locale setting in your python is causing > stdout output from the `mailman members` command to be encoded as > `latin1` and at least some user's display name contains a `\u0142` (i.e. > `ł` character. > > > > That I know. Question now is how to fix this. Any suggestion? What is > > the table? I probably can run some script for these specific lists that > > have the failure, import data as latim-1, and update back to the table as > > utf-8. > > That's not the issue. The issue is the Python in your venv has > sys.stdout.encoding set to latin1, probably for locale reasons. You ca > apply this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -17,6 +17,7 @@ > > """The 'members' subcommand.""" > > +import sys > import click > > from mailman.core.i18n import _ > @@ -30,6 +31,9 @@ from zope.component import getUtility > from zope.interface import implementer > > > +sys.stdout.reconfigure(encoding='utf-8') > + > + > def display_members(ctx, mlist, role, regular, digest, > nomail, outfp, email_only, count_only): > # Which type of digest recipients should we display? > ``` > to mailman/commands/cli_members.py to fix the issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

2 years

[MM3-users] Request Entity Too Large

by Christian Stalberg

Now mail sent to mm3 for distribution is not going out, for two different lists. The mailman.log shows this error: Oct 17 21:50:00 2021 (491) ACCEPT: <030601d7c3a0$ee342f20$ca9c8d60$(a)somedomain.com> Oct 17 21:50:04 2021 (488) HyperKitty failure on https://somedomain.net/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> (413) Oct 17 21:50:04 2021 (488) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Oct 17 21:50:04 2021 (488) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Please advise. TY. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, October 16, 2021 11:21 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen > and in the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/

4 years, 5 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Stefan Bauer

Dear Mark, thank you for your time. Here are the lists settings and an example mail attached. Filter content: NO Filter types: EMPTY Pass types: EMPTY Pass extensions: EMPTY Collapse alterantives: YES Convert html to plaintext: NO Thunderbird is showing the mail "correct". Outlook does show the attachments as attachments. Thank you. Stefan Am Mi., 18. Jan. 2023 um 18:02 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/17/23 23:45, Stefan Bauer wrote: > > Dear Users & Developers, > > > > we're running MM3 on Ubuntu 22 and used the venv-installation method. > > Last week we updated via¹ to > > > > Mailman Core-Version GNU Mailman 3.3.8 (Tom Sawyer) > > Mailman Core API-Version 3.1 > > Mailman Core Python-Version 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC > > 11.3.0] > > > > and now mailman attaches mime-attachments to email as text-files. That > > breaks many mails in our environment. > > > > For example: Now we have attachments like > > > > smime.p7s + ATT000001.txt as well as what looks like MM footers > > "mailing list --- test@domain ... To unsubscripbe send an email to ..." > > > > How can we get the "old" processing back? > > I doubt this has anything to do with the upgrade per se. It has to do > with MIME multipart (in this case, signed) messages and how MM > headers/footers are added. The MM 2.1 FAQ article at > <https://wiki.list.org/x/4030707> has some info on this. > > In order to say more, I would need to see the list's settings for > Filter types, Filter extensions, Pass types, Pass extensions, Collapse > alternatives and Convert html to plaintext and the complete MIME > structure of the incoming message. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 2 months

Search results for query "sapiro"