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

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Abhilash Raj

On Fri, Jun 21, 2019, at 2:07 PM, Mark Sapiro wrote: > On 6/21/19 6:54 AM, andrew.bernard(a)gmail.com wrote: > > How can one do this? Raw database access gets you involved in all the usual foreign key constraints. > > > In the HyperKitty thread view there is a link to "Delete this thread". > In the message view there is a link to "Delete this message". Do note that this option is only visible to "Superuser" in Django, i.e. Admin accounts. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 8 months

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

by Mark Sapiro

On 8/4/21 2:15 PM, Bryan Loniewski wrote: > Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. import21 was never intended to be run more than once for a particular list. > I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. That's not surprising. There may be other attributes that are duplicated or otherwise corrupted from running import21 multiple times. > Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? I don't think the 3.3.2 changes to import21 will avoid the duplications. I think there will be other issues as well. For example, if there are changes in membership or ownership on the 2.1 list import21 will probably pick up the additions but not the deletions. The intended use of import21 is for a one time migration of a MM 2.1 list to MM 3. It is not intended to somehow sync parallel MM 2.1 and MM 3 lists. If the idea is to run import21 to create a test MM 3 list while still running the MM 2.1 list in production, I would suggest to run import21 once and then when ready for the final migration, delete the MM 3 list, create a new, 'empty' list and run import21 on that. As far as hyperkitty_import is concerned, it can be run multiple times. If --since is not specified, it will only consider messages newer than the newest in the existing archive, and in any case will skip duplicate Message-IDs. -- 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: reset bounce-scores?

by Mark Sapiro

