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

[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

8 years, 11 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/ >

5 years, 7 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

4 years, 2 months

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 7:26 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 08:09, Odhiambo Washington wrote: > > > > [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ > kictanet.lists.kictanet.or.ke/en/ > > total 48 > > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. > > -rw------- 1 mailman mailman 615 Jan 17 13:57 > domain:admin:notice:new-list.txt > > This template is used in a domain context. It will never be accessed > here. It needs to be in /opt/mailman/mm/var/templates/site/en/ or > /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ The last time I referred to the link, I deliberately duplicated the <LC> folder in two locations: [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt Yet, it is NOT being picked. So definitely something is wrong somewhere. > > -rw------- 1 mailman mailman 341 Jan 17 13:54 > list:admin:action:post.txt > > -rw------- 1 mailman mailman 158 Dec 17 13:32 > list:member:digest:footer.txt > > -rw------- 1 mailman mailman 452 Jan 17 13:54 > list:member:digest:masthead.txt > > -rw------- 1 mailman mailman 137 Jan 17 13:55 > list:member:generic:footer.txt > > The generic footer is used for both regular messages and digests if > there isn't a specific regular or digest footer. In this case, you have > both so the generic footer won't ever be used. > Thank you for clarifying that. I actually will delete the generic footer in this case because I don't need it. > > -rw------- 1 mailman mailman 1219 Dec 8 15:12 > list:member:regular:footer.txt > > -rw------- 1 mailman mailman 944 Jan 17 15:50 > list:user:action:subscribe.txt > > -rw------- 1 mailman mailman 247 Jan 17 13:56 > list:user:notice:post.txt > > -rw------- 1 mailman mailman 802 Jan 17 13:56 > list:user:notice:probe.txt > > -rw------- 1 mailman mailman 639 Jan 17 13:57 > list:user:notice:welcome.txt > > Are the other templates such as list:member:regular:footer.txt used? > I do see that in posts to the list, but I believe that is perhaps only working because the list had that footer when it was imported from MM2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > On 13/2/21 20:00, Mark Sapiro wrote: > > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > But... here is a thing that I can not understand: If the source (the > > > .po > > > file) is from november 7th, it doesn't matter how many times you > > > recompile it: the result will be the same. > > Correct, but the point is if you download the latest > > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 > > file > > in the distribution, you will find they are identical, so it it appears > > that the weblate translation hasn't changed since that time. > > > > If there are issues in this mailman.po, they exist in weblate too and > > need to be fixed there. > > That clarifies all. Thanks. As I said in my previous message, I'll wait > for the next upgrade and hopingly the translations done after 7h of > november (by others and me) will be there. I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version. Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-) > > Also note that the translations on weblate only affect strings in the > > core code. The Mailman core templates are not currently translated in > > weblate and there are currently no Spanish language templates. One > > would > > need to create Spanish translations of all the templates in > > < > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en > > > > > and submit a merge request to add them to a mailman/templates/es/ > > directory. > > > I will make the template translations locally, test them, and then, if > they are yet lacking in the main repo, follow your suggestion. I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ... -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 7 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Abhilash Raj

> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html You seem to have landed on a very old version of the docs that I didn’t unfortunately knew was even available. I have disabled that page now. The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > > I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > How could I check, that the setting is used!? > > But maybe some additional information: > - I use the Debian installation on a stable buster, so mailman is version 3.2.1 > - I use apache2 as my web-server and use the given alias-conf-file > - Python is version 3.7.3 > - Postorius is Version 1.2.4 > - HyperKitty is version 1.2.2 > > -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de > -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above > -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de > -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de > -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains > > What do I miss? Or where to investigate? > > Thank you in advance, best regards. > > By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to individual projects. The second one is the individual Mailman Core project. Historically, Core was the only project and hence claims the name “mailman” in most places. > > Am 18.03.21 um 21:52 schrieb Mark Sapiro: >> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >> Set FILTER_VHOST = True in your settings_local.py or where ever you put >> your site Django settings. > _______________________________________________ > 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)

5 years, 5 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Allan Hansen

I asked the poster of one message what he had done. Apparently, he had put the list address (just one list, according to him) in the Bcc: field. The message was then held for moderator approval and, when approved, sent out without a body. Another message was stopped because it did not have a subject field. Again, it was approved and then sent out without a body. From what I can see (the hold messages are sent to me as well), the messages were stripped after approval, as the approval messages have the message bodies. I will try to ask my moderators not to approve messages that are held by the server and instead reply to the senders and discard the messages. Yours, Allan P.S.: I had hoped that the upgrade would now allow the moderators to see the list of members, as that is enabled for each of my lists. It's now our top issue, with the change-of-address issue made easier. If moderators should not see the members list then maybe a third option on the menu should be 'Only list owners.' But it would be good for the moderators to see the list, as well as being able to subscribe and unsubscribe members. On 12/5/22, 9:39 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/5/22 08:56, Allan Hansen wrote: > Thank you, Mark, as always. > > We upgraded to the latest versions: > > Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] > > Also, I don't have any umbrella lists. I need more information about this. As far as I know, this can only happen with messages that are cross posted to multiple lists and held for moderator approval on more than one list. This should have been fixed in Mailman 3.3.6 by <https://gitlab.com/mailman/mailman/-/merge_requests/932>. This should never happen with a post that is delivered to members without being held. Also, I think when this happens to a delivered post, the post in the archive will also have the content lost message. I would like to get as much information as possible about the circumstances when this happens. In particular, was the post held for moderation, was it posted to multiple lists, for how many lists was the content lost. Also, it may help to see the full raw message with the content lost notice. (If there are privacy concerns you can send these to me off list) -- 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: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/33OOQ4DNXTJUNT65CD2KHMOSCAIMRSLL/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: members.jpg

3 years, 9 months

[MM3-users] Re: signup / registration error - permissions and cert chains

by Victoriano Giralt

El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: > I'd like for regular (non-admin) list subscribers to be able to manage > their subscription preferences and view list archives. That's a good way to go :-) My response is more of a (very) old sysadmin and Django user (since 2008) hunch that a proper one based on code and documentation review, but I've been trying to contribute several times and always (super) Mark Sapiro beats me :-) > If I'm reading the error correctly, this is related to an inability to > verify the cert chain. The /etc/mailman3/settings.py file points to the > same cert and key files used by Nginx, Postfix, and Dovecot. You are right in your diagnose but not in your interpretation (see my comment below inside the traceback). It is certificate related, but not for server TLS, but for CLIENT authentication. > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = 'dnewman(a)networktest.com' > EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' > EMAIL_USE_TLS = 'True' > EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' > EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' All these settings above are used for SENDING messages and, if I'm not mistaken, the SSL key and cert are used for authenticating the user sending the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. I've been configuring SMTP servers since 1990 and my mail servers just accept mail form localhost, if they are broken into, the user and password have already been exposed :-) > But this might only be for email, not Postorius/Django. You are right (if I also am) > What additional configuration is needed to allow regular users to create > and manage their own accounts? I'd say that is more what is not needed (the SMTP TLS authentication) I'll remove the "noise". These are the tell tale lines: > "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt > p.py", line 67, in open > self.connection.starttls(keyfile=self.ssl_keyfile, > certfile=self.ssl_certfile) The SMTP Django backend is trying to connect to the mail server to send the Mailman account confirmation message and failing, probably because the user Django runs as cannot open the private key (which is a very sensible thing if that private key is the one used for the web facing TLS certificate, I can tell you how bad in private or search for my name, wasd, apache and VMS ;-)) That certificate is not needed for sending email from Django, and, as I said, not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on port 25 is not even recommended practice. Happy, healthy, safe and well ventilated New Year to all. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 8 months

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Odhiambo Washington

