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

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 9 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/27/20 2:24 PM, Bryan Loniewski wrote: > Hello -- > > I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: > > <snipped> > [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get > for archiver in archiver_set.archivers > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> > if archiver.system_archiver.is_enabled> File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver > raise AssertionError('Archiver not found: {}'.format(self.name)) > AssertionError: Archiver not found: hyperkitty I've been looking at the code, and I think this can occur if the mailing list has a configured archiver which is no longer known in mailman.config.config.archivers. I.e., the list has hyperkitty as an archiver, but hyperkitty is no longer configured as an archiver in Mailman. > and > > <snipped> > Traceback (most recent call last): ... > KeyError: 'file' This traceback is useless. All it says is a Django logging error occurred in trying to log the real exception. The interesting one is immediately before this in the log. > Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. > > Some relevant? config files... > > mailman.cfg: > > <snip> > [archiver.prototype] > enable: yes > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > <snip> That looks good. > mailman-hyperkitty.cfg: > [general] > base_url: https://a_real_domain/mm3/hyperkitty > api_key: <movealong> > > I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? I don't either and I don't know why., For example on lists.mailman3.org ``` mailman conf|grep [[]archiver [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: yes ``` doesn't show hyperkitty and neither does ``` mailman conf -k enable [archiver.mail_archive] enable: no [archiver.mhonarc] enable: no [archiver.prototype] enable: yes ``` but ``` /mailman conf -s archiver.hyperkitty [archiver.hyperkitty] class: mailman_hyperkitty.Archiver [archiver.hyperkitty] clobber_date: maybe [archiver.hyperkitty] clobber_skew: 1d [archiver.hyperkitty] configuration: /opt/mailman/mm/deployment/mailman-hyperkitty.cfg [archiver.hyperkitty] enable: yes ``` So I don't think this per se is the issue. > Any suggestions? Try ``` mailman shell May 28 00:35:47 2020 (15162) patched 1/1 modules (sqlalchemy) Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from mailman.config import config >>> list(config.archivers) [<mailman.archiving.mhonarc.MHonArc object at 0x7fdd9ccff6a0>, <mailman.archiving.mailarchive.MailArchive object at 0x7fdd9ccffac8>, <mailman.archiving.prototype.Prototype object at 0x7fdd9ccffb38>, <mailman_hyperkitty.Archiver object at 0x7fdd9ccffe80>] >>> ``` Does yours list hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can we modify the docs? Ok, I'm going to add that config to main.cf and test Thank you El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 09:36 AM, Rafael Mora wrote: > > > > Postfix <http://www.postfix.org/>: To setup Postfix, add the following > > configuration to master.cf: > > > > # Support the default VERP delimiter.recipient_delimiter = > > +unknown_local_recipient_reject_code = 550owner_request_special = > > notransport_maps = > > hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = > > hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = > > hash:/path-to-mailman/var/data/postfix_domains > > > > > > I added that config at the bottom of the master.cf file and did a > 'postfix > > reload' and I got this error message: > > > > [root@localhost ~]# postfix reload > > /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad > field > > count > > postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! > > > First of all, in a report such as this, it would really help if you > reported what is actually in master.cf in the vicinity of line 129. > > However, that said, the doc is wrong. The lines should be added to > main.cf, not master.cf. See > <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > Also, what you post above is quite garbled. It is not clear what you > meant, but the lines to add should be > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > local_recipient_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > relay_domains = > hash:/path-to-mailman/var/data/postfix_domains > > > and should not be wrapped as in your post. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

9 years

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi Mark, Thanks for your response. I found what the issue was. I actually misspelled hyperkitty as hyPperkitty on the url. So the error on mailman-hyperkitty.cfg was: base_url: http://localhost:8000/hypperkitty/ I moved to: base_url: http://localhost:8000/hyperkitty/ and it was solved. Problem was the wrong link was getting a generic page from Django instead of error. And it was failing to do the parsing probably, which was taking wrongly as key mistake. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/20/24 14:25, Helio Loureiro wrote: > > Hi, > > > > I keep receiving a lot of errors like this: > > > > --- Logging error --- > > Traceback (most recent call last): > ... > > > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > > line 55, in unsign > > raise BadSignature('Signature "%s" does not match' % sig) > > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > > does not match > ... > > > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and > MAILMAN_ARCHIVE_KEY > > on setting.py are the same. > > > Of those three, the api_key on mailman-hypperkitty.cfg and > MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django > thing and has nothing to do with the others. See > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key > > If you changed it, that's the issue. If you know what it was previously, > you could set the previous value in SECRET_KEY_FALLBACKS, see > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

2 years, 4 months

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 6:26 AM, sean_sullivan(a)rhoworld.com wrote: > > However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. > > from mailmanclient import Client You do not need to use mailmanclient with shell/withlist. mailmanclient is Python bindings for REST API functions. When you are under `mailman shell` (or `mailman withlist`, a synonym for `mailman shell`) you are working within mailman core and it's just extra baggage to use mailmanclient/REST. > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.testing.helpers import subscribe Here again, mailman.testing.helpers is to provide certain functions used in doctests. You don't need that with mailman shell. > addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > > client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') > > def set_owners(mlist): > > for email_addr in addresses: > try: > member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) See below. > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist): > my_list = client.get_list(mlist) > # print(my_list.fqdn_listname) > # for email_addr in addresses: > # my_list.remove_owner(email_addr) > > The errors I am getting are: > > ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com > Traceback (most recent call last): > File "./bin/mailman", line 8, in <module> > sys.exit(main()) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main > rv = self.invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > return super().invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke > return callback(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func > return f(get_current_context(), *args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell > r = call_name(dotted_name, m, *run_args) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name > return named_callable(*args, **kws) > File "/opt/mailman3/bin/set_owners.py", line 24, in remove > my_list = client.get_list(mlist) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list > 'lists/{0}'.format(fqdn_listname)) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: 404 Not Found > > > So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Here's what you want with addresses as arguments so you can save this as set_owners.py and run things like. $ bin/mailman shell --run set_owners -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' and $ bin/mailman shell --run set_owners.remove -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' > from mailman.app.membership import add_member, delete_member > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.interfaces.subscriptions import RequestRecord > > def set_owners(mlist, *addresses): > for email_addr in addresses: > try: > record = RequestRecord(email_addr) > member = add_member(mlist, record, role=MemberRole.owner) > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist, *addresses): > for owner in mlist.owners.members: > if owner.address.email in addresses: > owner.unsubscribe() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Dave Hall

