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

[MM3-users] Re: messages stuck in the bad queue

by Mark Sapiro

On 6/24/23 9:54 PM, Ken Alker wrote: > I am working on a mail server that was migrated from mailman V2 to > mailman V3 in February. I just noticed that there are over 1000 > messages in the bad queue. All of the messages in the bad queue are > dated 2/2/23 and all have a timestamp within a one-hour window of each > other. > > I used mailman qfile to inspect five random emails in the bad queue and > so far they are all "successfully subscribed" emails, This is a bit strange. See below. > but I presume > there are no guarantees there aren't others mixed in there that might be > legitimate emails (ie. I just unshunted 140 emails in the shunt queue > and they were all good emails and all got processed). Presumably these were shunted due to some issue that was subsequently fixed. > I figure that the easiest way to inspect these 1000 emails is just to > have them re-delivered. I tried moving one from the bad queue to the > shunt queue and I ran "mailman unshunt" but nothing happened. What does nothing happened mean? "mailman unshunt" should move the message to the original queue which was stored in the 'whichq' attribute in the msgdata when the message was shunted. Since this wasn't a shunted message, there's no 'whichq' attribute so it goes to the 'in' queue. I.e., "mailman unshunt" would have moved the message from the 'shunt' queue to the 'in' queue. If the message wound up back in the shunt queue, there should be messages in mailman.log indicating why. > Is there a way to reprocess the bad queue? You could just move the messages to the 'in' queue. > Also, what exactly is the bad queue? If Mailman's content filtering is enabled and Filter Action is Preserve, messages which have no remaining content after content filtering are put in the 'bad' queue. These are the only messages put there. When this happens there should a log message like <message-id> preserved in file base <queue_file> It is unclear to me how these 1000+ messages wound up in the 'bad' queue. If you have logs from Feb 2, they might help. My guess is there was some MTA misrouting that caused these list welcome messages (from some mass subscribe?) to be rerouted to the list posting address combined with some bad content filtering settings that removed all the content, but that seems pretty far fetched. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Stefan Bauer

Mother: Anonymous list: No First strip reply to: No Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Daughter: Anonymous list: No First strip reply to: Yes Reply goes to list: No Munging DMARC mitigation action: Replace From: with list address DMARC mitigate unconditionally: Yes Am Mi., 24. Nov. 2021 um 21:53 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 11/24/21 2:05 AM, Stefan Bauer wrote: > > That is already set. No change. > > This completely removes the reply-to: header and sets the iu-all > > list-address as new and only reply-to. > > > What are your current settings on both the mother and daughter lists for > Anonymous list, First strip reply to, Reply goes to list and under DMARC > Mitigations for DMARC mitigation action and DMARC Mitigate unconditionally? > > > -- > 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/ >

