Search results for "Postorius" - Mailman-users

Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

I have struggled for hours but cannot seem to figure it out. After registering new user accounts in Postorius, the "confirm your address" emails don't get sent via SMTP (my MTA does not even log connection attempts), but their content is displayed in uwsgi-error.log. I think I disabled developer mode in Core and Postorius: $ mailman conf | grep devmode [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s $ grep ^DEBUG settings.py DEBUG = False Users can subscribe via list-join(a)domain.tld, including confirmations. Account registration using the WebUI works as well, it's just the emails that don't get sent. What am I missing, I wonder? -Ralph

6 years, 7 months

Re: Github auth deprecated API

by Mark Sapiro

On 5/14/20 8:11 AM, Quanah Gibson-Mount wrote: > The version of mailman3 I'm running apparently uses a deprecated API for > GitHub authentication. Does anyone know if this has been fixed? I > couldn't find an issue for it on the postorius issue tracker. It's not in the Postorius tracker because it's not a Postorius issue. The issue is with django-allauth in the current 0.41.0 release. It is fixed in the django-allauth GitHub repository by <https://github.com/pennersr/django-allauth/pull/2458> You can apply the patch from that PR to your django-allauth installation to fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Mailman 3 Core user assistance

by Stephen J. Turnbull

Tony Deshields writes: > I currently have a docker mailman stack that utilizes Django LDAP > backend for authentication. I have my users attributes mapped as > you see below in my settings.py file. Whenever a user logs into > postorius with their 'uid', mailman-core uses their 'uid' as their > email address instead of the 'email' attribute. I don't think Mailman core is doing that, Mailman core just takes the token passed by Postorius verbatim. It's the Django LDAP auth module. You need to have that module pass the email value as the user identity token to Postorius rather than uid. There may be a way to configure that in settings.py. Check the module docs.

2 years, 10 months

Re: list footer questions

by Mohsen Masoudfar

Hi, Thanks again for your help. When I check the postorius version, it says 1.1.2-3: [509]# apt list | grep postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] It is on Ubuntu18.04 and has been installed with Ubuntu package Mailman-full. There is no update available yet. So it looks like I cannot use the easy way of modifying the templates. Question: Is there a way to achieve the same by updating the code? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 8, 2020 4:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list footer questions [EXTERNAL EMAIL] On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - > listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.list…> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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…

6 years, 5 months

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

Hi Mark, On 07.05.23 01:31, Mark Sapiro wrote: > On 5/6/23 16:02, volkmar(a)grote-family.com wrote: >> >> My urls.py: >>> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py >>> from django.contrib import admin >>> from django.urls import include, reverse_lazy, re_path >>> 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), >>> ] > > > We and the various docs are inconsistent about 'postorius' vs > 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these > > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > > to your urlpatterns list in urls.py to cover both variants. > thanks for the quick reply. I am one step closer to a solution, "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. I get the functionality, but it looks ugly w/o any graphics, for which I get yet another, slightly similar, error message: > > > Page not found (404) > > Request Method: GET > Request URL: > http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png > > Using the URLconf defined in |urls|, Django tried these URL patterns, > in this order: > > 1. ^$ > 2. ^mailman3/ > 3. ^archives/ > 4. ^postorius/ > 5. ^hyperkitty/ > 6. ^user-profile/delete$ [name='mm_user_account_delete'] > 7. ^user-profile/$ [name='mm_user_profile'] > 8. ^accounts/ > 9. ^admin/ > > The current path, |static/postorius/img/mailman_logo_small_trans.png|, > didn’t match any of these. > The file exists, world readable: > mailman@me:/opt/mailman/mm$ find . -name mailman_logo_small_trans.png -ls > 124610 2 -rw-r--r-- 1 mailman mailman 1163 May 6 12:18 > ./venv/lib/python3.9/site-packages/postorius/static/postorius/img/mailman_logo_small_trans.png > 125831 2 -rw-r--r-- 1 mailman mailman 1163 May 6 12:19 > ./static/postorius/img/mailman_logo_small_trans.png Q&D MM3 configuration check: > mailman@me:/opt/mailman/mm$ grep -i static *cfg *py|grep -v "#" > settings_local.py: 'django.contrib.staticfiles', > settings.py: 'django.contrib.staticfiles', > settings.py: 'django.template.context_processors.static', > settings.py:STATIC_ROOT = os.path.join(BASE_DIR, 'static') > settings.py:STATIC_URL = '/static/' > settings.py:STATICFILES_DIRS = ( > settings.py:STATICFILES_FINDERS = ( > settings.py: 'django.contrib.staticfiles.finders.FileSystemFinder', > settings.py: 'django.contrib.staticfiles.finders.AppDirectoriesFinder', Nginx, /etc/nginx/conf.d/me.domain.de.conf > server { > listen 80; > listen [::]:80; > > server_name me.domain.de; > ... > location /static/ { > alias /opt/mailman/mm/static/; > } Again, many thanks in advance for any clue Volkmar