On 10/3/24 01:15, IEM Network Operation Center (IOhannes m zmölnig) wrote: > i'm running a mailman-3.3.8 instance, and would like to reset the > bounce-score for a (number of) user(s). > i searched the internet and this list's archives, but haven't found > anything useful so far. > > due to a misconfiguration of our universities reverse DNS lookup, the > bounce score of some users has rocketed in the last days - some users > have already been unsubscribed because of that. > > could anybody please share how i can reset the bounce score? First of all, there are 3 categories of affected list members - those who are already unsubscribed, those who are still members but have delivery disabled by bounce, and those with delivery enabled but with bounce score > 0. For those that have been unsubscribed, you just have to re-subscribe them. For those that have delivery enabled but a non-zero bounce score, you may not need to do anything because they are presumably not currently bouncing so eventually the old bounce info will become stale and be ignored, but to guard against spurious bounces that may result in disabling, e.g.from an over aggressive user's spam filter, you can add `verp_probes: yes` to the `[mta]` section of mailman.cfg. The effect of this is when a members bounce score reaches threshold the score is reset and a special probe message is sent and delivery is disabled only if the probe bounces. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… That leaves those with delivery disabled by bounce. Assuming you want to enable delivery for all members of all lists with delivery disabled by bounce, the following `mailman shell` interaction will do it. ``` $ bin/mailman shell 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. >>> for mlist in getUtility(IListManager): ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` Watch out for a possible wrapped line above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 5/1/21 4:58 AM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> ``` >>> msg["Message-ID"] = "<%s>" % re.sub('[ <>\r\n]', '', self.message_id) >>> ``` >> >> Thanks that did the trick. Will this need to go in the upstream release or is there any way I could re-import those messages into the database with a newer version of the import command from the original mbox from 2.1 to fix this? > >Sorry for not following up sooner. This got deferred and then forgotten :( > >I would like to see the offending message from the original mbox so I can develop an appropriate fix. What is the best way of getting that to you? You can download the mbox from your end of course, or I can revert the change so you can see where the original stopped. Thanks. Andrew.

4 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I changed them to 127.0.0.1 and localhost as you suggested El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > 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, 6 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/4/21 12:52 PM, Duane Raymond wrote: > > Virtual Domains: > So based on the Postfix virtual domain documentation and the Mailman3 specific "Unusual Postfix configuration' section, I added the following to my postfix main.cf file: > virtual_alias_domains = emaillistA.com emaillistB.com > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > and removed those domains from the 'mydestination' setting. You probably do not have a configuration that is a "Unusual Postfix configuration" Putting Mailman aside, is there some reason why emaillistA.com and emaillistB.com need to be virtual_alias_domains? If these domains are only for mail lists, they do not need to be virtual_alias_domains? > I then created the postfix_vmap file and added to it: > emaillistA.com DOMAIN > # > emaillistB.com DOMAIN You don't create these files. Mailman creates them in its var/data directory when you run `mailman aliases` or just start mailman core. > ...then ran postmap with the path and reloaded postfix. Mailman also runs the appropriate postmap commands. You should have one of two setups in Postfix depending on whether emaillistA.com and emaillistB.com need to be virtual_alias_domains or not. If they are only for list mail, they should not be virtual_alias_domains in Postfix and their domain definitions in Mailman should not have an alias domain. In that case, in Postfix you want transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains and you want Mailman to generate those files. Also see the note in <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> about adding hash:/path-to-mailman/var/data/postfix_lmtp to local_recipient_maps rather than replacing it. If emaillistA.com and emaillistB.com do need to be virtual_alias_domains, you configure them in postfix according to the normal postfix configurationfor virtual_alias_domains and virtual_alias_maps. Then each of these domains needs a corresponding, otherwise unused alias domain defined in Mailman and what you need in Postfix is transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap Where again if you have existing settings for these things, add the mailman files rather that replacing the existing with them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 9:30 AM, bob B wrote: > So just want to make sure I have the latest information after searching this list and googling or have I missed something? It appears there is no way in mailman3 to delete archives. There has been discussion on implementing this, but it has not been developed? is that correct? I'm not sure when it first appeared, but current Hyperkitty has Delete Archive button on the list overview page, but it is only available to Django superusers, not to list owners. > I saw references to: >>>> from hyperkitty.models import MailingList >>>> ml = MailingList.objects.get(name="test2(a)freeculture.org") >>>> ml.delete() > > > But how do I run this? I believe it is run in mailman-core (I am in a docker environment but that should not matter). I can get into the mailman shell, but that command does not work It is run in a Django management shell, not mailman shell. > ************** Question 2 > > What about pruning archives? I use to run a script for mailman2 to prune archives of messages older than X days for a list, Is that possible in mailman3 There are a few ways to do this. You can export the archive for a list as an mbox and edit the mbox to delete the messages you want to prune. Then delete the archive for this list and finally run hyperkitty_import to import the pruned mbox. Alternatively, in a django management shell, you could try something like ``` import datetime from hyperkitty.models import Email for msg in Email.objects.filter(mailinglist_id=X): if msg.date < datetime.datetime(Y, M, D, tzinfo=datetime.timezone.utc): msg.delete() ``` where X is the id of the mailing list you want to prune, or if you wanted to do all lists, just use Email.objects.all() instead of filtering on mailinglist_id. And, Y, M and D are integer Year, Month and Day for the cutoff. Note that something like ``` from hyperkitty.models import MailingList for ml in MailingList.objects.all(): print('{}: {}'.format(ml.name, ml.id)) ``` will print all the list names and their ids. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 7:44 PM, Alan So wrote: > I just notice that if I send an email to a list with a Cc header broken into multiple lines and the pair of double quotes are put in different lines, the email addresses afterwards will be wrongly rewritten. > > For example, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> tl;dr It is not valid to fold a header inside of a quotes string. First of all, the above is invalid. Presumably the address is intended to be "ABC DEF (XYZ)" <name(a)example.com> RFC 5322, sec 2.2.3 says in part: "The general rule is that wherever this specification allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP." and the definitions in sec 3.4 say in part: address = mailbox / group mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr display-name = phrase In this case, the quoted-string "ABC DEF (XYZ)" is a phrase which is the display-name and the only places where comments or folding white space are allowed is immediately preceding the "<" or following the ">" surrounding the addr-spec. Folding in the middle of the quoted string is not allowed. Were there no quotes, e.g. ABC DEF (XYZ) <name(a)example.com> Then ABC DEF is a phrase and (XYZ) is a comment and folding between DEF and (XYZ) would be allowed > It will become the following after going through the mailing list: > > CC: XYZ <"ABC DEF"@mail.server.name> Which is clearly wrong, but GIGO. > It seems that Outlook often split the To/Cc header into multiple lines and they often add double quotes to the full name of the users. Is the rewriting of Cc header handled by Mailman's code or another Python class? I haven't looked at the code to see exactly what's responsible here. I do note that adding double quotes around a display name is not only allowed, but is required if the display name contains "specials". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Digest Formatting

by Mark Sapiro

On 11/7/20 9:08 AM, Stephen J. Turnbull wrote: > > I thought there was a way to trigger immediate distribution of a > digest immediately, but I guess I'm remembering that from Mailman 2. > Neither the Postorius management interface nor the core documentation > suggests there's such a trigger in Mailman 3. There is nothing in the web UI or REST, but the `mailman digests` command can send accumulated digests for one or more named lists or all lists unconditionally or only if the list's digest_send_periodic is set to True. see `mailkman digests --help` for details. > > 2) I have customized list:member:digest:header, but am not seeing > > the custom text where I thought it should be. The documentation > > seems to imply that both list:member:digest:header and > > list:member:digest:footer surround each message in the digest > > Which documentation do you mean? As far as I know (Mark will have > authoritative information if I'm wrong), the digest header and footer > appear at the top and bottom of the *whole* digest message (ie, once > each per digest), not surrounding or in the bodies of the component > messages. Steve is correct. The layout is as follows The masthead from the list:member:digest:masthead template. The digest header if any from the list:member:digest:header template. The table of contents. The individual messages. The digest footer from the list:member:digest:footer template. For the MIME digest, these are all separate MIME parts and the individual messages are message/rfc822 parts within a multipart/digest part. For the plain text digest, the digest is one text/plain part containing the above formatted par RFC 1153 And in another post, mailman(a)manygoodideas.com wrote: > I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks. This already exists, it is list:member:digest:footer. Your confusion seems to be because you think the list:member:digest:header template and list:member:digest:footer template are prepended/appended to each individual message in the digest which would not make sense and is not the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Attachement processings questions

