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

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by actionmystique＠gmail.com

Mark Sapiro wrote: > Did you replace <django_project_path>, <user> and <group> with > appropriate values? Yes, I did, otherwise qcluster service would not be able to start in the first place because it needs to be able to read settings.py (with the proper permissions) which is located in the django project. > They should be the same thing. Usually manage.py is just configured to > run the django-admin command for the particular project. You're right, running either command manually is successful and lead to the same result: ``` <django_project_path># python3 manage.py qcluster 10:49:41 [Q] INFO Q Cluster-1130205 starting. 10:49:41 [Q] INFO Process-1:1 ready for work at 1130235 10:49:41 [Q] INFO Process-1:2 ready for work at 1130236 10:49:41 [Q] INFO Process-1:3 ready for work at 1130237 10:49:41 [Q] INFO Process-1:4 ready for work at 1130238 10:49:41 [Q] INFO Process-1:5 monitoring at 1130239 10:49:41 [Q] INFO Process-1 guarding cluster at 1130234 10:49:41 [Q] INFO Q Cluster-1130205 running. 10:49:41 [Q] INFO Process-1:6 pushing tasks at 1130240 ``` If I replace: ``` ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings ``` with: ``` WorkingDirectory=<django_project_path> ExecStart=python3 manage.py qcluster ```` I get the same systemd service issue. If I remove the ``` remote-fs.target``` from ```After=...```, I get the following error: ``` # systemctl daemon-reload # systemctl restart qcluster # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-12-05 11:08:54 CET; 282ms ago Main PID: 1132324 (python3) Tasks: 1 (limit: 9284) Memory: 22.5M CGroup: /system.slice/qcluster.service └─1132324 python3 /usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3/dist-packages/django/utils/log.py", line 76, in configure_logging Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: logging_config_func(logging_settings) Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3.7/logging/config.py", line 800, in dictConfig Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: dictConfigClass(config).configure() Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3.7/logging/config.py", line 571, in configure Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: '%r' % name) from e Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: ValueError: Unable to configure handler 'file' Dec 05 11:08:54 samsung4-ubuntu systemd[1]: qcluster.service: Main process exited, code=exited, status=1/FAILURE Dec 05 11:08:54 samsung4-ubuntu systemd[1]: qcluster.service: Failed with result 'exit-code'. ``` This issue seems related to logging; I configured the following in ```/etc/mailman3/mailman.cfg```: ``` [logging.debian] format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: debug path: mailman.log [logging.root] level: debug [logging.archiver] level: debug [logging.bounce] level: debug [logging.config] level: debug [logging.database] level: debug [logging.debug] level: debug [logging.error] level: debug [logging.fromusenet] level: debug [logging.http] level: debug [logging.locks] level: debug [logging.mischief] level: debug [logging.plugins] level: debug [logging.runner] level: debug [logging.smtp] level: debug [logging.subscribe] level: debug [logging.vette] level: debug ```

5 years, 7 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: > >>> 1. Confirmation emails to Users has wrong domain name (example.com!) > >>> <https://docs.mailman3.org/en/latest/faq.html#id1> > >>> < > >> > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > >>> > >>> > >>> This happens when your reverse (SSL) proxy isn’t setting up the correct > >>> headers when proxying requests. Fix this by setting the right > >>> proxy_set_header directives: > >> ... > >>> How is this supposed to be mitigated in Apache when using WSGI? > >>> > >>> My config: > >>> > >>> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > >>> user=mailman group=mailman > >>> WSGIPythonHome "/usr/local" > >>> WSGIProcessGroup hyperkitty > >> > >> > >> You are using mod_wsgi and not proxying at all, so this is not relevant > >> in your case. > >> > >> Are you actually seeing this issue? If so, it might be related to > >> > >> > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > >> > > > > My issue is related to this, but the documentation referred to is not for > > the faint-hearted! > > I can't make head or tails of it. > > Click on “Domain” in Postorius from the top bar, which should take you to > the Domains page. > > For your domain (in the “Mail Host” column), see the corresponding “Web > Host” column, it should look something like: > > lists.mailman3.org (lists.mailman3.org) > (Edit) > SITE_ID = 1 > Mine looks different, slightly. But there is no example.com at all. [image: Abhilash.png] > > on a new-ish version of Postorius. > I have the newest versions of everything, having installed only yesterday. > > If it doesn’t show the right values and instead shows “example.com” for > you, click on the “Edit” link, which will take > you to a page that will allow you to edit both the values. > It shows the right values, but with "SITE_ID = 2". In my settings_local.py I have SITE_ID = 1. I suppose the example.com is the one tied to SITE_ID = 1 and that is what I have in my settings_local.py. Should I edit my settings_local.py? I am still confused. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 9 months

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by Odhiambo Washington

