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

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I think I found the bug; I have posted a comment to the issue mentioned by Mark https://gitlab.com/mailman/postorius/issues/58 Regards Claus Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: > Oh well. > > Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>> >>> Seemingly, at some point in the deep dungeons of the source code the >>> "Acceptable aliases" Text-Box is not interpreted correctly. >>> >>> Specifically, at the start it contains the string >>> >>> [] >> >> >> See <https://gitlab.com/mailman/postorius/issues/58>. > > there they talk about fancy "uni-code thinks" (email addresses?) where > the task is to convert a new-line separated text-field into an array. Oops. > > Kind thanks anyway. > >> >> In order to set things on this page, you need to clear the Acceptable >> aliases box before submitting changes. You can't actually set Acceptable >> aliases via Postorius until this is fixed. > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. > > Thanks > > Claus > > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 8 months

[MM3-users] Re: installation

by Henry S

Thanks Mark and Brian. I'll try the suggestions. My IP might have got blocked by CBL when testing mailman3 against a Gmail address. I have since removed it from CBL. I don't know how my IP got into the Outlook's block list. Maybe a used one. Will try DKIM signing and Microsoft programs. On 23/11/2020 11:59 am, Brian Carpenter wrote: > > On 11/22/20 6:54 PM, Henry S wrote: >> >> Now I am trying to figure out how to configure mailman+postfix to >> pass the unnecessarily convoluted world of spam-free certification >> and ip blockings by those 'security lawmakers'. >> >> Any suggestions on how to not be blocked by gmail, hotmail, etc? I >> have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an >> appropriate question to this mailman list. > > Mark Sapiro provided some very good suggestions. > > Is this a new IP address or one that has been used for mail traffic > for a white? The only way Gmail and Hotmail will block an IP address > is if you have some major outgoing spamming problems or in the case of > a new IP address, the IP address has a sordid history which will be > reveal if you do a RBL check on it. > > Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. > > For Hotmail deliveries, you will want to signed up for Microsoft's > Smart Network Data Service (SNDS) program which I find very good. Also > sign up for their JMRP program for your IP address. > >

