Search results for "Postorius" - Mailman-users

Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/29/2017 02:10 AM, Henrik Rasmussen wrote: > Thanks, Mark. > > @Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? > https://gitlab.com/mailman/mailman/issues/256 @Henrik, Contrary to what I said earlier, your issue is not exactly #256. #256 is fixed in Mailman to the extent that the defective message no longer breaks Postorius or causes exceptions in REST, but the underlying issue causing the "KeyError: 'content-transfer-encoding'" exception is not in Mailman. It's in the Python email package. The issue that needs to be fixed for that is <https://bugs.python.org/issue27321>. The bottom line is at this point, <https://bugs.python.org/issue27321> no longer affects Postorius, but it still affects message delivery. I have opened <https://gitlab.com/mailman/mailman/issues/406> about defending against that and also the UnicodeEncodeError you included in your OP. > @Mark, > > Mark Sapiro wrote: >>> >>> bin/mailman queue >>> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck > > Isn't this a Mailman 2 command? What is the Mailman 3 equivalent? No. 'bin/mailman queue' is the Mailman 3 command. The Mailman 2 command is 'bin/show_qfiles'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Re: bounce handling in mm3 available?

by Mark Sapiro

On 1/24/22 05:20, Stefan Bauer wrote: > Hi, > > what happens with bounce-mails that are processed by mailmans postfix > instance? What Mailman core version? Prior to 3.3.1, bounce events were recorded in the bounceevent table but not otherwise processed. Subsequent to that, they are scored if recognized and what notices are sent depends on list settings. > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > to=<company-newsletter-bounces(a)lists.company.tld>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > dsn=2.0.0, status=sent (250 Ok) > > But the list-owner does not get any notification, nor do i see any > bounce-information in the pistorious-gui. What are you expecting to see in Postorius? All you can see is if a member's delivery status is Disabled by Bounces. Things like Bounce score are not available in Postorius. What notices are sent depends on the settings in the Bounce Processing section in Postorius. For example, if your message logged by postfix was spam to the <company-newsletter-bounces(a)lists.company.tld> address that is not recognized as a DSN and `Forward unrecognized bounces` is Discard, the message will be silently discarded. Also, if that message was a non-fatal, message-delayed type of DSN, it will be ignored. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/8/21 10:50 PM, Kimmo L wrote: > Okay, i will try to explain the overall situation as far as I can understand: > Its a CentOS 7 host without any virtualenv. Mailman_suite_project git repo has been cloned to the host and after that some packages have been installed with the help of pip: > > # pip2 install django==1.10 postorius==1.1.0 hyperkitty whoosh xapian-haystack > # pip3.5 install mailman mailman-hyperkitty For current Mailman the minimum Python version is 3.6 and all components are Python 3. Nothing is Python 2. You should be installing the latest versions of everything. Do not install Django explicitly with pip. It will be installed as a dependency of Postorius and Hyperkitty. If you are going to use Xapian, you don't need whoosh. Also, you need to install Xapian itself, either from source or with yum if there is a yum package. > And now Im in trouble, what would be the right steps from here. I'm not that competent to use pip, so im confused - should i install python36 packages and try to upgrade pip2 and pip3 mailman packages after that or should i install these pip2 packages with pip3 and remove from pip2 list? There are no pip2 packages. Everything is Python >=3.6. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark Sapiro

On 5/8/23 09:52, Mark London via Mailman-users wrote: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. Many users, e.g. Jens Günther whose replied to this thread, have made custom templates to do this. > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. See https://gitlab.com/mailman/mailman/-/issues/901 and https://gitlab.com/mailman/mailman/-/issues/1055 Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for some documentation of templates, but note that you don't need to set URI's via REST, You can place list specific templates in Mailman's var/templates/lists/<list-id>/<lc>/ directory, domain specific templates in var/templates/domains/<domain-name>/<lc>/ and sitewide templates in var/templates/domain/site/<lc>/ or you can create list and/or domain specific templates via Postorius but see https://gitlab.com/mailman/postorius/-/issues/366 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: DMARC Mitigation Wrap

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > > MM3 has the option to wrap the main message with a wrap_message. It appears, however, that MM3 is oblivious to all my attempts to include whitespace, in this case a <cr>. When the enclosed message is automatically unwrapped by the receiving client, this causes the wrap and enclosed message's From: header to butt up against each other, which is rather ugly. I tried many tricks, but none worked, such as, <cr>, SPACE+, TAB+, <BLANKLINE>, SHIFT-RETURN, two RETURNS, \r\n and UTF-8 codes. They all either got ignored or copied as entered to the output message. Here’s an example. I just want to put a divider after the wrap_message main text. > > The From address of this message has been replaced with the list > address, while the From name has 'via list' appended. Please be > careful when using 'via list' addresses later for new emails, as they > will be sent to the whole list.\r\n -------------------------- > ----------------------------------------------------------------------\r\n > From: Allan Hansen <allan_hansen(a)icloud.com <mailto:allan_hansen@icloud.com>> > Subject: [Testlist] wrap with divider and BLANKLINE > > Which coding option am I missing? I have searched for one online. I assume you are entering your text in Postorius in the DMARC wrapped message text box. There are a number of things going on here. Postorius is wrapping and filling the text and stripping trailing whitespace. If you want more whitespace, I suggest following your text with one or more empty lines and a single dot as in The From address of this message has been replaced with the list address, while the From name has 'via list' appended. Please be careful when using 'via list' addresses later for new emails, as they will be sent to the whole list. ------------------------------------------------------------------- . In the above, the blank lines before and after the line of dashes will be preserved as will the final dot which should be unobtrusive enough. More importantly, the rendering of the received message is up to your mail client. Your's apparently begins the wrapped message immediately after the wrapper's text, but many will not do that. Unless you actually view the received message in every mail client used by your user's, you won't know what they actually see. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 11/2/21 20:15, Mark Sapiro wrote: > > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > I contributed in january to translate to spanish all the items > > > left in > > > Mailman Core, Django-mailman, HyperKitty and Postorius via > > > Weblate. I > > > thought they will be used in the next upgrade, but I cannot see > > > any > > > improvement and there are many words untranslated. > > > > The Spanish translations for Mailman core and HyperKitty are > > currently > > completely up to date with weblate. django-mailman3 differs in one > > string that was translated on Feb 10 and hasn't yet been merged. > > Postorius also differs in a few places from the Feb 10 version that > > hasn't yet been merged. > > Ok. Thanks for checking it. I put my little contribution in Weblate > and I like that it could be used by anyone. Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-) > I tried to run this using the same command as I did for the > "collectstatic" (that solved all my previous problems for the > upgrade) > and "migrate" runs but it shows me an error: > > su -m mailman3 -c "python3 manage.py compilemessages" > CommandError: This script should be run from the Django Git checkout > or your project or app tree, or with the settings module specified. I got this very same error, and was also confused, as manage.py runs at the project level, not application level. > I'm lost. Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-) Confused-with-translations-ly, Victoriano. -- 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, 9 months

