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

[MM3-users] Re: Bottom line of message footer

by Brian Carpenter

On 2/14/21 9:05 PM, Mark Sapiro wrote: > On 2/14/21 5:40 PM, Tom Stoddard wrote: >> Here's another question that I have. A regular message just came into my >> email from one of the lists I'm a member of and it had a 3 line footer. >> The first two lines are fine, they just include the list's email address >> and an address to send unsubscribe requests to. The third line is this: >> >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> It looks to me like it should be a link to the group's list info page. >> Is this a bug or is there something I can do to fix it? It looks like it >> might be missing a forward slash after the first "s". > This is a list whose msg_footer was imported by The Mailman 3 process > that imports Mailman 2.1 lists. This import process will recognize the > default msg_footer and not create a list specific template for it, but > other things in the footer result in a list specific template which > needs to be reviewed for issues like this. > > The way for you to fix it is to create a list:member:regular:footer (and > maybe a list:member:digest:footer) template in your web UI which will > then override the existing list specific template. The available > replacements are listed at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > In templates they are all $ strings, e.g. $name. The %(name)s > replacements are Mailman 2.1 and won't work. Also, there is no > replacement for web_page_url because Mailman Core doesn't know what that > is, so you have to include the actual 'https://.../' value if you want > to include a web link. Thank you Mark. @Tom the templates you want to modify to add a Mailman 3 footer to replace the above are: Regular Message Footer Digest Footer -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