On Sat, Jan 4, 2025 at 5:30 AM David Newman <dnewman(a)networktest.com> wrote: > > > On 1/3/25 5:44 PM, Mark Sapiro wrote: > > >> Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing > >> about 20-30 entries per day in the Postfix queue where it appears a > >> Gmail user signs up for a mailing list that requires confirmation, and > >> Gmail responds that the user is too busy to handle requests. > >> > >> There are no publicly advertised email lists on this server, and I > >> don't ever see anything in the Mailman logs indicating the user ever > >> tried signing up. > > > > > > This is an attack mail bombing the user. The requests that result in the > > can come via web or email. Mailman's logging of subscribes has been > > missing most events through Mailman 3.3.10. See https://gitlab.com/ > > mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but > > subscribes waiting user confirmation still won't be logged. > > > > However, the message with subject "Please Confirm Your Email Address" > > comes from Django allauth so it isn't actually Mailman sending it but > > rather Django allauth as a result of a request to sign up for a Django > > account at https://mail.example3.com/accounts/signup/. You can probably > > find that request in your web server logs, and you may find the user > > and/or email in the Django admin UI. > > Thanks VERY much for this. > > No such users in the Django UI, but the web server logs have 252 > attempts from 132 unique IPv4 addresses registered to different ISPs > throughout Europe. > > So, even though Mailman support for more detailed logging of sub and > unsub requests would be useful, it likely would not have helped with > attacks from many source IP addresses. > > > > > Since django-mailman3 1.3.6, you can disable these signups by putting > > > > ACCOUNT_ADAPTER = > 'django_mailman3.views.user_adapter.DisableSignupAdapter' > > > > in your Django settings, but then your users won't be able to sign up > > for web accounts. > > I have made this change. As for not having web accounts, this just means > new users cannot sign up to manage their Mailman settings, correct? I > presume existing web accounts will continue to work. > You could also try this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… It really helped in many cases, although with the change you already made, it becomes a useless effort. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Mark, Thank you for your thoughts so far. On 6/23/20 3:22 PM, Mark Sapiro wrote: > I have done further testing. See my comment at > <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. > > You need to set hostname: in mailman.cfg to the actual external IP > address of the Mailman host machine or to a name which resolves to that > IP both internally and externally, and also set that host name/IP in the > MAILMAN_REST_API_URL setting on the Postorius machine. I've done that, but there is no observed change in the browser (still get same 404 error). Specifically, I reset hostname to be a newly-added CNAME of the actual host address, and ensured that the 0.0.0.0 addresses were no longer there. > >> However I then get another issue. From the mailman.log file I now see in >> the last few lines. For clarity I've numbered them like this "{1}": >> >> {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" >> "GNU Mailman REST client v3.3.1" >> {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk >> HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" >> {3} [22/Jun/2020:00:58:24 +0000] "GET >> /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 >> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" >> >> At this point the browser screen reports "Something went wrong" and the >> message "HTTP Error 404: {"title": "404 Not Found"}" > Make the above changes and see if that solves this. If not, let us know > and we'll try to help. A tcpdump now shows the GET of /3.1/domains/mailman-web.ivimey.org/lists&advertised=true&count=0&page=1 directed at mailman-core and the reply being 404 not found. The extract from core's mailman.log is now: [24/Jun/2020:20:41:11 +0000] "GET /3.1/domains/mailman-web.ivimey.org/lists?advertised=true&count=0&page=1 HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" And the entry for postorius in mailmansuite.log: ERROR 2020-06-24 21:41:11,191 13310 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/opt/mailman3/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) [snip] File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 116, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} Note that the mailman-web.ivimey.org address is the newly-added CNAME of greyarea-web1, mailman-core is likewise the CNAME of greyarea-post. There is nothing I can see in the other logs that looks out of the ordinary. I guess this indicates that my earlier wondering if I had something left over from a past install is dispelled, as that name didn't exist until today.

5 years

[MM3-users] Re: hyperkitty_import Unicode Errors

by kdhall＠binghamton.edu

