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

[MM3-users] Re: bounce_score_threshold control

by Mark Sapiro

On 2/24/23 08:08, Tibor Molnar wrote: > > I have recently started receiving these mails from the system. First it was frighting me out that people's account got disabled, but actually nothing has happened, nobody got disabled. I however looking to figure out how can I control or change settings for this particular mechanism. Please advise me. > > emailname(a)example.it's subscription has been disabled on listname(a)domain.eu due to their bounce score > exceeding the mailing list's bounce_score_threshold. I'm not sure what you are looking at, but when you receive that message, it means the user's Delivery status has been set to Disabled by Bounces and the user will be sent `Bounce disable warnings` (default 3) warnings at intervals of `Bounce disabled warnings interval` (default 7 days) and if nothing is done the user will then be removed from the list. The notice you received, at least since Mailman 3.3.5, should contain a copy of the bounce DSN so you can determine if this user's address is actually undeliverable. Settings that control this are in the Postorius admin UI under Bounce Processing. The only other control is in mailman.cfg in the [mta] section where you can set `verp_probes: yes` See the docs at https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: "Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'

by Mark Sapiro

On 05/28/2017 12:40 PM, Simon Liebold via Mailman-users wrote: > I didn't find a 'delete message' button. But "Delete this thread" went > straight to the 500. Both, Hyperkitty and django-mailman are up-to-date > with master. 'Delete this message' is in the 'message' view. "Delete this thread" is in the 'thread' view. > ERROR 2017-05-28 13:04:14,496 29835 django.request Internal Server > Error: > /hyperkitty/list/simsimmer@lists.simonliebold.de/thread/4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM/delete > Traceback (most recent call last): > File > "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/exception.py", HyperKitty requires Django<1.11. The comment in the requirements in setup.py implies this is only a django-haystack requirement "Django>=1.8", # Don't upgrade to 1.11 until django-haystack supports it: # https://github.com/django-haystack/django-haystack/pull/1499 "Django<1.11", but since it works for me with Django 1.10, you might want to try that. ... > File > "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/forms/models.py", > line 1168, in __deepcopy__ > result.queryset = self.queryset.all() > AttributeError: 'NoneType' object has no attribute 'all' In particular, this looks like Django 1.11 bug <https://code.djangoproject.com/ticket/27975>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 10/11/2018 03:48 AM, Henrik Rasmussen wrote: > > Before running /usr/bin/docker exec mailman-core mailman digests --periodic --verbose > > Every 2.0s: ls -l;grep "Test 20181011" digest.mmdf;tail /var/log/mailman/core/smtp.log Thu Oct 11 12:23:32 2018 > > -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf > -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf > -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.mmdf ... > After running /usr/bin/docker exec mailman-core mailman digests --periodic --verbose > > Every 2.0s: ls -l;grep "Test 20181011" digest.mmdf;tail /var/log/mailman/core/smtp.log Thu Oct 11 12:44:45 2018 > > total 372 > -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf > -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf > -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.1.9.mmdf The mailman digests --periodic command renames the digest.mmdf file to (in this case) digest.1.9.mmdf and then queues an entry in the digest queue for DigestRunner to actually build the digests from the digest.1.9.mmdf file, send them and remove the digest.1.9.mmdf file. Something is going wrong in this process in DigestRunner. Is DigestRunner running? Is there anything in Mailman's digest or shunt queues? Is there anything logged in Mailman's 'mailman' log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Importing users and mas settings "Moderation Action"

by Mark Sapiro

On 5/19/22 06:17, bob B via Mailman-users wrote: > I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? Correct. > But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? Yes. > I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? That's correct, and that was also the case in Mailman 2.1 . > is there a way to change all their user's "Moderation Action" for a list in bulk? You could do it with `mailman shell`, but not in Postorius. > So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user? If you are a list owner whose only access is via Postorius, that's correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/27/24 18:44, Mark wrote: > > I created a text file as a custom welcome message and chowned it to > mailman:mailman, then edited the database record (template.uri) from > > http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… > TO > file:///home/mark/welcome.txt > > This delivered the custom welcome message to the user when subscribed > via Mass Subscribe. > > I'm not sure what this tells me other than a call can be made to a file > but not the database. The retrieval of a file does not involve calling requests.get() to retrieve the URL via http which is where the issue occurs. There's another way to set templates in the file system. If there is no entry in the template table matching the requested template name and context the file system is searched according to the algorithm described at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…>. $template_dir in that description is Mailman's var/templates/ directory. So for example, to create a lists specific english language welcome template for the list.example.com list you could just put the template in var/templates/lists/list.example.com/en/list:user:notice:welcome.txt or to make it sitewide, in var/templates/site/en/list:user:notice:welcome.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

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

