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

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Mark Sapiro

On 7/18/24 7:58 AM, willie.castillo(a)caemilusa.com wrote: > Not sure what's going on here. This is the output of the "mailman3 info". What am I doing wrong? > > $ /usr/bin/mailman3 info > Traceback (most recent call last): ... > alembic.script.revision.ResolutionError: No such revision or branch '2156fc3f6f7d' The `mailman3` command is trying to run all the alembic migrations as part of initialization and is failing with this error. Thus, it never gets to the point of actually doing what you ask. What is the version_num in the alembic_version table in the database? I.e., ``` SELECT version_num FROM alembic_version; ``` and what does ``` ls /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ and grep -r 2156fc3f6f7d /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ ``` give? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 12:14 AM, Henrik Rasmussen wrote: > I have a problem removing the footer(s) from a list imported from MM2.1. I have been testing by entering my message in Hyperkitty (the list forum). > > I an aware about the double footer issue[1], and I am aware that footers are cached, but I have removed the footer files according to [2], run Mailman shell according to [3], restarted the Mailman (Mailman core, Mailan web, Postgres database and postfix). > > Did I miss something in order to remove the footers? Removing the files won't work because Mailman will fall back the the built-in footer. You have to create empty files. The easiest thing is just to 'cp /dev/null' to the footer files created by import21 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Installing MM3 via pip fails…

by Mark Sapiro

On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > I followed the instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > As soon as I get to the Django part things get hairy. It seems Django requires > something that was removed from it. What exactly is the issue? I just tried following the doc starting at <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> and doing everything through (venv)$ python3 manage.py runserver and I encountered no issues. One possibility is the Ubuntu 18.04 box on which I did this already had ruby-sass and python3-dev globally installed. sudo apt install ruby-sass sudo apt install python3-dev Did you install these? -- 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: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/30/20 1:25 PM, john_warland(a)hotmail.com wrote: > I came across this same error and solved it doing some googling and came across this statement. > > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > > change it to: > local_recipient_maps = > > It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this. Setting local_recipient_maps = disables all local recipient checks. If you don't want to do that, you need to specify whatever the current or default setting is in addition, e.g. local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/var/data/postfix_lmtp See <http://www.postfix.org/LOCAL_RECIPIENT_README.html> We need to update the docs for that setting. -- 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: unknown encoding: windows-874

by Mark Sapiro

On 5/13/20 5:00 PM, Mark Dadgar wrote: > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > LookupError at /hyperkitty/api/mailman/archive > unknown encoding: windows-874 HyperKitty is trying to archive a message which has declared the charset of one or more parts as windows-874 (a variant of iso-8849-11, latin/Thai). Python doesn't recognize windows-874 as known charset. You can probably find the message in var/archives/hyperkitty/spool/. As long as it's there, HyperKitty will keep retrying. You can move it aside, and if it looks like something you actually want to archive, you might be able to fix it, but that's tricky. The file in var/archives/hyperkitty/spool/ is I think a pickled email message object. You can view it with `mailman qfile`, but editing is tricky. -- 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: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 11:20 PM, Stefan Bauer wrote: > Unfortunately i need this, as the postfix is listening on all interfaces > and we have the policy to enforce TLS only. Nothing special in the logs: > > Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery > object at 0x7fbc29b1c4a8> > Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 There should be a `Dec 07 08:14:14 2021 (12303) Starttls` entry here. > Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: > ['recipient(a)own.domain'], size(msgtext): 5809 ... > > Is my mailman version maybe too old for this setting? > > I'm running GNU Mailman 3.1.1 (Between The Wheels) Yes, it's too old. STARTTLS support was added in Mailman 3.3.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: New install - The Message have no valid senders

by Mark Sapiro

On 3/31/22 00:44, kenneth.karlsson(a)eco.cept.org wrote: > I found a solution, i inserted > > always_add_missing_headers = yes > > in main.cf of postfix. > That seems to make the mail go through. I still dont get why it failed as the From: field was there. There was no From: header in your example. There was an envelope from, aka envelope sender, aka unixfrom, so it should not have failed. The mystery here is why the code at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… apparently failed to set the `MAIL FROM:` value. However, I think it's all moot because your test sent a message without any headers. A real post would probably have a From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 13:43, Odhiambo Washington wrote: > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > as2020+github(a)fam.tuwien.ac.at> wrote: >> >> I am running MM2 und 3 in parallel without problems, I do have a >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. >> > > Your setup can handle list1(a)domain1.name via MM2 and MM3, simultaneously, > right? :-) It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` simultaneously on the same server, but what is the MTA going to do with incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to both MM2 and MM3, but I don't see any practical use case for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/16/23 8:00 AM, eboltz(a)lhtservices.com wrote: > Installed MM3 on Debian 11, followed the steps from the MM3 website. > > I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. In Postorius -> Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Mark Sapiro

On December 20, 2023 7:20:17 AM GMT, Pierre Malard via Mailman-users <mailman-users(a)mailman3.org> wrote: >Ok, don’t throw any more away! > >If you really don't recommend the Debian packaged solution, I just have one question: >Why have you included it in the Debian "main" repositories for so long? We have no control over what's in Debian repositories. Maintenance and distribution of the Debian packages is done by Debian. We would love it if all the downstream distributions included up to date and bug free Mailman packages. The problem is when people encounter difficulty with a downstream package, we are often unable to help because we don't know the details of that package. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 years, 10 months

Search results for query "sapiro"