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

[MM3-users] Re: Mailman web Stopped working after upgrade

by Mark Sapiro

On 3/3/20 1:26 PM, David Krantz wrote: > Hi, > > I tried psycopg2-binary and a few other rehashes of that. Now I got it > working by downloading the source for psycopg2 manually and building > it myself, then I installed it into my venv like any other self-built > package. https://pypi.org/project/psycopg2/#files I'm glad you got it working. I think installing psycopg2-binary with pip should have worked, so I suspect there was some residue of psycopg2 somewhere in the search path ahead of the psycopg2-binary that was the issue. > I run mod_wsgi in Apache so I thought it should be enough to restart > Apache. Yes, that should be sufficient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/3/20 3:32 PM, Brian Carpenter wrote: > Hello Everyone, > > There was a message sent to a list that could not be archived by > Hyperkitty for the following reason: > > > WARNING 2020-11-03 17:20:54,507 800 hyperkitty.views.mailman Could not > archive the email with message-id > '<67BEBD75-B3DC-45E3-9C2F-55482F811238(a)ispdomain.com>': A string literal > cannot contain NUL (0x00) characters. > > It looks like there was a problem with the email message itself. What > causes such an error? A null byte in the message body. I suspect the message is still queued in Mailman's var/archives/hyperkitty/spool/ directory and is being retried with each new post. You can examine the message with Mailman's `mailman qfile` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Mark Sapiro

On 3/11/21 3:10 PM, Gilles Filippini wrote: > > Looking at the offending message with 'mailman qfile', it appears it is > a legitimate one actually, sent from an Android phone. > > Couldn't hyperkitty be a bit less strict? Possibly. It looks like this may be <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What HyperKitty version is this? <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. If your HyperKitty is >= 1.3.2, please file a new issue at <https://gitlab.com/mailman/hyperkitty/-/issues> -- 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: message size

by Mark Sapiro

On 7/12/22 10:18 AM, ronald.clarke--- via Mailman-users wrote: > Dear Mailman users, > I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: > "Message body is too big: 5312119 bytes with a limit of 2000 KB". > Is there any way to increase the maximum allowable size of attachments? In Mailman 3, there is a list setting for maximum list size. See Postorius -> Settings -> Message Acceptance -> Maximum message size, but the message you got is from Mailman 2.1. The appropriate list for that is https://mail.python.org/mailman3/lists/mailman-users.python.org/ In MM 2.1 this is controlled by the list admin UI General Options -> max_message_size. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 12:33 PM, bryan.kartzman(a)yu.edu wrote: > Sorry for the multitude of posts. I probably should have saved it all up for one post. > > I see in the hyperhitty_email table right after the "date" field there is a "timezone" field. I altered the "date" field to "timestamp with time zone" when I changed every timestamp field in the database from "without time zone" to "with time zone". Are there some (like this "date" field) that should have remained "without time zone"? The date field and the archived_date field should be `timestamp with time zone` in spite of there being a separate timezone field. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: An issue with the postfix_domains directory creation and the mailman start command.

by Mark Sapiro

On July 10, 2024 1:35:03 PM PDT, Keith Christian via Mailman-users <mailman-users(a)mailman3.org> wrote: >Ron, I get this: > > > 1 (venv) [mailman3@somehost ~]$ mailman conf | grep layout > 2 [mailman] layout: local > >I've added your paths to /etc/mailman3/mailman.cfg: > > 1 # /etc/mailman3/mailman.cfg > 2 > 3 [paths.here] > 4 var_dir: /opt/mailman3/mm/var > 5 bin_dir: $argv > 6 log_dir: $var_dir/logs > 7 data_dir: $var_dir/data > 8 > 9 > 10 > 11 [mailman] > 12 layout: here > 13 layout: fhs > 14 layout: local > Everything you put on lines 4-7 is irrelevant because line 14 overrides line 12. Remove lines 13 and 14. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

11 months, 3 weeks

[MM3-users] Re: Counter-intuitive header filter processing

by Mark Sapiro

On 09/18/2018 10:26 AM, Jonas Meurer wrote: > > Apparently, that's not the case. If the default message acceptance > setting for members is set to "reject", then mails from > *(a)freesources.org get rejected even though the header filter says > "accept". In other words, the default message acceptance action seems to > overrule any header filters. > > Is this expected behaviour? Yes. Rules are normally checked in a sequence defined in mailman/chains/builtin.py and that sequence checks several things including member moderation before checking header matches, so if "Default action to take when a member posts to the list" is anything other than "Default processing", that action will take precedence over header matches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Configure MM3 with separate IMAP Mailserver

by Mark Sapiro

On 1/2/23 03:44, clemens.leider(a)gmail.com wrote: > Dear all, > > we have managed to setup MM3 following the docker Installation concept/Tutorial. So far so good. However now i am struggeling with connecting to MTA. We are using imap server of our hosting provider.how to integrate that properly? Google was not too much of help unfortunately…looking for some tutorial or howto/step by step if possible. Assuming your Docker container can send TCP requests to the outside world, you need to set things in mailman.cfg like [mta] smtp_host: name or IP address of the IMAP server smtp_port: 587 or whatever the server's submission port is smtp_user: credentials for IMAP login smtp_pass: " " " " -- 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

[MM3-users] Re: Verification links to localhost

by Mark Sapiro

On 2/4/23 22:50, Lars Bjørndal wrote: > The verification link I get back when trying to add an account, referes > to localhost, e.g. > > To confirm this is correct, go to https://localhost:8000/accounts/confirm-email/Mw:1... > > Where do I change that? This message comes from Django allauth and is probably using what it thinks is the host that is doing the add. This is based on your web server configuration which I would need to see to be more specific. I suspect you are proxying requests to https://localhost:8000/ and you are missing a directive to pass the host. For Apache I think you want ``` ProxyPreserveHost On ``` and for nginx ``` proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Template URI gets written incorrectly

by Mark Sapiro

On 5/23/23 16:51, Mark Dale via Mailman-users wrote: > > When I create a template, it writes the URI incorrectly into the > template table in the mailman3 database and the list stops working. > > For example, it writes: > > http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… > > When I correct it like so, all is well: > > https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… > > Have I missed a config setting somewhere, or is this a bug with the > older Debian Mailman 3.3.3 ? You need to set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/' in your Django settings. Debian probably has set it to 'http://localhost/'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Search results for query "sapiro"