Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Mailman3 via Docker and NGINX

by brian＠emwd.com

Mark Sapiro wrote: > They could be in a conf.d file, but in this case they are in > sites-available/020-mailman.conf and symlinked from sites-enabled/020-mailman.conf. I am not sure what you mean. What documentation recommends using sites-enabled/020-mailman.conf or is this your own custom setup you have for lists.mailman3.org? I am using Docker which has nothing that references the use of such file paths/directories.

6 years, 5 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On Thursday, 3 January 2019 20:58:19 CET Mark Sapiro wrote: > On 1/3/19 7:43 AM, Thomas Stein wrote: > > > > Just saw the message is in /var/lib/mailman3/queue/shunt. What messages are going there? Something > > wrong with my setup? > > > Look in Mailman's mailman.log for an error message and Traceback along > with the shunting message which will describe the exception that caused > the shunting. Thanks for your answer. So the the file in queue/shunt contains information too? I will have a look. cheers t.

6 years, 5 months

[MM3-users] Re: Separating Lists by Domain

by brian＠emwd.com

So who manages Postorius? Is that a whole separate application from Mailman 3? Is there a way we can get whoever the developer is to update it where we can separate lists by domain the way Hyperkitty does? Mark Sapiro refers to this in the following post: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Thanks, Brian

6 years, 5 months

[MM3-users] Re: Separating Lists by Domain

by Stephen J. Turnbull

Abhilash Raj writes: > > Is there a way we can get [Postorius updated] where we can > > separate lists by domain the way Hyperkitty does? Mark Sapiro > > refers to this in the following post: > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at > https://gitlab.com/mailman/postorius/issues Is this feature GSoC-able, or too small? Steve

6 years, 5 months

[MM3-users] Re: Avoiding the List name in TO or CC headers

by mail＠nickwynja.com

Mark Sapiro wrote: >No. It is placed in Cc: to facilitate replies to the list. To not do this you would need to modify mailman/handlers/cook_headers.py. I've raised an issue with a proposal to add this feature as an option: https://gitlab.com/mailman/mailman/issues/531 -- Nick Wynja

6 years, 5 months

[MM3-users] Re: Update a member's display_name

by Nick Wynja

On 01/17/19 at 14:43, Mark Sapiro <mark(a)msapiro.net> wrote: > > So there is no member display_name per se. The display_name is the > display_name of the associated IUser or IAddress, and these are global. > > The bottom line is there is not a way to update just a single instance > of "member" of a list rather than the site-wide user or address? I see; understood. Thanks for explaining.

6 years, 4 months

[MM3-users] Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Mark Sapiro wrote: > This looks like <https://gitlab.com/mailman/hyperkitty/issues/211> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian

6 years, 4 months

[MM3-users] Re: Tracking from gravatar

by worik

On 15/02/19 3:51 PM, Mark Sapiro wrote: > You can disable them by setting > > GRAVATAR_SECURE_URL = '' > > in your local settings. See > <https://github.com/twaddington/django-gravatar> Where do I make that setting? There is nothing like it in any of my files. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 3 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > If you post an issue at <https://gitlab.com/mailman/mailman/issues>, > one of our GSOC aspirants may pick it up. Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-) -Ralph

6 years, 2 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Stephen J. Turnbull

Ralph Seichter writes: > * Mark Sapiro: > > > If you post an issue at <https://gitlab.com/mailman/mailman/issues>, > > one of our GSOC aspirants may pick it up. > > Done, although I wonder if any GSOC participant would want to write > documentation instead of code... ;-) For their actual, Google-supported, project, Google explicitly excludes documentation. But for our purposes, they do need a qualifying commit to demonstrate they've figured out how to get changes through our process and into merge requests, a purely adminstrative qualification. Doc patches are easy to write and get approved quickly! :-) Steve

6 years, 2 months

Search results for query "sapiro"