Search results for "Postorius" - Mailman-users

Re: including a template failed

by Mark Sapiro

On 9/23/20 3:03 PM, Wolfgang Bock via Mailman-users wrote: > > Dear Mark, > > Q: Can you get > https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li > sts.domain-03.de/list:member:regular:footer on the Mailman machine? > > A: No > > Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? > > A: > was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' > > Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Can you get https://localhost/mailman3/postorius/api/templates/list/mylist.lists.domain… on the Mailman machine? > Now another problem occurs: > > Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool ... 'localhost' doesn't match either of > 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', > 'domain-04.de', 'www.domain-04.de'"))) The 'HTTPSConnectionPool' message has nothing to do with the 'Cannot connect' issue. > Port 25 entry results from the manual regarding the postfix configuration: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht > ml > > e.g.: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com > lmtp_port: 8024 > smtp_host: mail.example.com > smtp_port: 25 And I wonder why it's trying to connect to localhost when smtp_host is mail.example.com. -- 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: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 10:56 AM, Jonathan M wrote: >> On 7 Dec 2020, at 15:28, chris--- via Mailman-users <mailman-users(a)mailman3.org> wrote: >> >> I would like to be able to use the web form, but have a "notes" field that would get submitted with the signup request. the notes field would be where the user would note name/home address. So when one of our moderators get the request, they can figure out quick who the request is coming from. > > As far as I know this isn’t possible (though I wish it were). You could set up a separate form that emails you the notes, then emails the list subscription address. There is likely also a way to use the Mailman API. > I believe any fields that Postorius uses comes from Mailman 3 core's REST API. I don't think there is any field for a home address supported by Mailman 3 core. So, as Jonathan said, I don't think this is possible at all. Mailman 3 doesn't really need to know the street address of a mailman list user so I doubt you will ever see such functionality added to Mailman 3 core. Keep in mind that Mailman 3's REST API is only accessible locally. So to access Mailman 3's REST API from another server is not remotely possible. (see what I did there?) -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 8 months

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 12:10 AM, David Partain via Mailman-users wrote: > > I'm not on the latest mailman, unfortunately. I use the bundled packages on Ubuntu 18.04, which are > > mailman3 3.1.1-9 > mailman3-doc 3.1.1-9 > mailman3-full 3.1.1-9 > mailman3-web 0+20170523-14 > >>From the mailman-web logs, it looks like it's using python2. That would explain a lot. In particular, it would explain why the .pyc files aren't located per PEP 3147 <https://www.python.org/dev/peps/pep-3147/>. But it also raise the question of how anything works at all. Python >= 3.6 is required. HyperKitty and Postorius used to run under Python 2, but haven't for some time. I'm not sure what versions are in Debian/Ubuntu 0+20170523-14 package. > Put the symlink back, and it works again. (But still without the emojis working, of course.) > > Postgres is what's in settings.py, but I assume that should be overriden by what's in settings_local.py. > > Baffling. I don't really know what to do next, but I'll keep looking. I suggest removing all the .pyc files and restarting the services. That will probably recreate .pyc files, but they should then be good. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Telling Mailman/Hyperkitty where sass is

by Abhilash Raj

On Wed, 9 Aug 2017 17:12:35 -0700 Erin Justice <galaxyjustice(a)gmail.com> wrote: > Hi all, > > Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass. > > Specifically I'm getting errors like: > FilterError at /accounts/login/ > /bin/sh: sass: command not found > > I triple checked that sass is installed > which sass > /Applications/MAMP/Library/bin/sass > > /Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache. You change the command to be executed when the compressor is called in your Django's configuration file which in your case should be at mailman-suite/mailman-suite_project/settings.py See here https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… Instead of just `sass` or `sassc` command, you can change that to reflect the full path of the binary and it should work. Hope that is helpful! -- thanks, Abhilash Raj

8 years, 11 months

Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/23/19 7:12 AM, Franklin Weng wrote: > Hi list, > > I set up a mailman3 server and built a few lists to test. > > When I set the list name using Chinese characters, the web site shows > correctly. However in the subscribing welcome mail the list name was > shown in question marks. Screenshot is here: > > https://nextcloud.slat.org/index.php/s/CxPjpYMbQzQ6444 The name of the list from the screenshot seems to be zh-l10n(a)lists.linux.org.tw. The thing shown with ?s in the screenshot is the list's display_name (called Display name in Postorius). > The LANGUAGE_CODE settings.py (in Debian /etc/mailman3/mailman-web.py) > is set to zh-tw , and USE_I18N and USE_L10N are all set to True. These settings are all for Django and have nothing to do with how the list welcome message is sent. > Is there any other setting I should look at? The list's preferred_language setting (Postorius -> Settings -> List Identity -> Preferred Language. The list welcome message is encoded in Mailman's character set for the list's preferred_language. If this is English (USA), the character set is us-ascii. If it is set to Chinese (Taiwan), the character set is utf-8, and it should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Stephen J. Turnbull

