New question about configuration, maybe somebody has experience and know
what I should change it. I have tried to implement Google authorisation.
I have created Google credentials keys and successfully added using Django
I use UWSGI proxy for apache setup like "ProxyPass / http://127.0.0.1:8002",
UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects to
internal) What happens when I try Google auth...
If I set Authorised redirect URIs:
http://lists.example.com/accounts/google/login/callback/ , Google gives me
error 400 Error: redirect_uri_mismatch and requests for:
If I set that requested address to Google, then Google authorises me,
but and after authorisation redirects to
http://127.0.0.1:8002/accounts/google....../.... (very long line) Of
course this internal address does not open, but...
If I just manually replace part of address just: http://127.0.0.1:8002
replace to https://lists.example.com/.../...(long line) this makes me get
in as authorised user to the page.
How to make django to send external request to Google? Because
Google should not point back to internal address... This seems simple, but
I do not find what I should change in the configuration: Apache or Django
or uwsgi.ini I hope anybody of You have experience and made it to run.
Latest upgrade version has not improved matters. When I download, the file is generated but it is ten bytes long and obviously therefore corrupt.
Why am I the only one seeing this error?
What can I do to diagnose it?
In a long thread I asked this but have not gotten a clear enough explanation.
Presumably, to insure fewer problems with users of Yahoo etc,, there seem to be two settings:
1) Alter messages
2) Dmarc mitigations
I don’t understand how my choice in one affect the other, if they do even,
Two experts have tried to help, but I think I need a little hand holding.
I understand there is no consumer ready manual and all I have found us this:
REPLY GOES TO LIST (alter messages)--current settings
REPLACE FROM: with list (DMARC mitigations) -> current settings
DMARCH Mitigation YES OR NO (DMARC mitigations)--> currently NO
I was told that Dmarc mitigations YES might prevent people from not getting mail
How about Replace from with list?
How about reply goes to list?
In other words, what is the relationship between these two different menu items and the effect of the settings in one on the settings of the other?
Can anyone help a confused would be happy user?
If so, what about the Alter Messages settings:
Hi. All the project installation is under the same user / path and
it works. Archiving working as well, (just one remark: no matter what to set in postorius, hyperkitty shows list as public)
I have found work around - it is possible to change list as private in "admin" page.
I started to get issues with runjobs after I have created couple of new lists with "no archive" option.
If as owner user from project home I run:
Traceback (most recent call last):
line 84, in _execute
return self.cursor.execute(sql, params)
line 383, in execute
return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: attempt to write a readonly database
"django-admin runjob sync_mailman " - makes read only errors as well.
"django-admin runjob new_lists_from_mailman"
django.db.utils.OperationalError: attempt to write a readonly database
I did not find information how to fix this. It was worked without errors
I noticed, that if I stop mailman, "django-admin mailman_sync" starts to work.
If I start "mailman start", then "django-admin mailman_sync" failing again.
I did not check other jobs, but I think what is related to database, will get errors.
Seems mailman locking the database. It is not a file permissions issue.
Mailman db location is: /project_directory/var/data/mailman.db
if to rename /project_directory/var/data/mailman.db to something, mailman creates database file size 0, django-admin runjobs start working, but of course postorius stops working. I did it for testing. I have returned this database file back, postorius started to work again, but django-admin runjobs does not work, error: "database read only".
Please help me how to fix this issue.
Hi all -- think this is a bug. I had added some users as a mass subscribe. Some were Name Surname <name(a)foo.bar> format, some were just email addresses. I wanted to update the member list with complete name & email addresses. I unsubscribed the partials, and re-added them as full versions. However the updated member list keeps showing the partial address only.
This bug also works the other way. I added "Bob Smith <bob(a)bob.com>", checked it was there in list. Unsubscribed the address, and then re-added as "bob(a)bob.com" -- now in the members list it appears as the full "Bob Smith <bob(a)bob.com>.
In my tests where replies go to the list, when a person uses the email client? So far a reply to the original message and a reply to a reply to a reply all go in the same thread. Is this standard? Do I have to warn users not to have endless Re re re re?
And the other question is what happens if a user sends a message via email with a new subject? Does the list accept it as a new thread?
This should be one of my last big questions.
I am pleased to announce new releases for Mailman Suite, including
- Mailman Core 3.3.0 (Tom Swayer)
- Mailmanclient 3.3.0
- django-mailman3 1.3.0
- Postorius 1.3.0
- Hyperkitty 1.3.0
This is a feature release and also includes a bunch of bugfixes. I am really really thankful to a lot of contributors who have helped out with this release.
It is really nice to see Mailman 3 gaining more users and contributors.
Python 3.5 is the minimum supported version, but all the releases have been tested to work with Python 3.5-3.7. This is the last release to support Python 3.5 since it has been in security only maintenance mode for a while now.
Some of the highlights of this release includes:
Mailman Core 3.3.0
- Support for ARC signing. Thanks to Gene Shuman and Stephen Turnbull.
- Many many improvements to "mailman import21" command. Thanks to Mark Sapiro.
- Addition of French templates. Thanks to Stéphane Parunakian.
- A better and more scalable REST API server using Gunicorn.
- Support for SMTPS/STARTTLS. Thanks to J08ny.
A full copy of change log is available at:
- Many more settings for MailingList configuration exposed, including
preferred language, digest related settings.
- Support for FILTER_VHOST to filter MailingLists based on the serving
domain. Thanks to Nate Coraor.
- Ability to write MailingList info in Markdown to render info in HTML
instead of Plaintext.
A full copy of change log is available at:
- Unread messages, when logged in, are more easily recognizable with
blue envelope icon.
- Improved thread view with colored background for quoted parts of
- Improved readability on small screens by removing the indentation
in thread view.
A full copy of the change log is available at:
All the packages are available to download from PyPi (https://pypi.org).
Abhilash Raj (maxking)
Is it possible to use Amazon SES with Mailman? Despite my best efforts, I have conclusively verified my sending domain, but Amazon SES rejects mails with the 'sender email not verified' message. If you verify a domain, you do not have to verift individual senders. The help from amazon SES mentions it looks at several headers, but I am not sure what is what.
Has anybody had success with this?