Search results for "Postorius" - Mailman-users

Re: Maximum number of recipients Setting

by Brian Carpenter

On 4/3/21 5:04 PM, Mark Sapiro wrote: > On 4/3/21 1:45 PM, Brian Carpenter wrote: >> I have run several tests. It looks like on the 'Maximum number of >> recipients' setting, a 2 means 1. If I set it to 2, I can have the >> listname(a)listdomain.com only. If I have a CC, it comes to me for >> moderation. If I set it to a 3, I can send out to >> listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus >> the listname(a)listdomain.com address, it comes to me for moderation. > > I understand it's confusing, but it's been that way since the beginning > of Mailman 2.1. The docs at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> > say "For backward compatibility, the message must have fewer than the > maximum number of explicit recipients." > > I agree the description in Postorius could be clarified see > <https://gitlab.com/mailman/postorius/-/issues/515>. > That explains it. Thanks for solving this mystery. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

Re: Mailman 3 localization

by Simon Hanna

> Thanks for the reply, Simon! We were thinking of using plain .po-files > too, however, we couldn't find the matching "src" folder in our > installation, do you have any more details where it or the .po-files > may also be located? What component are you talking about? For Postorius and Hyperkitty you should be able to create the files needed according to this https://docs.djangoproject.com/en/2.0/topics/i18n/translation/#message-files First run "django-admin makemessages -l de" to create the .po files and after editing "django-admin compilemessages -l de" to compile them. You should be fine doing that in your production django-project. Otherwise you can clone the frontend projects and run the commands inside the project folders. (src/postorius or hyperkitty/). I know the second option works, since that's what I'm doing (I'm deploying from the git heads) but doing that in the production projects (where manage.py is located) should generate the same files. It might generate files for dependencies as well... As for core, I only know how to translate the templates. I have no idea how the messages included in the source code should be translated.

8 years, 2 months

Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > > 1. If I do not set up 'individual' or 'full' personalisation, all is > well and the default footer templates are expanded as expected. However > setting up personalisation causes template expansion to fail > completely, and messages get sent with a blank expansion. Your mailman-debug.patch makes changes to mailman/handlers/decorate.py including wrapping all the relevant code in a try:/except: that logs any exception. If you set the level for logging.error to debug, what do you get in the log? This issue doesn't occur in the unpatched code on my servers - personalized footers work fine - so I think the problem must be something in your patch. > 2. I would find the postorius UI much easier to cope with if the > default template was 'populated' into the UI wherever it was non-blank, > rather than the UI starting off as if no templates were defined at all. This is <https://gitlab.com/mailman/postorius/-/issues/366>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: mailman3 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

Re: Moderate mails from owner

by Henrik Rasmussen

Mark Sapiro wrote: > This can happen in a few ways., If this list was originally imported > from Mailman 2.1 by the 'mailman import21' command, there may be a > legacy accept_these_nonmembers attribute for the list. If so, and if a This makes sense. The list was in fact imported from Mailman 2.1. > You need to check the list's accept_these_nonmembers attribute and the > non-member address's moderation action. > > If you have recent Postorius, you can see nonmembers and their options > from the 'users' -> Non-members view. I currently have Postorius 1.2.2 so I don't have it yet. > mailman shell -l list.example.com The sender is in the list of accept_these_nonmembers, however the command memb.moderation_action = m.default_nonmember_action doesn't seem to remove it from accept_these_nonmembers. bash-4.3# mailman shell -l [LISTNAME].lists.example.com Welcome to the GNU Mailman shell The variable 'm' is the [LISTNAME].lists.example.com mailing list >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] >>> memb = m.nonmembers.get_member('listadmin(a)senderdep.example.com') >>> memb.moderation_action <Action.accept: 3> >>> memb.moderation_action = m.default_nonmember_action >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] -- Henrik

7 years, 4 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > When I want to get to Mailman Starting Page now I need to Enter the > following URL: https://mailman.xyz.de/mailman3/ to be directly > redirected as expected to > https://mailman.xyz.de/mailman3/postorius/lists/ -> works. > > Problem: When leave out the slash at the end and I ONLY enter the > following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly > redirected to a page, taht does not exist: > https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > Where can I change this misbehaviour? In Apache-conf everything seems as > it'S in the docs, for the vHost I do not have any other custom settings. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: How to configure an announce-only list?