See, that's the oddness. There appears to be SOME weird mail loop here where $ORIGIN (MS365/Exchange) hands it once, then there's back-and-forth between SMTPPROXY and Mailman. IT's really odd how it behaves, and I have no explanation for it. Right now I'm away from the office where this happens, but when I'm back there I'll grab logs from both sides. Thomas On 12/5/23 17:54, Mark Sapiro wrote: > On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >> We use a multi-hop SMTP system to go from the inside of our network >> out to the Internet at the domain test.lists.example.com. >> >> The setup is this way for ingress: >> >> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >> Connector) -> Mailman for delivery to listserv >> >> Egress is this: >> >> Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET >> >> -- >> >> When a message is sent an invalid list (we'll call it >> invalid(a)test.lists.example.com) we end up with a nasty side effect in >> the system. The "no such recipient" response gets sent to the >> smtpproxy machine and then *it gets redelivered back to Mailman* as a >> redelivery as if it isn't accepting a permanent-failure condition code. > > > I don't understand why this is happening. Whatever MTA is seeing the > "no such recipient" status and creating the response DSN should be > sending it to the envelope sender of the original message so it should > not be sent to the invalid mailman address. Is one of the MTAs in the > delivery chain to Mailman rewriting the envelope sender? > > What are the MTA log messages from all the MTAs whos logs you have > access to? >

2 years, 3 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew.

2 years, 6 months

[MM3-users] Re: Manual setup - permissions

by Abhilash Raj

On Mon, Sep 23, 2019, at 3:02 AM, Tobias Hachmer via Mailman-users wrote: > Hi Mark, > > thanks for your response. > > On 9/23/19 1:29 AM, Mark Sapiro wrote: > > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: > >> > >> Now, running the scheduled tasks (which run from user+group "nginx") for > >> django I ran into permission problems, because the nginx user can't > >> access/write to the needed files in /opt/mailman3/core/... > >> > >> I would appreciate any hints how to run the different peaces of mailman3 > >> with the correct user/groups/permissions. > > > > > > Set up everything as user:group mailman3:mailman3. I.e., > > > > chown -R mailman3:mailman3 /opt/mailman3/web > > > > and set the uwsgi service to drop privileges to user+group "mailman3". > > So simple, now the scheduled tasks are working, but the whole web > service did not work because the web server user nginx can't access and > write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. > > # chown -R nginx:mailman3 /opt/mailman3/web > > This works for all. But isn't it a security risk that e.g. manage.py and > settings.py is read- and writeable by the webserver? You just need them to be readable, not writable. You could possibly use xattrs to do just grant read privs. You could also configure uwsgi to create a socket somewhere nginx can read it, `/var/run/uwsgi.sock` should be good enough. You can in theory also try https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html for systemd setup in which case you don't have to manually create sockets as systemd can do that for you. > > Regards, > Tobias > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by Abhilash Raj

> On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > On Sat, 13 Mar 2021 14:46:55 -0500, > Mark Sapiro wrote: >> >> On 3/13/21 11:14 AM, John Covici wrote: >>> >>> Now one thing came up while trying to create the database, I got a >>> traceback complaining about a revision error because gentoo had a >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I >>> upgrade mailman, am I going to have to do something to the database as >>> well and why should the database have some kind of reference to the >>> mailman version? >> >> >> I don't know why this is an issue. You shouldn't need to do anything >> with the database when you upgrade. Please post the full traceback and >> error message. > > Sorry I can't reproduce it, after dropping and recreating the database > the error went away, but it was in alembic and it was talking about an > invalid revision and gave a long hex string. > My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2). But that’s just my guess without looking at the traceback. > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com <mailto:covici@ccs.covici.com> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years

[MM3-users] Re: Confusing mailman user model

by Gilles Filippini

Mark Sapiro a écrit le 19/07/2020 à 17:30 : > On 7/19/20 8:10 AM, Gilles Filippini wrote: >> Hi, >> >> I'm trying to understand the Mailman user model, and I'm confused about >> the respective roles of tables 'auth_user' and 'user'. > > > auth_user is a Django auth table. These are the users listed in the > Django admin web UI. > > user is Mailman core's users. > > >> Both have an 'id' column referred to as 'user_id' when used as a foreign >> key. But there seems to be no relation at all between them as they use >> different ids for the same user. > > > Right, they are unrelated. > > >> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >> ago, and there is an inconsistency I'd like to fix: >> 2 of our users have a registered Mailman account with their respective >> email addresses in table 'auth_user', but these very same addresses in >> the 'address' table are linked to another old admin account in the >> 'user' table. > > Their Mailman account is the 'old' one. the auth_user account is a > Django account >> >> Then if add one of these addresses as a domain owner, it it the old >> admin address which is selected instead. How could I fix that? > > > That's because domain owner in a Mailman thing and involvs the Mailman > user. You could delete the Django users via the Django admin UI and then > re-register them via Postorius. That *might* work. When login into postorius, it is the Django account that is used, right? Then how is the mailman account retrieved from there? It seems UUIDs are used in the process, but I fail understanding how, so far. Wouldn't it be safe to retrieve the new Mailman account associated to these Django users, and link there emails from 'address' table' to them? _g.

5 years, 8 months

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

Hello, That’s going again! If I understood your advice correctly, if we do not have lists for which the gateway to the mail is set to yes, we can comment on the CRON "gatenew". This is what I will do > Le 17 mars 2023 à 07:50, Pierre Malard via Mailman-users <mailman-users(a)mailman3.org> a écrit : > > Hi Mark, > > Thanks for your answer and your lead > >> Le 16 mars 2023 à 18:34, Mark Sapiro <mark(a)msapiro.net> a écrit : >> >> On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: >> >>> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read >>> with open(self._lockfile) as fp: >>> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' >>> —————————————————————————————————————————————————— >>> CRON content: >>> —————————————————————————————————————————————————— >> ... >>> # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured >>> */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi >> >> Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. > > No, we don’t have > >> >>> I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". >>> When I run "/usr/bin/mailman gatenews" by hand everything is correct. >> >> Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. > > Their is no file with this name! > listesman:~# ls -ld /var/lib/mailman3/locks/dbcreate.lck > ls: impossible d'accéder à '/var/lib/mailman3/locks/dbcreate.lck': Aucun fichier ou dossier de ce type > >> >> >>> The questions I have are these: >>> We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". >>> What are they for? >>> Can we delete them? >> >> They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. > > Ok, is done. > > We will see today if it continues > >> >>> We have 2 files "master.lck..." dated from the day after tomorrow ! >>> What is this date? >>> Aren't these files the problem? >> >> >> Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. > > Ok, that’s smart :-) > >> >> -- >> Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> >> >> This message sent to plm(a)teledetection.fr <mailto:plm@teledetection.fr> > > -- > Pierre Malard > Responsable architectures système CDS DINAMIS/THEIA Montpellier > IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra > Maison de la Télédétection > 500 rue Jean-François Breton > 34093 Montpellier Cx 5 > France > > « Je n'ai jamais séparé la République des idées de justice sociale, > sans laquelle elle n'est qu'un mot » > Jean Jaures - 1887 > |\ _,,,---,,_ > /,`.-'`' -. ;-;;,_ > |,4- ) )-,_. ,\ ( `'-' > '---''(_/--' `-'\_) πr > > perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' > - --> Ce message n’engage que son auteur <-- > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to plm(a)teledetection.fr <mailto:plm@teledetection.fr> -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « La façon de donner vaut mieux que ce que l'on donne » Pierre Corneille (1606-1684) - Le menteur |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years

[MM3-users] Re: hyperkitty_import Unicode Errors

by Stephen J Turnbull

On 2023-05-07 07:39 Mark Sapiro writes: > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: >> django.db.utils.OperationalError: (1366, "Incorrect string value: >> '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column >> `mailman3web`.`hyperkitty_email`.`content` at row 1") >> >> Is there a known cause for this? Almost always nonconforming user clients. You write "frequently", but I'm guessing it's maybe 1% or 2% of all the messages, right? I suspect it's a particular author or institution using such a client. >> Is it fixed in some release more recent than 0+20180916? This is almost surely not something we can fix. Based on the error, it's in third party code (Django) that we import. It's possible we could provide a more explanatory message, but the only thing we can sensibly do is hold the message for an admin to edit it by hand. As long as the text in question and the Content-Type header aren't too sensitive, we can help with identifying charset (often UTF-8 as Mark suggests but why someone would be encoding FINAL MIDDLE DOT is a mystery to me). > I'm not sure what's going on here. My first thought is the database is > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > column charset definition is utf8 and not utf8mb4, but > '\\xE1\\x90\\xA7\\x0A\\x0A' is the 3-byte UTF-8 encoding for CANADIAN > SYLLABICS FINAL MIDDLE DOT ('\\xE1\\x90\\xA7') followed by two > newlines. so I'm not sure what the issue is. I'm guessing home-made client, possibly Asian or a spammer, which provides no content-type header. Even today I see raw 8-bit encoded text without an encoding spec from legitimate Japanese and Chinese sources, and of course with spammers all bets are off -- they might even do it deliberately to crash filters. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

2 years, 10 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by David Newman

On 1/7/22 2:48 PM, Mark Sapiro wrote: > On 1/7/22 1:51 PM, David Newman wrote: >> >> However, there's no evidence test messages to the list are going out. >> (Nondelivery was the reason I was mucking around in the admin panel in >> the first place.) >> >> The Postfix log shows delivery to the list address. >> >> MM3's smtp.log shows the usual handshake. >> >> However, I do not then see messages going out to subscribers in the >> Postfix log, and as one of those subscribers I do not receive a copy >> even though my preferences are set to receive my own posts. > > > Are the messages in Mailman's var/queue/shunt queue? There are 24 messages in the shunt queue, the most recent of which is a digest from 0000 hours today. The test messages I sent later today are not there. There are also 13 messages in the out queue. I can't read these as the filenames appear to change on every invocation of ls. > Are there errors > and tracebacks in var/logs/mailman.log? Not in response to today's test messages. Here is an entry of a test message I sent going to Hyperkitty. Jan 07 12:49:03 2022 (252309) HyperKitty archived message <6e88ec49-1326-92f9-aa17-1d4c1d6828be(a)domain.tld> to https://lists.domain.tld/archives/list/listname@lists.domain.tld/message/FH… But the Postfix log doesn't show it being distributed to me or anyone else. Oddly, neither of the two list owner emails (me and someone else) show this message in the archive via the admin panel. However if I log in as the list owner directly to the archives: https://lists.domain.tld/archives/ I can see today's test posts if logged in as the list member, but do not see the posts if logged directly into the archive as the Django superuser. The nondelivery of list mail is more serious than the archive problem, though. Thanks in advance for further troubleshooting clues. dn > >

4 years, 2 months

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

by Jonas Meurer

Hi Mark, Am 18.09.2018 um 20:48 schrieb 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. Thanks for the clarification. Maybe then the description for chain "accept" in postorius needs to be adjusted. Currently it says "Accept immediately (bypass other rules)". This gives the impression, that it will overrule the default action. A related followup question: what configuration is recommended for an announcement list where only specific senders (e.g. sender(a)example.org) should be allowed to post and mail from all (other) subscribers should be rejected? The only way I see to achieve this currently is: * Set default action for member posts to "Default processing" * Add a header filter to accept "sender(a)example.org" * Add a header filter to reject ".*" In my eyes, that's very counter-intuitive and cumbersome to configure. But maybe I just missed a more obvious and elegant solution to achieve the same? And one more comment: if I make the list an "anonymous list" (i.e. "hide the sender of a message, replacing it with the list address"), then header filters for the "from" header don't work any longer. That's kind of unexpected as well. I would have expected mailman to process the header filters at reading the incoming mail, not after rewriting headers of the outgoing mail? Cheers jonas

7 years, 6 months

Search results for query "sapiro"