Search results for "Postorius" - Mailman-users

problem configuring mailman3 on debian bullseye

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hello all, I'm a blind server administrator living in Italy. I use mailman since 2010 and I was very happy for this list manager. When was released the version 3 I started to have many problems to configure it. In this days I installed a new server for my association and I have this problem that I don't know to solve. The server is a debian bullseye. I installed mailman3-full from the standard packege. I'm using nginx as web server. I configured mailman3 and mailman3-web wit https support. All is working fine, but if I attempt to subscribe someone it does not work. I send a subscription e-mail to the address list and I receive correctly the request to confirm subscription. When I reply to the request mailman log gives this error: requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /postorius/api/templates/list/listname.domain/list:user:notice:welcome (Caused by SSLError(SSLCertVerificationError("hostname 'localhost' doesn't match either of 'example.com', 'www.example.com'"))) The strange thing is that I configured a domain list.example.com and in the configuration files I put this domain. Mailman3-web works fine I can create lists and make settings. Have you an idea about this issue? Thanks -- Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it

1 year, 8 months

Re: Your Dashboard

by Mark Dadgar

On Feb 11, 2020, at 12:26 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. Awesome - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

Re: Ann: Mailman Core 3.3.5 is out

by Odhiambo Washington

@Eggert, I believe you used apt to install and so you have to wait for the package maintainer to avail the upgrades via apt. On Wed, Sep 29, 2021 at 7:48 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would > have > to bypass the Debian installer. Or will there be Debian packages > available? > Same question for Postorius 1.3.6 > > > Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > > Hey Everyone, > > > > I just tagged and uploaded Mailman Core 3.3.5 release. > > > > This release includes both bug fixes and some new features. A full list > of > > changes is available here: > > > > > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS > . > > html#news-3-3-5 > > > > You can install this version using pip: > > > > $ pip install mailman==3.3.5 > > > > The release tarball is available on PyPI as well: > > > > https://pypi.org/project/mailman/3.3.5/#files > > > > Thanks to everyone who made this release possible! > > > > Abhilash > > > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > > wrote: > > > > > > Hey Everyone, > > > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > > > This is identical to 3.3.5b1 in code, the only changes that have been > made > > > are in utility scripts and testing configuration.> > > > You can install this version using: > > > $ pip install --pre mailman==3.3.5rc1 > > > > > > If you want to download a release tarball, you can do so from here: > > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > > > This is the first (and only) planned release candidate for 3.3.5 > release. > > > The stable release is planned for next week. > > > > > > thanks, > > > Abhilash > > > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > > >> Hello Everyone, > > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from > now. > > >> I am planning for a 2 week beta period, after which I'll release the > > >> first RC and then stable a week after. Right now I am not planning to > > >> release a second beta version, but if there are several changes in > Core > > >> in the next week or so, then I might. This release includes a lot of > bug > > >> fixes and some new features. It also includes a security enhancement > > >> that improves the authentication of REST API by adding resistance to > > >> some timing channel attacks. A full list of changes in this version > can > > >> be found here[1]. > > >> [1]: > > >> > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > > >> and now the email templates are updated from the translated messages > in > > >> the .po files that we get from Weblate. Documentation for translators > is > > >> available here[2] if you want to help translate Mailman into your > native > > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > > >> > > >> This is a pre-release version, if you want to test it with your > setup, > you can install it using: > > >> $ pip install --pre mailman==3.3.5b1 > > >> > > >> If you want to download a release tarball, you can do so from here: > > >> https://pypi.org/project/mailman/3.3.5b1/#files > > >> > > >> This release received a lot of contributions from community, which I > am > > >> really happy about! I'd like to thank everyone who made this release > > >> possible!> > > > -- > > > thanks, > > > Abhilash Raj (maxking) > > > > -- > > thanks, > > Abhilash Raj (maxking) > > > > > _______________________________________________ > 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/ > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 1 month

Re: can't get mail into mailman3 in docker

by Stephen J. Turnbull

