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

[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

4 years, 4 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

2 years, 5 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

9 years

[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

7 years, 7 months

[MM3-users] Re: Accept these non-members

by Mark Sapiro

On 3/6/26 12:52, Lars Bjørndal wrote: > Thanks! You wrote: > >> On 3/6/26 02:43, Lars Bjørndal wrote: >>> Hi, list! >>> >>> I have an announce only Mailman3 list. When I log into the web interface >>> as an admin user, and go to the specified list, and choose Settings, I find >>> the Message Acceptance tab. There, I find the edit field Accept these >>> non-members. But this field is empty, although I know that some people >>> have permissions and are able to post to this list. How can I find the >>> list of these non-members and add more people or delete someone? >>> >>> I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. >> >> I don't know what mailman-web version 4.2.21 is. Is this some downstream >> package? > > With `pip list`, some of the packages is: > > Django 4.2.21 > django-mailman3 1.3.15 > HyperKitty 1.3.12 > mailman 3.3.10 > mailman-hyperkitty 1.2.1 > mailman-web 0.0.9 > mailmanclient 3.3.5 > postorius 1.3.13 So your mailman-web is 0.0.9 and it's Django that's 4.2.21. I understand. >> These are nonmembers whose moderation action is accept or defer. If your >> Postorius is >= 1.3.6, and the number of nonmembers is manageable you can >> just view the nonmembers list in Postorius and see their moderation action. > > You mean from the web interface at example.com/mailman3 > list? Yes >> Otherwise a `mailman shell` interaction like >> ``` >> $ mailman shell -l list.example.com >> 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. >> The variable 'm' is the list.example.com mailing list >>>>> for nm in m.nonmembers.members: >> ... if nm.moderation_action in (Action.accept, Action.defer): >> ... print(f'{nm} {nm.moderation_action}') >> ... >>>>> >> ``` >> will print those nonmembers with Action.accept or Action.defer. > > What's the difference between Action.accept and Action.defer? Action.accept accepts the message immediately with no further checks. Action.defer passes the membership checks but still goes on to check other things like mis-addressed email commands messages with implicit destination messages with too many explicit recipients messages that are bigger than a specified maximum messages with no, or empty, Subject headers messages with digest Subject or boilerplate quote messages matching a bounce_matching_header line -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: New install - The Message have no valid senders

by Mark Sapiro

On 3/30/22 04:30, kenneth.karlsson(a)eco.cept.org wrote: > > The command: > EHLO contoso.com > mail from: <xxx(a)xxx.com> > rcpt to: <mhtest(a)list.cept.org> > DATA > This is a test message > . Some headers in the message might be nice. > Accepted by Postfix: > Mar 29 11:17:17 lits01a postfix/smtpd[4088]: B86DD6A04B9: client=unknown[192.168.200.157] > Mar 29 11:17:30 lits01a postfix/cleanup[4091]: B86DD6A04B9: message-id=<> In my case, Postfix adds a Message-ID: header and logs it here. > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: from=<xxx(a)xxx.com>, size=200, nrcpt=1 (queue active) > Mar 29 11:17:30 lits01a postfix/lmtp[4109]: B86DD6A04B9: to=<mhtest(a)list.cept.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=24, delays=24/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Mar 29 11:17:30 lits01a postfix/qmgr[3952]: B86DD6A04B9: removed > > MM receives it: > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) handling connection > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'LHLO list.cept.org' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'MAIL FROM:<xxx(a)xxx.com>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) sender: xxx(a)xxx.com > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'RCPT TO:<mhtest(a)list.cept.org>' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) recip: mhtest(a)list.cept.org > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'DATA' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) Data: b'QUIT' > Mar 29 11:17:30 2022 (3940) ('127.0.0.1', 37146) connection lost > Mar 29 11:17:30 2022 (3940) Connection lost during _handle_client() These log messages come from aiosmtpd which is used by mailman/runners/lmtp.py to implement Mailman's LMTP server. Clearly, aiosmtpd sees the envelope sender as xxx(a)xxx.com, but > But MM3 discards it: > Mar 29 10:08:03 2022 (1767) DISCARD: <164854848338.1768.3954079936807939297@lits01a>; ['The message has no valid senders'] This is because Mailman's NoSenders rule gets an empty response from the messages `sender` method. This means there is no address in any of the messages From:, Reply-To: or Sender: headers which is expected, but it also says that the message's get_unixfrom() method didn't return an address as this is checked between From: and Reply-To:. I tried a similar test, but in my case, Postfix (3.4.13) added Message-Id:, Date: and From: headers, so that wasn't definitive, but I then added logging to the LMTP runner at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… to log the unixfrom and the message and the message did have a unixfrom as added by the LMTP runner, so even without the Postfix added header, it had a sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 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/

5 years, 7 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Michael Sage

Thanks for your tip about digging deeper into the logs! Turns out it was a postfix issue (the hash files hadn't been created), which was causing it to loop and crash out. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: 12 June 2019 17:56 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup On 6/12/19 9:53 AM, Michael Sage wrote: >> This seems like something I've seen reported before, but I can't find it now. > >> Is anything logged in the various Mailman, Django, Apache logs? > > Nothing at the time in the Mailman, Mailman web or apache (error or > access) logs, I can't find any Django logs I am afraid. I only have > standard logging, happy to turn any debugging logging that you think > might help The Django log is most likely the one named mailman_web. -- 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/

7 years, 2 months

[MM3-users] Re: list owner creation

by Christian Stalberg

Via Postorius. I added the user back using the same page. Thank you! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, February 21, 2021 4:29 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list owner creation On 2/21/21 4:15 PM, Brian Carpenter wrote: > On 2/21/21 6:50 PM, Christian Stalberg via Mailman-users wrote: >> If one inadvertently deleted a list owner account, how could one >> either create a new account and make them a list owner -or- make an >> existing account a list owner? Thanks! > > Are you talking about deleting the account via the Django admin > interface or via Postorius? > Yes, the answer depends on what you did and what tools you have available. For example, if you deleted the owner via the Delete button on the page at <https://example.com/mailman3/lists/list.example.com>/members/owner/>, you can add it back on the same page. You need to tell us what you did. -- 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/

5 years, 5 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/10/19 5:35 AM, Marvin Gülker wrote: > Am 10. Dezember 2019 um 17:09 Uhr +0900 schrieb Stephen J. Turnbull: > >> I would guess this is in the shunt queue. If there's only one file >> there, you can just delete it. The issue in this case is not a shunted message. it is a message held for moderation. The message itself is in Mailman's var/messages/ directory. It is pointed to by an entry in the database 'message' table. The var/messages/ directory contains two levels of subdirectories and the message files. The file name is the message-id hash. The first subdirectory is the first two characters of the name and the second subdirectory is the next two characters of the name. E.g. a message with message-id hash = UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X will be stored as a pickle in the file var/messages/UP/ZX/UPZXRAAO6Q7HDDJR7LH5NAYTIX57C32X. The underlying issue here is probably <https://bugs.python.org/issue32330>, but that knowledge doesn't help us. We need to get rid of the offending message in the message store. The first step is in mailman shell. Note the paths /opt/mailman/mm/bin/ and /opt/mailman/mm/var/ will need to be adjusted. /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/opt/mailman/mm/var/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID-Hash']) ... This should print the file name and Message-ID-Hash (two lines the same) for each message in the messages directory until it prints only one line followed by the UnicodeEncodeError exception. That list line is the file name/Message-ID-Hash of the offending message. Then you need to run the query DELETE FROM message WHERE message_id_hash = xxx; against the mailman database where xxx is the hash value you found above. > I confess that I haven't visited the held messages page for a very long > time (because I didn't have a reason to; I received no notifications of > held messages). Only after I received the notification that my > errorneous message was being held, I visited it, and I was faced with > the 500 error. If Mailman failed to notify me of held messages > previously, they might have been in hold status already and one of them > might be the cause. As of Mailman core 3.3.0 there is a 'mailman notify' command designed to be run periodically by cron to notify owners/moderators of prnding requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Search results for query "sapiro"