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

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by Mark Sapiro

On 1/26/22 11:05, nate wrote: > > Can I suggest the messaging to new users be improved to communicate > this situation as it is not clear. > > The automated message I got said this was the reason my message was > held: The message comes from a moderated member. > > Which makes sense if I REALLY think about it(I was a moderated member > at first), but then the next question is why was I moderated. Your > explanation makes sense. > > It would be nice if it had more info along the lines of what you > said, or even better adjust the messaging for the "Welcome" email > to indicate your first message(s) will be held for moderation(I checked > both emails I got back from the list just now to verify this info is > not there). I was confused for a while(again 21 year veteran of mailman) > thinking I sent my message using the wrong email address, after confirming > I sent with the right one I just decided to wait to see what would > happen. The situation is no different in Mailman 2.1. The issue is that what may be appropriate in the held message to the user or the list welcome message depends on list configuration and the policies of the particular list. Thus, we can't really modify the default message templates in this way. It requires making list specific templates or possibly domain or site specific templates where all the lists in a domain or site have the same policies. This can be done by list, domain or site admins, but doing or suggesting this on a site like, e.g., mail.python.org which has 232 Mailman 2.1 lists with a total of 243 unique owners and 182 Mailman 3 lists with a total of 212 unique owners is a daunting prospect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 18:35, Joel Lord wrote: > > The periodic digests do seem to be coming out. I also now have > confirmation that the one message in this morning's digest that was from > May 4th was also included in the last digest back on May 4th, so it > seems that the one message was left behind in the digest queue when the > periodic digest was sent. I don't see how that can happen. The process that sends a digest renames the var/lists/<list-id>/digest.mmdf mailbox file in which the messages are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and <issue> are the volume and issue numbers of that digest, and then queues a message in the `digest` queue to tell the digest runner to create the digest from the messages in that mbox and send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that is created anew when the next post arrives. Further, if there is a non-empty digest.mmdf file, its messages should be sent no later than the next 11 PM `cron digests`. > There was one earlier message to the list > back on May 4th, before the one that got duplicated, but I can't tell if > that triggered a size-based digest to be sent: the logs aren't clear > enough on that detail for me to tell. OK > Just to inform things: > > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman > django-mailman3==1.3.9 > mailman==3.3.8 > mailman-hyperkitty==1.2.1 > mailman-web==0.0.6 > mailmanclient==3.3.5 > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper > mailman-hyperkitty==1.2.1 Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others. > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post > postorius==1.3.8 > > -- 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: Why aren't I getting bounce texts any more?

by Mark Sapiro

On 6/9/26 9:13 AM, Paul Tomblin via Mailman-users wrote: > > I use Postfix for my MTA, and like I said I swear I used to see the DSNs before, but this round I’m not seeing them. What were the list settings for `Notify owner on bounce increment` and `Notify owner on disable` during this round. You said in an earlier post that `Notify owner on bounce increment` was off. If `Notify owner on disable` was also off, that would explain why you didn't get these notifications. One wrinkle is the fact that I’m hosted on Linode, and one of the big RBL providers has a bug up his ass about Linode and so instead of just blacklisting the instances that produce spam, he’s basically blacklisting all of Linode. And because of that, I relay my outgoing mail through a friend in Norway. I wonder if that relay has started swallowing the bounce message while still returning the bounce status? If it returned a bounce status to the sending MTA, the sending MTA would have generated a bounce DSN. Further, if the notification settings were on, you would have received notices even if the DSNs were unavailable for some reason. > I did, however, get a plaintive email from a little old lady on the list who said “But I don’t want to unsubscribe from the list”. So I guess she at least got her “you’ve been removed’ email. Which again, increases the mystery. > > This particular round of “too many bounces” disables all happened in a matter of an hour or so, preceded a couple of days earlier by some others. Does mailman bundle those up and process them all in a batch? No, they are processed at intervals defined by the bounce runner's sleep_time as defined in mailman.cfg with a default of 2 minutes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: Attachement processings questions

by Lars Schimmer

On 2020-02-04 19:15, Mark Sapiro wrote: > On 2/4/20 9:02 AM, Mark Sapiro wrote: >> >> You can fix it by patching the Python library email/generator.py as at >> <https://github.com/python/cpython/pull/18056/files#diff-220640ea02a24dfdbb0…>. > > > > And once you have patched email/generator.py and restarted Mailman core, > you can deliver the messages by running the `mailman unshunt` command, > but first look in var/queue/shunt/ to ensure you won't be unshunting any > unwanted messages. You can examine those files with `mailman qfile`. Great This did helped. Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

