Search results for "Postorius" - Mailman-users

Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > > I'm not sure what you mean by drop and recreate the databases. You > should just drop the `social_auth*` tables, or if there's nothing in the > database you want, just starting with an empty database should work. Very good! Thank you very much, I got a bit further. The database contained a couple of test lists that I can recreate, so nothing of value. The strange thing was that drop database followed by create database did not yield an empty database in Postgres. I probably forgot a commit somewhere. I got a bit further. The problem with not being an expert on Django is that the configuration of all web frameworks is that is a bit involved. I have no experience of Django outside of this and I just want to get it running in this case. Now I get the following errors in the mailman_web-log, somehow complaining on the url mapping. ERROR 2017-03-31 00:51:31,558 exception 2456 140113416898304 Internal Server Error: /mailman3/lists/ Traceback (most recent call last): [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/template/defaulttags.py", line 458, in render url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/base.py", line 91, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/resolvers.py", line 497, in _reverse_with_prefix raise NoReverseMatch(msg) NoReverseMatch: Reverse for 'hk_user_login' not found. 'hk_user_login' is not a valid view function or pattern name. The Django 1.18 points to a Django 1.11rc1, should probably be mentioned. My urls.py (a copy from the docs, I think) from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin # Comment the next two lines to disable the admin: #admin.autodiscover() urlpatterns = [ url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), ] cheers // David

8 years, 2 months

bypassing rules on an individual basis

by Stephen J. Turnbull

via Mailman-users writes: > I have a mailing list that, due to specific circumstances, has a > requirement to allow messages from a user that sends messages with > no subject. Do you mean "any user who sends a message with no subject", or are there specific users who do this? If there is one such user (or a handful), and you trust that user not to abuse the privilege, you can directly pre-approve that user from Users menu in the list configuration (see Mark's post for details). This also works if there is no Subject field at all! If you don't know who might post with no subject (or there are annoyingly many, especially if some are less than clueful), you could use the header match: > I also added header filters to immediately accept the message, but > they still get held. Specifically, the rules I defined are: > [...] Those were all incorrect. What you want is > Header, Pattern, Action > > subject, ^\s*([[{(]?no[_ ]subject[]})]?)?\s*$, Accept Immediately I believe the surrounding whitespace is stripped, so the "\s*" are unnecessary but do no harm since they match 0 spaces. However this has two potential flaws: it doesn't work if there is no Subject field at all, and it allows anyone to bypass all of Mailman's checks. Finally, there is the "pre-approved" mechanism. It's a little bit complicated because it requires setting a moderator password, which has to be done using the Python interpreter; there's no option in Postorius. It also requires a small bit of clue from the poster to add the password to the post, preferably in the header (but it can also be the first line). In either case the password is removed before distribution. For details, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… > Is there a better way to bypass this rule? Each of the three approaches has advantages and disadvantages, so you'll have to decide. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

Re: Masking email addresses in the archives

by Odhiambo Washington

On Mon, May 26, 2025 at 6:38 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Odhiambo Washington via Mailman-users writes: > > > I must have missed this if it was ever discussed, but is it > > possible to mask the list members' email addresses in the archives? > > I saw Mark's response and Danil's issue, but I would recommend not > doing it even if available. People often do want to contact the > author of a post, and sometimes the CCs, but it's not very effective > in preventing spammers from harvesting. > > If you control subscription and generally trust the the subscribers, > then making the archives private can be moderately effective. > Anonymization is more effective, but of course you completely give up > the ability of subscribers to contact posters. And even then, many of > those addresses you've masked are going to be available to the > spammers because they're going to be in hacked address books and > random S3 buckets with lax permissions and on lists that you don't > run, or shared/sold by unscrupulous Internet sites. > > The other thing you can do (if you're confident in your own spam > filters) is to assign your subscribers addresses at your domain, and > forward them on. But Gmail probably does spam filtering better. And > of course your traffic will increase to a greater or lesser extent. > I have realized that much as this particular list's archives are publicly accessible, no one can view the members' addresses unless they log in to Postorius. That is safe enough. Initially I was worried because I was able to open a thread, click on the poster and see their email address, but I had forgotten that I was logged in as the List Admin. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 week, 5 days

Re: Importing Mailman 2 Lists apart from Django

by Brian Carpenter

On 4/30/20 11:59 AM, Mark Sapiro wrote: > On 4/30/20 7:59 AM, Brian Carpenter wrote: >> Hello Mailman Users, >> >> Are there instructions on importing a Mailman 2 list into a Mailman 3 >> core installation only? Does the import21 script not need >> Django/Postorius/Hyperkitty? > > import21 requires only Mailman core. > > >> It seems Django is required to import archives I guess because of the >> use of Hyperkitty. How about importing archives without having a Django >> installation? Is that what the prototype archiver for? > > The only current archive import we support is `django-admin > hyperkitty_import` which imports archive .mbox files into HyperKitty. > > The prototype archiver is just a maildir format collection of messages. > > Converting an mbox file to a maildir is trivial. > > from mailbox import Maildir, mbox > mb = mbox('/path/to/mbox', create=False) > md = Maildir('/path/to/maildir', create=True) > for msg in mb: > md.add(msg) > > >> We are getting ready to start working on a custom forum application for >> Mailman 3 (called Empathy) and I am would like to import some mailman 2 >> archives into the development server to work with. > > First you have to decide how Empathy will store messages. Look at > <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. > This is how HyperKitty gets messages from a mbox and adds them to its > database. It's actually fairly simple - a lot of the code is handling > exceptions due to defective messages. > > Presumably Empathy will have a method for adding a message to the > archive, so importing is just getting messages from the mbox and using > Empathy's method to add it. > Thank you Mark. Your response was very helpful. This should help my developer make some decisions. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 1 month

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/ >

7 years, 1 month

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.

5 years, 1 month

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)

4 years, 8 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 Дилян

10 months

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

4 years, 7 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

6 years, 1 month

Mailman-users search results for query "Postorius"