Stephen J Turnbull wrote: > On 2023-05-07 07:39 Mark Sapiro writes: > > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: > > > django.db.utils.OperationalError: (1366, "Incorrect string value: > > '\xE1\x90\xA7\x0A\x0AO...' for column > > mailman3web.hyperkitty_email.content at row 1") > > Is there a known cause for this? > > Almost always nonconforming user clients. You write "frequently", but > I'm > guessing it's maybe 1% or 2% of all the messages, right? I suspect it's > a > particular author or institution using such a client. > > Is it fixed in some release more recent than 0+20180916? > > This is almost surely not something we can fix. Based on the error, > it's in third > party code (Django) that we import. It's possible we could provide a > more explanatory message, but the only thing we can sensibly do is hold > the > message for an admin to edit it by hand. As long as the text in > question and the > Content-Type header aren't too sensitive, we can help with identifying > charset > (often UTF-8 as Mark suggests but why someone would be encoding FINAL > MIDDLE DOT is a mystery to me). > > I'm not sure what's going on here. My first thought is the database is > > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > > column charset definition is utf8 and not utf8mb4, but > > '\xE1\x90\xA7\x0A\x0A' is the 3-byte UTF-8 encoding for CANADIAN > > SYLLABICS FINAL MIDDLE DOT ('\xE1\x90\xA7') followed by two > > newlines. so I'm not sure what the issue is. > > I'm guessing home-made client, possibly Asian or a spammer, which > provides no > content-type header. Even today I see raw 8-bit encoded text without an > encoding > spec from legitimate Japanese and Chinese sources, and of course with > spammers > all bets are off -- they might even do it deliberately to crash filters. I have located an email with a similar error in a V2.1 .mbox file. The post was by a faculty member in my organization using Thunderbird 60.2.1 on a Mac - OSX 10.13. The list was used to correspond with students taking a programming course. The message body is multi-part MIME with two sections: This is a multi-part message in MIME format. --------------4BAB6CD38F4927471D366565 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit and --------------4BAB6CD38F4927471D366565 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit The hexadecimal sting \\xEF\\xBB\\xBF\\xEF\\xBB\\xBF appears one place in each section. I'm not sure exactly what this means. I did check my MariaDB (as Mark hinted) and found that it set for utf8 rather than utf8mb4. I'd be willing to change this, but would I also have to do something to update the Mailman databases since those tables are already created? Thanks. -Dave

2 years, 2 months

[MM3-users] Re: mail loops back to myself

by Florian Sukup

On 6/13/25 01:58, Mark Sapiro wrote: > On 6/12/25 15:05, Florian Sukup wrote: >> >> I always restart mailman3 after changing main.cf > > I asked if you restarted/reloaded Postfix. I would assume that you had, Sorry, I meant postfix which I restart after changing main.cf or master.cf. > but I'm at a loss to understand the issue, unless your > /etc/postfix/master.cf is missing an uncommented entry for lmtp like > ``` > lmtp unix - - y - - lmtp > ``` > I found it there, here is my master.cf: vvvvvvvvvvvvvvvvvvvvvvvvvvvvvv smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth -o smtpd_tls_auth_only=yes -o smtpd_reject_unlisted_recipient=no pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd maildrop unix - n n - - pipe flags=DRXhu user=vmail argv=/usr/bin/maildrop -d ${recipient} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Is the last line a problem? It seems to be from mailman2. Is there a possibility to debug in more detail? To find out when and where it takes the wrong turn? The system running has grown over many years and even if the hardware changed the configuration was kept. So there may a flaw outside the postfix/mailman configuration which causes the error, ie. network configuration. Another thing I can do is to upgrade from bullseye to bookworm. Which I haven't done yet because I was with mailman2/sendmail. That's the reason to change to mailman3/postfix. Since, mailman2 doesn't work anymore I could do it and hope for a miracle ... . This would mean postfix 3.5.25 -> 3.7.11 and mailman3 3.3.3 -> 3.3.8 . That's more an act of desperation. Thanks for your help, Florian.

3 weeks, 6 days

[MM3-users] Re: Docker, Mailman 3, templates and list user accounts

by Abhilash Raj

Hi, On Mon, Aug 7, 2017, at 06:06 AM, Henrik Rasmussen wrote: > I used Docker to installed Mailman 3. > > The top header of the web interface says "Example.Com" while linking to > the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a > post[1], Mark Sapiro referred to the template system in Mailman 3 by > pointing out that "a custom template can be put in > var/templates/site/en/welcome.txt or > var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> > or > var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> > where var is Mailman's configured var_dir". I believe this refers to the > mail templates. Yes, these are email templates. > > 1) Where do I change the similar template system, for the web > interface, without breaking a laver upgrade? I am not sure if you can do that for now without tinkering with the source code. > 2) How do I change the site name in the top of the web interface on > Mailman 3 to my subside and ? When you deploy the web interface, the domain it is being served from is used at the top of the web interface. It is defined by SITE_ID in the settings.py file for Django (or settings_local.py if you are using the container images). The default value is set to 1 and points to example.com. In the newer versions of Container Images, the SERVE_FROM_DOMAIN environment variable's value will replace the `example.com` domain and you will be able to see that instead of example.com. For now, you should just login into the admin interface at /admin/ and just create a new Site model. And then use the id of that Site in your Django's settings.py. Each domain that you add gets their own id and depending on which domain you are serving from, you can set the SITE_ID in the settings. Mailman 3 supports multiple domains at the same time. > [1] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > The Mailman command in Mailman Core doesn't seem to have a command for > listing the accounts users have created by using Sign up in the web > interface, so I believe that accounts may be created in the webinterface. The Core and and Web frontend handle users separately. Ideally, a user shouldn't have to worry about the Core ever and only interact with the Web Interface. > Is there similar commands for the web interface like the mailman commands > for the Mailman core? You can interact with the Django shell to get almost any internal data structure. But you can go to the admin interface at /admin/ and you will find the list of users there along with a whole lot of other information. > > Regards, Henrik Rasmussen > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 11 months