Mailman3 is wrongly display name a list member

by Stephen J. Turnbull

Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

3 years, 10 months

Re: mail host choices when creating a new list

by Andrew Hodder

Abhilash, I'm not sure what you're referring to, there's no "web hosts" in the admin panel and I already added the "mail hosts" there (of the four added, only the first one shows up in the postorius drop down). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi Andrew, > > On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: > > Hi! > > > > So, I'm trying to create a new list and pick one of the other mail > > domains > > we have configured (from the django admin panel), yet in the "Create New > > List" page in postorius, I see only a single option (the first domain > > we'd > > added/set as the default) in the drop-down under "Mail Host". Am I > > missing > > somewhere else I need to add alternative mail domains to? Thanks in > > advance! > > Yes, you can add new 'Web Hosts' from the Django's Admin console > (admin/django_mailman3/maildomain/). Note that you need to be a > superuser to do this. > > > -- > Abhilash Raj > maxking(a)asynchronous.in >

8 years, 1 month

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/22/21 5:47 PM, dancab(a)caltech.edu wrote: > I've imported a list from Mailman2 and had the owner send a message for testing purposes. > > His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. > > However if we attempt to view the message in Postorius web UI then an error is thrown. Can you see the message in the held messages view and only get the error when you click the message, or can you not see the held messages view at all? Is it only this list that has an issue? Can you visit other pages for this list? > In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." > > But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. > > [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages > > Does "Service Unavailable" mean I'm missing something in the configuration? Possibly, but I don't think so. What is the Traceback from the message Django sends to the server admin? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/22 00:00, Odhiambo Washington wrote: > > > > These are my files: > > 1. urls.py > > <CUT > > > from django.conf.urls import include > > from django.urls import re_path > > from django.contrib import admin > > from django.urls import reverse_lazy > > from django.views.generic import RedirectView > > > > urlpatterns = [ > > re_path(r'^$', RedirectView.as_view( > > url=reverse_lazy('list_index'), > > permanent=True)), > > re_path(r'^postorius/', include('postorius.urls')), > > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > > re_path(r'', include('django_mailman3.urls')), > > re_path(r'^accounts/', include('allauth.urls')), > > # Django admin > > re_path(r'^admin/', admin.site.urls), > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > ] > > </CUT> > > > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, but > having both is OK. > That urls.py was picked from https://wiki.list.org/DOC/Mailman%203%20installation%20experience. Maybe that page needs some edits/revision now? > 2. apache.conf > > <CUT> > > ... > > Alias /static "/opt/mailman/mm/static" > > <Directory "/opt/mailman/mm/static"> > > Require all granted > > </Directory> > > # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py > > # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py > > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > > > This will send every http request to mod_wsgi except for requests to > /static. This is OK if there are no other web sites on this server and > the only http requests are for Django related things. > This is just a virtual host. There are other websites on the server. ... > > I have tested with creating all those commented out aliases and that > ended > > up still giving me /mailman3/mailman3/* which I did not > > like, although everything appeared to work. > > I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" > > and now when I type https://mm3-lists.kictanet.or.ke I end > > up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course > something > > has appended "/mailman3" > > So this has resulted in all URLs having /mailman3/ appended, except for > the > > /archives link. > > > How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > I have uncommented the line "WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py", I don't see any definition for it in urls.py as well. Perhaps that's the issue? When I uncomment /user-profile, I end up with an ugly URL: https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ So instead of aliasing the /user-profile, I have decided to add another definition to urls.py: re_path(r'^user-profile/', include('allauth.urls')), Which I think gives me a cleaner URL: https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ I also had to alias /accounts, which then brings me to: https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I believe is fine because one gets the option to either login or signup. And I think that "/account" and "/user-profile" are synonymous. > Now my question is about what could be adding the /mailman3. Is it > possible > > that I installed something out of the ordinary? > > > It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > (I now use gunicorn on all the sites I manage), but when I did I think I > had > WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > > and all the URLs were like https://example.com/mm3/mailman3/..., > https://example.com/mm3/archives/..., etc. > I already had gunicorn working too, but I just need to also figure out this mod_wsgi. I will stop bothering about the /mailman3 being appended, as long as it serves the required purpose. Thank you for all the help. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

Mailman-users search results for query "Postorius"