- Mailman-users - lists.mailman3.org

getting spammed when sending lots of mails (>1000)
by Asaf Ohayon 06 Aug '18

06 Aug '18

Hello Using Mailman 3.2 / Posfix 2.10.1 I have a list configured, when having only few members, all is OK, email gets to inbox (at GMail) But when sending to thousands of members, it gets to the Spam folder, Is it a matter of rate-limiting at postfix ? Thanks -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

"To:" header field
by Asaf Ohayon 05 Aug '18

05 Aug '18

Hello I'm having trouble with getting into spam folder (at least at gmail), I'm suspecting to "To:" field (among other things). Comparing to Mailman 2.1, which we recently upgrading from, and didn't got spammed, the "To:" field was set to the actual reciever, While in Mailman 3.2, the "To:" field is set to the list's address. How can this be configured ? Thanks -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

2 1

Archiving error
by Eric Abrahamsen 03 Aug '18

03 Aug '18

Since about two days ago, all attempts to archive messages via Hyperkitty have raised the error below. So far as I know, I haven't updated any packages, or changed any config. I don't know why this has started happening. Internal Server Error: /hyperkitty/api/mailman/archive IntegrityError at /hyperkitty/api/mailman/archive NOT NULL constraint failed: hyperkitty_attachment.size Request Method: POST Request URL: http://lists.my-domain.org/hyperkitty/api/mailman/archive?key=NotMyRealKey Django Version: 2.0.5 Python Executable: /home/eric/.local/share/virtualenvs/mailman-FH66s6f7/bin/python Python Version: 3.5.2 Traceback: File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py" in execute 303. return Database.Cursor.execute(self, query, params) The above exception (NOT NULL constraint failed: hyperkitty_attachment.size) was the direct cause of the following exception: File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/base.py" in _get_response 128. response = self.process_exception_by_middleware(e, request) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/core/handlers/base.py" in _get_response 126. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/views/mailman.py" in _decorator 72. return func(request, *args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/views/decorators/csrf.py" in wrapped_view 54. return view_func(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/views/mailman.py" in archive 119. add_to_list(mlist_fqdn, msg) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/hyperkitty/lib/incoming.py" in add_to_list 162. encoding=encoding) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/query.py" in create 417. obj.save(force_insert=True, using=self.db) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in save 729. force_update=force_update, update_fields=update_fields) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in save_base 759. updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in _save_table 842. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/base.py" in _do_insert 880. using=using, raw=raw) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/query.py" in _insert 1125. return query.get_compiler(using=using).execute_sql(return_id) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/models/sql/compiler.py" in execute_sql 1283. cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in execute 68. return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute_with_wrappers 77. return executor(sql, params, many, context) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/utils.py" in __exit__ 89. raise dj_exc_value.with_traceback(traceback) from exc_value File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/utils.py" in _execute 85. return self.cursor.execute(sql, params) File "/home/eric/.local/share/virtualenvs/mailman-FH66s6f7/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py" in execute 303. return Database.Cursor.execute(self, query, params) Exception Type: IntegrityError at /hyperkitty/api/mailman/archive Exception Value: NOT NULL constraint failed: hyperkitty_attachment.size Request information: USER: AnonymousUser GET: key = 'NotMyRealKey' POST: mlist = 'my-list(a)lists.my-domain.org' FILES: message = <InMemoryUploadedFile: message.txt ()> COOKIES: No cookie data META: CONTENT_LENGTH = '579002' CONTENT_TYPE = 'multipart/form-data; boundary=4c9a29456f514b2a9ef4f9a5d042abc6' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_CONNECTION = 'close' HTTP_HOST = 'lists.my-domain.org' HTTP_USER_AGENT = 'python-requests/2.18.4' HTTP_X_FORWARDED_FOR = 'xxx.xxx.xx.xxx' HTTP_X_FORWARDED_HOST = 'lists.my-domain.org' HTTP_X_REAL_IP = 'xxx.xxx.xx.xxx' PATH_INFO = '/hyperkitty/api/mailman/archive' QUERY_STRING = 'key=NotMyRealKey' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'POST' SCRIPT_NAME = '' SERVER_NAME = '127.0.0.1' SERVER_PORT = '231742768' SERVER_PROTOCOL = 'HTTP/1.0' wsgi.errors = <_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <_io.BytesIO object at 0x7f940d0055c8> wsgi.multiprocess = True wsgi.multithread = False wsgi.run_once = False wsgi.url_scheme = 'http' wsgi.version = '(1, 0)'

1 0

Removing banned emails
by Kaleb White 02 Aug '18

02 Aug '18

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 31 Jul '18

31 Jul '18

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 31 Jul '18

31 Jul '18

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 31 Jul '18

31 Jul '18

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 29 Jul '18

29 Jul '18

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 28 Jul '18

28 Jul '18

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 27 Jul '18

27 Jul '18

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