Search results for "Postorius" - Mailman-users

Re: Archive Policy not reflecting in Hyperkitty

by Nathan Dixon

The change to the archiving policy aren't reflected in Hyperkitty after many days for all the lists. The only error that I am seeing in the /web/mailmanweb.log is: INFO 2019-05-02 14:16:55,062 38 hyperkitty.tasks AsyncTask task "<function unlock_and_call at 0x7f5d8851f048>" with args "(<function update_from_mailman at 0x7f5d88544a60>, 'task:status:%s:%s', '<list address>')" and kwargs "{}" finished with errors. I'm not sure if that could be related? (I have changed the actual list address to <list address> for security reasons) Thank you On Sat, 4 May 2019 at 16:24, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Fri, May 3, 2019, at 8:38 AM, Nathan Dixon wrote: > > So the issue I am seeing is that when I set a lists archive policy to > > prviate, it isn't reflecting that in Hyperkitty. > > > > I am running the docker installation of Mailman, postorius and > hyperkitty. > > So I go into the docker instance of mailman-core and run this: > > > > python3 manage.py shell from hyperkitty.models.mailinglist import > > MailingList MailingList.objects.all().values_list('name', > 'archive_policy') > > > > And all my lists are showing '2', regardless of how I set the mailing > list > > archive policy. > > > > This might be a duplicate of > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > Am I missing something in my install? Or is this a bug? > > It can take upto an hour for this change to reflect in Hyperkitty. Did you > wait > for that long? > > This happens because Hyperkitty stores it's own data, and queries Mailman > Core periodically to fetch updates every hour. In future, we might be able > to > do this in more realtime fashion by using an event based pub/sub model. > But, > we are not there yet. > > > > > > Many thanks for your attention, > > > > -- > > > > *Nathan Dixon* MEng > > Senior Software Architect > > m: +44 (0)7402 690311 > > > > t: +44 (0)20 81231252 > > e: nathan.dixon(a)evadon.com > > w: www.evadon.com > > > > This e-mail and any attachments are confidential and may be protected by > > legal, professional or other privilege. If you are not the intended > > recipient you should not store it, copy it, re-transmit it, use it or > > disclose its contents, but should return it to the sender immediately and > > delete your copy from your system. The views expressed are those of the > > sender and not necessarily those of Evadon. Please note that whilst we > scan > > all e-mails for viruses we cannot guarantee that any e-mail is > virus-free. > > Please be advised that we expressly reserve the right to monitor email > > content for the purposes of ensuring compliance with legal requirements > and > > company policies and your sending to, or receiving from, us of any email > > constitutes your agreement to these terms. > > > > > > Evadon Dynamics Limited, registered in England No. 09494097. Registered > > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, > Sheffield, > > S1 2BJ > > _______________________________________________ > > 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) > _______________________________________________ > 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/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 11 months

Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:58 PM, Rafael Mora wrote: > > > > Does the rDNS PTR record should be placed in my Centos7 server? > > You can't do this. Hostgator or whoever manages the network (Telmex > Colombia S.A. ?) has to do this. > > > > I've created the DNS A record for lists.labbrands.com with the IP but I > > don't know the port that it uses so I can make a port redirect to my > local > > ip address wich is 192.168.1.42, do you know the port????? > > > You need to forward port 25 for SMTP mail delivery and if you want the > web UI (Postorius and HyperKitty) accessible from the outside, port 80 > for http and/or port 443 for https > < > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >. > I mean for incoming mail redirected from my hostgator hosting, because when I suscribe an email address MM3 sends a confirmation email, so I have to reply to be suscribed to the list. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 8 months

Re: new list not working

by Mark Sapiro

On 3/9/23 15:49, Christian via Mailman-users wrote: > Mail.log > > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from > box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: > client=box.ecovillage.cc[45.79.28.18] > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: > header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; > from=<christian(a)naturalintelligence.us> > to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP > helo=<box.ecovillage.cc> > Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: > message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: > from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) > Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from > box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: > to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed That's only the delivery of the post to Mailman. What about any log messages relating to messages from redlatinleg-bounces(a)lists.ccalternatives.org? Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: list of subscribers