bob B writes: > Anyone have any ideas? First, what docker configuration are you using? One supplied by the Mailman project? If not, you need to tell us more about what's going on. If so, are there any containers other than those running the Mailman suite (Mailman 3 core, Postorius, HyperKitty)? In mydestination you have mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com I do not understand the "localhost.$mydomain" entry. I guess that's a Postfix-ism, but I can't find any documentation about it. You could try taking it out (this is a very random suggestion). You say you have no /etc/postfix-mailman.cfg. Where are you looking for it? That file will only exist in the container, not in the host OS. (If it were in the host OS, it would be located somewhere like /opt/mailman/core/postfix-mailman.cfg.) Try `find /opt/mailman/core -name postfix-mailman.cfg`, although "automatically" might mean it's generated in the container when it starts. Abhilash would know, but he doesn't seem to be available. I really don't think it's the issue because I assume "bmimailmandr1" is the Docker container running Mailman core. If so Postfix is connecting to the configured LMTP port on localhost which is what it's supposed to do from the configuration. Since the container's Postfix appears to be connecting to the right place but the connection is refused, that Mailman core may not be running. For more help you'll have to wait for Abhilash. Steve

3 years, 3 months

Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by Abhilash Raj

On Sun, Feb 28, 2021, at 10:17 AM, blackout69 wrote: > Hello everybody,I received this error message and from that moment the > maiilan3 has stopped working.I restarted the following services mailman3 > and mailman3-web and everything started working fine.Can you tell me > what is the problem my django server has encountered? What version of Hyperkitty are you running? It might be useful to include the versions of all the related Mailman packages, including: hyperkitty, django-mailman3, mailmanclient. > Internal Server Error: > /hyperkitty/list/direttivo(a)catania.linux.it/top-threads > > DoesNotExist at /hyperkitty/list/direttivo(a)catania.linux.it/top-threads > Thread matching query does not exist. > > Request Method: GET > Request URL: > https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t… > Django Version: 1.11.29 > Python Executable: /usr/bin/uwsgi-core > Python Version: 3.7.3 > Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', > '/usr/lib/python3.7/lib-dynload', > '/usr/local/lib/python3.7/dist-packages', > '/usr/lib/python3/dist-packages'] > Server time: Ven, 26 Feb 2021 20:10:53 +0100 > Installed Applications: > ('hyperkitty', > 'postorius', > 'django_mailman3', > 'django.contrib.admin', > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > 'rest_framework', > 'django_gravatar', > 'compressor', > 'haystack', > 'django_extensions', > 'django_q', > 'allauth', > 'allauth.account', > 'allauth.socialaccount') > Installed Middleware: > ('django.contrib.sessions.middleware.SessionMiddleware', > 'django.middleware.common.CommonMiddleware', > 'django.middleware.csrf.CsrfViewMiddleware', > 'django.middleware.locale.LocaleMiddleware', > 'django.contrib.auth.middleware.AuthenticationMiddleware', > 'django.contrib.messages.middleware.MessageMiddleware', > 'django.middleware.clickjacking.XFrameOptionsMiddleware', > 'django.middleware.security.SecurityMiddleware', > 'django_mailman3.middleware.TimezoneMiddleware', > 'postorius.middleware.PostoriusMiddleware') > > > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" > in inner > 41. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in > _get_response > 187. response = > self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in > _get_response > 185. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in > inner > 134. return func(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in > overview_top_threads > 196. 'threads': mlist.top_threads, > > File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" > in top_threads > 157. return self.cached_values["top_threads"]() > > File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in > __call__ > 59. return self.get_or_set(*args, **kwargs) > > File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" > in get_or_set > 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] > > File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" > in <listcomp> > 365. return [Thread.objects.get(pk=pk) for pk in thread_ids] > > File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in > manager_method > 85. return getattr(self.get_queryset(), name)(*args, > **kwargs) > > File "/usr/lib/python3/dist-packages/django/db/models/query.py" in get > 380. self.model._meta.object_name > > Exception Type: DoesNotExist at > /hyperkitty/list/direttivo(a)catania.linux.it/top-threads > Exception Value: Thread matching query does not exist. > Request information: > USER: blackout69 > > GET: No GET data > > POST: No POST data > > FILES: No FILES data > > COOKIES: > csrftoken = > 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' > sessionid = 'brhb9jd3ko9blnluuc6bz3c1627u6h22' > > META: > CONTENT_LENGTH = '' > CONTENT_TYPE = '' > CSRF_COOKIE = > 'tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb' > DOCUMENT_ROOT = '/usr/share/nginx/html' > HTTPS = 'on' > HTTP_ACCEPT = 'text/html, */*; q=0.01' > HTTP_ACCEPT_ENCODING = 'gzip, deflate, br' > HTTP_ACCEPT_LANGUAGE = 'it-IT' > HTTP_COOKIE = > 'csrftoken=tqNIiLrMWyYNHYhkmnmQfjRdd0AtCeCAAW46VOL24wk2g7Opl5LSZWB2dZ2p79Sb; > sessionid=brhb9jd3ko9blnluuc6bz3c1627u6h22' > HTTP_HOST = 'lists.catania.linux.it' > HTTP_REFERER = > 'https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/' > HTTP_TE = 'trailers' > HTTP_USER_AGENT = 'Mozilla/5.0 (Android 11; Mobile; rv:86.0) Gecko/86.0 > Firefox/86.0' > HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' > PATH_INFO = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' > QUERY_STRING = '' > REMOTE_ADDR = '2.38.155.170' > REMOTE_PORT = '39208' > REQUEST_METHOD = 'GET' > REQUEST_SCHEME = 'https' > REQUEST_URI = '/hyperkitty/list/direttivo(a)catania.linux.it/top-threads' > SCRIPT_NAME = '' > SERVER_NAME = 'lists.catania.linux.it' > SERVER_PORT = '443' > SERVER_PROTOCOL = 'HTTP/2.0' > uwsgi.core = 1 > uwsgi.node = b'glugct.catania.linux.it' > uwsgi.version = b'2.0.18-debian' > wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> > wsgi.file_wrapper = '' > wsgi.input = <uwsgi._Input object at 0x7f0e65582f00> > wsgi.multiprocess = False > wsgi.multithread = True > wsgi.run_once = False > wsgi.url_scheme = 'https' > wsgi.version = '(1, 0)' > > > Thank you in advance > > -- > blackout69 > > _______________________________________________ > 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)

