Search results for "Postorius" - Mailman-users

Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > 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, 3 months

Can it work on FreebSD

by Stephen J. Turnbull

Peter Fraser writes: > Hi All > > I would really be interested in getting this working of FreeBSD. I find > the BSD’s to be very stable and easy to maintain. Please could anyone > point me to any document or suggestions to get it working on FreeBSD? > Much Appreciated. Mailman 3 is a collections of pure Python applications, and should be installable from source and work as is on any POSIX system. Documents on mailman.readthedocs.io should support installation and operation on any such system. If you find anything that doesn't work on FreeBSD, please let us know. Specifically you need an MTA that supports receiving SMTP and sending LMTP such as Exim4 or Postfix (I assume Sendmail and qmail also work but don't know of much use of those among Mailman 3 sites), a webserver that supports the Python WGSI standard, such as Apache with mod_wsgi or gunicorn (other components such as nginx or uswgi also figure in some configurations), and an RDBMS such as PostgreSQL or MySQL. I would guess the most "vanilla" stack is Mailman 3 suite (core, Postorius, and HyperKitty) + Postfix + Apache + mod_wsgi + PostgreSQL, but that's not the highest-performance configuration, and of course you may have specific requirements or preferences for MTA or webserver. The most important choice is the RDBMS. We have very little experience with changing those after the initial installation, and there are minor differences among them so it's possible (unlikely but possible) that you would have trouble if you change your mind after initializing mailing lists. I would recommend PostgreSQL, as at least some configurations of MySQL cause some Mailman output documented as alphabetically ordered to come out unordered.[1] However, if you like MySQL, I doubt you will lose much by using it. The other components are pretty much mix-and-match as you please, even after you've initialized mailing lists. Footnotes: [1] This appears to be a Mailman bug, which as far as I know is still pending. According to MySQL documentation, Mailman's SQL is not conformant to the SQL standard, but it's not easy to fix since the SQL is written by a 3rd-party library.

6 years, 3 months

Re: Template path

by Abhilash Raj

