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

[MM3-users] Re: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > Thanks for your reply. My wife has fallen ill, so I am taking a break from working on this to take care of her. I'll reply substantively in a week or so, I hope. billo

7 months, 1 week

[MM3-users] Rejection based on total message size including attachments

by leith＠khimaira.com

As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Thank you for your time.

6 years, 8 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 06:52, Mark Sapiro wrote: > On 11/30/22 05:32, Jan Eden via Mailman-users wrote: > > > > I tried setting permissions on /opt/mailman/fulltext_index to 777 > > temporarily, but the issue remained (as expected). > > Are you running some security manager (SELinux, apparmor, ???) > > I suspect that's the issue. apparmor is disabled, and the error is only triggered when the directory does not exist: > # Make sure the index is there. > if self.use_file_storage and not os.path.exists(self.path): > os.makedirs(self.path) > new_index = True /opt/mailman/fulltext_index exists (and is populated), so I must assume that the Whoosh backend uses some other (non-writeable) path at this point. - Jan

2 years, 5 months

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

by Alan So

Mark Sapiro wrote: > In the absence of an issue at > https://gitlab.com/mailman/mailman/-/issues, > probably never. <hint> Is that anyone with a gitlab account can file an issue? If it is appropriate, I can try to file one. > Have you asked Microsoft to fix Outlook to not create these defective > messages? That's the real solution. Yes and I agree. My colleague has actually done so but it is probably not yet escalated to the appropriate tier of support. Here is the comment of my colleague: "I can submit this problem to Microsoft. However, it may take a long time to fix it or not even important enough to be fixed."

5 years

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 1:57 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> THANK YOU for all the help. > > > I'm glad we finally got it resolved. I may have spoken too soon: [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 729081): Term too long (> 245): XSUBJECT95251413 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 492, in update database.replace_document(document_id, document) xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 "XSUBJECT95251413“ has some serious weirdness embedded in it. Not sure how to search for that in the django shell? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 11 months

[MM3-users] Re: MM3 statistics

by Tom Browder

On Sun, Jul 23, 2017 at 20:57 Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Mark Sapiro writes: > > On 07/20/2017 01:22 PM, Tom Browder wrote: > > > Are there any plugins or programs for mm3 statistics? ... > If you can be more specific about the statistics you want, I can > compare to the Systers' implementation. I have no real thoughts about it. I have been talking up my pending mm3 server to my friends who are familiar with using some the paid mail services that provide various usage stats I assume are like resposnes to marketing mails and such. Our local community and tech groups are always interested in surveys that may be sent by e-mail. Thanks, Steve. -Tom

7 years, 10 months

[MM3-users] Re: /bin/sh: sassc: command not found

by Ralf Wiegand

Thank you Mark, where do I find this section of code? On 4/22/20 2:56 PM, Mark Sapiro wrote: > On 4/22/20 11:38 AM, Ralf Wiegand wrote: >> /bin/sh: sassc: command not found - Not sure on what I am missing? > > You currently have something like: > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > in your settings. > > Either install sassc or you can install ruby-sass and change the settings to > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > >

5 years, 1 month

[MM3-users] Re: Archive date/time vs elapsed time

by Mark

On 2023-06-28 00:42, Mark Sapiro wrote: > On 6/26/23 11:41 PM, Mark wrote: >> >> No, I don't see it on the MM users' archive. >> The archive where I'm seeing it is HyperKitty version 1.3.4 on a >> Debian packaged MM 3.3.3 >> The problem lay therein? > > > I don't know if this is a change since 1.3.4 or an issue with the > Debian package. The latest Debian stable (bookworm) has more up to > date packages if you can upgrade. > > In any case, this does not seem to be an issue in current HyperKitty. > Thank you Mark. I will try out the upgrade and report back.

1 year, 11 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Morris Jones

On 2/26/2021 10:55 AM, Mark Sapiro wrote: > Brian is correct. Essentially, you would need to run database queries to > get all the relevant data from the database and then add it to the > database of the new instance. A tool could be created to do the export > and import, but it doesn't currently exist unless some user has > developed one and not reported it. Would it be unreasonable to do a database dump on the old instance and a restore on the new one? Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 3 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by David Newman

On 1/6/22 2:40 PM, gordon(a)dickens.com wrote: > the mailman3-web and mailman3-full post-installation scripts These look like the Debian packages. Mark Sapiro can speak to this much better than I can, but the packages both on 10 and 11 are outdated and have some components that don't work, or don't work well. Better IMO to uninstall these and install current versions using the venv and web instructions: https://docs.mailman3.org/en/latest/install/virtualenv.html https://docs.mailman3.org/en/latest/config-web.html There is some overlap between these docs, but I can verify that this setup worked on Debian 10, and continued to work after upgrading to Debian 11. dn

3 years, 4 months

Search results for query "sapiro"