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

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/27/20 5:15 AM, skenny(a)scss.tcd.ie wrote: > > The effect of the template files not being readable by user "mailman" was interesting. Hundreds of lines like the following got written to mailman-core's var/log/smtp.log file at the rate of 4 per second: > > Jul 23 17:09:54 2020 (25) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fdf9e7b5f28> > > (the hex number was different each time). That's a `debug` level log message written for every delivery. It has nothing to do with the unreadable templates except that the unreadable template causes looping in an attempt to send the message. Did you perhaps set [logging.smtp] level: debug in an effort to diagnose the template issue? > Having excessively restrictive permissions on the template files is a silly - but easy enough - mistake to make. If it were possible to add it to Mailman 3, a more descriptive logging message could point others who make it in the right direction, perhaps. I spent a long time trying to figure out why messages weren't getting sent out from Mailman core, and in the end it was luck in form of a colleague's suggestion about file permissions that got me out of the rut. There is clearly a bug in that an unreadable template should just be skipped and the fact logged. I have reported <https://gitlab.com/mailman/mailman/-/issues/745>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/30/21 6:23 AM, Lucia Moreno wrote: > Hi Mark, > > We are facing the same issue. My postgres database is growing too fast and > I would need to do some creaning of old archives dated from 2001 and keep > only the last, lets say... 5 years. > > Could you please help us with the development of such a script? I have no > experience in python. The attached script is a rough idea. It assumes your Mailman is installed in a virtualenv at /opt/mailman/mm/venv and the django settings module is /opt/mailman/mm/settings.py. The pruned messages will be in a mbox at /opt/mailman/pruned.mbox. The age of messages to prune is defined by the days=365*5 argument in CUTOFF = datetime.datetime.today() - datetime.timedelta(days=365*5) All these things may need adjustment for your purpose. There is also a commented bit showing how you could do just one list. It's probably good to do just one list at a time since it's not clear how useful the pruned.mbox will be if it contains messages from multiple lists. I.e., run it for one list and move the pruned.mbox aside before doing the next list. Note that I've tested that this works, but it's possible that it will leave HyperKitty in a bad state. Backup your database before running this. -- 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: Archive download - unexpected end of file

by Mark Sapiro

On 3/1/25 13:58, Mark wrote: > > I have a MM3 list to whose archive I recently added an mbox file of > older emails. > > Viewing/searching the archive (Hyperkitty) is working fine. > > Downloading archives "for the month" or "last 30 days" delivers the > expected ".mbox.gz" file and those are fine. > > However, when I download the "Entire archive" and attempt to gunzip that > ".mbox.gz" file I get the error: " ... unexpected end of file". The process creating the zip for download times out. You can increase the timeout. If your wsgi server is Gunicorn, see https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi see https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri However, it's probably easier to get it in pieces. You can prpbably get chunks bigger than a month. Look at the URL for a month, e.g. for Jun, 2005 it will be something like https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. The start and end parameters determine what's included. E.g. for all of 2024 https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 Note that the end date is the first date not included, i.e. the day after the last date included. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Questions regarding message acceptance

by Mark Sapiro

On 7/28/20 6:35 AM, Pawel Grzywaczewski wrote: > Hello, > > I have few questions regarding usage of Mailman3: > > 1) We have list1 and list2 with members. Can we specify that all members of list1 can post messages to list2? This is a Mailman 2.1 feature that does not currently exist in Mailman 3. > 2) In explanation of “Accept these non-members” it’s written: “While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing”. > > I noticed that if someone posts to a list then he is added automatically to non-members. Which means that next time he will be able to post. > My understanding is that it’s better to use the feature “Accept these non-members”. Am I correct? You are mistaken. When a non-member attempts to post to a list she is automatically added to non-members with a moderation action of list default, which means that this and subsequent posts will be handled according to the list's "Default action to take when a non-member posts to the list" If you want to accept a non-member's posts you need to set that non-member's moderation action to "Default Processing" to still apply other tests that might hold the message or to "Accept" if you want to accept anything from that non-member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 9/30/24 14:44, jkoral(a)luc.edu wrote: > That makes sense. Are there instructions on how to do this? It depends on the MTA. For Postfix you probably have a set of aliases for each of the form: mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman" You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server. > Then once we are done migrating to the new server, then we can just change the DNS, correct? Yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: How to process emails with Mailman3?

by Kyle Lahnakoski