by Peter Münster

On Mon, Feb 05 2018, Simon Hanna wrote: >> from django.contrib.auth.models import User >> user = User.objects.get(email='address(a)of.user') >> print(user.first_name) >> print(user.last_name) >> >> So, I'll try to make some loop over a list with email addresses, that I >> can get on the web interface. > > These are names that are saved in Postorius' (django) database and have > nothing to do with mailman. I know, but for my use case, it's just what I want, and it seems to work. > Displaying the names stored in django probably won't happen. > Matching the names in django with the members in lists > would require lots of code Really? I don't know Python, but wouldn't it be possible (just as an option) to do something like this: user = User.objects.get(email = ...) if user is found then print next to email address: user.first_name + user.last_name If there is no Django account associated to the email address, the columns would just be empty. I think, that my use case is perhaps not so special: whenever you manage a sports club, you'll need lists like - members(a)my-club.com - board(a)my-club.com - team-1(a)my-club.com - team-2(a)my-club.com - and so on Whenever there is a new member, the administrator will do the sign up with create_user(...) and subscribe him to the right lists. And the members (or the moderators) should be able to check the subscriber list sometimes. -- Peter

8 years, 2 months

Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

On Thu, Mar 30, 2023 at 6:55 PM Zaheer Abbas <zaheer.psg(a)gmail.com> wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. > > I believe it was previously available in mailman2 > via Accept_these_nonmembers attribute. > > But I cannot find this attribute anywhere on postorius. > > I am using mailman 3.2.2 > > Any help would be really appreciated. > > Best regards, > I would do this at the MTA level with either a router or a filter (milter in Postfix lingo): IF $sender_address_domain IS NOT "example.com" AND $recipient is "listname@domain" THEN send-to-dev-null. Exim (MTA) has a filter plugin to do this. I don't know about Postfix and Sendmail (as I am not willing to read on your behalf). It is easier that way. I don't remember is Mailman3 has the logic to deal with that, but maybe it does. If you did not manage to find it, then my solution is plausible, no? Filter at the MTA level. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

