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

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 9:57 PM, Paul Arenson wrote: > Success. I first tried to send a sample here but it was over 40k so it is being held for moderation. Then I realized my own list is set to hold all messages now, including my own, so I sent it and I got a message telling me it was held for moderation. I could see the message and it looked perfect (have to look in mail client, not hyperkitty). > > Sent it out and it looks fine on both my computer and on my iPhone. > > > Hyperkitty archive is without the html view but it looks ok and the images show up as attachments. I have now accepted your held message. This list's content filtering collapses alternatives so what you see from the list and in HyperKitty is the plain text alternative that your MUA (Mac mail) created, but all the URLs seem to work as links even though displayed as truncated in the Hyperkitty view. Also this list will filter out images. HyperKitty will only display plain text parts in the message and thread views. Other parts such as html and images that pass the list's content filtering will appear as attachment links in HyperKitty. Anyway, it appears your issue is resolved by setting Filter content and Collapse alternatives to No. I'm glad it's working for you. -- 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: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/11/22 13:32, gordon(a)dickens.com wrote: > Hi Mark, > > I think that I found a hint as to the cause of my problems. > > I changed the apache2 LogLevel to debug and the following was then generated in /var/log/apache2/ssl_error_log: > > [Fri Feb 11 15:40:18.325675 2022] [core:debug] [pid 3982011] core.c(5280): (95)Operation not supported: [remote /var/lib/mailman3/web/static/uwsgi.sock:12150] AH00139: apr_socket_opt_set(APR_TCP_NODELAY) > > Apparently, there appears to be a problem with uwsgi.sock. > > My uwsgi.ini file has the following: > > uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock > > Also, my apache.conf for mailman3 has the followig: > > ProxyPass /mailman3 unix:/var/lib/mailman3/web/static/uwsgi.sock|uwsgi://localhost > > So do you see a problem in my configuration files that would cause the Operation Not Supported error with the uwsgi.sock file. I don't use uWSGI and have no experience with it at all, however here are some things to consider: For Apache to support uwsgi protocol you may need ``` a2enmod mod_proxy_uwsgi ``` However, I would suggest you use http rather than a unix socket. In your uwsgi.ini file instead of ``` uwsgi-socket = /var/lib/mailman3/web/static/uwsgi.sock ``` which requires Apache support for uwsgi protocol, put ``` http-socket = 0.0.0.0:8000 ``` which will tell uwsgi to listen on TCP port 8000 and in Apache, use ``` ProxyPass /mailman3 http://127.0.0.1:8000 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Changing default message limit (max_message_size)

by Mark Sapiro

On 5/24/19 7:05 AM, roger(a)reasonal.com wrote: > > $ bin/mailman shell -l list(a)example.com // Welcome to the GNU Mailman shell // The variable 'm' is the list(a)example.com // mailing list m.max_message_size = nn // commit() > > Unfortunately this does not work in the containerised mailman. > > So I get the container ID and run: > docker exec 3373d426996d /usr/local/bin/mailman shell -i test-list(a)iotcouncil.org.za > > (in the post by Mark it says "-l" but I get "unrecognized argument" -- I assume it should be -i for "interactive"? It should be -l or --listspec followed by the list posting address or list ID. I can't explain why you get "unrecognized argument". > Either way, it fires up the mailman shell and then throws me straight out back to the command line: > > Welcome to the GNU Mailman shell > The variable 'm' is the test-list(a)iotcouncil.org.za mailing list > >>> > [root@listman ~]# The above indicates there was a recognized '-l test-list(a)iotcouncil.org.za' argument because it knew to instantiate the list and assign it to 'm'. > So that doesn't help... I really can't help with Docker, but there is some issue that causes the command to exit as soon as it asks for input. It is waiting for interactive input and gets an end of file. Maybe @maxking can help with this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 10:16 AM, Abhijith PA via Mailman-users wrote: > > When I restarted mailman. I got, > > Jul 29 16:58:21 2020 (14473) SHUNTING: > 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > >> I think Mailman's var/ directory in the Debian package is >> /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? >> Is there a .pck file either in shunt/ or in out/? > > There is many .pck files in /var/lib/mailman3/queue/shunt and > /var/lib/mailman3/queue/out. And a lot of .psv files in > /var/lib/mailman3/queue/bad The .pck and (presumably one) .bak files in queue/out are messages waiting to be processed by out runner, the .bak is the one currently being processed. It appears your out queue is backlogged, but that is a separate issue and may just be transient. For every message in queue/shunt there should be a SHUNTING message and also an exception with Traceback logged in mailman.log. It is these Tracebacks we need to see to know what the issue might be. (If they're all the same exception, we only need one.) The .psv files in queue/bad are unparseable messages. There should be a "Skipping and preserving unparseable message:" entry in mailman.log for each of these. The messages can be seen with `mailman qfile` pointing to the .psv file. If they look like legitimate messages, it is possible a permissions issue that caused them to be unparseable. -- 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: new list not working

by Mark Sapiro