3 years, 8 months

Mailman web interface / uwsgi

by Jan Eden

Hi, I followed the installation instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, which thankfully shielded me from configuring the Django applications for the web interface manually. All Django applications (postorius, hyperkitty, haystack etc) are loaded via mailman_web/settings/base.py, which is in turn referenced by the top-level settings file in /etc/mailman3. uwsgi is linked to mailman_web via /etc/mailman3/uwsgi.ini. So far, so good. I do not want to dive into the interaction between the various components and just want to switch from a http socket (http-socket = 0.0.0.0:8000) to a file socket (socket = /opt/mailman/mm/var/mailman.sock). After making this change in /etc/mailman3/uwsgi.ini, I applied it in the nginx proxy configuration proxy_pass http://127.0.0.1:8000; → proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock; and received an error message (as expected): 2022/11/25 18:39:12 [error] 2978606#2978606: *3 upstream prematurely closed connection while reading response header from upstream, client: 37.201.155.65, server: lists.eden.one, request: "GET /mailman3/lists/ HTTP/2.0", upstream: "http://unix:/opt/mailman/mm/var/mailman.sock:/mailman3/lists/", host: "lists.eden.one" There are obviously a couple of places where the http-socket on port 8000 is referenced (e.g. mailman_web/settings/mailman.py, /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the required changes when using a different (file) socket? Related question: My own (much simpler) Django applications use the following (e.g. in mysite_nginx.conf): upstream django { server unix:///private/tmp/mysite.sock; } location / { uwsgi_pass django; } instead of the "http://unix:/..." notation I tried for Mailman above. Is there any difference between the upstream/uwsgi_pass combination and the proxy_pass variant? Thanks, Jan

