Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > > ... > > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 1 month

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Abhilash Raj

On Wed, Nov 25, 2020, at 9:24 AM, Mark Sapiro wrote: > On 11/24/20 7:22 PM, Abhilash Raj wrote: > > > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). > > > It's more complicated than that. Sometimes the fragment name is the > heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor > #3.3.3 work at all as these are #id2 and #id1 respectively. Currently > the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is > #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs > under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but > when a Command line section is added under 3.3.3, that will probably get > the command-line id. > > Thus, the note "Permalink to this headline" es misleading at best > because it isn't very permanent fo an evolving document. Yeah, I was thinking about internal references, `:ref:` which accepts heading names, but anchors aren't added you are right. > > > > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. > > > I too think this is correct. I suppose it might be worth doing for > NEWS.rst in particular since Sphinx doesn't seem to like fragments like > n.n.n. Another way to deal with this would be to always use code names. > It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. > `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` Yep, I created news-3.3.3 for 3.3.3 and we can keep the convention going. I tested it out and it worked for me. https://gitlab.com/mailman/mailman/-/merge_requests/736 > -- > 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 > 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, 11 months

[MM3-users] Re: Weird behavior with Outlook and any MM3 List

by Thomas Ward

Ye it gets a little tricky when we have custom thread IDs being added. I could do some postprocessing on a reply and see what the "In-Reply-To" header says if I can figure out how to fetch the previous message subject line for the custom need for my workplace with a thread/post ID in the subject line. I'm going to experiment with alternative brackets and see if it still does it. While also opening a support ticket with Microsoft to give me a chance to rage at them. I'll report back if I find a solution/alternative. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, November 1, 2023 2:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Weird behavior with Outlook and any MM3 List On 11/1/23 09:42, Thomas Ward via Mailman-users wrote: > I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). > > When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. > > While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. > > Has anyone observed this behavior before? If so, have you found any workarounds? This is a Microsoft/Outlook issue. As you note at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… this is just the way Outlook displays the message subject. I know of now way around this, but I don't use Microsoft MUAs. Does Outlook also strip the prefix from replies? This probably wouldn't matter for replies to the list as the list will add it back, but might be an issue for other direct recipients. Presumably, Outlook is looking at the [] around the prefix. You might try either dropping the brackets or using something else such as _My-List_ instead of [MyList]. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

1 year, 11 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

To make it work, I have to comment out like this: Also only commenting out the .de section doesn’t help # The default language for this server. default_language: en # [language.en] # charset: utf-8 # enabled: yes # [language.de] # description: German # charset: iso-8859-1 # enabled: yes > Am 09.01.2019 um 21:50 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 12:20 PM, "Jörg M. Schulz" wrote: >> when I use the lines below, the templates are looked for in //var. >> When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. > > > //var refers to the directory defined in mailman.cfg (or the default in > mailman/config/schema.cfg) as > > [paths.master] > var_dir: > > > Exactly which of the following lines did you add and then comment out? > Just the three lines > >> [language.en] >> charset: utf-8 >> enabled: yes > > > or something more? > > >> mailman.cfg: >> >> [mailman] >> # This address is the "site owner" address. Certain messages which must be >> # delivered to a human, but which can't be delivered to a list owner (e.g. a >> # bounce from a list owner), will be sent to this address. It should point to >> # a human. >> site_owner: help(a)elternserver.de >> >> # This is the local-part of an email address used in the From field whenever a >> # message comes from some entity to which there is no natural reply recipient. >> # Mailman will append '@' and the host name of the list involved. This >> # address must not bounce and it must not point to a Mailman process. >> noreply_address: noreply >> >> # The default language for this server. >> default_language: en >> [language.en] >> charset: utf-8 >> enabled: yes >> >> [language.de] >> description: German >> charset: iso-8859-1 >> enabled: yes > > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 9 months

[MM3-users] Re: Hyperkitty: AttributeError: 'NoneType' object has no attribute 'subject'

by Mark Sapiro

On 01/13/2018 09:46 AM, Alex McLean wrote: > I'm getting a 500 server error with some threads in hyperkitty, e.g. this one: > https://we.lurk.org/hyperkitty/list/tidal@we.lurk.org/thread/3IN5NFFFPVAQSR… > > The following appears in the log, any pointers much appreciated! > > ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ > Traceback (most recent call last): > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response > response = self._get_response(request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index > return render(request, "hyperkitty/thread.html", context) > File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render > content = loader.render_to_string(template_name, context, request, using=using) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string > return template.render(context, request) > File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render > return self.template.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render > return self._render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render > return compiled_parent._render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render > result = block.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render > return nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render > output = self.filter_expression.resolve(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve > obj = self.var.resolve(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve > value = self._resolve_lookup(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup > current = getattr(current, bit) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject > return self.cached_values["subject"]() > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ > return self.get_or_set(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set > value = self.rebuild(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild > value = self.get_value(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value > return self.instance.starting_email.subject > AttributeError: 'NoneType' object has no attribute 'subject' This may be related to our not clearing cache when deleting messages/threads. See <https://gitlab.com/mailman/hyperkitty/issues/160>. If so, restarting your web server may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