Wikinaut writes: > I followed all single steps until this: > https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… > (I will improve the documentation with the missing parts later > today), > > Now I got this and got stucked and need your help: > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE If you use the mailman-web setup, the allauth, allauth.account, and allauth.socialaccount applications are present in the initial INSTALLED_APPS tuple in the settings package. The example_projects in Postorius and HyperKitty each provide a very similar settings.py but with more extensive provision of socialauth providers. I strongly recommend you use the mailman-web settings package as a template for your own. Regarding the PostgreSQL bias, PostgreSQL is just more Mailman-friendly. We'll be happy to add more MySQL documentation, but I don't think any of the core devs use it where they have to make a choice. (For example I myself use MySQL only in my MediaWiki instance and I have done zero configuration of it.) There is at least one known gotcha for default installations of MySQL (it's terribly ungraceful when there are non-BMP UTF-8 characters), but any other warts or optimizations would be very welcome. Steve

2 years, 9 months

Re: Something wrong with my Hyperkitty base_url?

by Andrew Hodder

Ah, I thought that only was affecting the web ui, didn't realize. Confirmed; that did the trick, thank you so much Abhilash! 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 Mon, Oct 2, 2017 at 3:38 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Mon, Oct 2, 2017, at 12:29 PM, Andrew Hodder wrote: > > from django.conf.urls import include, url > from django.core.urlresolvers import reverse_lazy > from django.views.generic import RedirectView > from django.contrib import admin > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('hk_root'))), > url(r'^hyperkitty/', include('hyperkitty.urls')), > #url(r'^postorius/', include('postorius.urls')), > url(r'', include('django_mailman3.urls')), > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', include(admin.site.urls)), > url(r'^hyperkitty/admin/', include(admin.site.urls)), > I removed the archives from the base_url, it still errors out just with a > different path: > > ValueError: <h1>Not Found</h1><p>The requested URL /api/mailman/archive > was not found on this server.</p> > > Now I should note, I'm running the web ui for hyperkitty on nginx with > http://FQDN/hyperkitty/ (where the non-/hyperkitty/ path would just go to > postorius). > > > > That is what you should be using for hyperkitty's `base_url` then: > > http://<whatever django is listening on>/hyperkitty/ > > > > > > > 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 Mon, Oct 2, 2017 at 3:22 PM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > > > On Mon, Oct 2, 2017, at 12:17 PM, Andrew Hodder wrote: > > Finally have everything stood up and working, except for HyperKitty > > mailman > > plugin. I'm getting a path issue of sorts I can see in the archiver.log > > (have it set to debug log level in the mailman core): > > > > Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_ > hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 154, in _archive_message > > url = self._send_message(mlist, msg) > > File > > "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_ > hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", > > line 210, in _send_message > > raise ValueError(result.text) > > ValueError: <h1>Not Found</h1><p>The requested URL > > /archives/api/mailman/archive was not found on this server.</p> > > > > > > My base_url in the mailman-hyperkitty.cfg: > > Can you show the contents of 'urls.py' in mailman-suite or whatever > Django project you are using to deploy hyperkitty? That would give more > ideas about whether the '/archives/' URL is valid or not. > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

8 years, 10 months

Re: 3rd Party Account is not working

by Matthew Alberti

Same thing happens to me. If I comment out all the socialauth plugins, the web service doesnt work. Are you using the docker-mailman installation method? ⁣Get BlueMail for Android On Feb 16, 2021, 7:32 PM, at 7:32 PM, kwp.klein(a)gmail.com wrote: >Here is my /mailamn/config/mailman-web/settings_local.py. I get an >error message > >curl http://172.19.199.3:8000/postorius/lists/ >curl: (7) Failed connect to 172.19.199.3:8000; No route to host >Please comment out all the lines that are not necessary. > > >MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >EMAIL_HOST = '172.19.199.1' >EMAIL_PORT = 25 >USE_SSL = False > >INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > # 'django.contrib.admindocs', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'paintstore', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount', > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', >) >_______________________________________________ >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, 5 months

Re: Bounce processing HTML

by Mark Sapiro