On Mon, Aug 4, 2025 at 4:53 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > > I wonder what this means and whether it's fatal. > > > > How do I fix it? > > > > ``` > > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) > ... > > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > > returned more than one EmailAddress -- it returned 2!* > > It appears you created a new list, and that list' owner email address > has two Django user records with emails differing only in case. I did not create a new list actually. I was working on an existing list. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you > can just go to the Django web UI and delete the mixed case user. > The script did not work for me as-is because I use MySQL on this site. > > I suspect it's something to do with my action yesterday while attempting > to > > reply to a thread from HyperKitty. > > Possibly, if hyperkitty was looking at a mixed case email address that > it didn't recognize as a list member and subscribed it. > Happens to not have been the case either. No mixed case address. > > The superuser account uses my address - odhiambo at gmail dot com.I am > also > > the listowner for most lists. > > I tried unsuccessfully to create an account on Postorious using the same > > email address. > > I kept getting sent links to verify the account, over and over. > > Finally, I was able to verify the account, but cannot login with it. > > This too is probably because there are two accounts with email addresses > differing only in case. > With assistance from ChatGpt, I went digging into the DB and what I found (as I expected) turned out to be slightly different: [email slightly obfuscated!] ``` MariaDB [mailmansuite]> SELECT id, user_id, email, verified, `primary` FROM account_emailaddress WHERE LOWER(email) = 'odhiambo__gmail.com'; +------+---------+--------------------+----------+---------+ | id | user_id | email | verified | primary | +------+---------+--------------------+----------+---------+ | 1844 | 1823 | odhiambo__gmail.com | 1 | 0 | | 2548 | 4 | odhiambo__gmail.com | 0 | 0 | +------+---------+--------------------+----------+---------+ 2 rows in set (0.002 sec) ``` MariaDB [mailmansuite]> SELECT id, username, email, is_active FROM auth_user WHERE id IN (SELECT user_id FROM account_emailaddress WHERE LOWER(email) = 'odhiambo__gmail.com' ); +------+----------+-------------------------+-----------+ | id | username | email | is_active | +------+----------+-------------------------+-----------+ | 4 | odhiambo | odhiambo__gmail.com | 1 | | 1823 | admin | odhiambo__kictanet.or.ke | 1 | +------+----------+-------------------------+-----------+ 2 rows in set (0.011 sec) So I resolved it by deleting the duplicate: MariaDB [mailmansuite]> DELETE FROM account_emailaddress WHERE id = 1844; Now I need to find a way for me to subscribe my email address as an ordinary user for starters. This is refusing. -- 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]

