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

[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

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

4 years, 3 months

[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

3 years, 2 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/ >

6 years, 3 months

[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

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

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

2 years, 3 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.

4 years, 11 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

ok, thanks Mark, I'm getting an error doing: (env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management What do you suggest?? El vie., 21 jul. 2017 a las 14:31, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:07 PM, Rafael Mora wrote: > > Installing mailman-suite for web ui. I did this: > > > > (env) [mailman@localhost ~]$ git clone > > https://gitlab.com/mailman/mailman-suite/ > > Cloning into 'mailman-suite'... > > error: RPC failed; result=22, HTTP code = 404 > > fatal: The remote end hung up unexpectedly > > > > > > but it returned an error, what should I do?? > > > It's another case of incorrect docs. It should be > > git clone https://gitlab.com/mailman/mailman-suite.git > > See <https://gitlab.com/mailman/mailman-suite-doc/issues/15>. > > -- > 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

Search results for query "sapiro"