On Thu, Sep 17, 2020, at 9:33 AM, Seth Seeger wrote: > Hello everyone, > > I’m running Mailman from Docker containers, without much customization. > (Postorius 1.3.3, Core 3.3.1, API 3.1, Python 3.8.5). I’ve created a > list:user:notice:welcome template, and when I try to confirm a > subscription, I get an error. > > I followed previous emails on this list which told me to set > POSTORIUS_TEMPLATE_BASE_URL in /opt/mailman/web/settings_local.py, but > that doesn’t seem to make any difference. (I set it to a different > value and the error message didn’t change. I also tried setting it in > /opt/mailman/core/settings_local.py to no effect. After each change, I > restarted mailman-web and mailman-core containers.) > > From within mailman-web and mailman-core containers, I can reach > “mailman-web:8000”. > > In the webpage, I see: Mailman REST API not available. Please start > Mailman core. > > In /opt/mailman/core/var/logs/mailman.log, I get: > > [17/Sep/2020:16:23:29 +0000] "GET /3.1/lists/xxx.example.com HTTP/1.1" > 200 416 "-" "GNU Mailman REST client v3.3.1" > Sep 17 16:23:35 2020 (48) deque: > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 426, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.8/http/client.py", line 1347, in getresponse > response.begin() > File "/usr/lib/python3.8/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.8/http/client.py", line 268, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.8/socket.py", line 669, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/requests/adapters.py", line > 439, in send > resp = conn.urlopen( > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 724, in urlopen > retries = retries.increment( > File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line > 403, in increment > raise six.reraise(type(error), error, _stacktrace) > File "/usr/lib/python3.8/site-packages/urllib3/packages/six.py", line > 735, in reraise > raise value > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 670, in urlopen > httplib_response = self._make_request( > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 428, in _make_request > self._raise_timeout(err=e, url=url, timeout_value=read_timeout) > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 335, in _raise_timeout > raise ReadTimeoutError( > urllib3.exceptions.ReadTimeoutError: > HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. > (read timeout=5) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line > 69, in __next__ > return step() > File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", > line 332, in _step_do_subscription > self.member = self.mlist.subscribe( > File > "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", > line 505, in subscribe > notify(SubscriptionEvent( > File "/usr/lib/python3.8/site-packages/zope/event/__init__.py", line > 32, in notify > subscriber(event) > File "/usr/lib/python3.8/site-packages/mailman/app/membership.py", > line 176, in handle_SubscriptionEvent > send_welcome_message(mlist, member, member.preferred_language) > File "/usr/lib/python3.8/site-packages/mailman/app/notifications.py", > line 51, in send_welcome_message > welcome_message = wrap(getUtility(ITemplateLoader).get( > File "/usr/lib/python3.8/site-packages/mailman/model/template.py", > line 188, in get > contents = getUtility(ITemplateManager).get( > File > "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3.8/site-packages/mailman/model/template.py", > line 110, in get > contents = protocols.get(actual_uri, **auth) > File > "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line > 38, in get > response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) > File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in > get > return request('get', url, params=params, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in > request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/sessions.py", line > 530, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3.8/site-packages/requests/sessions.py", line > 643, in send > r = adapter.send(request, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/adapters.py", line > 529, in send > raise ReadTimeout(e, request=request) > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', > port=8000): Read timed out. (read timeout=5) > [2020-09-17 16:23:35 +0000] [48] [ERROR] Socket error processing > request. > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 426, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.8/http/client.py", line 1347, in getresponse > response.begin() > File "/usr/lib/python3.8/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.8/http/client.py", line 268, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.8/socket.py", line 669, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out > > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/requests/adapters.py", line > 439, in send > resp = conn.urlopen( > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 724, in urlopen > retries = retries.increment( > File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line > 403, in increment > raise six.reraise(type(error), error, _stacktrace) > File "/usr/lib/python3.8/site-packages/urllib3/packages/six.py", line > 735, in reraise > raise value > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 670, in urlopen > httplib_response = self._make_request( > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 428, in _make_request > self._raise_timeout(err=e, url=url, timeout_value=read_timeout) > File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", > line 335, in _raise_timeout > raise ReadTimeoutError( > urllib3.exceptions.ReadTimeoutError: > HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. > (read timeout=5) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/gunicorn/workers/sync.py", > line 135, in handle > self.handle_request(listener, req, client, addr) > File "/usr/lib/python3.8/site-packages/gunicorn/workers/sync.py", > line 191, in handle_request > six.reraise(*sys.exc_info()) > File "/usr/lib/python3.8/site-packages/gunicorn/six.py", line 625, in > reraise > raise value > File "/usr/lib/python3.8/site-packages/gunicorn/workers/sync.py", > line 176, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File > "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3.8/site-packages/mailman/rest/wsgiapp.py", line > 193, in __call__ > return super().__call__(environ, start_response) > File "/usr/lib/python3.8/site-packages/falcon/api.py", line 269, in > __call__ > responder(req, resp, **params) > File > "/usr/lib/python3.8/site-packages/mailman/rest/sub_moderation.py", line > 88, in on_post > self._registrar.confirm(self._token) > File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", > line 559, in confirm > list(workflow) > File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line > 69, in __next__ > return step() > File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", > line 332, in _step_do_subscription > self.member = self.mlist.subscribe( > File > "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", > line 505, in subscribe > notify(SubscriptionEvent( > File "/usr/lib/python3.8/site-packages/zope/event/__init__.py", line > 32, in notify > subscriber(event) > File "/usr/lib/python3.8/site-packages/mailman/app/membership.py", > line 176, in handle_SubscriptionEvent > send_welcome_message(mlist, member, member.preferred_language) > File "/usr/lib/python3.8/site-packages/mailman/app/notifications.py", > line 51, in send_welcome_message > welcome_message = wrap(getUtility(ITemplateLoader).get( > File "/usr/lib/python3.8/site-packages/mailman/model/template.py", > line 188, in get > contents = getUtility(ITemplateManager).get( > File > "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3.8/site-packages/mailman/model/template.py", > line 110, in get > contents = protocols.get(actual_uri, **auth) > File > "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line > 38, in get > response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) > File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in > get > return request('get', url, params=params, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in > request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/sessions.py", line > 530, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3.8/site-packages/requests/sessions.py", line > 643, in send > r = adapter.send(request, **kwargs) > File "/usr/lib/python3.8/site-packages/requests/adapters.py", line > 529, in send > raise ReadTimeout(e, request=request) > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', > port=8000): Read timed out. (read timeout=5) > > > > What’s the next step to get templates working? Are you using the provided docker-compose file or are you using something else like Kubernetes to deploy the container images? It seems like your mailman-core container isn't able to talk to Postorius on the default dns name, mailman-web, in the provided docker-compose file. These dns names are setup by default if you are using the docker-compose.yaml provided with the repo, but would otherwise needs either changing the value of POSTORIUS_TEMPLATES_BASE_URL or manually setting up the mailman-web DNS in the `/etc/host` of the mailman-core container. > Thank you, > Seth > > > _______________________________________________ > 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, 10 months

Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello, Has anybody managed to use the Django-Allauth Yahoo provider to authenticate towards Mailman3? I have integrated mailman3/django-allauth/gmail — it works. I want in the same way to integrate mailman3 with yahoo mail. As advised at https://docs.allauth.org/en/latest/socialaccount/providers/yahoo.html , in yahoo I register an application with redirect URL https://l.bapha.be/mm3/accounts/yahoo/login/callback/ , then I add credentials under mm3/admin/socialaccount/socialapp/: client ID and Private Key. I append in settings.py:INSTALLED_APPS = [… 'allauth.socialaccount.providers.yahoo' ]. After I do all of this, I eventually visit /mm3/accounts/login/?next=/mm3/postorius/lists/at.l.bapha.be/, click on Yahoo: “Sign In Via Yahoo . You are about to sign in using a third-party account from Yahoo.” → [Continue]. Now at https://login.yahoo.com I enter user name and password. Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: Messages: Confirmation of email address sent to ...(a)yahoo.com Menu: Entrance \r\n New registration Confirm your email address: We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I have indeed received an email, which states: New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. Any idea what can I improve? In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? Greetings Дилян

2 years

Re: migration from 2.1 - owners and moderators

by Brian Carpenter

On 10/23/20 8:31 PM, Alex Schuilenburg via Mailman-users wrote: > We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It > may be something different in the way mailman3 works, or a > misconfiguration on my part. > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the > owners dont get notified of held messages - unlike 2.1 where they > did. Is this a change or is there something I am missing in the > configuration? > > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes > 6.5 minutes to run* - but I doubt this is the cause. > > While for the moment I have found the held messages in files in > /var/lib/mailman3/messages and figured out which lists are in need of > attention (and notified the owners), it seems I may have to do a bit > of coding myself to walk through the lists and notify owners when > their list is in need of attention. There must surely be something > that does this already - or is this moderators only in mailman3? > > Guidance appreciated. > > Thanks > > -- Alex > > * From the list I realise this is because I am still using the default > whoosh backend to haystack and need urgently to switch to xapian or > solr, but the info on how to get this working for a noob like me is > unfortunately lacking Hi Alex, List owners should be receiving moderation notifications and are able to moderate messages when they log into Postorius. Have you checked your MTA logs to see if they are or are not being sent out? If you don't mind having some paid assistance, I may be able to assist you with getting Xapian up and running. We use Xapian on our vanilla MM3 servers and Elasticsearch on our MM3 Affinity/Empathy servers. You can contact me off list if you are interested. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 9 months

Report problems NOW if you're not *sure* it's *not* a bug

by Stephen J. Turnbull

Nathan Dixon writes: > Am I missing something in my install? Or is this a bug? One of us will get to it specifically "soon" (we're all at PyCon YEAH! so not paying much attention BOO!) Right now I HAVE SOMETHING I WANT TO SAY TO YOU ALL: Sprints are coming up! This is your chance to report bugs and maybe get something done quickly. (Not all bugs get fixed quickly, sorree. But this is the best chance ) RFEs are welcome, too. What's a bug? Well, if you're sure it's NOT a bug, don't report it, post to this mailing list and get help on what you can do to make your life better. That's the best way, because some of the users are smarter and more experienced and more available than the developers. If you're pretty sure it is a bug, report it at https://gitlab.com/mailman/mailman/issues https://gitlab.com/mailman/postorius/issues https://gitlab.com/mailman/hyperkitty/issues Do your best but don't get too frantic about picking the right one. We can move (close and re-report on the correct component) issues. If it's somewhere in the middle, do both! First, report on the issue tracker so you can cite it in the mailing list post. Then post to the mailing list because it might not be a bug, and the logic above applies. If you've got the time, Google for "howto report bugs". It is time well-invested, because the more useful information you provide up front, the faster we can diagnose the harder bugs, and thus the faster we can fix them or provide a workaround. Again, don't get frantic about it, we'll ask for more information if we need it. And yes, I should ensure there's a HOWTO-BUG on the sites with both generic advice and common Mailman requirements for diagnosing bugs. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 3 months

Re: Digests not working correctly

by Joel Lord

On 6/4/2023 9:25 PM, Mark Sapiro wrote: > On 6/4/23 11:45, Joel Lord wrote: Thanks for the explanation on size-triggered digests. >> Periodic is much more complicated, even to explain. I have the cron >> job running nightly at 11:00 PM and it certainly seems to be working, >> except for one really odd thing. The list also definitely has >> periodic digests enabled in the web UI. This is a very bursty list, >> so it will go mad with traffic for a few weeks and then will go mostly >> idle for a month or so. The first digest of a burst is definitely >> size-triggered, but pretty reliably it has the last few messages from >> the previous burst in there. So the one I got today had three >> messages from today and one message from May 4th. But that May 4th >> message should have gone out at 11:00 PM on May 4th with the daily >> digest and then gotten flushed from the pending digest queue, right? > > That's correct. Do you ever get periodic digests sent at 11:00 PM? If > not, there is some issue either with configuration or something. If you > get them sometimes, I don't know what could be wrong. The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent. There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell. Just to inform things: (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8 -- Joel Lord

3 years, 2 months

Re: Filter who can send on mailman3 list?

by Ruth Ivimey-Cook

Marcus, I'm with you in not understanding Mark's instructions -- I think there is a typo somewhere :-) To create a non-member user in Mailman, Go to the List Settings page in Postorius, select Non-members from the User menu, and add a user there. Of course, that does nothing for your email system, which must also be configured. I would very strongly encourage you to have the no-reply address be 'real' in the sense that the email system will agree it is valid and deliverable, or some recipient email servers will refuse to accept email from that address, either. The right thing is for email to that address accepted as normal and then immediately discarded. You could send back a message "this address is not monitored" but there is an issue with spam backscattering which makes that less good than it first seems. Regards, Ruth On 06/04/2021 10:00, marcus.granath(a)gmail.com wrote: > Thank you @Mark Sapiro for you quick reply. > > So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: > > Settings -> Message Acceptance > > "Default action to take when a member posts to the list": "Hold for moderation" > "Default action to take when a non-member posts to thelist": "Hold for moderation" > > Members -> Administration options -> Moderation: "List default" > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? > > Also, how do I create a "non-member" user "no-reply(a)abc.com"? > Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there? > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 4 months

Re: Unsubscribe Notifications to List Owners and Members

by Brian Carpenter

What list are you trying to unsubscribe from and how are you doing it? On 10/22/20 4:58 PM, Jerry Koutavas wrote: > > No offense but been trying to unsubscribe for months, nothing happens > > *From:*Brian Carpenter [mailto:brian_carpenter@emwd.com] > *Sent:* Thursday, October 22, 2020 4:56 PM > *To:* Mailman users <mailman-users(a)mailman3.org> > *Subject:* [MM3-users] Unsubscribe Notifications to List Owners and > Members > > It seems that the only time an unsubscribe notification is sent to a > list owner and/or list member is when a list member sends an email to > lisname-unsubscribe@listdomain <mailto:lisname-unsubscribe@listdomain> > and that list member is not registered > with Affinity/Postorius. Can anyone confirm this and if confirmed, is > this considered a bug? > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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/ > > ------------------------------------------------------------------------ > > *Total Control Panel* > > > > Login <https://asp.reflexion.net/login?domain=ascii.com> > > To: jk(a)ascii.com > <https://asp.reflexion.net/address-properties?aID=10188568&domain=ascii.com> > > From: mailman-users-bounces+jk=ascii.com(a)mailman3.org > <mailto:mailman-users-bounces+jk=ascii.com@mailman3.org> > > > > Message Score: 70 > > > > High (60): Fail > > My Spam Blocking Level: Medium > > > > Medium (75): Pass > > > > > Low (90): Pass > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-address=1&hID=458079…> > this sender / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-address=1&hID=…> > this sender enterprise-wide > > > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-domain=1&hID=4580794…> > mailman3.org / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-domain=1&hID=4…> > mailman3.org enterprise-wide > > > > /This message was delivered because the content filter score did not > exceed your filter level./ > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 9 months

Re: Newbie hyperkitty question

by Mark Sapiro

On 1/11/22 8:27 AM, Stephen Daniel wrote: > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. In Postorius, in the list's `info` view can you click the Archives button and see archived messages? That's HyperKitty. If the messages aren't there with the hyperkitty archiving option enabled, check `mailman.log` for why. Also do messages from the list have an Archived-At: header? > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. No this says the prototype archiver is working. It says nothing about Hyperkitty. > So, this opens up a raft of questions on hyperkitty: David Newman has answered some of this, but ... > - How do I tell if hyperkitty is actually running? It doesn't actually run. it is a Django web UI and a web API that serves things on request. > - Does hyperkitty have a web-UI for admins or users? How would I access > it? See above. > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? No, not really. > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? Messages are kept forever unless you do something to delete them. HyperKitty's messages are stored in the database configured in the DATABASES setting in your Django settings. How you backup the database depends on the database manager. You already found the prototype archiver's messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Mailman-users search results for query "Postorius"