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

[MM3-users] Re: Null sender?

by Mark Sapiro

On 6/28/20 6:58 AM, tom(a)gather.coop wrote: > Does Mailman generally send email with a null sender? > > This is what I see in the log: > > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' > > Notice the empty MAIL FROM. > > Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. > > Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail. It isn't Mailman doing this. It is the MTA at mail.example.coop that is reporting the bounce of some message from the techque(a)example.org list. The log messages you see are Mailman's receipt of the bounce DSN. Bounce DSNs are always sent with a null envelope sender so if they are undeliverable, it doesn't result in another bounce. See <https://www.rfc-editor.org/rfc/rfc3461.html#section-6.1>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/25/24 23:07, Mark wrote: > > So, the template is all good, it can be accessed by Lynx, but the part > of the Mailman suite that sends out the custom Welcome message cannot > access it and spits out the error. > > Where are the custom templates stored? Is there a permissions issue > perhaps? A grep for the text of my Welcome message turns up zero results. They are stored in the postorius_emailtemplate table in the mailmanweb database. And yes, I think there is some permissions issue, but it is not simple. It probably involves apparmor or some other security manager. If it were simple, the mailman shell test I suggested at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… would fail. > By the way, in Lynx when the template's URI uses the public ip adress -- > ie. > > http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… > > ... it returns a "404 page not found" in Lynx. Which is probably why that setting sent the welcome with empty content. > Given that this is pretty much an out-of-the-box installation (venv > installation as per the docs) and everything else works perfectly I'm > thinking surely others have encountered this. Or is it just me? I just did a test on my development system and I see the same timeout error, so it's not just you. I'll work on this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: slow restart time for mailmanweb

by Mark Sapiro

On 12/28/21 1:28 PM, William Oliver wrote: > > If I just stop the thing and then start it, it goes fast. Here's that > log: > > Dec 28 16:27:22 emergenus systemd[1]: Stopping GNU Mailing List > Manager... > Dec 28 16:27:24 emergenus mailman[23408]: Shutting down Mailman's > master runner > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Succeeded. > Dec 28 16:27:27 emergenus systemd[1]: Stopped GNU Mailing List Manager. > Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Consumed > 42.834s CPU time. > Dec 28 16:27:27 emergenus systemd[1]: Starting GNU Mailing List > Manager... > Dec 28 16:27:29 emergenus kernel: [ 8076.868797] [UFW BLOCK] IN=eth0 > OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.108 > DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=58971 PROTO=TCP > SPT=44610 DPT=21987 WINDOW=1024 RES=0x00 SYN URGP=0 > Dec 28 16:27:29 emergenus mailman[23433]: Starting Mailman's master > runner > Dec 28 16:27:29 emergenus mailman[23433]: Generating MTA alias maps These log entries are from restarting mailman, not mailmanweb. > Dec 28 16:27:30 emergenus systemd[1]: mailman3.service: Can't open PID > file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not > permitted > > I don't know what's up with the pid thing -- it moves right on in about > 1 second. It's a race condition. systemd (systemctl start) is trying to read /opt/mailman/mm/var/master.pid before the master has created it. That's why it says (yet?). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: mailman findmember runs very slow

by Mark Sapiro

On 7/12/24 3:34 PM, Wong, Wesley wrote: > Hi, I am noticing a performance issue with Mailman 3 when using the "mailman findmember" CLI command to search for email address or name. On average, it takes about 15 - 20 seconds to run a query which is very slow IMHO. When searching through web administrator interface for Users, it takes only 1 -2 seconds. Is there a reason for such a discrepancy between the two interfaces? Is there any tuning to the CLI that could help with the performance issue? Here is the setup information regarding the VM hosting the Mailman 3 server: This is actually https://gitlab.com/mailman/mailman/-/issues/1095 The basic loop is at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… and the time consuming part is https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_f… On mail.python.org which has about 75,000 users ``` for user in getUtility(IUserManager).users: continue ``` takes a few seconds, but ``` for user in getUtility(IUserManager).users: emails = [address.email for address in user.addresses] continue ``` takes almost 3 minutes which is about the time that `findmembers` takes in total. I've tried changing this to ``` for user in getUtility(IUserManager).users: if len(user.addresses) == 1: emails = [user.addresses[0].emails] else: emails = [address.email for address in user.addresses] continue ``` but it doesn't help. Just referencing user.addresses in the loop as in ``` for user in getUtility(IUserManager).users: x = user.addresses continue ``` takes 3 minutes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Creating and placing custom templates