On 11/25/25 8:51 AM, pashdown(a)xmission.com wrote: > Where do I set forward_unrecognized_bounces_to ? I can't find documentation on this. If you have Postorius it's Settings -> Bounce Processing -> Forward unrecognized bounces. It is a list attribute with 3 possible values which are discard them, forward to list owners/moderators or forward to the site admin. The default value when lists are created is forward to list owners/moderators. However none of this is relevant to your situation because the bounces you are getting that result in the Bounce message for a non subscriber log messages you are seeing are not unrecognized. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I think these are spam sent to the list-bounces address that one of the heuristic recognizers treats as a real DSN and parses those non-addresses. In order to see the actual messages, you will have to configure your MTA to deliver them to a human or you could apply this patch ``` --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -49,6 +49,7 @@ class BounceRunner(Runner): # List isn't doing bounce processing? if not mlist.process_bounces: return False + maybe_forward(mlist, msg) # Try VERP detection first, since it's quick and easy context = BounceContext.normal addresses = StandardVERP().get_verp(mlist, msg) ``` to copy all bounce messages to the forward_unrecognized_bounces_to destination. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: broken route to accounts

by Stephen J. Turnbull

Thomas Krichel writes: > Note the absence of CSS. This should give a pointer of what is > wrong. I have no idea what you're saying. The absence of CSS is clearly by design -- no class or id attributes, no style attributes, no link to a stylesheet. Any CSS would have to attach directly to elements, presumably via a script. If you want CSS, say so, maybe we can give it to you, but its absence tells me nothing. > The "contact us" should ideally have more information. That is the stock verification message from Django's allauth/templates/account/verification_sent template. It can be overridden, but what information do you want. > The python 3.13 installation for lists.repec.info, which is brand > new, I have a problem of multiple logins attached to the email > address krichel(a)openlib.org. I follow that What logins? System logins? Postorius logins? Social auth logins? As far as I can tell, it should not be possible to attach one email address to multiple confirmed identities. In the Mailman database, there's an explicit constraint that User -> Address is one-many. Possibly it could happen in the Django database, but it's clearly intended to be either one identity to multiple addresses, or one-to-one (there is code that prevents the confirmation process from "claiming" previously confirmed address. It is possible to have multiple *pending* identities associated with the same email, but the first valid confirmation received from that address will "shut out" any others from successful confirmation. > https://lists.repec.info/accounts/confirm-email/Ng:1w9VGF:RwCZVc95UU8SomhAs… A request to this link should complete the confirmation process for some identity-address pair. If it does not, something is broken in your installation. > The anchor "issue a new e-mail confirmation request" links to > > https://lists.repec.info/accounts/login/?next=/accounts/email/ > > which is not a screen to get a new confirmation email, but > the login. That's correct behavior, I think. The query part doesn't control the response to this request. It controls the next step in some process. Why you get that link, I'm not sure, but it's probably due to the fact that you have successfully confirmed, so getting a new confirmation email doesn't make sense. The source of the link is buried in multiple layers of template and code spread across several packages. > On that screen, the user names krichel or krichel(a)openlib.org > that I remember, and the password I wrote down, lead to login > failure. "krichel" probably can no longer be attached to that email address because of the one-to-many constraint. I don't understand why the email address doesn't work as an identifier for that account, though. > So the only way to get in is to ask for a password > reset. The password reset generates an email just fine > > https://lists.repec.info/accounts/password/reset/done/ > > Again, that screen has no CSS, but the email arrives. In fact, > three emails arrive, each for an account I associated with that > email address. These logins are krichel, krichel(a)openlib.org and > mailman. That means all three of them are still pending I guess? Or maybe one has been confirmed, but I don't understand why they're still pending. > These lead to reset the password screens, I use the same password > everywhere. When I enter the passwords and confirm, I get to [the login page] > this screen has no CSS. When I click that confirmation email, I am > told I have confirmed, and I can login, say, as mailman. It would be helpful if you listed exactly which user identifiers ("account" or "user" at sign-in) allow you to log in, which ones ask you to confirm the email address, and whether that confirmation succeeds. You should also check the Postorius logs (mailmanweb.log, error.log, and the web server's access and error logs for information about the status and any error information associated with these requents. > It is still unclear to me why I am asked to confirm my email > address. Because you have tried to associate it with multiple identities and that is incompatible with Mailman's user model. > But so far so good. If I login as krichel, I am again asked to > verify my email. > > Tomorrow I will report on other installation. Users complain they > can't create accounts. Due to Summer of Code, I cannot spend much more time on this until May. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 4 weeks

Mailman-users search results for query "Postorius"