by Mark Sapiro

On 4/28/26 5:17 PM, Craig Leres via Mailman-users wrote: > I want to create a mailing list that is used for announcements only. I'd > like attempts to post to be rejected with a notification. > > I was able to set the list pw and verify it works with the Approved > header using this reference: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/ > docs/approved.html > > I find that if both: > > Default action to take when a member posts to the list > Default action to take when a non-member posts to the list > > are set to "reject (with notification)", the approved header is ignored > and messages are always rejected (posted via "mailman inject") This should not be the case. The message is checked for an Approved: header prior to the member/nonmember checks. > Would it be bad to test the approved header before rejecting a message? > Essentially always accept a message with a valid approved header? Is > there another way for me to achieve this? That's the way it should be working. There is a potential issue if the password in the Approved: header when encrypted doesn't match the encrypted value in the lists moderator_password attribute, it is treated as if there were no Approved: header. This is a bug <https://gitlab.com/mailman/mailman/-/work_items/1276>. I.e., the message should be rejected but with a reason indicating the password was wrong. > On another front, I'm unable to have messages posted via "mailman > inject" use postorius created list templates. Would it be difficult to > add this functionality? That should not be the case. Are you saying messages posted via email use Postorius created templates, but messages posted via mailman inject do not? If the templates are used for messages posted via email, they should also me used for messages posted via mailman inject. Have you verified that the templates are used for messages posted via email? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Stefan Bauer

Dear Users, trying to update mailman3 to lastest version, we fail during mailman-web migrate with: Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower...Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email We found a workaround to fake the migration with migrate --fake Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower... FAKED Applying account.0007_emailaddress_idx_email... FAKED Applying account.0008_emailaddress_unique_primary_email_fixup... FAKED Applying account.0009_emailaddress_unique_primary_email... FAKED Applying django_q.0015_alter_schedule_schedule_type... FAKED Applying django_q.0016_schedule_intended_date_kwarg... FAKED Applying django_q.0017_task_cluster_alter... FAKED Applying django_q.0018_task_success_index... FAKED Applying postorius.0019_alter_emailtemplate_data... FAKED And mailman 3 is still processing mails. I'm unsure if i should recover from snapshot or keep it going? Could this be some duplicate users with same mail-address? I have at least spotted one user and delete him. thank you. Stefan

1 year, 6 months

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

Mark, Is it only this list that has an issue? Yes, this is the only list that is having the issue. Can you visit other pages for this list? Yes, I'm able to view the members list, list settings, templates, etc. I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen chunked=chunked, File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib64/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 756, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/util/retry.py", line 531, in increment raise six.reraise(type(error), error, _stacktrace) File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/packages/six.py", line 734, in reraise raise value.with_traceback(tb) File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen chunked=chunked, File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request httplib_response = conn.getresponse() File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse response.begin() File "/usr/lib64/python3.6/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status raise RemoteDisconnected("Remote end closed connection without" urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call headers=headers) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailmanve/lib64/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/postorius/auth/decorators.py", line 60, in wrapper return fn(*args, **kwargs) File "/opt/mailmanve/lib64/python3.6/site-packages/postorius/views/list.py", line 620, in list_moderation paginator_class=MailmanPaginator) File "/opt/mailmanve/lib64/python3.6/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailmanve/lib64/python3.6/site-packages/django_mailman3/lib/paginator.py", line 47, in page result = self.function(count=self.per_page, page=number) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 132, in get_held_page return Page(self._connection, url, HeldMessage, count, page) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailmanve/lib64/python3.6/site-packages/mailmanclient/restbase/connection.py", line 136, in call 'Could not connect to Mailman API: ', repr(e)) mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', "ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',)),)") ERROR 2021-02-25 17:28:14,271 393 django.request Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages ERROR 2021-02-25 17:28:14,271 393 django.request Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages

5 years, 6 months

Mailman-users search results for query "Postorius"