- Mailman-users - lists.mailman3.org

Removing banned emails
by Kaleb White Aug. 2, 2018

Aug. 2, 2018

I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… <Response [404]>

3 2

Re: Mailman 3 Keeps Forgettings Imported Lists
by Ryan McClung July 31, 2018

July 31, 2018

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

2 3

Mailman 3 Keeps Forgettings Imported Lists
by Ryan McClung July 31, 2018

July 31, 2018

GNU Mailman 3.2.0 (La Villa Strangiato) Python 3.6.5 (default, Apr 10 2018, 17:08:37) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] config file: /opt/mailman/var/etc/mailman.cfg db url: sqlite:////opt/mailman/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ Shortly after I run an import on a bunch of lists they all disappear. [root@mailman3(stg) mailman]# mailman lists No matching mailing lists found I have 30+ lists. Any thoughts? -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

2 4

mailman command to remove members
by Asaf Ohayon July 31, 2018

July 31, 2018

Is there command like mailman members --add, to mass-remove members from a list ? Thanks

2 1

Autorespond postings: does not seem to work on 3.2?
by Asaf Ohayon July 29, 2018

July 29, 2018

Hello Maybe I'm not understanding the meaning of this setting correctly, When I set this, I don't see any extra emails going out when I'm posting to the list Thanks

2 1

MM3 installation recommendation: Docker or individual components?
by Tom Browder July 28, 2018

July 28, 2018

I want to install MM3 on a virgin host running Debian 9. I want to minimize problems as bugs are fixed and necessary upgrades are published. I will use PostgreSQL, nginx, and Postfix, and am reasonably competent runnng my own remote server (full control, hard iron server, not virtual). The host will only serve mail to the public and nothing else (no websites, no other users). I did run a successful MM2 site (thanks to Mark’s copious and gracious help!) for a couple of years from 2011 to 2013, so I’m no stranger to some of the MM3 jargon. I have been running Apache 2.4+ with 10+ virtual https websites since 2010. I use Letsencrypt certificates for all of them. I have no experience with Docker, Django, or nginx. Should I choose the Docker method or individual compnent installation? I realize this is an open ended and very subjective request, but I would appreciate any advice. Best regards, -Tom

2 2

Re: [Mailman-Developers] Container Images for Mailman 3.2 release
by Abhilash Raj July 27, 2018

July 27, 2018

On Fri, Jul 27, 2018, at 1:16 PM, Kamran Soomro wrote: > Hi Abhilash, > > This is great. Thank you very much. Might I make a small suggestion? I > think it might be less confusing to use tags for your images that > conform to the mailman release. E.g. 3.2 should contain mailman 3.2, 3.3 > should contain mailman 3.3 etc. At the moment it’s hard to tell which > image contains which release. Sounds like a good idea! I will push 3.2 tags as soon as I can! > > Just my two cents. > > –Kamran > > > On 27 Jul 2018, at 21:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > Hi All, > > > > I have updated and pushed releases for Container Images with 3.2 release of the suite. > > > > They are available at: > > > > docker.io/maxking/mailman-web:0.2 > > docker.io/maxking/mailman-core:0.2 > > > > A similar copy of both is also available at quay: > > > > quay.io/maxking/mailman-web:0.2 > > quay.io/maxking/mailman-core:0.2 > > > > The releases contain the following versions of components: > > > > mailman-core: > > - Mailman Core 3.2.0 > > - Mailman-hyperkitty 1.1.0 > > > > mailman-web: > > - Postorius 1.2.1 > > - Hyperkitty 1.2.0 > > - Django-mailman3 1.2.0 > > - MailmanClient 3.2.0 > > > > The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: > > > > $ docker exec -it mailman-web bash > > bash # python manage.py rebuild_index > > > > If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). > > > > The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. > > > > Documentation for these images is available at: > > > > https://github.com/maxking/docker-mailman > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-Developers mailing list -- mailman-developers(a)python.org > > To unsubscribe send an email to mailman-developers-leave(a)python.org > > https://mail.python.org/mm3/mailman3/lists/mailman-developers.python.org/ > > Mailman FAQ: https://wiki.list.org/x/AgA3 > > > > Security Policy: https://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj (maxking)

1 0

Container Images for Mailman 3.2 release
by Abhilash Raj July 27, 2018

July 27, 2018

Hi All, I have updated and pushed releases for Container Images with 3.2 release of the suite. They are available at: docker.io/maxking/mailman-web:0.2 docker.io/maxking/mailman-core:0.2 A similar copy of both is also available at quay: quay.io/maxking/mailman-web:0.2 quay.io/maxking/mailman-core:0.2 The releases contain the following versions of components: mailman-core: - Mailman Core 3.2.0 - Mailman-hyperkitty 1.1.0 mailman-web: - Postorius 1.2.1 - Hyperkitty 1.2.0 - Django-mailman3 1.2.0 - MailmanClient 3.2.0 The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: $ docker exec -it mailman-web bash bash # python manage.py rebuild_index If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. Documentation for these images is available at: https://github.com/maxking/docker-mailman -- thanks, Abhilash Raj (maxking)

1 0

Double footer
by Asaf Ohayon July 23, 2018

July 23, 2018

Hello Upon a clean installation of Mailman 3.2.0a1, Without any additional configuration, nor custom footers, When accepting message from the list on Gmail client for example, The footer shows twice, also in the message source I see two identical footer parts, accept for the message barrier: --===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Info mailing list -- info(a)mailman.sysbind.biz To unsubscribe send an email to info-leave(a)mailman.sysbind.biz --===============4363779446011731395== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Info mailing list -- info(a)mailman.sysbind.biz To unsubscribe send an email to info-leave(a)mailman.sysbind.biz --===============4363779446011731395==--

3 4

Migrating from SQLite to PostgreSQL
by Joe Steeve July 20, 2018

July 20, 2018

Hello All, I have an installation on SQLite. I want to migrate it to PostgreSQL. Is that feasible? Any gotchas I need to watch for? -- Joe Steeve HiPro IT Solutions Private Limited http://www.hipro.co.in/

6 8