Hey there, Im going to breakdown my response into sections: 1) Yes, there is only one install of mailman on the box. 2) I created the list using the script below 3) My method of importing it is by copying the lists to /opt/mailman/old/lists and running these commands (within lists) MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman import21 "${DIR}"@afilias.info "${DIR}"/config.pck; done However, if you look at the above you can see where I am going wrong. What it should actually be doing is: MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ afilias.info "${DIR}"/config.pck; done Sorry for wasting your time on this one. Coffee is on me. On Mon, Jul 30, 2018 at 6:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/30/2018 07:37 AM, Ryan McClung wrote: > > GNU Mailman 3.2.0 (La Villa Strangiato) > > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > > config file: /opt/mailman/var/etc/mailman.cfg > > db url: sqlite:////opt/mailman/var/data/mailman.db > > devmode: DISABLED > > REST root url: http://localhost:8001/3.1/ > > > > Shortly after I run an import on a bunch of lists they all disappear. > > [root@mailman3(stg) mailman]# mailman lists > > No matching mailing lists found > > > > I have 30+ lists. > > > Does the 'mailman lists' command invoke the identical 'mailman' file as > the 'mailman import21' command that did the imports. And how did you > create the lists before importing them? > > We have done several imports of 2.1 lists to > <https://mail.python.org/mm3/mailman3/> and have never seen an issue > like this. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 2 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark for your response. But I am having a final query over this issue. Out of the two hyperkitty records I observed in the database, I am confused which record do I need to remove directly from the database? Because I doubt still there is one more list with the same style i.e. with two hyperkitty records. Please advise. On Mon, Jul 27, 2020 at 4:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > > Thank you Mark. > > > > What you have said is right.. > > > > I found a list with two "hyperkitty" records in the listarchiver in the > > database. I had removed the list and recreated it and now I found it is > > working fine. The recreated list is having only one record. > > > OK, but that's not a reasonable way to fix this in general. You can just > remove the `extra` record using a direct database query which is > probably the least disruptive way to fix this. > > > > After searching the links you provided I found there is just a work > around > > but not the precaution to be taken for not getting the duplicate record. > > > > Can you say what might be the reason for this duplication? If I need to > > provide any details, please let me know. > > > As noted in the threads I referenced, we don't know the cause. Yours is > the first report of this issue with the `hyperkitty` archiver. In all > the other reports, the duplicate archiver has been `mhonarc`. > > If it happens again and you know the exact sequence of events that led > to it, i.e. what was done with the list between the last time it worked > and when it stopped working, that might give us clues, but currently we > are at a total loss to understand how this happens. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 3 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, I checked the database; nothing there. Note that there are only 3x entries and only one is list:member:regular:header (my test), so just nothing of interest. The URL works and produces the proper template information. I finally did a find/grep in the mailman tree and found a match for this errant string. It is under the cache folder. This corresponds to the cache_dir value. I could wipe the file out, but what is the proper way of doing so and should they be cleaned out via a schedule? These don’t appear to be web related, as far as I can tell. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Friday, February 7, 2025 at 10:37 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/7/25 10:08, Lieuallen, Thomas Otis via Mailman-users wrote: > > I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. What do you get from the following database queries? SELECT * FROM template WHERE name = 'list:member:regular:header'; SELECT * FROM postorius_emailtemplate WHERE name = 'list:member:regular:header'; Depending on your installation, these tables may be in separate databases, i.e., template table in mailman db and postorius_emailtemplate in mailmanweb db. And what do you get if you go to the uri in the result(s) from the first query? The context in the first results and maybe the second results should also be a clue. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

8 months, 3 weeks

[MM3-users] Re: List description as sender

by Henrik Rasmussen

It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. I try to keep the descriptions as short as possible, and I don't consider "Newsletter to the members of the Anthropology Society" a long message, when displayed in https://list.example.com/postorius/lists/, but when the description is displayed as From: in mails, I agree it is a long description. On lists.mailman3.org, the description "General list for Mailman 3 users and others interested in Mailman 3" is also short, but when used as From: it is fairly long. -----Oprindelig meddelelse----- From: Mailman-users is an infrequent newsletter sent to list administrators <mailman-users(a)lists.example.com> Sent: 14. september 2018 13:20 To: mailman-users(a)lists.example.com Subject: Test 201809141319 [cid:image001.png@01D44E6C.A57045A0] -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 14. september 2018 17:36 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: List description as sender On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com<mailto:project@lists.example.com>>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<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/

7 years, 1 month

Search results for query "sapiro"