3 years, 6 months

Re: postorius / adjusted settings menu

by Abhilash Raj

On Wed, Mar 3, 2021, at 9:59 AM, Andreas Barth wrote: > Hi together, > > I want to adjust the settings menu to reduce to the options really > needed. > > The easiest way would be to edit src/postorius/views/list* but I don't > think that's a good idea. There is an easier way actually, you can update the forms[1] that generate those views to remove the fields you don't want to be presented. [1]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… For example, see this form for creating a new list [2]. The layout defines the fields that show up and also the order that they show up in. [2]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/list… So, you can add those layout to all the list settings form, each one controlled with a setting and choose the fields and their order. You won't be able to move the fields around in different groups though. > So what comes to my mind is to have some variable in the configuration > that contains the menu items and - if set - the submenus. > > E.g. the following: > { > 'list_identity': ['!gateway_to_mail', '!gateway_to_news', > '!linked_newsgroup', '!newsgroup_moderation', > '!nntp_prefix_subject_too' ], > 'automatic_responses', > 'alter_messages', > 'dmarc_mitigations', > 'digest', > 'message_acceptance', > 'archiving', > 'subscription_policy', > 'bounce_processing' > } > > would express: default menu and just remove the mentioned items. > > Of course, something like ['advertised', 'description', 'info', > 'display_name', 'subject_prefix'] would work as well. > > > Resorting should also be possible, so something like > { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } > would give a very small list of items to select from. > > > > What do you think about the idea? > > > Andi > _______________________________________________ > 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, 8 months

Re: Several Postorius errors over the weekend

by Mark Sapiro

On 8/14/24 02:59, Andrew Hodgson wrote: > Hi. > > I've had several Postorius error messages which have resulted in an email. Is this someone up to mischief or have I missed a configuration somewhere? We had several of these over a short period and nothing since then which makes me think someone was running a script on the endpoint, but would be interested in confirmation from those that know better. > > Thanks. > Andrew. > > Internal Server Error: /accounts/login/ > > TemplateDoesNotExist at /accounts/login/ 429.html > > Request Method: HEAD > Request URL: http://lists.hodgsonfamily.org/accounts/login/?next=%2F%61%63%63%6F%75%6E%7… Script kiddies at work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Can I go back to any previous version which is felt as working fine ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 11:43 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Mark Sapiro writes: > > > I think the issue is your mailmanclient is too old. The version of > > Postorius you are running requires mailmanclient >3.3.1 which is only > > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > > > What version of Postorius is this? It appears to be >1.3.3. If you > > install Postorius from unreleased code on GitLab, you have to install > > all of mailman, mailmanclient and django-mailman3 as well. > > Shouldn't Postorius's setup.py be checking for this? > > Steve > _______________________________________________ > 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 & Regards, Shashi Kanth.K 9052671936

6 years

Re: broken route to accounts

by Stephen J. Turnbull

Thomas Krichel writes: > Stephen J. Turnbull writes > > > > > > What does "is broken" mean here? Well, since I have debug on, > > > GET "http://127.0.0.1:4386/accounts" > > > > This isn't going to match as far as I can see (but see comments below > > about customized systems). > > I found the line > > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" That line is almost certainly correct for Apache configuration. It does not mean that the system matches any URL with that prefix. What will match with that prefix is determined by the content of the URLconf (../site-packages/mailman_web/urls.py). But you probably haven't touched that file (I didn't realize that was a Python module rather than the reference to a filesystem path). Probably that file contains: urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ] which means these routes are the ones that match /accounts: > > Here are the routes stock Postorius serves > > from postorius/urls.py: > > > > r'^accounts/subscriptions/$', > > r'^accounts/per-address-preferences/$', > > r'^accounts/per-subscription-preferences/$', > > r'^accounts/mailmansettings/$', > > r'^accounts/list-options/(?P<member_id>[^/]+)/$', > (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/postorius$ ls -l urls.py > -rw-rw-r-- 1 mailman mailman 8623 Mar 18 08:25 urls.py > (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/postorius$ md5sum urls.py > 19b266d9ddec888c2614ea4915c52d68 urls.py > http://127.0.0.1:8000/accounts > > should respond without a debugging message, (You mean with port 4386, right?) It should tell you 404 No such resource, but if you set DEBUG=True it tells you that more verbosely. > I doubt this is any good because fundamentally, the queries to > > http://127.0.0.1:8000/accounts > > using 8000 here to illustrate don't work. The question is *how* do they fail. > The URL should reponds other that with a debug output. What does "GET http://127.0.0.1:4386/accounts/confirm-email/" respond with? (Don't omit the trailing "/".) Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 2 weeks

Mailman-users search results for query "Postorius"