On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/7/23 13:43, Odhiambo Washington wrote: > > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > > as2020+github(a)fam.tuwien.ac.at> wrote: > >> > >> I am running MM2 und 3 in parallel without problems, I do have a > >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. > >> > > > > Your setup can handle list1(a)domain1.name via MM2 and MM3, > simultaneously, > > right? :-) > > It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` > simultaneously on the same server, but what is the MTA going to do with > incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to > both MM2 and MM3, but I don't see any practical use case for this. > > I run Exim4 on my servers so I can comment from this perspective. Exim had a concept of 'routers' which are stacked and processed in order of appearance. There is a router for MM2 and one for MM3 that pick off incoming mail based on whether the email address matches a list name. WIth this setup, you could have the same list name in both MM2 and MM3, but it would go to whichever router appears first and the second one would never see it. So I have the MM3 router first, and as I migrate my lists from MM3 the email for those lists no longer gets to MM2. > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kdhall(a)binghamton.edu -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office)

3 years, 4 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:22 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/22 21:47, Odhiambo Washington wrote: > > On Fri, Dec 16, 2022 at 11:17 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> I suggest you run > >> ``` > >> django-admin collectstatic --clear --noinput --verbosity 2 > >> > > > > The output is here: https://pastebin.ubuntu.com/p/qkR2bDYv3G/ > > > > > > > >> django-admin compress --verbosity 2 > >> > > > > The output of the above is here: > https://pastebin.ubuntu.com/p/T7jQPrs3JX/ > > > Those look OK. > > I suggest you look at ownership and permissions. > I doubt it's about ownership and permissions given the fact that I have even done "chown -R mailman.mailman /opt/mailman" just for the kicks. > > ``` > find /opt/mailman/mm/static/ -not -user mailman > find /opt/mailman/mm/static/ -not -perm -u+rw > find /opt/mailman/mm/static/ -type d -not -perm -u+x > ``` > and the same on > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > root@list:/home/wash# find /opt/mailman/mm/static/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/static/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/static/ -type d -not -perm -u+x root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -type d -not -perm -u+x root@list:/home/wash# Yielded nothing - perms and ownership are all okay. > If the above doesn't reveal anything substantial, then let me know and I > > can bump up the verbosity. > > > I don't know if --verbosity 3 will reveal anything or not. You could try. > I did check, but the output looks the same as when it's set to 2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml. 2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > > I assume you mean HyperKitty. Postorius has no facility for posting > messages to a list. > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > When you post from HyperKitty, HyperKitty creates a > django.core.mail.EmailMessage() instance and calls it's send() method > which causes Django to send the message to the list address. It then has > to be received and processed by Mailman the same as any email post > before it will appear in the archive. > > Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. > > If DEBUG = False and normal posting is working, perhaps there is some > Postfix issue in delivery of the message from Django to Mailman. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 8 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote: > On 7/30/21 10:47 AM, bob B wrote: > > > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? > > > I'm not sure what the actual command would be do run the django-admin > interface in the docker image, but from below, it looks like it's > `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command. You can run commands with `docker exec -it mailman-web ./manage.py <command>`. For creating the superuser, you can run[1] [1]: https://asynchronous.in/docker-mailman/web.html#running Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process. Although, you can create a second admin and set the password for it and login using that using the command mentioned at [1]. > > > > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. You can run docker exec -it mailman-web ./manage.py sendtestemail youremailid@domain > > This command tries to send the mail via SMTP to localhost port 25. > > > > How can I make sure my containers can send and receive mail? > > > The MTA should be listening on port 25 and that need to be visible in > the mailman-web container. See > <https://asynchronous.in/docker-mailman/#setting-up-your-mta> > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Search results for query "sapiro"