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

[MM3-users] Re: Messages Showing Up as "Forwarded"

by Mark Sapiro

On 7/21/22 14:08, Mail Person wrote: > Sorry if this is an easy question, but I've got mailman3 up and running and all my test messages show up with forwarding language around them rather than just the message, see below: > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > This is a wonderful test > > > > ---------- Forwarded message ---------- > From: Person <person(a)gmail.com> > To: all(a)domain.com > Cc: > Bcc: > Date: Thu, 21 Jul 2022 13:56:22 -0700 > Subject: Hello Members > _______________________________________________ > Mailing list footer Are you looking at a MIME format digest or individual messages? If you are looking at a MIME format digest, this is expected depending on your mail program. You might prefer Plain Text Digests. If you are looking at individual messages, you probably have in your list's Settings -> DMARC Mitigations, DMARC mitigation action = "Wrap the message in an outer message From: the list" and DMARC Mitigate unconditionally = Yes. If you set DMARC mitigation action = "Replace From: with list address", the From: will be replaced, but the message won't be an attachment, and if you set DMARC Mitigate unconditionally = No, the selected action will be applied only to messages whose From: domain publishes a DMARC policy of reject or quarantine. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/22/23 09:32, Stephen J. Turnbull wrote: > > To diagnose, we really need to see that in context of the raw message > as received by the user. It was posted. The issue is the message declares Content-Transfer-Encoding: base64 but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output. > The only other thing I can think of is it might have something to do > with your internationalization settings. What is the default language > of the list? (This is available in Postorius.) Have you changed the > default encoding for English on your site? (I think you need to look > in mailman.cfg for this.) What is the default language of the site? I note that the message also declares Content-Type: text/plain; charset="utf-8" and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8. I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with Subject: =?utf-8?q?The_results_of_your_email_commands?= and Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -- 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: postfix virtual domain and mailman 3

by Mark Sapiro

On 12/25/19 1:53 PM, work(a)andrefincato.info wrote: > > question: i tried to add the `alias_domain` to mailman using Mailman Core REST APIs because I read about https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-… ; entering the mailman console and doing `dump_json('http://localhost:9001/3.0/domains/example.com/lists')` was giving me error that `dump_json` is not an available module. > > is that the way to go? should I add a an `alias_domain` to Mailman in order for it to output a `postfix_vmap` when doing `mailman aliases`? and then add it to postfix `main.cf` like so > > ``` > virtual_alias_maps = hash:/etc/postfix/valias, regexp:/opt/mailman/var/data//postfix_vmap > ``` I think the above should work for you. As far as `dump_json` is not an available module goes, the docs reference a lot of helper functions that are described at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/docs/documentati…>. These need to be imported. I.e., for dump_json ``` from mailman.testing.documentation import dump_json ``` But, if you are just trying to set an alias_domain for the domain and you have Postorius, you can do that via Postorius. If not Postorius you can use `mailman shell`, For example ``` $ mailman shell Welcome to the GNU Mailman shell >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = 'x.example.com' >>> ``` Then you need to do `mailman aliases` to create/update the maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Mark Sapiro

On 3/16/21 11:34 AM, Per Jessen wrote: > > I'm trying with this: > > find /var/spool/mailman/bad -type f -name \*pck |\ > while read m > do > (mailman qfile $m | grep -q ad.dr@ess) && echo $m > done > > Is there a better way? Yes, as you've noticed there is a significant startup cost every time you invoke the `mailman` command. to invoke it only once first see ``` mailman shell --details ``` (that refers to `mailman withlist` which is just another way to spell `mailman shell`). You will want to create a script similar to the following: import pickle from os import listdir def findaddr(address): for fname in listdir('/var/spool/mailman/bad'): if not fname.endswith('.pck'): continue with open(fname, 'rb') as fp: msg = pickle.load(fp) if address in msg.as_string(): print(fname) That's your script. Save it as findaddr.py where `mailman shell` can import it and run ``` mailman shell -r findaddr.py -- ad.dr@ess ``` This should print the names of any pickles that contain 'ad.dr@ess' Note however that this may not be necessary. If all you want is the names of the .pck files that mention 'ad.dr@ess', ``` grep ad.dr@ess /var/spool/mailman/bad/*.pck ``` should actually work reporting things like Binary file /var/spool/mailman/bad/*.pck matches with the actual file name, not *. -- 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: Permissions Error on /var/mail/mailman

by Mark Sapiro

On 2/3/26 10:28, dap1--- via Mailman-users wrote: > I am going in circles between postfix issues and mailman. However, before I continue with postfix debugging I want to resolve this first as it may be related for all I know. I'm getting this error in the postfix mail log: > > 2026-02-01T11:00:10.106626-05:00 dap002 postfix/local[113730]: 01623500076: to=<mailman(a)myhost.localdomain>, orig_to=<mailman>, relay=local, delay=0.16, de > lays=0.11/0.01/0/0.04, dsn=5.2.0, status=bounced (cannot update mailbox /var/mail/mailman for user mailman. cannot open file: Permission denied) > > I'm not sure why mailman is trying to write to that file but it is owned by root:mail. It is obvious why permission is denied to mailman. Is that directory really part of mailman3 and if so what should ownership and permissions be? If not then why is mailman trying to write to it? That path does not appear in any of the files in /etc/mailman3. Postfix is trying to deliver mail to a mailman@... address to the local user `mailman`. The user:group of the file /var/lib/mailman should be mailman:mail. if you `sudo chown mailman /var/lib/mailman`, those messages will be delivered to that mailbox and you can see what they are. What are all the log messages from `grep 01623500076 /var/log/mail.log`? Possibly you have set site_owner: mailman in mailman.cfg which would cause Mailman to send various notices to the local `mailman` user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/12/16 3:46 PM, deu8yz2mpq(a)snkmail.com wrote: > My quibble is that the multipart/digest encapsulation level is > gone. > > Barry Warsaw wrote at 15:16 -0400 on May 12, 2016: > > The MIME format of MIME digests should roughly be: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > But mm 2 had: > > multipart/mixed > text/plain (the digest heading) > text/plain (the TOC) > multipart/digest <--- this is the part that's gone in mm3 > message/rfc822 > message-1 > message/rfc822 > message-2 > ... > text/plain (footer) > > So was that removal intentional, a bug or ?? I'm sorry. I missed the point of your OP. I think it's a bug. The doctest at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, the part just after "The MIME digest has lots of good stuff, all contained in the multipart." is clearly missing the multipart/digest part. It appears that this got lost in the refactoring of the MM2 code for MM3. Please file an issue at <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me (msapiro), but it any case, I'll work on fixing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 1 month

[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, 8 months

[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

4 years, 4 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

7 years, 1 month

[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, 10 months

Search results for query "sapiro"