by Mark Sapiro

On 2/10/25 12:09, Lieuallen, Thomas Otis via Mailman-users wrote: > > I haven’t figured out how to work with these cache files. I found some mention that a runner would clean up cache files after a week (default) and that one could use ‘cache_life’ to change that default. So, I set the following and restarted mailman. The cache files hadn’t been removed after > 4 hours, so I unset it and restarted again. > > Cache_life: 1d The setting is actually `cache_lifetime` in the `[mailman]` section of mailman.cfg, however when a file is cached, it's lifetime is saved in the database and won't be changed by changing that setting. > Without further information or direction, I’m tempted to just remove those cache files and move on with life. Removing them is OK, but a database entry will still exist pointing to them and attempt to retrieve them will return `Cache content lost`. The way to properly remove them is in Mailman shell ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> cm = getUtility(ICacheManager) >>> cm.clear() >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Link another address

by Mark Sapiro

On 5/18/20 5:13 PM, Brian Carpenter wrote: > I am thinking about incorporating the following Postorius/Django account feature into Affinity: > > Other emails: (no other email) Link another address > > However I cannot think of a serious real-world need for this. What are the developers' reasoning behind this? Was this feature highly demanded by Mailman 3 users? Just trying to find out what I am missing here. In mailman 2.1 there was no concept of user. There were only lists and list members and list members were just email addresses that had no connection to other list members even if they happened to have the same email address. In mailman 3 we have users. Users can have multiple addresses. a user or a particular user's address can be a regular member and an owner of one list, a moderator of another list and a non-member of a third list. Some other address of that user can be a digest member of the first list. All of these addresses and roles can belong to a single user and be managed from that user's one account. Sure, each address can be separate with it's own login, but isn't it more convenient if they are all linked under one login if they all belong to one individual. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Hyperkitty "All Threads" results in error

by Mark Sapiro

On 10/14/20 11:12 AM, Mark Dadgar wrote: >> On Oct 4, 2020, at 10:34 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >> >> So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. Does this happen on all lists, only some lists or only one list? >> I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… What did you google? This query gets a lot of stuff with some hints, but nothing definitive. django render raises VariableDoesNotExist("Failed lookup for key " One thing I noted at <https://askbot.org/en/question/3095/django-error-variabledoesnotexist-faile…> was models out of date - run python manage.py syncdb and python manage.py migrate You could try that. Note that your django admin command might be something other than `python manage.py`. Also note syncdb has been removed from Django >=1.9. Currently, the above becomes `makemigrations` followed by `migrate`. I also suggest running the django admin commands `collectstatic --clear --noinput` and `compress` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 11:31 AM, Brian Carpenter wrote: > I keep seeing bounces being recorded in logs/bounce.log that have no > corresponding entry in Postfix's mail.log. For instance one address had > registered about 2 dozen bounces in the past week in bounce.log and yet > every single entry for this address in mail.log has a status=sent. What > am I missing here? They are being bounced by a downstream MTA. If you want to know why, you have a few choices. You can mail the address yourself and hopefully get a DSN back. You can install this patch: ``` > diff --git a/src/mailman/runners/lmtp.py b/src/mailman/runners/lmtp.py > index 6a0bdcf5e..eca474089 100644 > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -217,6 +217,8 @@ class LMTPHandler: > slog.debug('%s subaddress: %s, queue: %s', > message_id, canonical_subaddress, queue) > status.append('250 Ok') > + if queue == 'bounces': > + config.switchboards['bad'].enqueue(msg, msgdata) > except Exception: > slog.exception('Queue detection: %s', msg['message-id']) > config.db.abort() ``` which will add all received bounces as queue files in Mailman's var/queue/bad. At some point, we need to implement the attachment of the bounce DSN to the notices sent to the admin, but that isn't done yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

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

by Mark Sapiro

On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote: > Running Mailman 3.3.10 > > I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. Are old ones being delivered and new ones added or the same ones just being renamed? I suspect the latter and I suspect the issue in that case is probably due to the OUT runner trying to access a template file like list:member:{regular|generic}:{header|footer}.txt and not having permission. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. The files are python pickles and `strings` shows lots of stuff. The ! may be something in the pickle that's not part of the email address. The way to examine these files is with the `mailman qfile` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Search results for query "sapiro"