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

[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, 1 month

[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, 3 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/

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

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Mark, Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow. Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image. The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error... Now answering your questions: ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? > I've checked settings.py inside the container and I haven't found any of the mentioned configurations there. Does the manage.py that's being run here point to the right settings.py? > No clue. Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image? https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Danil > -- > 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: Cannot Run Web Frontend

by Mark Sapiro

On 12/26/25 08:02, dap1--- via Mailman-users wrote: > SELECT name FROM hyperkitty_mailinglist; > +--------------------------+ > | name | > +--------------------------+ > | lllllllll(a)ddddddddd.net | > | lllllllll(a)gmail.com | > +--------------------------+ > 2 rows in set (0.00 sec) > > It seems just deleting lllllllll(a)ddddddddd.net is non-trivial. > Cannot delete or update a parent row: a foreign key constraint fails (`mailmanweb`.`hyperkitty_email > `, CONSTRAINT `hyperkitty_email_mailinglist_id_2c2b6f03_fk_hyperkitt` FOREIGN KEY (`mailinglist_id`) REFERENCES `hyperki > tty_mailinglist` (`id`)) This is not a critical issue so you can just ignore it until you get the web UI working at which time a Django superuser or the list owner can delete the list in HyperKitty's web UI. If you want to do it in the database, I think you can first do DELETE FROM hyperkitty_attachment WHERE hyperkitty_attachment.email_id IN (SELECT id FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net')); to delete attachments and then do DELETE FROM hyperkitty_email WHERE hyperkitty_email.mailinglist_id IN (SELECT id FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net'); to delete the emails and finally DELETE FROM hyperkitty_mailinglist WHERE hyperkitty_mailinglist.name = 'lllllllll(a)ddddddddd.net'; But this may possibly run into other foreign key constraint issues. It's probably easier to get the web UI up and do it there. > netstat -lntp > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 1103/systemd-resolv > tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1407/mysqld > tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1644/smbd > tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1644/smbd > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 74794/python3 > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 74791/python3 > tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 1103/systemd-resolv > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 74696/master > tcp 0 0 0.0.0.0:26 0.0.0.0:* LISTEN 1/init > tcp 0 0 127.0.0.1:33060 0.0.0.0:* LISTEN 1407/mysqld > tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 160003/cupsd > tcp6 0 0 :::443 :::* LISTEN 132763/apache2 > tcp6 0 0 :::445 :::* LISTEN 1644/smbd > tcp6 0 0 :::139 :::* LISTEN 1644/smbd > tcp6 0 0 :::80 :::* LISTEN 132763/apache2 > tcp6 0 0 :::25 :::* LISTEN 74696/master > tcp6 0 0 :::26 :::* LISTEN 1/init > tcp6 0 0 ::1:631 :::* LISTEN 160003/cupsd > > I'm not using IPV6. Nothing is listening on 8000, just 8001 and 8024. > > It appears that guicorn is not running if there is supposed to be a process by that name. There is also no such service. See https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… Particularly the part that says: If using Gunicorn, the ExecStart line above becomes: ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application Do you have that and is the mailmanweb service running? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 14:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 12:15 PM, Rafael Mora wrote: > > > > Should I configure my private Centos7 server with subdomain > > lists.labbrands.com? > > Doing so how do I redirect the email to the private Centos where postfix > > and MM3 are installed? > > > Create a DNS A record for lists.labbrands.com with the IP of the Mailman > server. You will also want a rDNS PTR record pointing from the IP to > lists.labbrands.com. > Does the rDNS PTR record should be placed in my Centos7 server? I've created the DNS A record for lists.labbrands.com with the IP but I don't know the port that it uses so I can make a port redirect to my local ip address wich is 192.168.1.42, do you know the port????? > > -- > 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

8 years, 9 months

[MM3-users] Re: Mailman will not restart

by Christian

Yes, thank you Mark & Peter. I did that and also eliminated locks that were appearing and it is now working. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, March 8, 2023 3:10 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman will not restart On 3/8/23 12:34, peter(a)chubb.wattle.id.au wrote: >>>>>> "Christian" == Christian via Mailman-users <mailman-users(a)mailman3.org> writes: > > Christian> , line 36, in <module> Mar 08 20:17:45 > Christian> zarathustra.ccalternatives.org mailman[31893]: from > Christian> typing_extensions import Concatenate as Concatenate # 3.10 > > You probably need to update the typing_extensions package. inside your > venv. Yes, but why? Something upgraded sqlalchemy > 2.0 but didn't install all its dependencies. The latest versions of sqlalchemy require typing-extensions but sqlalchemy<2.0 didn't require that. So in the venv, `pip install typing-extensions` will probably solve 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ 2SXACQYNAHYSUYY4G33PQQDJKKAIBZZM/ This message sent to csa(a)web-analysts.net

3 years, 2 months

[MM3-users] Re: Mail control not given from Mailman 3 to postfix

by Mark Sapiro

To follow up, I received the traceback and the dump of the shunted message off-list. The traceback is ``` Jul 07 21:36:47 2020 (26815) Uncaught runner exception: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues) TypeError: sequence item 0: expected str instance, Header found Jul 07 21:36:47 2020 (26815) SHUNTING: 1594138007.5613732+1a5932f41fb4cfcd18c9b0b0ac6f999c84408577 ``` This was apparently caused by an invalid RFC 2047 encoded To: header which encoded the entire header including the address as one base64, unknown-8bit character set encoded word. However, despite trying with several different Python versions, I was unable to recreate the TypeError, so the reason for this exception remains unknown.

5 years, 9 months

Search results for query "sapiro"