3 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Does this have anything to do with the problem?: (env) [mailman@localhost logs]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project/logs (env) [mailman@localhost logs]$ tail -f mailmansuite.log File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 204, in hunks precompiled, value = self.precompile(value, **options) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 265, in precompile return True, filter.input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sassc: command not found Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/27/20 9:52 PM, joseverde(a)gmail.com wrote: > The settings match the Django settings, yes. As far as the rest runner, the following shows on that command: > > root 25868 25475 0 21:50 pts/0 00:00:00 grep --color=auto runner=rest So the rest runner is not running as all you see is your grep command. On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: > On 7/27/20 10:34 PM, joseverde(a)gmail.com wrote: >> And one last infopoint for tonight, I checked on a whim to see if mailman3 was still running, it wasn't since the last time I checked. (the command mailman status, on the other hand, shows it is up and running. The following error was shown when starting to start: >> >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 88, in process >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: status, lock = master_state() >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 133, in master_state >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: hostname, pid, tempfile = lock.details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 145, in details >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: with open(self._lockfile) as fp: >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/master.lck' >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Control process exited, code=exited status=1 >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Failed with result 'exit-code'. >> Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: Failed to start Mailman3 server. >> It appears there is a permissions issue in trying to read the locks. Does your systemd script set the user to the Mailman user, and does the Mailman user have read/write permission on Mailman's var/locks/? Also, is any of Mailman core running? Try ps -fwwA|egrep 'master|runner' If a master is running, try service mailman stop If that doesn't stop it, send it a sigterm or, only if necessary, a sigkill. Then if there are an runners left, sigterm them. Finally if there's anything in var/locks, remove it. Then try to start Mailman. Note that if you've previously started Mailman as root, there may be locks and or other files owned by root that are now inaccessible to mailman. You may need to `chown -R mailman` in Mailman's var directory. -- 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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This is the content of my /var/log: [root@localhost log]# pwd /var/log [root@localhost log]# ls anaconda grubby messages-20170716 spooler-20170710 audit grubby_prune_debug messages-20170723 spooler-20170716 boot.log httpd mysqld.log spooler-20170723 btmp lastlog php-fpm tallylog btmp-20170701 letsencrypt ppp tuned chrony maillog rhsm wtmp cron maillog-20170702 samba xferlog cron-20170702 maillog-20170710 secure xferlog-20170702 cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 cron-20170723 mailman secure-20170716 xferlog-20170723 dmesg messages secure-20170723 yum.log dmesg.old messages-20170702 spooler firewalld messages-20170710 spooler-20170702 El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/22/2017 05:29 PM, Rafael Mora wrote: > > > > How can I config Mailman/Postfix to send the confirmation email for the > > superuser I created this morning??? > > > What is in Postfix's logs relevant to the attempt to send the mail > (probably /var/log/mail.log)? > > What is the output from 'postconf -n' > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/12/22 11:45, David Newman wrote: > > To rule out the smtp module, I sent a PGP-signed message using a > different MUA (Thunderbird, in my case). Mailman3 accepted this post > without complaint, and I reported back to list users that this appears > to be an Apple Mail encoding issue. > > Normally, that'd be the end of it. But this is a list for a bunch of > Internet graybeards, including one of the authors of the SMTP protocols > and the subscriber is a former IETF chair. He's grumbling that if this > really were an Apple Mail issue, wouldn't it be far more widespread? Maybe, but who knows. The issue is with at least macOS 12.0.1, Mail.app Version 15.0 (3693.20.0.1.32), and GPG Mail 6.0, Build 2023. That combination at least produces multipart/signed messages with multipart/* parts containing a Content-Transfer-Encoding: header. The Python 3 email library considers this to be a InvalidMultipartContentTransferEncodingDefect() message defect. I had a long exchange with Barry Warsaw about this. an excerpt is It's definitely an Apple Mail issue. Both the message you sent and the original message part have the same defect: InvalidMultipartContentTransferEncodingDefect() Also, My Thunderbird MUA wouldn't display the message content at all. Interesting though that your original message was also signed and sent by Apple Mail and didn't have the defect. It's structure was multipart/signed multipart/alternative text/plain text/html application/pgp-signature and none of the multipart parts have Content-Transfer-Encoding. The follow up you sent with the original message was multipart/signed multipart/mixed * text/plain message/rfc822 (the attached message) * multipart/signed * text/plain application/pgp-signature text/plain (an empty plain text part) text/plain (a quote of my message to you) application/pgp-signature All the asterisked parts have a Content-Transfer-Encoding header which is the defect. It seems to be related to the presence of the empty text/plain part following the signature. > I don't think it would be, because (a) Mailman2 is still far more > pervasive than Mailman3 and (b) the combination of PGP signing and Apple > Mail on MacOS and Mailman3 is still pretty unusual. > > Has anyone else hit this encoding issue, other than the post above? And > did Mailman2 silently accept this because it was less strict about > checking for bad encoding? To my knowledge it's only been hit by Barry and the poster of the original report Mailman 2.1 is has the Python 2 email package which doesn't report InvalidMultipartContentTransferEncodingDefect(). I reported it in November at https://feedbackassistant.apple.com/feedback/9768496 which is open with no reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: MIME Digests with posts and index inline likewise Plain Text Digests

by Mark Sapiro

On 1/18/19 5:11 AM, Henrik Rasmussen wrote: > Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. > > Would it be possible for Mailman to send both posts and index inline in the MIME digest? The format of the MIME digest is specified by RFC 2046 which defines the multipart/digest format in section 5.1.5. This defines the MIME digest as a multipart/digest message part containing the individual messages as message/rfc822 sub-parts. It also says (after spelling corrections - ErrataID: 510): Note: Though it is possible to specify a Content-Type value for a body part in a digest which is other than "message/rfc822", such as a "text/plain" part containing a description of the material in the digest, actually doing so is undesirable. The "multipart/digest" Content-Type is intended to be used to send collections of messages. If a "text/plain" part is needed, it should be included as a separate part of a "multipart/mixed" message. The MIME format digest Mailman produces has the structure multipart/mixed text/plain the "masthead" text/plain (only if a digest header) the digest header text/plain the table of contents multipart/digest message/rfc822 the first message message/rfc822 the next message ... message/rfc822 the last message text/plain (only if a digest footer) the digest footer The only change that could be made while keeping the digest compliant would be to combine the masthead, digest header if any and table of contents in a single text/plain part. While this might solve the the issue of the table of contents being an "attachment" in some MUA's rendering, it won't address the larger issue of the messages being rendered as attachments. As you note, Gmail's web mail does an OK job of rendering the MIME digest as do other mainstream MUAs such as Thunderbird. The real solution is for those people who insist on using non-compliant MUAs to subscribe to the plain format digest. The whole point here is if you want a digest which has everything in line, that's what the plain text digest is. If you want a digest which maintains the original structure of the messages without flattening them to plain text, the messages have to be separate message/rfc822 parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' I have checked if there is already a subscription with that email address, but that's not the case. Best Regards,Eric On Thursday, January 14, 2021, 08:43:54 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/9/21 5:39 AM, Eric Broens via Mailman-users wrote: > For one of our mailinglists we also have a problem with accepting a subscription request. > When Clicking "Accept", we get a 404 Not found error. > See the attached screenshot. > Is there a way to solve this? Content filtering removed your screenshot so we can't see it. What is the URL that gives the 404? How does this compare to the URL of the held message view? -- 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, 5 months

Search results for query "sapiro"