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

[MM3-users] Re: Errors while importing mm2 list archives

by Mark Sapiro

On 12/8/22 07:23, Odhiambo Washington wrote: > MM3-3.3.7, Hyperkitty-1.3.6 > > While importing, I encountered several of this error: > > <CUT> > MySQLdb.OperationalError: (1366, "Incorrect string value: > '\\xF0\\x9F\\x98\\x8A, ...' for column 'content' at row 1") > The above exception was the direct cause of the following exception: ... > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", That's a 4-byte utf-8 encoding for an emoji. MySQL and MariaDB have to be told to accept 4-byte encodings. In the DATABASES['default'] definition, you need to set `'OPTIONS': {'charset': 'utf8mb4'}` Also, although it doesn't affect this, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/datab… You might also need to modify the tables, particularly hyperkitty_email with something like ``` ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4, MODIFY subject varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, MODIFY content CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; ``` -- 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: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 2/24/23 01:18, zoltan(a)circle-interactive.co.uk wrote: > Hi Everyone, > > we have mailman 3.3.8 venv test installation which in general works fine however > our mysql error log is filled up with messages below because they are so frequent. > > 2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) > 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) See https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html for information on debugging 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, 4 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Mark Sapiro

On 9/19/19 2:22 AM, Manos Pitsidianakis wrote: > Thank you again for your reply, Mark. > > Στις 2019-09-18 21:53, Mark Sapiro έγραψε: >> What are these entries? > > > I have these log entries, are these what you were referring to? > > https://paste.debian.net/hidden/37d863f6/ No. You referred to "shunted" mails. I assumed that mail was winding up in the shunt queue, but this is apparently not the case. >> The "Cannot connect to SMTP server" log message should not occur >> immediately on startup unless there are queued messages. That log >> message should only occur on an attempt to actually send a message. > > I think the problematic e-mails that cause this issue are stuck on the > outgoing queue. Right now there are 2 pck files and one .bak in > var/queue/out changing filenames repeatedly. What is happening is you have three messages in the out queue which are problematic. When Mailman or the out runner is restarted, for some reason the attempt to send these triggers the "Cannot connect to SMTP server" issue which is logged only once. Here's what happens: The oldest .pck file in the out queue gets picked up by the out runner and renamed to a .bak. The runner attempts to send the message and gets a socket.error exception so it requeues the message to be tried again. This removes the .bak and creates a new .pck. This process continues so the files keep getting renamed. I suggest you stop Mailman, and move the three files out of the out/ queue, and then restart Mailman. This should stop the out runner from "spinning" on these messages. Then you can examine the files with Mailman's 'bin/mailman qfile' command and see if you can identify something in the recipients list or other metadata that might be causing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Set Postorius interface locale

by Mark Sapiro

On 3/2/21 7:55 AM, Duane Raymond wrote: > > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? > 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Multiple things are required. In order to be able to set the list's preferred_language via Postorius, the language must be included in the LANGUAGES definition in postorius/utils.py. However, you can set the list's preferred_language in Mailman core via `REST` or `mailman shell` or direct update of the database. Then there must be message catalogs for the language in postorius/locale, django_mailman3/locale and hyperkitty/locale and these must be compiled by the Django management command `compilemessages`. -- 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: Missing Base64 encoding from control message reply

by Mark Sapiro

I have now seen a similar instance on one of my servers. I was able to get the raw garbled response from the user. I have asked to get the raw message that was sent, but unfortunately, I haven't gotten it and I suspect I won't. I think it was an attempted post sent by mistake to the LIST-confirm address. I have tried, so far without success, to duplicate this, but I will keep at it. The raw message is attached. This one is worse than the one in the OP in that the Content-Transfer-Encoding is base64, but the content is unreadable in the raw message. It is clearly not a valid base64 encoding. I'm guessing that the original message looked similar to the one in the OP, but Microsoft Exchange garbled it by doing some attempt at base64 decoding the unencoded plain text and placing that result in the message body -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: "From address" for list moderation notification

by Mark Sapiro