by Mark Sapiro

On 5/2/19 12:45 PM, kelly.close(a)lrewater.com wrote: > > Here's what I'm doing: > > I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ What is the setting, if any, for 'layout' in your mailman.cfg? If, for example, you have layout: fhs The default var_dir in that layout is /var/lib/mailman, not /var/lib/mailman3, although that could be changed in a [paths.fhs] section. > In that folder I created the following folders and made sure they were properly owned (by list:list) > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ > > Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". Yes, you do need the .txt extension. If this doesn't work, it's possible you have a different URI for the template. Try bin/mailman shell Welcome to the GNU Mailman shell'list:member:regular:footer', >>> tm = getUtility(ITemplateManager) >>> tm.raw('list:member:regular:footer', 'f2p2-test.udfcd-lists.org') This should return something like 'mailman:///$listname/$language/list:member:regular:footer.txt' Does it? -- 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: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Christian Stalberg

When I go to https://.../admin/ I get a Django Administration screen and in the upper right hand corner I see WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 13, 2021 5:55 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/13/21 5:11 PM, Mark Sapiro wrote: > On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: >> Is this anything to be concerned about? It seems like an attempted >> break-in as I have no user named alekos.pantazis. > > > First, this is a Django user, not a Mailman user.... > The error you see seems to say that > django_mailman3/templates/django_mailman3/profile/profile.py contains > {% load gravatar %} at line 3 but there is no > django_mailman3/templatetags/d_gravatar.py file. The above should say `contains {% > load d_gravatar %} at line 3` Regarding attempted breakin. It's not that. Just someone signing up or logging in at your web UI and visiting their user profile. If you go to your Django admin UI (https://.../admin/) you should see that user. The error seems to be something broken in your installation. Can you visit your user-profile? -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

[MM3-users] Re: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote: > Hello, > > We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings. You can accept HTML and not convert it if in Postorius -> Settings -> Alter Messages, assuming Filter content is yes, ensure Pass types includes `text/html` or maybe `text` to include all text maintypes and both Collapse alternatives and Convert html to plaintext are set to No. > The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash. > We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything. When you say you changed the character set to UTF-8, what did you do? If you set ``` [language.en] charset: utf-8 ``` in mailman.cfg and restart mailman core, that should allow those characters without replacing them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Mark Sapiro

On 3/3/25 07:52, Stefan Bauer via Mailman-users wrote: > > trying to update mailman3 to lastest version, we fail during > > mailman-web migrate with: > > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, > django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying account.0006_emailaddress_lower...Traceback (most recent call > last): > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", > line 89, in _execute > return self.cursor.execute(sql, params) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", > line 328, in execute > return super().execute(query, params) > sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang and replace psycopg2 with sqlite3. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… > We found a workaround to fake the migration with > > migrate --fake You should fix the issue with the DB and run the migrations. > Could this be some duplicate users with same mail-address? This is not related to Mailman users. It is Django users. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

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

by Mark Sapiro

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? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Subject Munging

by Mark Sapiro

On 7/5/24 08:34, Sam Darwin via Mailman-users wrote: > Hi, > > We have a user who is proposing that reply messages from a mailing list should be in the following format: > > Re: [MM3-users] Ubuntu 24.04 upgrade notes > > and not > > [MM3-users] Re: Ubuntu 24.04 upgrade notes > > Their reason... is that mailman2, and other lists, used to do it that way. > > I myself am agnostic about the difference, and probably prefer to keep things the way mailman3 recommends. > > The questions are: > 1. What could be explained to the user to convince them the new method is preferable. This is to support prefixes that contain %d for the message number. Suppose the prefix is [List #%d] and a post to the list has prefixed subject [List #501] A Subject. With old style, a reply a few posts later might have subject Re: [List #504] A Subject. But it is not a reply to [List #504], it is message [List #504] replying to `A Subject.` so the appropriate subject is [List #504] Re: A Subject. > 2. Can this be customized with a Setting? (Not that we will end up modifying it. Just curious). In mailman 2.1 this was called OLD_STYLE_PREFIXING and prefixes without %d could optionally do it the old way or the new way , but prefixes with %d always did it the new way. For Mailman 3 we always do it the new way even if the prefix does not contain %d. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Search results for query "sapiro"