1 year

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 25 jan 2024, om 14:16 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 24 jan 2024, om 13:46 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >> Op 24 jan 2024, om 12:24 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >>> Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >>>> >>>> On 1/23/24 05:49, Marco van Tol wrote: >>>>> Small unfortunate twist, this leads to: >>>>> --- >>>>> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >>>>> --- >>>>> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? >>>> >>>> This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. >>>> There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. >>>> >>>> I use the one from the PR, but it requires a substitution `s/force_text/str/`. >>> >>> Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? >>> >>> I found a comment on this topic regarding django-4 where they advice to use force_str. >>> https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… >> >> Hm, never mind, sorry. I now see the current file already has str() rather than force_text() in it. > > Okay, so, I got a bit further, but something still gets stuck. > > Here’s what I did. > Keep in mind I’m using containers that are built from some CI/CD pipeline, so I updated the pipeline to apply the patch attached to this email to `/usr/lib/python3.11/site-packages/xapian_backend.py`. > > Before I had 2 list servers with the “Term too long” issue, 1 got resolved by this, and the other did not. > I opened a shell in the newly deployed container to confirm the patch was applied in it. > > The other attachment to this email is a copy/paste from the full error from `./manage.py rebuild_index`. > > Is there something else special in the email that makes it choke that evades the xapian patch? > > Thank you very much in advance! I tried to change to ‘hash’, but the code in that bit of the function has not been tested enough. For example `hole = sha224(hole.encode('utf8')).hexdigest()` comes back with that the bytes object hole does not have an encode() method. When I change it to `hole = sha224(hole).hexdigest()`, the following error is: text = text[:match.start()] + hole + text[match.end():] TypeError: can't concat str to bytes The ‘hash’ part of that function needs some debugging. Marco

2 years, 7 months

Search results for query "sapiro"