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

[MM3-users] Re: repeated headers in mails from mailinglists

by Mark Sapiro

On 7/12/24 11:30 PM, Tobias Diekershoff wrote: > Dear all, > > we have recently migrated from Mailman2 to Mailman3 and now discovered > that all mails going through Mailman3 have the headers Archived-At and > List-Archive repeated identically in the mail header ~100 times each. This should definitely not happen unless mailman/handlers/rfc_2369.py is broken. > We are running Mailman3 on Debian Bookworm from the Debian repositories > (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and > hyperkitty (1.2.1-1). This may be a Debian issue. See https://wiki.list.org/x/12812344 > Can somebody of you help me to get rid of the repeated header? You could in Postorius set Alter Messages -> Include RFC2369 headers to No, but this will not include any of the List-* or Archived-At headers at all which is not what you want. -- 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: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 9/30/24 03:00, Chupin Maxime via Mailman-users wrote: > Hi, > I upgraded my debian version, Issues with the Debian Mailman packages should be reported to Debian. Please see https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… > and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: > ``` > CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). > To fix them run 'python manage.py makemigrations --merge' > ``` > So I tried `mailman-web makemigrations --merge` that ended with > ``` > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' > ``` Did you run this as the Mailman user (`list` in the Debian packages)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/27/24 5:58 PM, Alain D D Williams wrote: > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > I am concerned about the connection lost message above. It is normal and not a concern. > Mailman sees it, the message ID matches that at the end of the first line > in the exim log (above): > /var/log/mailman3/mailman.log > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> So Mailman got the message and accepted it. > Is there any more logging that I can look-at/switch-on to see what is happening ? Is there anything else in mailman.log? Does the message get archived? Is there anthing in any of Mailman's var/queue/* directories? Is Mailman core running? Does `mailman members --nomail enabled` list any members? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/14/22 08:21, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > That combination at least produces multipart/signed messages with > > multipart/* parts containing a Content-Transfer-Encoding: header. > > > > The Python 3 email library considers this to be a > > InvalidMultipartContentTransferEncodingDefect() message defect. > > Merely containing C-T-E is not an error per RFC 2045, although it > seems to consider it a stupid thing to do. If present, it may be > "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). > > Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening > that restriction been published since? (I don't know why it would, > though.) Yes. The C-T-E on all the multipart parts was quoted-printable, not allowed under RFC 2045. > Even with a non-cleartext C-T-E, it seems reasonable for Mailman to > treat it as application/octet-stream and pass it through, unless the > list is configured to do something like strip application/octet-stream > or that requires decoding like spam-filtering (Postel principle, > although one could argue it shouldn't be sent on on the same principle > -- ah, the joys of being an e-mail Mediator). That would be > especially true it if were quoted-printable, since any relevant MIME > headers would (presumably) be pure ASCII and therefore unencoded. The Python email library says the message is defective. Mailman's lmtp runner in turn rejects the defective message with a 501 status https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… It could accept a defective message or one with specific defects, but this is problematic for further processing. For example, at least one MUA, Thunderbird, renders such a message with an empty body. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: ARC issues

by Mark Sapiro

On 3/2/20 7:45 AM, Stephen J. Turnbull wrote: > David Krantz writes: > > > Is there any known issues with ARC that I should be aware of? > > Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a > couple of Linux distros, supports the milter interface that Postfix > uses to call out to 3rd party processes, and the website looks good. > See rspamd.com. That said, if you want to use Mailman's support... I've been trying openarc <https://github.com/trusteddomainproject/OpenARC> with Postfix as well as Mailman's ARC. I still haven't got it all worked out - I have a fairly convoluted mail flow with the possibility of messages being altered before they ever get to Mailman. There is an issue with Mailman's ARC signing in a supporting library. See <https://github.com/ValiMail/authentication-headers/issues/5>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Where do I find the check_hk_archive script

by Mark Sapiro

On 11/18/23 11:21, Lars Bjørndal wrote: > In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run > the check_hk_archive script found in hyperkitty/contrib. When trying > `git clone https://gitlab.com/mailman/hyperkity`I get: > > Username for 'https://gitlab.com': > > Is it possible to get the script without an account on gitlab? I've updated some project settings. You should now be able to `git clone https://gitlab.com/mailman/hyperkity` without a gitlab account. However, why are you wanting to do this. If you have HyperKitty installed, there should be a hyperkitty/contrib directory in your installation, e.g. /opt/mailman/venv/lib/python3.x/site-packages/hyperkitty/contrib/ containing the check_hk_import and cleanarch3 scripts. Even if you don't have that, you can download the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/chec… -- 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: "mailman start" hangs

by Mark Sapiro

On 02/13/2018 05:40 AM, Peter Münster wrote: > Hi, > > When starting mailman in a terminal, then it works: > > --8<---------------cut here---------------start------------->8--- > $ mailman start > Starting Mailman's master runner > $ > --8<---------------cut here---------------end--------------->8--- > > But from "cron", it seems to hang. Output of pstree: > > --8<---------------cut here---------------start------------->8--- > |-cron(3022)---cron(21962)-+-mailman(21986) > | `-sendmail(22043)---postdrop(22044) > --8<---------------cut here---------------end--------------->8--- > > So it seems, that mailman does not go into the background, and the email > with the output is never sent... I think Abhilash's answer is probably closer to the mark, but there can be issues with running 'mailman' from cron or init scripts which don't set a UTF-8 compatible LANG in the environment as described at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html#runni…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: Changing posting address

by Mark Sapiro

On 11/7/18 10:59 PM, Johannes Winter wrote: > Dear list, > > I'd like to change the sending address of a mailinglist, but when I try > to set it via mmclient with > > ./manage.py mmclient > lists=client.lists > l=lists[listnumber] > l.settings['posting_address']='new name' > > > I get `ValueError: value is read-only`. > > Is it possible to change this value, or should I use another setting > for this objective? You can't change the list's posting_address. You have to change the list_name which you can't do via mmclient, but you can do via 'mailman shell'. If you want to change the posting_address without changing the list name, you can alias the desired posting address to the list_name@domain address in the MTA and add the desired posting address to the list's acceptable_aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Shunt Error Mail?

by Mark Sapiro

On 3/2/21 2:52 PM, Pete Ashdown wrote: > I have a number of list managers with subscribers who are confused as to > why their messages are silently disappearing. I've read the archives on > how to decipher why a message was shunted, but this is not workable at > scale. Is sending an error email back to the sender a consideration? Why are messages being shunted? Each shunted message has thrown some kind of uncaught exception which is logged with a traceback in Mailman's mailman.log. These should be due to bugs that should get fixed or possibly malformed messages which are almost always spam. In short, under normal circumstances messages should not be shunted at all and when they are it is something the site admins need to address. It is normally not something the sender of the message can do anything about. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Help! List traffic shunted to gmail/yahoo spam folders

by Mark Sapiro

On 7/10/21 2:42 PM, Matt Wilbur EFS via Mailman-users wrote: > Hello, > > I've been through DKIM hell and back. Now I'm to the point where when I > "show original" mail with gmail it says SPF, DKIM and DMARC all pass, > but it's still going to the spam folders. Does your list domain publish a DMARC record? If not publishing a DMARC record with policy of none may help, but it seems you are probably doing that. Beyond that, it is probably filtering based on something in the message content and the recipient ISPs will never tell you what because they consider that kind of information proprietary. Setting up feedback loops with gmail and yahoo also may help, but there's really not much else you can do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Search results for query "sapiro"