On 12/29/23 10:58 AM, ronn.ramirez(a)pge.com wrote: > Hi Mailman Group, > > I noticed that the from address for list moderation notifications are coming from a certain user address. > May you please help me figure out where to change this? > > In this example, I would like to change the From address "listadmin(a)domain.com" > > ================================================================ > -----Original Message----- > From: Admin <listadmin(a)domain.com> > Sent: Thursday, December 28, 2023 12:00 AM > To: dummy-list <dummy-list(a)domainx.com> > Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. > > The dummy-list(a)domainx.com list has 2 moderation requests waiting. > ... I do not understand "certain user address". I also don't undersatnd the above example. These notices are sent both From: and To: the list owner address. In the above example it would be From: dummy-list-owner(a)domainx.com To: dummy-list-owner(a)domainx.com Is this not what you see? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Mark Sapiro

On 4/17/25 11:35 AM, Mihai Moldovan wrote: > > New incoming messages will have the correct data, of course, but > imported ones wouldn't, so I'll have to use a more sophisticated > approach to handle them, probably by going through mailman's email > wrapper, figuring out how to generate a msgdata object for a message, > using RFC2369.process and maybe more. Here's an example script. You need to run this with /opt/mailman/mm/venv/bin/python to get access to the mailman imports. ``` from mailbox import Maildir, mbox from mailman.email.message import Message from mailman.handlers.rfc2369 import process from mailman.interfaces.listmanager import IListManager from mailman.utilities.email import add_message_hash from zope.component import getUtility mb = mbox('path/to/mbox', factory=Message, create=False) md = Maildir('path/to/maildir', create=False) mlist = getUtility(IListManager).get_by_list_id('your.list.id') for msg in mb: add_message_hash(msg) process(mlist, msg, {}) md.add(msg) mb.close() md.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 1:22 PM, Mark Dadgar wrote: > > Brian specified: > > verp_personalized_deliveries: no > > Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? That depends on the setting of verp_delivery_interval. If verp_delivery_interval = 1, every message will be VERPed regardless of verp_personalized_deliveries. If verp_delivery_interval = 0 and verp_personalized_deliveries = no, deliveries won't be VERPed as you note. If verp_delivery_interval = 0 and verp_personalized_deliveries = yes, only personalized deliveries (i.e. individual messages, not digests, from lists with Personalization enabled) will be VERPed. The theory is VERPing has a cost because it requires a separate message sent to each recipient rather than a single message with multiple recipients, but personalization also requires a separate message sent to each recipient, so those can be VERPed at no extra cost. But to be clear, automated bounce processing does not require VERP. It just works a tiny bit more reliably with VERP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 05:31, itservice--- via Mailman-users wrote: > How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net > I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. > unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. Unfortunately, there are some ESPs that will silently discard mail without giving any clue as to the reason. I think this is wrong, but there's nothing we can do about it. > At web.de they go to the SPAM folder. Is your mail server properly configured with a fixed IP and full circle DNS? Is it on any block lists (check at http://mxtoolbox.com/blacklists.aspx)? Are you DKIM signing your outgoing mail? Are you applying DMARC mitigations to your list mail? All these things are important. -- 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: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 2:14 PM, Andrew Hodgson wrote: > Mark Sapiro wrote: > >> The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no >memberships are deleted. > > Thanks, I ran this script and it did delete a load of Mailman users, I got output similar to this: > <User "" (47600399411039288509336192576257642185) at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? That was a choice I made. you could change ``` with transaction(): user_manager.delete_user(mm_user) print(f'{mm_user} deleted from Mailman') ``` to ``` with transaction(): try: email = user.preferred_address.email except AttributeError: email = 'no_preferred_address' user_manager.delete_user(mm_user) print(f'{email} deleted from Mailman') ``` to display the email address from the user's preferred_address if the user has one. All users should have one, but I've seen cases where there isn't one. It could also be ``` email = user.addresses[0].email ``` which might be better. In the above case, the empty string, "", is the user's display_name which in this case is empty, and the number in parentheses is the UUID of the user expressed as a decimal integer which isn't really useful. My thought was the display_name was as useful as anything, but obviously not if it's empty. I actually started with the preferred_address.email code above, but in testing, I got the 'no_preferred_address' result with the one deleted user so I, perhaps erroneously, went with the representation of the user. I'll probably update the script again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Search results for query "sapiro"