Search results for "Postorius" - Mailman-users

Adding user - Error 409 Subscription request already pending

by kevin＠coastalaska.org

We have a couple of people trying to subscribe to our list but receive an error similar to: {"title": "409 Conflict", "description": "Subscription request already pending"} If I try to Mass Subscribe them in Postorius I get this error: HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' In Postorius I don't see them hung up in Subscription requests. What to do? Thanks, Kevin

6 years, 8 months

Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Ah. Base ignorance at play. It helps if one overcomes indolence and actually reads up on the docs for Django. I see that django-admin does all that the manage.py script does. So all is good. I shall proceed! >

6 years, 7 months

Re: Mass subscribe gives HTTP Error 500 when using custom template

by Jeffrey D

Mark Sapiro wrote: > On 1/28/20 6:15 AM, Jeffrey D wrote: > > What is your setting in settings(_local).py for > POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > It should be the base URL for connecting to Postorius. I.e., if you > normally connect to Postorius via https://www.example.com/postorius, it > should be https://www.example.com Thanks, changing the POSTORIUS_TEMPLATE_BASE_URL fixing the issue.

5 years, 11 months

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

by Mark Sapiro

On 3/28/20 3:53 PM, Ralph Seichter wrote: > > As I said, the MTA does not log connection attempts from the Suite, nor > do I find evidence that Django actually tries to send out email. Weird. What is the complete log message from uwsgi-error.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

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

by Ralph Seichter

* Abhilash Raj: > It definitely would help if you paste the diff of the settings > required. See attached diff file. > Also, can you jump into a django shell and see if you can get any > exceptions trying to send emails [...] Sending email from the Django shell in the manner you described works. -Ralph

5 years, 9 months

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

by Ralph Seichter

* Ralph Seichter: > See attached diff file. > >> Also, can you jump into a django shell and see if you can get any >> exceptions trying to send emails [...] > > Sending email from the Django shell in the manner you described works. Is there anything else I can provide? I have let this lie for a bit, hoping that coming back with a fresh perspective might help me figure out what I missed (I still hope it's me and not Mailman). Alas, I am still stuck. -Ralph

5 years, 9 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/23/20 10:27 AM, Gilles Filippini wrote: > > You'll have also to remove the compiled files from the __pycache__ > directory: This is not necessary. If the .py file is newer than the .pyc file in the __pycache__ directory, the interpreter will use the .py file and if it has permission will rewrite the .pyc file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 20:02 : > On 4/23/20 10:27 AM, Gilles Filippini wrote: >> >> You'll have also to remove the compiled files from the __pycache__ >> directory: > > > This is not necessary. If the .py file is newer than the .pyc file in > the __pycache__ directory, the interpreter will use the .py file and if > it has permission will rewrite the .pyc file. Indeed, if it has permission. When testing in user space it does not have permission. These files are owned by root. _g.

5 years, 8 months

HyperKitty Question

by Samir Faci

Okay, I have mailman3 working to allow me to send/receive emails. postorius seems to be working fine. My only issue seems to be with hyperkitty saving the archive. postorius seems to be working fine. Hyperkitty on the other hand is failing. I have nginx running with multiple website being serviced from the same server. I updated the config where port 80 gets redirected to SSL. I tried setting mailman3-hyperkitty.conf to both: base_url: http://localhost/hyperkitty/ base_url: https://lists.domain.com/hyperkitty/ But neither seem to be working. Does hyperkitty require traffic to be going over port 80? -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 8 months

Re: performance report - mailman 3.3.1rc1 / postorius 1.3.1

by sunil soprey

One more config item - QCLUSTER / Cache = AWS ElasticCache - 2 nodes DB = AWS RDS = r5.large

5 years, 7 months

Mailman-users search results for query "Postorius"