On 3/9/23 13:26, Christian via Mailman-users wrote: > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost during _handle_client() > What else is in the smtp.log? There should be messages like <timestamp> (<pid>) <message-id> smtp to redlatinleg(a)lists.ccalternatives.org for nn recips, completed in n.nnn seconds <timestamp> (<pid>) <message-id> post to redlatinleg(a)lists.ccalternatives.org from christian(a)naturalintelligence.us nnn bytes If there aren't, try setting [logging.smtp] level: debug in mailman.cfg, restarting Mailman core and see what you then get in smtp.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/23/24 11:56, Helio Loureiro wrote: > Hi, > it is python 3.10. Problem is... some mailing lists were created long ago, > with python2 something. Most probably 2.5. And the tables on mysql were > set to latin1. This has nothing to do with the data or the charsets/collation in the database. The issue is the locale setting in your python is causing stdout output from the `mailman members` command to be encoded as `latin1` and at least some user's display name contains a `\u0142` (i.e. `ł` character. > That I know. Question now is how to fix this. Any suggestion? What is > the table? I probably can run some script for these specific lists that > have the failure, import data as latim-1, and update back to the table as > utf-8. That's not the issue. The issue is the Python in your venv has sys.stdout.encoding set to latin1, probably for locale reasons. You ca apply this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -17,6 +17,7 @@ """The 'members' subcommand.""" +import sys import click from mailman.core.i18n import _ @@ -30,6 +31,9 @@ from zope.component import getUtility from zope.interface import implementer +sys.stdout.reconfigure(encoding='utf-8') + + def display_members(ctx, mlist, role, regular, digest, nomail, outfp, email_only, count_only): # Which type of digest recipients should we display? ``` to mailman/commands/cli_members.py to fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: particular list member seems unmanageable from CLI

by Mark Sapiro

On 8/22/25 02:32, Stephan via Mailman-users wrote: > We have a list member that got disabled due to bounces, but that should be fixed after we implemented DMARC and SPF. > > So as I don't know how to access the disabled status from the CLI (we have no GUI), I tried to delete and re-subscribe them. But although they are listed as a member, they cannot be deleted: > > # sudo -u list mailman members list(a)domain.tld | grep "$x" > M... <M....@web...> > # sudo -u list mailman delmembers -m "$x" -l list(a)domain.tld > Member not subscribed (skipping): M... <M....@web...> It looks like $x is `M... <M....@web...>`. It should be just `M....@web...` > How can I fix this from the command line? Either by restoring their "disabled" status, or deleting and re-subscribing them? There is no `mailman` subcommand to change a members delivery status. You can do it in `mailman shell` with an interaction like ``` # sudo -u list mailman shell -l list(a)domain.tld 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. The variable 'm' is the list(a)domain.tld mailing list >>> mbr = m.members.get('M....@web...') >>> mbr.preferences.delivery_status = DeliveryStatus.enabled >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Use own mail server

by Mark Sapiro

On 11/27/25 12:10 PM, johannes.wolf--- via Mailman-users wrote: > Thanks for your responses. > I just did a few tests and I changed my config the following way for the mailing: > > mailman.cfg > <<<<< looks OK >>>>>> > > postconf -n > <<<<< Looks OK >>>>>> > > When I try to subscribe to a list called "Smartcity" the email is processed and the smtp.log shows the following lines: > <<<<< All of which look as they should. >>>>>> > > mailman.log > <<<<< Looks OK >>>>>> > > On my relaying mail host the email is coming up in "MAIL FROM" is set "smartcity-bounces+johannes.wolf=tester.de(a)mailing.tester.de" but the fields "Header-From", "Recipient" and "subject" are empty. > Why is the e-mail passed to my MTA but the adresses are not resolved correctly from before in Mailman3? What's in your postfix mail.log or whatever it's called? What's in the relay host's log? What happens to the mail? You say the fields "Header-From", "Recipient" and "subject" are empty, but I don't know what this means. The relevant SMTP commands are MAIL FROM, RCPT TO and DATA. Any RFC 5122 headers such as Subject: are included in the message passed as DATA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 2 days

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/22/23 03:42, thomas--- via Mailman-users wrote: > Hello, > very new to mailman3, I used to manage mailman2 on a Debian 10 server. > The server has been upgraded to Debian 11 and mailman2 disappear… > > I try fresh install of mailman3, prerequisite to data migration, but without success. > If some can help, I would be really greatful. > > <VirtualHost *:80> > ServerName newsletter.mydomain.tld > > Alias /static /var/lib/mailman3/web/static > Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > > DocumentRoot /var/lib/mailman3/web/static > <Directory "/var/lib/mailman3/web/static"> > Require all granted You can probably fix the below error by adding options +Indexes here, but see below. > And now I have a 404 answer when consulting my http page. > > When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. It is unclear to me what is doing a GET of /static/admin/ and why. GETs should by of actual files, e.g., things like /static/admin/css/base.css > I am a bit lost with that. So are we. Questions about the Debian package are better asked of Debian. See https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… We can provide much better help and support if you install via the resources mentioned in the reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Rejecting held emails

by Mark Sapiro

On 04/26/2018 08:43 AM, Darren Smith wrote: > > We recently had a phishing message make it through our spam filters and > arrive at a mailing list. The good news is that since it was not from a > list member it was in the held message queue. > > I was able to find the message in the var/messages directory by searching > for a keyword in the subject. However, after rejecting the message from > Postorius, the message doesn't seem to be removed from the var/messages > directory. Do you mean Reject and not Discard? Phishing/Spam should never be "rejected" for backscatter reasons. Reject should only be used for somehow inappropriate posts from known people. > Is this expected behavior? I know that infosec people won't be too happy > about a phishing email sitting around on our disk. (Infosec guys are > notoriously paranoid. :) ) > > Is there some sort of cleanup process that would remove these messages? If > not, does this pose an issue where over time disk usage will creep up? This > could be a pretty significant problem if that is the case. It's not the behavior I would "expect", but it is the way it currently works, and yes, all your concerns are valid. This is <https://gitlab.com/mailman/mailman/issues/257> which I just edited to note that in addition to not removing the pending db entry, the message isn't removed either. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Search results for query "sapiro"