Add old email address

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > We've recently migrated our project's email lists from mailman2 to > mailman3. Given the project has been around for a few decades, many people > have used different email addresesses over the years, some of which they no > longer have access to. However, it would be useful to still be able to > associate those emails with a given account. Is there a way that I can do > this as an administrator of the mailman3 system? You can certainly add extra addresses to a Mailman 3 user (I don't know offhand whether/how an admin can do it through Postorius, but the core database certainly has that facility and the REST API allows it). However, this doesn't have the same semantics as in Mailman 2 because Mailman 2 doesn't have users at all. So as an admin how do you know which addresses correspond to particular users? More generally, what do you mean by "associate with an account", and why do you want to do it? Normally I would not ask the latter question, it's your business why you want to do it. But here I'm trying to get at what semantics you want. If I were going to do this for the kind of purposes I can imagine, it would be a matter of informing the users that this feature is available, and I'd ask the users to do it if they care. It seems you have some project goal in mind though. Steve

6 years, 1 month

Exception when rendering certain emails ([Django] ERROR (EXTERNAL IP): Internal Server Error...)

by Matt Blissett

Hi, I get exceptions logged when certain pages in the email archives (imported from Mailman 2) are opened. For example, this thread: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Could this be a bug in parsing the message? It's deployed using the maxking Docker packages, v0.5.3b1. Thanks, Matt Log follows: Internal Server Error: /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies No exception message supplied Request Method: GET Request URL: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Django Version: 4.2.20 Python Executable: /usr/bin/uwsgi Python Version: 3.12.10 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/usr/lib/python3.12/site-packages'] Server time: Wed, 30 Apr 2025 15:04:09 +0000 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', 'django.contrib.humanize', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google'] 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', 'allauth.account.middleware.AccountMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/views/thread.py", line 269, in replies replies_html = replies_tpl.render(context, request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 175, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/loader_tags.py", line 208, in render return template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 177, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1064, in render output = self.filter_expression.resolve(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 742, in resolve new_obj = func(obj, *arg_vals) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/templatetags/decorate.py", line 42, in render return mark_safe(text_renderer(content)) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 120, in __call__ return self.parse(s)[0] ^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 93, in parse self.block.parse(state) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 368, in parse_block_quote text, end_pos = self.extract_block_quote(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 345, in extract_block_quote end_pos = self.parse_method(m4, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 387, in parse_list return parse_list(self, m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 64, in parse_list groups = _parse_list_item(block, bullet, groups, token, state, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 174, in _parse_list_item block.parse(child, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 214, in parse_method assert lastgroup ^^^^^^^^^ Exception Type: AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies Raised during: hyperkitty.views.thread.replies Request information: USER: mailman-admin GET: sort = 'thread' last_view = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = '********************' sessionid = '********************'

11 months, 4 weeks

Re: Message Sent to A Re-Created List Results In Error

by Morris Jones

Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously. I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/m… See if that helps ... Best regards, Mojo On 12/14/20 9:38 PM, matthew(a)alberti.us wrote: > I checked all over the mailman core logs and couldn't find a > problem. But then I noticed that the 550 error was coming from dovecot-lmtp. > I should rename this thread because the actual problem seems to be unrelated > to re-created lists. > > It seems like the actual problem seems to occur in the following > situation: > > * Using Postfix > * Using Dovecot > * /etc/postfix/virtual includes addresses with same domain as mailman > lists. > * An e-mail address subscribed to a mailman list is in the > /etc/postfix/virtual file as an alias (possibly also if destination address > for an alias). > * (Possibly related) E-mail address is also one of the list owners. > > In that environment, Postfix seems to check only 'virtual_transport' > list, which in my case is dovecot-lmtp, and when it doesn't find the mailman > listname@domain entry in there, it sends a 550 user unknown. It seems to be > that it isn't getting passed to 'transport_maps', which is mailman-lmtp. > > When I remove that one address (that is in /etc/postfix/virtual) > from the list of subscribers, I'm able to post again. Interestingly enough, > when I put it back in as a subscriber. I'm still able to post. So it seems > unsubscribing and re-subscribing that address fixed it, or adding an > additional list owner and deleting it fixed it, or some combination of > those. > > I know this might be shaping up to be a very unlikely scenario. But > basically the account is mine, an admin, doing testing before/after a > deployment.. I'll try to create a few test procedures to document the method > to reproduce the problem, and also hopefully fix it. If I can do that, I'll > open another thread. This could also be a postfix config error of some kind, > which is definitely possible if not likely. > > Thanks for reading. > > - Matt Alberti > > > > -----Original Message----- > From: Abhilash Raj <maxking(a)asynchronous.in> > Sent: Monday, December 14, 2020 11:42 PM > To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> > Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error > > > > On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us > <mailto:matthew@alberti.us> wrote: >> I created a list in the Postorius interface, used it, and then deleted >> it. A week or so later, I re-created the list, and things were fine >> thru the creation and subscription process. But when I sent a message >> to the list, a >> "550 user unknown" error was sent back. > > Can you share more error details from the Mailman logs? If 550 error > response was sent, there must be some internal error traceback in the logs. > >> >> >> I tried to determine if this is a known issue by searching the issues >> in Gitlab; but didn't find anything. But wanted to ask if this was a >> known issue or not? > > I personally don't remember seeing such an issue, but Mark or others might > know. > >> >> >> >> Thanks. >> >> >> >> - Matt Alberti >> >> _______________________________________________ >> 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/ >> > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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/ > _______________________________________________ > 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/ > -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 4 months

Mailman-users search results for query "Postorius"