6 years, 6 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

On 6/28/20 12:55 PM, Mark Dadgar wrote: > > So in trying to download the recent archives ("export/trackjunkies-new.mbox.gz?start=2019-10-10&end=2020-06-28”), I end up with an 8.5MB file with one day’s worth of posts in it (2019-10-10). > > I see these errors in the mailman-web.log: > > Traceback (most recent call last): > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2060, in get_msg_id > token, value = get_dot_atom_text(value) > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1325, in get_dot_atom_text > raise errors.HeaderParseError("expected atom at a start of " > email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found ' <BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>' If I'm reading the above correctly, it appears that there is a message in the archive database whose message_id value is 'BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>'. The trailing '>' is causing HyperKitty's Email.as_message() method to try to set a value of '<BYAPR02MB5976132151FF19510269C44CB3940(a)BYAPR02MB5976.namprd02.prod.outlook.com>>'. Or maybe there's leading white space in the value, or both. Try the following patch. --- a/hyperkitty/models/email.py +++ b/hyperkitty/models/email.py @@ -24,7 +24,7 @@ import logging import os import re from email.message import EmailMessage -from email.utils import formataddr +from email.utils import formataddr, make_msgid from django.conf import settings from django.db import IntegrityError, models @@ -175,7 +175,12 @@ class Email(models.Model): header_date = self.date.astimezone(tz).replace(microsecond=0) # Date format: http://tools.ietf.org/html/rfc5322#section-3.3 msg["Date"] = header_date.strftime("%a, %d %b %Y %H:%M:%S %z") - msg["Message-ID"] = "<%s>" % self.message_id + try: + msg["Message-ID"] = "<%s>" % re.sub('[<>\s]', '', + self.message_id) + except: + msg["Message-ID"] = make_msgid() if self.in_reply_to: msg["In-Reply-To"] = unfold(self.in_reply_to) Also note that if you got 8.5.MB for one day's messages, probably the entire range will time out and you'll have to get it in pieces. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/4/26 02:21, Chihurumnaya Ibiam via Mailman-users wrote: > > You're right about "localhost" causing confusion, I switched to using the > > IP address instead, the logs > > showed that Mailman tried to connect on [::1] and there wasn't a response, > > that might be from Mailman itself though as the > > port is open. > > I don't have a preference for IPv6. > > Edit /etc/hosts and change the localhost entry from ::1 to 127.0.0.1 > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan I just did.

6 months, 2 weeks

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/23/21 10:51 AM, David Bremner wrote: > > I'm getting (many) uncaught bounce messages for one user. Other than > forcibly unsubscribing them, is there anything I can do? I hesitate to > post this message publically, but here is what I can see, somewhat > anonymized If you send me the complete bounce message off list, I can see if it should be added to the recognition at https://gitlab.com/warsaw/flufl.bounce/. BTW, is flufl.bounce in your installation version 4.0? If not you can update via pip install -U flufl.bounce which may help. Actually, depending on how these where installed, it might be necessart=y to do pip install -U flufl.bounce flufl.lock flufl.i18n To avoid import errors due to packaging issues. > The MIME structure looks like > > └┬╴multipart/mixed 7030 bytes > ├─╴text/plain 442 bytes > ├─╴message/delivery-status 176 bytes > └─╴text/rfc822-headers 5301 bytes This is not a RFC 3464 compliant DSN which looks like the above except the top level is multipart/report, not multipart/mixed. However, our recognizer shouldn't care as it only looks at the message/delivery-status part. > In /var/log/mailman3/bounce.log I see lines like > > Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> <hex-digits(a)foo.bar> is the Message-ID: > In the delivery-status part I see A compliant DSN will also have a Reporting-MTA: section preceding the Final-Recipient: section. > Final-Recipient: rfc822; fub(a)foo.bar > Action: delayed > Status: 4.0.0 This is not a bounce. It is a 'delivery delayed' message. If delivery is not accomplished within an MTA configured time (days), it will turn into a 5.x.x failure which is a bounce, but since fub(a)foo.bar was not recognized, the DSN is non-compliant in some way. In any case, please send me a copy of the bounce so I can see about recognizing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: How do you remove the Hold on all non-member forwarded emails?

by Mark Sapiro

On 5/26/23 12:38 PM, Sean Westfall wrote: > > But I am having trouble using one of its configurations. I configured my mailmain3 instance to accept all non-member emails, as I want all emails that are sent to the mailman client to go to all subscribers without having it held for moderation -- I did this by setting this setting: > > https://i.imgur.com/PGzaD0k.png > > Action to take for postings from non-members for which no explicit action is defined. (Details for generic_nonmember_action) -> "Accept" That screen shot and language is from Mailman 2.1, not Mailman 3. > But this doesn't work for forwarded emails. Even if the email address that is being forwarded from is included in the "List of non-member addresses whose postings should be automatically accepted." > > I noticed that all emails that are forwarded to the mailing list are always held for moderation -- though this isn't the case for email that are sent to the mailing list directly. But I want it so that emails that are even forwarded to my mailman mailing list don't get held in moderation. > > How do I set mailman to do this? I was thinking if there is no way to configure this easily then I might have to do this from the code, which means I might have to ask on the developer mailing list -- or I have to go with an entirely different solution (using something other than mailman3). Please clarify whether you are using Mailman 2.1 or Mailman 3. There should be no difference between a message sent directly vs. a forwarded message. What is the reason given for why the message is held? Also, the appropriate list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. -- 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: Message does not appear in archive

by Mark Sapiro

On 09/03/2018 06:13 PM, Paul Arenson wrote: > Hi again. I take it the lack of responses mean I should wait it out a little longer? It's of course up to you, but I recommend Mailman 3. There are still some rough edges, and there are a number of settings not yet exposed in Postorius, but we are working on it and it is quite usable today. > I was considering, as mentioned, Fed Forum (but not much help in setting up), Slack and Flock. Would all mean more work than I can afford. > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > > We would then have the perfect upgrade to Mailman 2, where people could more easily find their topics (aided by a lot of nudging to be proactive in choosing the topic to post in and not doing thread hijacking). Do you mean Mailman 3? > I looked to see if there was anyone doing this sort of service. All I could find is someone doing their own hosting called https://mailman3.com/. mailman3.com is a Mailman 3 hosting service unaffiliated with the GNU Mailman project. > I would much prefer to upgrade my C-Panel installation of the lists, which by the way are here: > > https://gale-sig.org/mailman/listinfo/galemembers_gale-sig.org > https://gale-sig.org/mailman/listinfo/galeexec_gale-sig.org > > Any estimate on if/when I would be able to upgrade these c-panel forums (or possibly get someone to help me move them?) I suspect it will be some time before Cpanel offers Mailman 3. It is fairly straightforward to migrate an existing Mailman 2.1 list and it's archives to Mailman 3, but it requires access to the underlying Mailman 2 file system which you may not have in a hosted cPanel environment. See <http://docs.list.org/en/latest/migration.html> for more on migration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/26/24 02:44, Marco van Tol wrote: > Op 25 jan 2024, om 14:16 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >> >> Okay, so, I got a bit further, but something still gets stuck. >> >> Here’s what I did. >> Keep in mind I’m using containers that are built from some CI/CD pipeline, so I updated the pipeline to apply the patch attached to this email to `/usr/lib/python3.11/site-packages/xapian_backend.py`. >> >> Before I had 2 list servers with the “Term too long” issue, 1 got resolved by this, and the other did not. >> I opened a shell in the newly deployed container to confirm the patch was applied in it. >> >> The other attachment to this email is a copy/paste from the full error from `./manage.py rebuild_index`. >> >> Is there something else special in the email that makes it choke that evades the xapian patch? >> >> Thank you very much in advance! The message above with the attached "full error" never got to the list. What is the error report? > > I tried to change to ‘hash’, but the code in that bit of the function has not been tested enough. > > For example `hole = sha224(hole.encode('utf8')).hexdigest()` comes back with that the bytes object hole does not have an encode() method. > When I change it to `hole = sha224(hole).hexdigest()`, the following error is: That's only part of it. You need hole = sha224(hole).hexdigest().encode('utf8') > text = text[:match.start()] + hole + text[match.end():] > TypeError: can't concat str to bytes > > The ‘hash’ part of that function needs some debugging. Yes, presumably because no one sets `XAPIAN_LONG_TERM_METHOD=hash` in the environment. Do you have a reason for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Search results for query "sapiro"