4 years, 5 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi Mark, thanks for correcting my assumption. Based on your information I have been able to identify the suspect message file in /var/lib/mailman3/messages, replace the suspect file with another file, update the file permissions and successfully load the held messages page. This allowed me to discard the suspect message and other held messages are then available for review again. In case the steps below help someone else who is having this issue here are the steps I followed with my initial search string redacted: Searched all files in messages folder for matching string: cd /var/lib/mailman3/messages grep -ir [REDACTED] * Finds string in one file: Binary file HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV matches Check whether file can be parsed using mailman command: mailman qfile ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Throws a matching error: [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 97, in main args.func(args) File "/usr/lib/python3/dist-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/lib/python3.6/pprint.py", line 161, in _format rep = self._repr(object, context, level) File "/usr/lib/python3.6/pprint.py", line 393, in _repr self._depth, level) File "/usr/lib/python3.6/pprint.py", line 405, in format return _safe_repr(object, context, maxlevels, level) File "/usr/lib/python3.6/pprint.py", line 555, in _safe_repr rep = repr(object) File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 45, in __repr__ return self.__str__() File "/usr/lib/python3.6/email/message.py", line 135, in __str__ return self.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) Move suspicious file out of messages: mv ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV /root/20200914/ held_messages page still throws 500 error. Checking debug log, it is now because the database references a file that is no longer there. Can I just copy a parseable file to the path of the bad file so I can delete it or do I need to remove the reference from the database? Copy some other file: cp ZZ/B2/ZZB24ADTZ2BOKBWTQWI7KG4XACGR6DTJ HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Still throws an error but this time it's a permissions error. mailman can't access the copied file: ls -l HE/D7/ -rw-r----- 1 root root 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chown list:list HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chmod g+w HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV ls -l HE/D7/ -rw-rw---- 1 list list 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV held_messages now loads OK. Cheers, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, 12 September 2020 06:17 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 8 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Mon, 31 Oct 2022 09:38:37 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/22 00:17, Onyeibo Oku wrote: > > > > It is not finding the logger file. The other django project on this > > machine is running fine. I can confirm that the logger plugin is > > installed. I must be missing something. > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > take note of > ``` > # Make sure that this directory is created or Django will fail on > start. LOGGING['handlers']['file']['filename'] = > '/opt/mailman/web/logs/mailmanweb.log' > ``` > ` [Reviving this thread]. I abandoned the hyperkitty setup for a while and returned to it again today. I made progress. It turns out that I needed the uwsgi-logger-file rpm package and It wasn't installed with the uwsgi server. I adapted the settings also, since I was using Emperor mode (recall that there are other Django projects on the box). Currently, mailman, uwsgi and nginx are all running. They all seem to be happy until I assess the mailman-web home URL (e.g. http://my.server.com) The outcome: "502 Bad Gateway" Nothing shows in the logs except at /var/log/nginx/error.log: 2022/12/08 15:35:10 [error] 5879#5879: *7 upstream prematurely closed connection while reading response header from upstream, client: 105.113.33.89, server: my.server.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8000/favicon.ico", host: "my.server.com", referrer: "https://my.server.com/". Something seems to be wrong between uwsgi and mailman, but I don't know where to look. Regards Onyeibo

2 years, 5 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

> Fra: Mark Sapiro [mailto:mark@msapiro.net] > Sendt: 2. oktober 2017 17:26 > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > There is no user or list admin workaround, but the defense is a fairly > simple patch. See the MR at > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > at > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > The commit changes 7 files, but only two are needed. The rests are tests > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't >necessary. > > The only changes you need are those to mailman/email/message.py and > mailman/mta/connection.py. I am using Docker-mailman (not yet very familiar Docker and version control). I would expect I have to wait for a Docker-mailman release including this change, right? I have at least five+ lists which almost haven't been working since my switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am desperate trying to figure out whether it is best to fall back to the Mailman 2 server, for the time being, where the lists came from, or it is better to wait for an update to the Docker-image. Will https://github.com/maxking/docker-mailman/milestone/2 fix my problems regarding failed mail handling and will it become available soon (when?) (https://github.com/maxking/docker-mailman/issues/147)? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 7 months

[MM3-users] Re: mailing list aliases

by Abhilash Raj

On Fri, 2018-01-19 at 16:30 -0800, Mark Sapiro wrote: > On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > > Not sure whether to mark this "SOLVED" yet - but when I manually updated > > postgres DB with the aliases I wanted - everything started to work as > > expected. > > > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > > was it already fixed in 3.3.1 (anouncement page didn't list that fix) > > > As far as I know, this is not a bug in core. It is > <https://gitlab.com/mailman/postorius/issues/58> however, this may in > fact be a bug in the REST API in which case I don't think it's fixed in > API 3.3.1 I guess we are all talking about the same thing, but just to mention, 3.1.1 is the latest release (instead of 3.3.1). > > > > 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to > > > foo(a)lists.my.com however we've preserved old addresses. But in new setup > > > mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: > > > implicit-dest" . What's the best course of action here to get mailing > > > list respond to multiple email addresses? > > > acceptable_aliases is the way to address this, but as you note, it can't > be properly set via Postorius and possibly via REST. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 3 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/31/20 10:28 AM, Brian Carpenter wrote: > Hi Mark, > > This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. Now the email address that made this request does not show up at all in any of my logs. There is no record of them making a previous subscription attempt before the subscription policy was changed to moderate. Here are some observations: > > 1. The two occurrences of this happening was to Gmail users. > 2. The two occurrences of this happening was when an email is being sent to the listname-subscribe@listdomain address. > 3. This is only happening on 1 list. > > This may have no bearing on the issue but the list address of this problematic list is ******-owners@listdomain. I know there is an alias created for each list that is listname-owner@listdomain. Just throwing that out there. > > <princess-leia-voice>Help me Obi-Wan Sapiro. You are my only hope.</princess-leia-voice> > _______________________________________________ > 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/ So I confirmed this happening on another MM3 server. Setting a subscription policy to open/moderate and sending an email to listname-subscribe@listdomain from an email address that has no previous interaction with the MM3 server results in a confirmation email being sent out. So the question now is: Is this a bug? Or an intentional design? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Allan Hansen

Thank you, Mark, as always. We upgraded to the latest versions: Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] Also, I don't have any umbrella lists. Yours, Allan On 12/4/22, 20:33 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- 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: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/PTXMXLRL4XLU5O7VW6X347FMQ3DLLXIK/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 5 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by IEM Network Operation Center (IOhannes m zmölnig)

thanks both Mark and Odhiambo (who replied off-list) for your answers. On 8/6/24 18:40, Mark Sapiro wrote: > On 8/6/24 01:43, noc(a)iem.at wrote: >> >> but how can i export an entire MM3 list (including 20 years of >> archives) to some serialization format, and import it again in another >> instance? > > > With the dump and other utilities from your database manager. Almost > everything is in the database. There are some things in Mailman's var/ > directory, but those can simply be moved. > urgh. while this will (hopefully) work with a fresh installation, i'm somewhat afraid whether this will also work for: - migrating a single list from one instance to another (at least, if you (like me) do not have have an intimate knowledge about the db layout) - importing lists into an instance that is already populated with other lists (things like changed db schemas come to my mind) right now my task is to move both some MM3 lists (from an old MM3 instance) and some MM2 lists onto a single server with a fresh installation, so i guess i will be fine. my worries are mostly about future migrations. is a feature-request warranted, or am i worrying too much? gfasmdr IOhannes PS: thanks for finding and fixing the issue with my PGP signature not allowing me to post! ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

9 months, 1 week

[MM3-users] Re: Prototype import [was: Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)]

by Mihai Moldovan

* On 4/20/25 02:26, Mark Sapiro wrote: > This appears to be a bug in mailbox.mbox. To work around it, try this: > ``` > [...] > ``` Thanks, that works! > Those headers are added by the rfc_2369 handler based on the archivers > configured for the list. They will never point to the prototype archiver > or the message in the prototype archive. > > Normally they will point to HyperKitty and to the archived message in > HyperKitty. This is the case even for messages in the prototype archiver > as those messages are just the message as delivered to the list members > absent any personalization. Yes, it iterates through all archivers and gets the permalink and archiver's URL, adding it to the message if the data is non-empty. > Note that the generation of these headers by the rfc_2369 handler > depends on this script being run in an installation that has hyperkitty > and mailman-hyperkitty installed and the hyperkitty archiver enabled for > the list. There is one other thing that caught me off-guard: I had the Hyperkitty archiver enabled, of course, but the service was not running (I essentially turned off everything, including the cron jobs, for the migration, to make sure that no new data is coming in). In order for mailman to query the required data, it has to communicate with the archivers (like Hyperkitty) and that in turn means that the archiver must be running. After starting Hyperkitty, the headers magically gained proper values! Thank you very much for your help. Mihai

4 weeks, 1 day

Search results for query "sapiro"