Search results for "Postorius" - Mailman-users

Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 21:19, Abhilash Raj wrote: > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >> >> I restarted de server and the error changed. Now the log >> shows "KeyError: 'subscription_mode'": >> >> Did you also restart Mailman Core after the upgrade? >> >> Yes, indeed: I stopped mailman core and all the processes related. >> Did the upgrades. Started all again. Find the errors in the web user >> interface. Stopped all again. Looked for errors in the log. Restarted >> the complete server. Found the second error that this second mail is >> about to. It happens when, in the main page that shows all the lists >> you click to see one of them. It seems to me that it has been >> database structure changes in django that the upgrade is not aware... >> but it's a very long shot from my side. > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > a derived atrribute and not stored in Database. Mailman's API should be > returning this attribute for each Member, but for some reason it seems > to me like it isn't doing that even though do have Mailman 3.3.3 running > like you said. > If you have Curl installed, can you send me the output of: > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 This is the output you asked for (it's the same you can see when you try to interact with one list): /usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> No log entry has been produced... TIA. > It should ideally return an output that looks something like shown > here[1]. You > can put the username/password of Core's API server in the above command. > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Abhilash >> I'm using sqlite as django database and mysql for mailman. >> >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >> Server Error: >> /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'subscription_mode' During handling of the above exception, >> another exception occurred: Traceback (most recent call >> last): File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner response = get_response(request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response response = >> self.process_exception_by_middleware(e, request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response response = >> wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view return self.dispatch(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch return super(MailingListView, >> self).dispatch(request, *args, **kwargs) File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch return handler(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >> line 295, in get member.subscription_mode == File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute >> 'subscription_mode' *********************** some info about >> the installed versions via pip list: pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 pip list | grep postorius >> postorius 1.3.4 On 6/2/21 11:12, >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I've just upgrade mailman 3 installation following Mr. >> Sapiro advice: did a pip install --upgrade >> django-mailman3 hyperkitty mailman mailmanclient >> mailman-hyperkitty postorius I did a "python3 manage.py >> migrate" after, too. And all seemed to run well. All the >> lists showed in postorius via web, but when I try to >> accesss into one of them the browser shows an error. In >> the log you can see: *-*-*-*-*-*-* Traceback (most recent >> call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'get_requests_count' .. (And after all the traceback >> lines) AttributeError: 'MailingList' object has no >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >> seem to be distributing messeages well.. but I cannot >> acces via web administration (django/postorius) Can >> anyone point me in the right direction to solve this, >> please? _______________________________________________ >> 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.mailman3org/> >> >> >> _______________________________________________ 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.mailman3org/> >> >> >> _______________________________________________ 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.mailman3org/>

5 years, 3 months

Re: "Private archives" aren't private

by Simon Liebold

Am 04.06.2017 um 15:55 schrieb Simon Hanna: > > Where are you seeing this behaviour? In my test archive: https://lists.simonliebold.de/hyperkitty/list/simsimmer@lists.simonliebold.… > > What version of Hyperkitty are you using? Master, commit 4c5eaead. > > Can you check what is stored in the database of Hyperkitty? > > ``` > > python manage.py shell > > from hyperkitty.models.mailinglist import MailingList > > MailingList.objects.all().values_list('name', 'archive_policy') > > ``` > > If the value for your list is 1 then we have a problem. 2 is for public > archives and 0 should never be archived. OK, no problem there: <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> > > It's possible that you changed the archive_policy of a list and the > change wasn't reflected in Hyperkitty. Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected. Postorius is on 52c9c3a5. > > For such a possibly sensitive issue, you should open a hidden issue in > Gitlab ;-) > The issue is probably my setup. Simon

8 years, 11 months

Re: hello， Discussion on how to subscribe to themailing list

by Stephen J. Turnbull

朱超 writes: > Yes, You got it. It is too cumbersome to ask the user to write a > reply email for email confirmation. Surely clicking on "reply" then "send" is not cumbersome (unless there's a way to get rid of confirmation altogether). Your problem is that some of your subscribers can't do that. I have not previously heard of a MTA that refuses to *send* mail because the addressee's mailbox is too long. IIRC there's a limit of 256 characters on domains, but only the (long-obsolete) recommendation that lines in the message be 998 bytes or less restricts the length of the local-part. I don't really see a good reason to change this default because there are a number of configurations where there is no web service available. I suggest a partial remediation in the issue I just filed. (I think dealing with the rest of the issue is a Simple Matter of Programming, but the question of determining existence and status of an appropriate web service is more complex so I did address that.) > Why do you need to modify the mailman-core service， >I suggest we should modify the code of the postorius, We are not going to do that, because 1. Mailman provides no guarantee that any web service is present, and we're not going to make changes that require one. 2. Mailman provids no guarantee that the web service is Postorius even if there is one, and we are definitely not going to make creating compatible implementations more annoying than necessary. > Currently I have achieved it this way。 We encourage you to use your code. ;-) But using it exclusively to accomplish this change would go against several of our goals in term of separation of concerns. If we can do it in an alternative way that serves those goals, there's no point in complexifying Postorius in this way as well. Regards, Steve

3 years, 3 months

Re: missing graphics in Postorius

by Mark Sapiro

On 12/7/21 4:01 PM, David Newman wrote: > On 12/7/21 11:17 AM, Mark Sapiro wrote: >> Add '127.0.0.1' to ALLOWED_HOSTS anyway. > > Done, thanks. > > Given that DNS works fine on this host, with localhost and 127.0.0.1 > resolving backward and forward, this seems like a bug. Shouldn't the > resolver be able to recognize localhost without hard-coding an address? It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about. ... >> Assuming you have >> ``` >> STATIC_ROOT = '/opt/mailman/web/static' >> ``` >> in your /etc/mailman3/settings.py file, you may need to create that >> directory if it doesn't exist. You shouldn't need to manually create >> the /opt/mailman/web/static/postorius directory if the >> /opt/mailman/web/static directory exists and is writable/searchable by >> the Mailman user. > > Yes, that was it. Thanks. > > Previously you'd pointed out what you considered an error in the venv > docs, with the workaround to manually create the /opt/mailman/web > directory [1]. I think the same issue applies here, and also that > /opt/mailman/web and subdirectories need to be owned by the mailman user. I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it says ``` Make sure that the logging path is created. You can run mkdir -p /opt/mailman/web/logs to create the path. ``` I added ``` Also make sure the ``STATIC_ROOT`` directory is created. ``` after that. As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says ``` Make sure that you are running commands as mailman user from here forth. Setup Mailman user. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: Key Error when clicking on a list

by Mark Sapiro

On 6/19/20 9:02 AM, Jacob Bargery wrote: > I looked back and tried to see if this is related to the Filter_Vhost = true error. In the email log I received at the bottom where it lists settings I am seeing Filter_Vhost = false. So I am guessing it is not related I could be wrong though. > > I can see lists populated that have been created, but when I click to open them it immediately goes to page titled "Server Error" and reading "An error occurred while processing your request.". This is part of the email, I can include the rest with settings if that will help. > > > Internal Server Error: /mailman3/postorius/lists/testlist.groups.smccme.edu/ > > KeyError at /postorius/lists/testlist.groups.smccme.edu/ > 'file' As has been mentioned many times on this list, the KeyError at ... 'file' exception is not the issue. It is a result of Django encountering this issue in trying to log the real exception. > Request Method: GET > Request URL: http://groups.smccme.edu/mailman3/postorius/lists/testlist.groups.smccme.ed… You are trying to get the list view for the testlist.groups.smccme.edu list ant that causes: > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view > 71. return self.dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch > 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch > 97. return handler(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get > 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 The above appears to be where the issue arises. The full code bit here is > if ('hyperkitty' in settings.INSTALLED_APPS and # noqa: W504 > 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 > self.mailing_list.archivers['hyperkitty']): > data['hyperkitty_enabled'] = True The condition `'hyperkitty' in self.mailing_list.archivers` is causing Postorius to try to get the archivers associated with this list, and that's where the 500 occurs. > File "/usr/lib/python3.8/_collections_abc.py" in __contains__ > 666. self[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ > 151. return self._get(key) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get > 90. return self.rest_data[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 76. response, content = self._connection.call(self._url) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) this 500 return from Mailman core: > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: This "another exception occurred" is irrelevant. For more information on exactly what caused the 500 from core, you have to look in var/logs/mailman.log. There is presumably something wrong with that list's archivers configuration. This shouldn't happen, but without the error and traceback information from mailman.log, we don't know what the problem is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Confirmation emails aren't sent to users.

by Stephen J. Turnbull

Ibiam Chihurumnaya via Mailman-users writes: > Confirmation emails aren't being sent to users and there's nothing > in the logs that make it obvious what's happening. As I explained earlier, this backtrace > 233830 File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner [...] > 233908 File "/opt/mailman/venv/lib/python3.10/site-packages/mistune/core.py", line 214, in parse_method > 233909 assert lastgroup > 233910 AssertionError is a known issue with mistune, which used by HyperKitty to display messages from the archives. Whatever is happening with the confirmation messages, it's unrelated to this. - What confirmation messages are missing? Mailman may ask for confirmation if a user adds an email address via Postorius, if the user asks for a password reset from Postorius, if a user who is not logged in subscribes to a list (either by email or by Postorius), and there may be other cases. Please describe all that apply. - What makes you think that they are missing? Sometimes users or sites have filters that throw them away, or they may be swallowed by MTAs because of misconfigurations. - Is your "virgin" runner and "out" runner running? (Usually "ps aux | grep mailman" will list only the processes running under mailman. The full command at the end of the line will tell you the names of the runners each process is handling.) - Are there messages collecting in the "virgin" or "out" queues? - Are there messages collecting in the MTA queue (the mailq utility will usually tell you about those)? - Normally you would see log messages for outgoing confirmations in /opt/mailman/mm/var/logs/smtp.log. You might see errors in mailman.log if Mailman core is requesting the confirmations. If Postorius is requesting the confirmations, I think it would probably be in mailmanweb.log (Django has its own mail-sending facility, those don't go through Mailman core). -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 3 weeks

Re: Messages disappearing into hole??

by Mark Sapiro

On 8/30/20 6:15 AM, Ruth Ivimey-Cook wrote: > > I looked around the interface and decided to set up the sender as a > non-member, as that appeared to permit them to be "special" and outside > of the normal access rules for the list. Before I did that I could send > a message from this sender and that would be sent to me as list owner > for moderation, so both incoming (from my mailserver) and outgoing (to > it) can be completed. > > However, with a non-member who is auto-accepted the message is passed > from my mailserver to mailman and then disappears. I cannot find > anything in the logs to indicate what happened next. I have tried > setting the default non-member policy to both 'hold' and 'default' with > no change in that behaviour. The logs for the mailserver show the > message being sent to mailman; mailman's "smtp.log" shows an LMTP > message being received ok, and then nothing. > > Any ideas how to find out what is going on? I can share config if that > helps but not sure what would be useful. First, this is a bad way to configure an announce list because anyone can post by spoofing the authorized posting address. The better way is to set a list moderator password and post using an Approved: <password> header or pseudo header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> for details. As far as the disappearing message is concerned, it's hard to say. What is the non-member's moderation action? Unless it is 'list default' setting the list's default non-member policy has no effect. Also, if the non-member's address or a pattern matching it is in accept_these_nonmembers, that takes precedence over whatever the non-member's moderation action is. One guess about the disappearing message is content filtering may be removing all the message. What is the setting for Filter Action? > As a side-issue, at one point I added a regex matching the sender > address to the acceptable members list, but find that I cannot now > delete it (using postorius): If I delete the field and Save, it returns > on page refresh. There is an issue with Postorius. You can't empty these settings. If you clear the box or or have it contain only whitespace, Postorius won't change the prior setting. In order to remove the only entry in Postorius, you have to replace it with a bogus entry or you can remove it with `mailman shell`. I've just filed <https://gitlab.com/mailman/postorius/-/issues/444> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: list of subscribers

by Simon Hanna

On 02/04/2018 01:45 PM, Peter Münster wrote: > On Fri, Feb 02 2018, Mark Sapiro wrote: > >>> Yes, the question is rather: where can *normal* members (or moderators) >>> can see the subscriber list? >> Currently, they can't. If you think they should be able to, you can file >> an issue at <https://gitlab.com/mailman/postorius/issues/new>. > Thanks. Done. > > It seems, that even the owner of the list cannot get the full names of > the subscribers, only the email addresses. Is there any other > possibility for the owner (or the site admin) to get the subscriber list > with full names (perhaps with some Python scripting)? You should be able to use mailmanclient to get a list of subscribers with names. Names are optional though, if people signup without them you won't be able to get them. Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated. IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...

8 years, 3 months

Re: Digest Formatting

by Stephen J. Turnbull

mailman(a)manygoodideas.com writes: > 1) Is there a way to trigger a digest for a user (for testing > purposes)? Specifically, is there a function that can be > revealed via the REST api to an interface like Postorius and > Affinity? You can't trigger a digest to an individual member (unless they're the only active digest subscriber to the list, of course, so you can experiment on a test list if it's not specific to a particular list). I thought there was a way to trigger immediate distribution of a digest immediately, but I guess I'm remembering that from Mailman 2. Neither the Postorius management interface nor the core documentation suggests there's such a trigger in Mailman 3. > > 2) I have customized list:member:digest:header, but am not seeing > the custom text where I thought it should be. The documentation > seems to imply that both list:member:digest:header and > list:member:digest:footer surround each message in the digest Which documentation do you mean? As far as I know (Mark will have authoritative information if I'm wrong), the digest header and footer appear at the top and bottom of the *whole* digest message (ie, once each per digest), not surrounding or in the bodies of the component messages.

5 years, 6 months

Re: Verification Failed Error

by Odhiambo Washington

On Fri, 21 Dec 2018 at 03:25, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Thu, Dec 20, 2018, at 4:05 PM, brian(a)emwd.com wrote: > > Abhilash Raj wrote: > > > It should be pointing to Exim running on host, so > > > > > > EMAIL_HOST = 172.19.199.1 > > > > That fixed the network not found error. Thank you for your help there. > > > > Now I am back to the verification error: > > > > "smtplib.SMTPRecipientsRefused: {'brian(a)emwd.com': (550, b'Verification > > failed for <postorius(a)host.name.com>\nUnknown user\nSender verify > > failed')}" > > > > I am at a lost on how to get exim to allow mail sent from > > postorius(a)host.name.com. Obviously host.name.com is the mm3 domain that > > I am using. > > A quick search says that Exim is trying to verify that ` > postorius(a)host.name.com` > is a real mailbox (which I am assuming it is not), and rejecting the email > coming > from Postorius. > > You probably have > > verify = sender > > somewhere in your exim.conf, which is causing this. You can either modify > the > > DEFAULT_FROM_EMAIL > > in your settings_local.py so that it is a real address that Exim can > verify, or, > you can remove verify = sender from your Exim configuration. 2nd option > might > not be the best if you want to properly combat spam. > > Exim experts would be able to help you better with this. > > > > > Hi Brian, In postorius(a)host.name.com, please change the host.name.com to match the MM3_DOMAINS or whatever it is called in your MACROS. Remember, it has to be a VALID hostname that you will be using for Mailman3 lists. That, coupled with the IPs 172.19.199.x being in relay_from_hosts should let the address to pass verification with Exim. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

7 years, 4 months

Mailman-users search results for query "Postorius"