[MM3-users] The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters.

by Henrik Rasmussen

Hi Mark. This was originally from another thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, but as it isn't related to the problem in the thread, I'll split it in another thread. On 09/29/2017 05:46 AM Mark Sapiro wrote: >> In addition, the log contains other trace backs that might or might not associate to this problem: >> >> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> Sep 24 21:11:28 2017 (34) Traceback (most recent call last): >> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose >> self._func(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver >> refused = agent.deliver(mlist, msg, msgdata) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver >> mlist, msg, msgdata, recipients) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients >> sender, sorted(recipients), msg.as_string()) >> File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail >> results = self._connection.sendmail(envsender, recipients, msgtext) >> File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail >> msg = _fix_eols(msg).encode('ascii') >> UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 > > > This may be a bug. The msgtext argument in > 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed > to be a string containing only ascii characters. I'm interested in > what's in Mailman's > var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. > You may be able to print the contents with Mailman's > > bin/mailman queue > var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck > > There shouldn't be raw unicodes like \udcea in the text of the message, > but we should defend against that anyway. [root@lstapp01pl ~]# docker exec -it mailman-core mailman qfile var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.6/site-packages/mailman/bin/mailman.py", line 100, in main args.func(args) File "/usr/local/lib/python3.6/site-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/local/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/local/lib/python3.6/pprint.py", line 176, in _format stream.write(rep) UnicodeEncodeError: 'utf-8' codec can't encode character '\udcea' in position 3025: surrogates not allowed -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 9 months

[MM3-users] error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Guillermo Hernandez (Oldno7)

I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I've just upgrade mailman 3 installation following Mr. Sapiro advice: > did a > > pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient > mailman-hyperkitty postorius > > I did a "python3 manage.py migrate" after, too. > > And all seemed to run well. > > All the lists showed in postorius via web, but when I try to accesss > into one of them the browser shows an error. > > In the log you can see: > > *-*-*-*-*-*-* > > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 86, in _get > raise KeyError(key) > KeyError: 'get_requests_count' > > ... (And after all the traceback lines) > > AttributeError: 'MailingList' object has no attribute > 'get_requests_count' > > *-*-*-*-*-*-*-* > > The lists seem to be distributing messeages well.. but I cannot acces > via web administration (django/postorius) > > Can anyone point me in the right direction to solve this, please? > > _______________________________________________ > 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: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hi Mark, On Sat, Jul 09, 2022 at 09:06:55AM -0700, Mark Sapiro wrote: > I can't explain what happened in your case. It seems that somehow the > original post was delivered to the -bounces address and parsed by one of the > heuristic recognizers (probably simplematch), but how could that happen? This seems to have been the DSN that caused that bounce score (Exim mainlog): 2022-07-09 12:46:13 1oA9qf-007qVv-2R <= <> R=1oA9qc-007qOx-0T U=Debian-exim P=local S=44941 2022-07-09 12:46:13 1oA9qf-007qVv-2R => users-bounces(a)mailman.bitfolk.com R=mailman3_router T=mailman3_transport H=127.0.0.1 [127.0.0.1] C="250 Ok" 2022-07-09 12:46:13 1oA9qf-007qVv-2R Completed The P=local is a local submission, so I think that was generated by Mailman in response to the SMTP reject. In the smtp.log, mail from list poster came in: Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) handling connection Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) Data: b'LHLO lists0.bitfolk.com' Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) Data: b'MAIL FROM:<xxxxx(a)xxxxx.com>' Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) sender: xxxxx(a)xxxxx.com Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) Data: b'RCPT TO:<users(a)mailman.bitfolk.com>' Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) recip: users(a)mailman.bitfolk.com Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) Data: b'DATA' Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) Data: b'QUIT' Jul 09 12:46:04 2022 (71509) ('127.0.0.1', 45530) connection lost Jul 09 12:46:04 2022 (71509) Connection lost during _handle_client() Over in Exim's mainlog I then see that delivered out to list members. One of them rejects it at SMTP time, which I think causes this: Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() …and I think that bounce message somehow incremented the bounce score for andy(a)bitfolk.com even though that address was only present in the original post's Cc: and body. Is there a good way to further debug this? Maybe by being able to see the full content of the DSNs that Mailman generates? I think I've seen this before in the last couple of weeks so I'm sure it'll crop up again soon. I've seen it mention about bounce score for users-leave before, but I only really paid attention today when it also listed my own address. Thanks, Andy

3 years

Search results for query "sapiro"