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

[MM3-users] Re: HyperKitty Question

by Samir Faci

Sorry about this, I had a draft ready to go sitting there for the past few hours. I stand corrected. I'm not sure what combinations of factors fixed this but it's all good now. base_url: https://lists.domain.org/hyperkitty/ worked. I have an archive and about 50 emails of me talking to myself while testing all this out. Thank you for all the help Marc and everyone else on the list. -- Samir Faci On Mon, May 4, 2020 at 7:36 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/4/20 6:11 PM, Samir Faci wrote: > > > > I have nginx running with multiple website being serviced from the same > > server. > > > > I updated the config where port 80 gets redirected to SSL. > > > > I tried setting mailman3-hyperkitty.conf to both: > > > > base_url: http://localhost/hyperkitty> base_url: > https://lists.domain.com/hyperkitty/ > > > > Either should be OK, possibly dependent of your nginx config. > > > But neither seem to be working. Does hyperkitty require traffic to be > > going over port 80? > > > No. https should work. Can you go to > https://lists.domain.com/hyperkitty/ in a browser? > > Do you have api_key: set in mailman3-hyperkitty.conf and is it set to > the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django > settings. > > Note the value needs to be quoted in > > MAILMAN_ARCHIVER_KEY = 'the_value' > > and not in > > api_key: the_value > > because the former is a Python string and the latter is a config value. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 4 months

[MM3-users] Re: RDS CA changes

by Hirayama, Pat

Thanks, Mark. That's what it looked like to me, but I wanted someone with more expertise / experience to weigh in. Have a great day! Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, August 12, 2024 10:49 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: RDS CA changes CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 8/12/24 10:23, Hirayama, Pat wrote: > > As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end? There are two places where the database access is defined. They are the [database] section in mailman.cfg and the DATABASES definition in Django's settings. I don't see a way in either of these to specify TLS for the connection, possibly it is set on the PostgreSQL side. In any case, I don't think there'd be any issue if the DBAs go ahead and update the certificates on their end. -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

1 year

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

I have run the below commands for sure: $ cd mailmanclient $ python setup.py develop And as you have suggested, I navigate to mailmanclient directory and ran the git log to provide you the version output. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 12:12 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > > Thank you Mark for your response. > > > > All the mentioned versions of all the components are taken from my > > currently running system only in which I am facing the issue. > > Did you run > > $ cd mailmanclient > $ python setup.py develop > > as it says at <https://docs.mailman3.org/en/latest/devsetup.html> > > I do not understand exactly how the various components are installed in > your installation, so I can't tell you what is wrong, but the version of > mailmanclient that gives you the AttributeError: 'MailingList' object > has no attribute 'get_requests_count' is not the one whose latest commit is > > ### Mailmanclient Version ### > > commit aaa529808e2d61899f90509da4ea802a70d2c8ff > Merge: ff39dd8 8670751 > Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> > Date: Thu Oct 15 01:09:32 2020 +0000 > > Merge branch 'fix-ci' into 'master'* > > Use GHCR for the CI image* > > See merge request mailman/mailmanclient!130* > > because that one won't have this error. > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

Thanks for your prompt reply.To import the config and archives I ran the commands as outlined in Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation : mailman import21 foo-list(a)example.com /path/to/mailman2/foo-list/config.pck python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox After running these commands the archives became available for most of the mailinglists. I didn't run the Django admin command with arguments "update_index_one_list" to build the indices for each mailinglist seperately. After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. Best regards,Eric On Sunday, December 13, 2020, 12:12:46 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote: > Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. > Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. > The imported members and other settings are correctly shown in the postorius page. > Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing? -- 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: Cron error

by Mark Sapiro

On 10/25/20 6:14 AM, Gordon Dickens wrote: > Hi Mark, and other helpful souls, > This cron error continues to occur at 12AM several times each week > but not each day > .Here is the output from the error message that is sent to the mailman3 > admin: > > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lo > ck > os.link(self._claimfile, self._lockfile) > FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|s > lc.mailhub4u.com|19728|1804933663424130229' -> '/var/lib/mailman3/locks/dbcreate > .lck' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/usr/lib/python3/dist-packages/click/core.py", line 716, in main > with self.make_context(prog_name, args, **extra) as ctx: > File "/usr/lib/python3/dist-packages/click/core.py", line 641, in make_context > self.parse_args(ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1089, in parse_args > rest = Command.parse_args(self, ctx, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 940, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > File "/usr/lib/python3/dist-packages/click/core.py", line 1477, in handle_pars > e_result > self.callback, ctx, self, value) > File "/usr/lib/python3/dist-packages/click/core.py", line 96, in invoke_param_ > callback > return callback(ctx, param, value) > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in init > ialize_config > initialize(value) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 218, in > initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 177, in > initialize_2 > config.db = getUtility(IDatabaseFactory, utility_name).create() > File "/usr/lib/python3/dist-packages/mailman/database/factory.py", line 50, in > create > with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __ > enter__ > self.lock() > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 248, in lo > ck > elif self._read() == self._claimfile: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _r > ead > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate > .lck' > > Then, the contents of the /var/lib/mailman3/locks directory is as > follows: > > -rw-rw---- 1 list list 80 Oct 25 00:00 > 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229' > -rw-rw---- 2 list list 78 Oct 26 2020 master.lck > -rw-rw---- 2 list list 78 Oct 26 2020 > 'master.lck|slc.mailhub4u.com|25024|3254783301248355113' > > I have since removed the file > 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229'. > . > Also, I had previously changed the permissions on the > /var/lib/mailman3/locks directory to give universal read/write > permissions:: > > drwxrwxrwx 2 list list 4096 Oct 25 08:11 locks > > Also, as user = list, I am able to create, edit and delete files in > that directory which really doesn't make any sense because mailman3 is > alsoÂ running as user = list when it creates the Permission denied > error. > Does anybody have an idea as to what is going on here and how to fix > it? The FileExistsError is possibly due to some kind of race condition between two `mailman` commands. Are you perhaps running both `mailman digests --periodic` and `mailman notify` via cron at midnight each night? If so, try running one if them a minute later. The permissions error is on reading the lock file itself. I don't understand what is causing that, but I doubt permissions on the locks directory are involved. -- 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: Help with some 'withlist' configuration changes