2 years

Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 9:22 PM, David Newman wrote: > > On my system that file lives here: > > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/urls.py It appears that you have installed following https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… and in that case, this is the file. > But the error persists after this addition and restarting MM3 and > mailmanweb and nginx: > > url(r'^mailman/', include('postorius.urls')), > > There is this 404 error in uwsgi.log: > > [pid: 73356|app: 0|req: 3/3] 127.0.0.1 () {48 vars in 1544 bytes} [Wed > Dec 22 21:13:48 2021] GET /mailman/admindb/listname => generated 5328 > bytes in 14 msecs (HTTP/1.0 404) 6 headers in 197 bytes (1 switches on > core 0) However, that's not the issue. You originally reported and I didn't look closely enough: > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. That URL is from a Mailman 2.1 installation. Are you still running Mailman 2.1? If so, you need to support Mailman 2.1's CGIs. In Apache, this would be something like ScriptAlias /mailman/ /parh/to/mailman/cgi-bin/ but nginx doesn't do that. You would need something like location /mailman/ { proxy_pass <something that can serve Mailman 2.1's CGIs.> } The something could be apache or ?? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: MM3 templates

by Mark Sapiro

On 2/16/23 11:14, Odhiambo Washington wrote: > On Thu, Feb 16, 2023 at 9:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> I don't know why? What's the content of the template table in the database? >> ``` >> SELECT * FROM template; >> ``` >> > > root@localhost [mailmansuite]> SELECT * FROM template; > Empty set (0.03 sec) Well, that eliminates one possibility. I still don't know why. Mailman should be using all the list: templates from /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ for messages from the kictanet(a)lists.kictanet.or.ke where the target language is English. Is the list's preferred language English and is the recipient's preferred language English? >> That's just wasting space. If you're putting the exact same templates in >> site/, domains/ and lists/, you might just as well delete the ones in >> domains/ and lists/ and Mailman will use the ones from site/. >> > > Well, space is cheap these days. More importantly, it could lead you to edit a template that isn't used because one of the other places is searched first. I would like to figure out what the issue is, but I don't know how to proceed. Have you checked /opt/mailman/mm/var/logs/mailman.log for anything relevant? If all else fails and we can't figure this out, you could always set the template(s) in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/22/23 09:32, Stephen J. Turnbull wrote: > > To diagnose, we really need to see that in context of the raw message > as received by the user. It was posted. The issue is the message declares Content-Transfer-Encoding: base64 but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output. > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? I note that the message also declares Content-Type: text/plain; charset="utf-8" and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8. I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with Subject: =?utf-8?q?The_results_of_your_email_commands?= and Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Docker Mailman3 installation frustration

by ccsmith＠cetsi.com

I've been working on installing Mailman3 for several weeks now, with limited success. I have tried various installation methods following instructions on numerous different web pages. My experience has been that the instructions are often conflicting and never complete. My best success has been with the Docker version, so that's what I'm going to concentrate on here. I'm running Ubuntu 16.04 (under Citrix XenServer), with Apache httpd and postfix. Following the instructions on https://asynchronous.in/docker-mailman/, I did the following: * created the directories "/opt/mailman/core" and "/opt/mailman/web", * created "/opt/mailman/core/mailman-extra.cfg" and inserted the suggested [mta] directives, * inserted the "transport_maps", "local-recipient_maps", and "relay_domains" entries in the /etc/postfix/main.cf file, * created the necessary apache config files, * cloned "https://github.com/maxking/docker-mailman", * ran "docker-compose up -d" At this point, I am able to connect with Postorius. All of the text and icons show up properly; all is well. It tells me (correctly) that "There are currently no mailing lists." When I click on the "Login" link at the top right, the "Sign In" page displays correctly. (Aside: Why do so many apps/sites have difficulty with choosing between "login" and "sign in" and, in fact, use both terms? It can really be off-putting to non-tech users... and me.) If I input an incorrect login, I receive (correctly) the message "The username and/or password you specified are not correct." However, if I input the correct sign-in, I receive: "Server Error (500)". Running "sudo docker exec -it mailman-web cat ../mailman-web-data/logs/mailmanweb.log" shows me: ERROR 2017-07-12 20:34:25,073 25 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) ... more stuff ... File "/usr/local/lib/python2.7/smtplib.py", line 747, in sendmail raise SMTPRecipientsRefused(senderrs) SMTPRecipientsRefused: {u'pacetechadmin(a)cetsi.com': (451, '4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure')} On the Docker host (ubuntuServer2), /var/log/mail.log shows: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: connect from unknown[172.19.199.3] Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <pacetechadmin(a)cetsi.com>: Temporary lookup failure; from=<postorius(a)localhost.local> to=<pacetechadmin(a)cetsi.com> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: connect from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_domains is unavailable. open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: table lookup problem Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: relay_domains lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp is unavailable. open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: regexp:/opt/mailman/core/var/data/postfix_lmtp lookup error for "root@localhost" Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: warning: transport_maps lookup failure Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: NOQUEUE: reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <root@localhost>: Temporary lookup failure; from=<root(a)localhost.local> to=<root@localhost> proto=ESMTP helo=<mailman-web> Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: lost connection after RSET from unknown[172.19.199.3] Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: disconnect from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 commands=3/4 And /var/log/mail.err is filling up with: Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_domains: No such file or directory Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory Any thoughts on what the problem is? Have I missed a step?

7 years, 4 months

Mailman-users search results for query "Postorius"