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

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/31/25 04:29, Stephan Krinetzki wrote: > > /opt/mailman/var/queue/out: > total 2868 > drwxrwx--- 2 mailman mailman 4096 Jul 31 13:26 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 221708 Jul 30 13:16 1753874180.0845337+0cc7849043859a79dc3678a0d8b63c1c66df0c66.pck.tmp > -rw-rw---- 1 mailman mailman 733425 Jul 31 00:00 1753912841.8847518+da55f8789ae41b75d19a02b595e3fd6d45983ade.pck.tmp These indicate a problem of some sort. .pck.tmp files should only exist for a fraction of a second. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/switchboa… What does `mailman qfile report for these? Are they the missing messages? > -rw-rw---- 1 mailman mailman 17758 Jul 31 13:26 1753961185.0481033+6adf966467266567275f1146f5054c95e4365c13.pck > -rw-rw---- 1 mailman mailman 31122 Jul 31 13:26 1753961185.1064982+b1f502e2af56b9b11680135c6de5fcc5285d967e.bak > -rw-rw---- 1 mailman mailman 12945 Jul 31 13:26 1753961185.1562705+a88534cfa9b03012c248ac00cbb54f4fc08c8dcc.pck > -rw-rw---- 1 mailman mailman 1407634 Jul 31 13:26 1753961185.2598634+96e501d7aa8e72fbb9f9a5c953d48fc2c7db2bc7.pck > -rw-rw---- 1 mailman mailman 17570 Jul 31 13:26 1753961185.3654013+d693065f2b9a2338f887d3ac9c0669c957131100.pck > -rw-rw---- 1 mailman mailman 60624 Jul 31 13:26 1753961185.4132354+8998ee9eb9a8a99faf1fcf045d604e669f5d0c9e.pck > -rw-rw---- 1 mailman mailman 7361 Jul 31 13:26 1753961185.413462+50dcef9bb178f54ecb2d4707ccfe02773f92336c.pck > -rw-rw---- 1 mailman mailman 84848 Jul 31 13:26 1753961185.4464717+17836b8875aa6643f7e5fb0744e72940ce5603c6.pck > -rw-rw---- 1 mailman mailman 18003 Jul 31 13:26 1753961185.4929028+17e9c78a2721cbc344124c6e04a129217ea6c794.pck > -rw-rw---- 1 mailman mailman 66982 Jul 31 13:26 1753961185.5228019+4ef59e61c6a79dd4cdee6d1110fb0582fcfafb6c.pck > -rw-rw---- 1 mailman mailman 221723 Jul 31 13:26 1753961185.5756643+6de90ae99b3d528ce5234b78a287e19f7b6686fc.pck Also, this is a lot of outgoing messages to be queued. Are you sending periodic digests at this time? If you normally see a lot of messages in the out queue, you might consider setting it's `instances` to 2 or 4. E.g., ``` [runner.out] instances: 4 ``` in mailman.cfg > /opt/mailman/var/queue/shunt: > total 3304 > drwxrwx--- 2 mailman mailman 4096 Jul 31 11:44 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 451 Jul 31 00:00 1753912822.2651796+28eceef7e18eb70393377b88dc7117af8f9362a0.pck > -rw-rw---- 1 mailman mailman 490 Jul 31 00:00 1753912838.4197352+ea531cf0262c1faa58b1679b907fee92bc16822c.pck > -rw-rw---- 1 mailman mailman 1407870 Jul 31 00:00 1753912841.9177196+ccea15bdefce3a54301281c8eddf86e8230244a6.pck > -rw-rw---- 1 mailman mailman 86108 Jul 31 00:00 1753912841.9197443+7dcef4febc71e44c6d9309a24a08b08753e1ff42.pck > -rw-rw---- 1 mailman mailman 1407668 Jul 31 00:00 1753912841.9849963+a3f1869b750060c97262ece38737480d91652828.pck > -rw-rw---- 1 mailman mailman 38992 Jul 31 00:01 1753912860.5167956+940584c4f361cbd8c29e390b2f60590558effe40.pck > -rw-rw---- 1 mailman mailman 440 Jul 31 00:01 1753912860.6972685+635c065bac8dff5f9d562275d707001d773b84c1.pck > -rw-rw---- 1 mailman mailman 445 Jul 31 00:01 1753912868.7903054+befa066f254d7a3529a8555a6c942a554715d837.pck > -rw-rw---- 1 mailman mailman 33494 Jul 31 00:01 1753912878.7562895+82b724fd93260ab9a2bb49709d3a42a2f32f2c80.pck > -rw-rw---- 1 mailman mailman 217073 Jul 31 00:01 1753912878.9337828+de73a65d9c6febfa80275853921f4b53fd1d9e2a.pck > -rw-rw---- 1 mailman mailman 85888 Jul 31 00:02 1753912950.303359+8a87bce0be63ac1df8493c6b1ad6ae154fcedba7.pck > -rw-rw---- 1 mailman mailman 50244 Jul 31 00:02 1753912950.4970112+d44d493912bb3024547b8a5112f86f035dcb352f.pck > -rw-rw---- 1 mailman mailman 12887 Jul 31 00:02 1753912970.038427+31bcbd7fb2ebdf81f6de24b7283b50bcda6ded21.pck.tmp > -rw-rw---- 1 mailman mailman 443 Jul 31 11:44 1753955094.900898+67bc76525412da66a7c76363f65f583989716305.pck > > /opt/mailman/var/queue/virgin: > total 32 > drwxrwx--- 2 mailman mailman 81 Jul 31 13:17 . > drwxr-xr-x 14 mailman mailman 165 Jun 27 2024 .. > -rw-rw---- 1 mailman mailman 32013 Jan 11 2025 1736550035.6163204+472f81ece5e45a2651a4499bef418f611b43c619.pck.tmp > > Nothing special there (shunt should be checked, but not in correlation with my mail). Actually those .pck.tmp files indicate some issue. > I have one list which archives the mail. In the archive there is the mail, but it doesn't get deliverd Which says the pipeline to_archive handler is adding the message to the archive queue and the archive runner is handling it, so presumably the pipeline to_outgoing handler is adding the message to the out queue, so the issue is in the outging runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Mark Sapiro

On 5/24/21 10:43 AM, christopher.claus(a)tgcamberg1848.de wrote: > > I found the file > [code] > /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt > [/code] > which includes the old footer: > [code] > _______________________________________________ > $display_name Mailingliste -- $listname > Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} > [/code] > > but no configuration item to disable this behaviour. That is the default footer template that's part of the Mailman distribution. That template is overridden by those in Mailman's var/templates/ directory. Mailmnan's import21 process created footers template in var/templates/lists/<LIST_ID>/list:member:regular:footer.txt and var/templates/lists/<LIST_ID>/list:member:digest:footer.txt > I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used where did you put it? > in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. > > In the logfiles I found an error and a warning: > [code] > ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. > WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer > [/code] It appears you created the new template with Postorius, but there is an issue for Postorius templates. Possibly your Django setting for POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. > Obviously I have a problem with the hostname. I set > [code] > POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 > [/code] > where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost > [code] > wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… > [/code] > will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? If that works, yes. > I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. > > Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. The issue you are seeing has only to do with the fact that the footer is non-empty. It is not related to footer content. It is because you are posting other than text/plain messages and the MUAs you are viewing the mail with are confused by the footer being a separate MIME part. See the FAQ article at https://wiki.list.org/x/4030707 for discussion of this issue in MM 2.1 which is also relevant to MM 3. To disable adding footers entirely, sitewide, create an empty file, readable by Mailman at Mailman's ``` var/templates/site/de/list:member:generic:footer.txt ``` More about templates and search rules is at templates/de/list:member:generic:footer.txt and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: update_index

by Darren Smith

Holy cow I think that's exactly what the problem is. I will give that a try and let you know what happens! On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/03/2018 09:02 AM, Darren Smith wrote: > > Hello, > > > > If I'm reading the docs correctly, when we run manage.py update_index, it > > should be an incremental index of new emails that have been added since > the > > last time update_index was run - can anyone confirm that this is the > > expected behavior? Or is there another command line option that I am > > missing? > > > There are two ways to run update_index. > > Hyperkitty's update_index is incremental and is run by > > manage.py runjob update_index > > Running > > manage.py update_index > > runs haystack's update_index which with no options does a full update. Run > > manage.py update_index --help > > to see the options. The incremental 'manage.py runjob update_index' > should be run every minute by 'manage.py runjobs minutely' assuming cron > is running the periodic Django jobs, so running either update_index job > manually shouldn't be necessary > > > ... > > So...can anyone help with how to get the update_index to do only emails > > added since the last time the update_index was run? > > > manage.py runjob update_index > > -- > 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/ >

8 years, 1 month

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

by "Jörg M. Schulz"

start fails when I use # The default language for this server. default_language: en [language.en] charset: utf-8 enabled: yes when I comment out the lines above, mailman starts. > Am 09.01.2019 um 20:53 schrieb Jörg M. Schulz <js(a)jslz.de>: > > and: When I put the stanza >>> [language.en] > into the mailman.cfg, the service doesn’t restart: > … > PermissionError: [Errno 13] Permission denied: '//var/templates' > > somehow the template path gets lost by defining this section. Possibly, somewhere the path to the .en / language templates must be set. How, where? > > > >> Am 09.01.2019 um 20:50 schrieb Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>>: >> >> Mark Sapiro wrote: >>> >>> You can change this for English by putting >>> >>> [language.en] >>> charset: utf-8 >>> >>> in your mailman.cfg. This works because us-ascii is a proper subset of >>> utf-8. >> >> >> I forgot to mention that there is a potential downside to the above. Because of the way the Python email library treats UTF-8 message bodies, list messages with UTF-8 bodies are sent with the body base64 encoded. This may or may not be an issue depending on whether you look at raw messages or perhaps grep mailboxes looking for things. >> _______________________________________________ >> 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/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >

7 years, 4 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and DMARC Mitigate unconditionally to > 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/ >

4 years, 4 months

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/16/2018 09:01 AM, Aymeric Mansoux wrote: > > However, while I was testing this happily on a list that was not affected with the JSON error, I finally tested discard_held_messages() on one of the problematic list, and I get the exact same problem as when trying to view the moderation queue API: > >>>> discard_held_messages_queue('xxx(a)xxx.xxx') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "<console>", line 6, in discard_held_messages_queue > File "/usr/local/lib/python3.5/dist-packages/mailman/app/moderator.py", line 97, in handle_message > key, msgdata = requestdb.get_request(id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > > With that said, even though I cannot pass the discard action, I can export the queue without problem, so I will send you off-list a sample, because I am not sure what I should be looking for. Unfortunately, that didn't help. I was able to post all the messages in your sample to a test list and even with all the messages held, I could view them and discard them in postorius. This may not be too surprising as looking at the traceback, the exception is thrown in trying to delete the pending confirmation from the pending database. The issue is when a message is held an entry is made in the pending database with a confirmation token that can be used for example to approve or discard the message by email. There is an issue that affects MySQL databases only in that prior to the merge of <https://gitlab.com/mailman/mailman/merge_requests/333> values in the pendedkeyvalue table could be truncated (or exceptions thrown depending on MySQL settings). That appears to be the issue here. The fix was only merged in January and is not in Mailman 3.1.1. > Finally, is there another way to get rid of these messages? Are there consequences if I would use message_store.delete_message(message_id) instead of handle_message(m, req.id, Action.discard)? As I said, I think the issue is with the pendedkeyvalue table, not with the message itself. The table contains entries which are pickled versions of various things. A big issue is rule_misses. For one of your messages, the rule_misses list is ['dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation'] this gets pickled into b'\x80\x03]q\x00(X\x10\x00\x00\x00dmarc-mitigationq\x01X\n\x00\x00\x00no-sendersq\x02X\x08\x00\x00\x00approvedq\x03X\t\x00\x00\x00emergencyq\x04X\x04\x00\x00\x00loopq\x05X\x0e\x00\x00\x00banned-addressq\x06X\x11\x00\x00\x00member-moderationq\x07e.' which ultimately gets stored in the pendedkeyvalue table as a value for '_pck_rule_misses' which is '"\u0080\u0003]q\u0000(X\u0010\u0000\u0000\u0000dmarc-mitigationq\u0001X\n\u0000\u0000\u0000no-sendersq\u0002X\b\u0000\u0000\u0000approvedq\u0003X\t\u0000\u0000\u0000emergencyq\u0004X\u0004\u0000\u0000\u0000loopq\u0005X\u000e\u0000\u0000\u0000banned-addressq\u0006X\u0011\u0000\u0000\u0000member-moderationq\u0007e."' Which is longer than the VARCHAR(255) MySQL field for that value prior to <https://gitlab.com/mailman/mailman/merge_requests/333>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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/

4 years, 6 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Mark Sapiro

On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 10:22 AM, Nathanael Schneider wrote: > > I then created a completely new List which did not exists in mm2.1, > subscribed two addresses and sent myself an EMail. That one worked as > intended. I then deleted the whole broken list and created it cleanly, > added the same two people, sent an email and nothing. This seems strange. If I understand, you are essentially saying the two lists are the same. I.e., you created a completely new List which did not exists in mm2.1, and that one worked. Then you deleted the whole broken list and created it cleanly ... What was different between this cleanly created list and the completely new List? > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb49b143780> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net > May 19 18:54:40 2021 (8280) Using agent: <mailman.mta.deliver.Deliver object at 0x7fb4974541d0> > May 19 18:54:40 2021 (8280) IndividualDelivery to: nathanael(a)lumenliquid.net The fact that these are the only messages says that the attempt to send that message via smtp raised no exception as exceptions would have been logged, yet you say there's nothing in the maillog so there was no connect to Postfix. What are your settings for smtp_host: and smtp_port: in the [mta] section of mailman.cfg? ... > I have no clue what to do with this. I then turned the debug module > loglevel to debug. Also nothing useful. Just an endless list of > > [...] > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > May 19 18:17:29 2021 (7203) [ArchiveRunner] starting oneloop > May 19 18:17:29 2021 (7203) [ArchiveRunner] ending oneloop: 0 > May 19 18:17:29 2021 (7209) [OutgoingRunner] finishing filebase: > 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd > May 19 18:17:29 2021 (7209) [OutgoingRunner] doing periodic > May 19 18:17:29 2021 (7209) [OutgoingRunner] committing transaction > May 19 18:17:29 2021 (7209) [OutgoingRunner] checking short circuit > May 19 18:17:29 2021 (7209) [OutgoingRunner] ending oneloop: 1 > May 19 18:17:29 2021 (7209) [OutgoingRunner] starting oneloop > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing filebase: > 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e > May 19 18:17:29 2021 (7209) [OutgoingRunner] processing onefile > May 19 18:17:29 2021 (7209) [outgoing] <function deliver at > 0x7f2faf384c80>: <B9531076-2480-4925-9A2B-57802B53D5ED(a)gmx.de> > [...] > > Which also tells me nothing I can understand. It says the message in queue entry 1621441049.4089153+6dff56673dc64b890dd352941267782c264586dd is handled but gets requeued as 1621441049.4628382+6a0437ea387a2508ad947c0a51712075cbdb6d2e which presumably is handled and requeued again ... > I have no clue what's > going wrong. (I've turned on debugging both on the original member list > and the reduced member list. Both hang on the first delivery they do). > If I restart mailman, the message gets correctly shunted as it is > interrupted mid-delivery. My maillogs don't register any activity beside > the listpost. Any ideas what I need to do to figure out what's not > working here or where the culprit could be? Not sure if it is related to > the mailinglist being in mailman2.1 before. I have no real understanding of why this isn't working. I don't think it's likely that it has to do with the mailing list being imported from MM 2.1, but I suppose it could be. How did you create and import the list? When you say you deleted the whole broken list and created it cleanly, what did you actually do? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: hidden list is hidden even to the owner

by Mohsen Masoudfar

As always: Thanks a lot! To answer your question, I am running 1.1.2-3 # apt search postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] Web user interface to access GNU Mailman3 This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, July 1, 2020 5:43 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: hidden list is hidden even to the owner [EXTERNAL EMAIL] On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… and if you are a member as well as owner of an unadvertised list, you will see it at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…. But (here's the tricky part) if you go to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…, you will not see any unadvertised lists, not even ones you own. -- 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…

5 years, 10 months

Search results for query "sapiro"