Thank you for this answer. In both the inject case and the netcat case I must know the recipient. My complex setup looses that metadata; leaving me with only the message. I guess I will be parsing the message to find that recipient. Thanks again On 2025-03-09 10:50 p.m., Mark Sapiro wrote: > Mark Sapiro wrote: >> The issue is you are not using nc correctly. >> When you do >> >> $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr >> >> you are telling nc to take commands from the file >> /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send >> the file. > Actually, what I said is not correct. The issue is you are just sending the data rather than engaging in an LMTP dialog. > > You need to send LMTP commands so you might prepend the message with > ``` > LHLO mymaillist.org > MAIL FROM: <sender(a)example.com> > RCPT TO: <all-request(a)mymaillist.org> > DATA > ``` > and append to the message > ``` > . > QUIT > ``` > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to kyle(a)lahnakoski.com >

11 months, 2 weeks

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > I wonder what this means and whether it's fatal. > > How do I fix it? > > ``` > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) ... > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > returned more than one EmailAddress -- it returned 2!* It appears you created a new list, and that list' owner email address has two Django user records with emails differing only in case. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you can just go to the Django web UI and delete the mixed case user. > I suspect it's something to do with my action yesterday while attempting to > reply to a thread from HyperKitty. Possibly, if hyperkitty was looking at a mixed case email address that it didn't recognize as a list member and subscribed it. > The superuser account uses my address - odhiambo at gmail dot com.I am also > the listowner for most lists. > I tried unsuccessfully to create an account on Postorious using the same > email address. > I kept getting sent links to verify the account, over and over. > Finally, I was able to verify the account, but cannot login with it. This too is probably because there are two accounts with email addresses differing only in case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Attack on Mailman Server?

by Mark Sapiro

On 3/9/23 11:34, Eggert Ehmke via Mailman-users wrote: > I had some attacks on my wordpress homepage today, I added some IPs to the > blacklist of my firewall. At the same time, I got several reports like this: > > Internal Server Error: /accounts/signup/ > > TemplateDoesNotExist at /accounts/signup/ > 429.html I suspect that's a coincidence. > Request Method: OPTIONS > Request URL: https://lists.eehmke.de/accounts/signup/ > Django Version: 3.2.16 > Python Executable: /opt/mailman/venv/bin/uwsgi > Python Version: 3.9.2 > Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/ > python3.9', '/usr/lib/python3.9/lib-dynload', '/opt/mailman/venv/lib/ > python3.9/site-packages'] > Server time: Thu, 09 Mar 2023 13:09:34 +0100 > > So it seems there were attempts to register new users but this caused this > internal error. Where can I send the complete error message? I would look in the web server logs to see what the actual accesses were. I'm guessing you'll find that some bot or script kiddies did a GET of /accounts/signup/429.html. You could also look for more detail in whatever log Django writes. This is defined in Django's settings as LOGGING['handlers']['file']['filename'] and is often Mailman's var/logs/mailmansuite.log. If you followed https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it is /opt/mailman/web/logs/mailmanweb.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I'm NOT blaming any of the parts involved... Sure, most probably is my > fault. But the last upgrade shows that the process that fail is involved > with mailman upgrade. The last server was working smoothly and it has > higher traffic than the first I tried. It cannot be that I missed that > something was not working for weeks (since the last upgrade of the OS) It depends on what you did. Mailman's lmtp runner would only encounter this issue at startup, so unless you restarted Mailman or rebooted the server, lmtp runner would have continued without issue even if there was an underlying OS problem. Also, I don't think the problem is with Mailman per se. The underlying issue is in the Python library socket module. Try the following in a Python 3 shell ``` $ python3 Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() ``` This is essentially what aiosmtpd does and I expect that `sock = makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] Protocol not supported` exception. -- 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: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 20:53, Bryan Fields wrote: > mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; > ERROR: update or delete on table "hyperkitty_thread" violates foreign > key constraint > "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table > "hyperkitty_email" > DETAIL: Key (id)=(35670) is still referenced from table > "hyperkitty_email". > mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; > ERROR: update or delete on table "hyperkitty_email" violates foreign > key constraint > "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table > "hyperkitty_thread" > DETAIL: Key (id)=(150555) is still referenced from table > "hyperkitty_thread". Well, that's a catch 22, you can't delete the email because it's referenced by the thread and you can't delete the thread because it's referenced by the email. You could always update those entries to remove the references, but deleting and reimporting is probably better. > I'll attempt to clean this up tomorrow an clean it up/re-import. > > Is there a quick/easy way to drop the entire archive from the db or must I > delete the entire list? If you can get to https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/ as a Django staff user or superuser, there is a Delete Archive button to delete the entire archive. Even if you can't get there, you may be able to get to the confirmation page at https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/del… -- 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

Search results for query "sapiro"