by Mark Sapiro

On 6/23/21 6:30 AM, David Partain via Mailman-users wrote: > Hi, > > Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version. > > In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do: > > sudo -u list mailman withlist somemailmanlist > m.max_num_recipients = 0 > commit() > sudo -u list mailman unshunt > > I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia. There is some other issue here as these things should only cause a message to be held, not shunted. Some exception is being thrown in the process of holding the messgage, and thaty is the real issue. What are the tracebacks in Mailman's mailman.log for these shunts? > My questions are undoubtedly foolish, but here goes: > > 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions. dir(m) or maybe you want >>> for x in dir(m): ... if not x.startswith('_'): ... print(f'{x}: {m.__getattribute__(x)}') ... > 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how... > > a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject'] > > b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages. As I note above, these things are reasons to hold the message. The shunting occurs because something is going wrong in the holding process. Find the errors and tracebacks in Mailman's mailman.log to see what the real issue might be. > 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile': > > ------------------------------------------------------snip snip---------------------------------------------- > [----- start pickle -----] > <----- start object 1 -----> > > <----- start object 2 -----> > { '_parsemsg': False, > 'digest_number': 457, > 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf', > 'lang': 'en', > 'listid': 'somelistid', > 'version': 3, > 'volume': 31, > 'whichq': 'digest'} > [----- end pickle -----] > ------------------------------------------------------snip snip---------------------------------------------- That is telling you there was in issue in sending the digest, the mailbox for which is /var/lib/mailman3/lists/somelist/digest.31.457.mmdf. Unshunting that will retry sending that digest. > 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas? > > 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these? You need to find the errors in the log and figure out what the underlying issue is. I'm guessing it's a permissions issue, possibly because of having at one time rum `mailman start` as root causing files to be created and owned by root and not be readable/writable by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

I followed instructions provided here. Well, I rebooted the server and I'm getting the same error again at the web page of "Mailman REST API not available. Please start Mailman core." I again found locks in /opt/mailman/mm/var/locks . Once I removed them I could start mailman. Perhaps I made a boo boo. I want mailman to start without locks upon reboot. Help! (thanks) -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 1:12 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-m > ailman > -automatically it says > > "Pay attention to the config file output above and make sure that you > see /etc/mailman3/mailman.cfg there. If the config path is different, > you should make sure to create a new config file at > /etc/mailman3/mailman.cfg and re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: > /opt/mailman/mm/mailman.cfg db url: > postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ REST credentials: > restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- 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/ NYAIOPZ3PLQCPT3QPLLRKMOUY52UORBM/ This message sent to csa(a)web-analysts.net

6 months, 4 weeks

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

Thanks. I'll think on that. My tables have a different prefix, so I'll have to remember where to change those config files... billo On Wed, 2024-10-09 at 13:18 -0700, Mark Sapiro wrote: > On 10/8/24 5:45 PM, Bill Oliver wrote: > > > > Is there a tutorial/instructions on migrating data from an old > > system > > to a new one? It's actually not the end of the world if I don't > > get > > all the old emails transferred, but I'd like to get the email > > addresses > > of the participants moved over easily... I believe that I set it > > up > > in 2020, but did not do any version upgrades since then... > > > There's no explicit doc, but there are some posts in the archives of > this list, e.g. > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/FTIC47FPQER5FLR4IW4CGI7JB6ALKIX4/>. > > The easiest scenario is if you want to migrate everything. You just > dump > the database on the old server and load it on the new one using the > database manager's tools. > > If you only want to move some, but not all lists, it's more > complicated, > but possibly the easiest thing is to migrate everything and then > delete > the unwanted lists and their archives from Postorius and HyperKitty. > > > -- > 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 billo(a)billoblog.com

11 months

[MM3-users] Re: Performance issues with Mailman 3

by Wong, Wesley

I can confirm the settings on the old Mailman 2.1 setup had "VERP_DELIVERY_INTERVAL=0" set. In Mailman 3, I had copied the configuration from an example with the following defined for the mta: verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 I'll disable it and see how things go on it. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 7, 2022 5:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Performance issues with Mailman 3 On 10/6/22 15:08, Wong, Wesley wrote: > Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I suspect the difference is your Mailman 3 instance has full VERP enabled and your Mailman 2.1 instance did not. I.e., In MM 2.1, you did not override the default `VERP_DELIVERY_INTERVAL = 0` in mm_cfg.py, but in MM 3 you have `verp_delivery_interval: 1` in the `mta` section of mailman.cfg. > I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: Search the Titles for `performance` at https://wiki.list.org/. The articles you find are all written for MM 2.1, but you're really dealing with the MTA and the issues are the same for MM 3. -- 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/

2 years, 11 months

[MM3-users] Re: Welcome message issue

by Mohsen Masoudfar

Thank you Mark! You are helpful as always. I am running: Postorius Version 1.1.2 That explains the issue. Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 22, 2024 5:38 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Welcome message issue [EXTERNAL EMAIL] On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

10 months, 1 week

Search results for query "sapiro"