by Mark Sapiro

On 2/4/20 1:17 AM, Lars Schimmer wrote: > > Those mails are in the mailinglist archives, not on hold or anything. > Just the attachement missing. > > > So, please, howto fix the ascii encoding error in mailman3? > > Full trace: > Jan 31 03:02:43 2020 (32591) Uncaught runner exception: 'ascii' codec > can't encode character '\xe9' in position 109: ordinal not in range(128) > Jan 31 03:02:43 2020 (32591) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line > 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line > 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/pipeline.py", > line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/lib/python3/dist-packages/mailman/core/pipelines.py", line > 50, in process > handler.process(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/handlers/to_digest.py", > line 48, in process > mbox.add(msg) > File "/usr/lib/python3.7/mailbox.py", line 603, in add > self._toc[self._next_key] = self._append_message(message) > File "/usr/lib/python3.7/mailbox.py", line 758, in _append_message > offsets = self._install_message(message) > File "/usr/lib/python3.7/mailbox.py", line 830, in _install_message > self._dump_message(message, self._file, self._mangle_from_) > File "/usr/lib/python3.7/mailbox.py", line 215, in _dump_message > gen.flatten(message) > File "/usr/lib/python3.7/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/lib/python3.7/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/lib/python3.7/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/lib/python3.7/email/generator.py", line 432, in _handle_text > super(BytesGenerator,self)._handle_text(msg) > File "/usr/lib/python3.7/email/generator.py", line 249, in _handle_text > self._write_lines(payload) > File "/usr/lib/python3.7/email/generator.py", line 155, in _write_lines > self.write(line) > File "/usr/lib/python3.7/email/generator.py", line 406, in write > self._fp.write(s.encode('ascii', 'surrogateescape')) > UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in > position 109: ordinal not in range(128) This is <https://bugs.python.org/issue39384> You can fix it by patching the Python library email/generator.py as at <https://github.com/python/cpython/pull/18056/files#diff-220640ea02a24dfdbb0…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Search results for query "sapiro"