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

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

Thanks all! I will use these pronto. On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > > > >> Mistakes were made, and for while every single outbound email bounced. > >> I've fixed the mistakes, but now in my largest and most active email > list, > >> every single user's delivery status is "Disabled by Bounces". > >> > >> Is there a way to bulk fix this? Or do I have to go into each user, > one at > >> a time, and fix them? > > > > Please see this thread: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > The script in that post does all lists. For a single list see > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > but note that the command line > ``` > $ shell -l list(a)example.com > ``` > should be > ``` > $ mailman shell -l list(a)example.com > ``` > > -- > 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 swd(a)pobox.com >

7 months

[MM3-users] Re: 120 gmail users removed from lists !

by Thomas Ward

Mark: Gmail will handle it as Gmail handles it. If the mail domain is Google even if it's custom-domain-example.com and it points to Google Workspace and Google Mail stuff, it'll bounce on the same rules unfortunately. I know this from working with Google Workspace domains myself with lists, it's a pain and they want a lot more stringent controls now. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 1:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: 120 gmail users removed from lists ! On 10/24/23 10:04 AM, Andrew Hodgson wrote: > > Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. The only domains you need to consider are those of your list members, probably only gmail.com, and maybe googlemail.com. I'm not sure how gmail would treat mail From: user(a)some.other.domain where the MX for some.other.domain is a google server, but that could be potentially any domain. -- 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 teward(a)thomas-ward.net

1 year, 7 months

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Mark Sapiro

On 10/26/20 10:07 AM, Torge Riedel wrote: > Hi, > > I frequently get this warning mail.log. stat'ing the files give: > > # stat /opt/mailman/var/data/postfix_domains > File: /opt/mailman/var/data/postfix_domains > Size: 361 Blocks: 8 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1573095 Links: 1 > Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-24 19:52:16.887258326 +0200 > Modify: 2020-10-20 07:09:48.792000000 +0200 > Change: 2020-10-20 07:09:48.792000000 +0200 > Birth: - > # stat /opt/mailman/var/data/postfix_domains.db > File: /opt/mailman/var/data/postfix_domains.db > Size: 12288 Blocks: 24 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1583965 Links: 1 > Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-26 07:46:54.569935782 +0100 > Modify: 2020-10-20 07:09:47.575889000 +0200 > Change: 2020-10-20 07:09:47.575889000 +0200 > Birth: - I don't understand how this is happening. With defaults for mailman.cfg settings you should have in the [mta] section configuration: python:mailman.config.postfix which points to the file mailman/config.postfix.py in the installation which has in its [postfix] section postmap_command: /usr/sbin/postmap These settings say whenever mailman updates `/opt/mailman/var/data/postfix_domains`, it runs `/usr/sbin/postmap` /opt/mailman/var/data/postfix_domains` to update `/opt/mailman/var/data/postfix_domains.db`. These files, `postfix_domains` and `postfix_lmtp`should be written and closed before invoking the posymap command, so Y don't understand why the modify/change times on the .db files would be 1.22 seconds earlier than those on the source. > I do not have the feeling that this is really a problem, cause > everything works well. But it is confusing and misleading and might > makes me missing a problem in the future, when the database is really > outdated. > > Could this be easily fixed in mailman? I don't think it's a Mailman issue. For example on the server that supports this list I see $ stat /opt/mailman/mm/var/data/postfix_* File: ‘/opt/mailman/mm/var/data/postfix_domains’ Size: 391 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113910 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.787818101 +0000 Modify: 2020-10-24 19:30:44.731817318 +0000 Change: 2020-10-24 19:30:44.731817318 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_domains.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112421 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:39:45.452615116 +0000 Modify: 2020-10-24 19:30:44.787818101 +0000 Change: 2020-10-24 19:30:44.787818101 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp’ Size: 3465 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113909 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.775817934 +0000 Modify: 2020-10-24 19:30:44.719817150 +0000 Change: 2020-10-24 19:30:44.719817150 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112424 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:40:38.509356931 +0000 Modify: 2020-10-24 19:30:44.775817934 +0000 Change: 2020-10-24 19:30:44.775817934 +0000 Birth: - Which is what I expect. Note that the only times both the `postfix_domains` and `postfix_lmtp` are updated together is when one of the `mailman` subcommands `aliases` or `start` is run. Are you possibly running both these at the same time causing some kind of race condition? -- 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: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Jered Floyd

This was entirely my fault. *facepalm* I replace styles/base.py when I do my container builds, so that I can override list defaults (personalization, subscription_policy, and dmarc_mitigate_action). I failed to notice the added dmarc_attributes attribute added to apply() --Jered ----- On Nov 25, 2023, at 7:49 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 11/25/23 16:25, Jered Floyd wrote: >> Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home >> from another episode of turkey overconsumption. >> >> I confess that I am not a python expert - once I create a new list, what’s the >> easiest way to inspect the object state? > > ``` > $ mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list(a)example.com mailing list > >>> print(m.dmarc_addresses) > [] > >>> > ``` > > -- > 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 jered(a)convivian.com

1 year, 6 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/26/19 5:22 AM, brunol(a)agro.uba.ar wrote: > > No errors/tracebacks in mailman.log. This is the output of debug.log configured as shown in my first post: > > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> to: lispruebas(a)mailman3.agro.uba.ar, list: lispruebas, sub: None, dom: mailman3.agro.uba.ar > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> subaddress: None, queue: in > Dec 26 10:02:37 2019 (696) b'250 Ok\r\n' > Dec 26 10:02:37 2019 (696) _handle_client readline: b'QUIT\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) Data: b'QUIT' > Dec 26 10:02:37 2019 (696) b'221 Bye\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) connection lost > Dec 26 10:02:37 2019 (696) Connection lost during _handle_client() > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbbb70> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f83fd0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483e0b8> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d8079438> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f70f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4a60f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981860> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483eda0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e2f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d80792b0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981e10> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e9780> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4d02c50> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbb550> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49cf048> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4983fd0> > > Those "Using agent: <mailman.mta.bulk.BulkDelivery object at " are constantly appearing, is this behavior normal due to the verbosity of the level? What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? On 12/26/19 10:24 AM, brunol(a)agro.uba.ar wrote: > I've also noticed that the messages are stuck in the "message" table (postgresql) and the corresponding files exists under /var/lib/mailman3/messages/ This indicates the held message has not been removed from the held message queue. You previously posted that you saw a log message > Dec 23 12:35:47 2019 (701) held message approved, message-id: CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com This message comes from mailman.app.moderator.handle_message() (in mailman/app/moderator.py). After logging that message, it requeues it in the 'pipeline' queue for further processing and deletes it from the message table and /var/lib/mailman3/messages/. This indicates that possibly subsequent processing is holding the message again. > Is there any relevant logger i should look on debug too besides the ones i already configured? set [logging.debug] level: debug in mailman.cfg to get more in debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/27/22 21:46, Odhiambo Washington wrote: > > On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> I see from another post that you've decided against using Twitter, but > >> to answer the question, Twitter does not require adding anything to > >> SOCIALACCOUNT_PROVIDERS. > >> > > > > I tried it and ended up with: > > > > ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: > > /accounts/twitter/login/ > > Traceback (most recent call last): > ... > > allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > > query does not exist. > > > Do you have > > 'allauth.socialaccount.providers.twitter', > > in INSTALLED_APPS? > Here is what I have in settings_local.py: INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', 'allauth.socialaccount.providers.facebook', 'allauth.socialaccount.providers.twitter', #'allauth.socialaccount.providers.stackexchange', ) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Cron error

by Mark Sapiro

On 9/28/20 7:38 AM, gordon(a)dickens.com wrote: > I recently upgraded to mailman3 on two Debian servers and I am getting a cron error periodically sent to me as depicted below. It looks like a permission problem, however, /var/lib/mailman3/locks and /var/lib/mailman3/* all have user = "list" and group = "list" and the cron job runs as user = "list" so I don't quite understand why I am getting these errors. > > ls -l locks" output: > total 12 > -rw-rw---- 1 list list 80 Sep 28 00:00 'dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' Does PID 24435 exist and if so, what is it? This is strange because it says PID 24435 has claimed the lock, but there is no lock which would be a file named dbcreate.lck if there is no PID 24435 or if it isn't related to Mailman, just remove the 'dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' file. > -rw-rw---- 2 list list 77 Sep 28 2020 master.lck > -rw-rw---- 2 list list 77 Sep 28 2020 'master.lck|slc.mailhub4u.com|5291|3708878559945320758' > > Here is the error message that is emailed to me: What command is cron running? Although it is some `mailman` command and the sub-command isn't relevant as it never gets that far, but the -C/--config option may be. > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lock > os.link(self._claimfile, self._lockfile) > FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|slc.mailhub4u.com|24435|4056142050254595815' -> '/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_parse_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 initialize_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 lock > elif self._read() == self._claimfile: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _read > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/

by Mohsen Masoudfar

Thank you Mark for your help. I see fedora under Django administration: Home > Social Accounts > Social Accounts as a provider listed, but we do not use it and I would like to remove it. So far I did not find a way to delete it. We do not need Hyper Kitty either, because we do not archive any emails. I appreciate if you could point me how I may delete Fedora as a provider. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, December 27, 2022 4:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /mailman3/accounts/fedora/login/ [EXTERNAL EMAIL] On 12/27/22 10:27, Mohsen Masoudfar wrote: > Hi, > I am getting the following errors starting some days ago. It is unclear to me what is causing this. I searched internet, there are some similar reports that mention bugs causing this. I am running mailman3 as Ubuntu 18 package and they do not provide any update for this. These are probably from some spammer trying to post to the sec_g_zoom(a)listserv2.aaas.org list from hyperkitty and trying to login via the fedora OpenID app which is not properly configured on your server. Do you actually want to support fedora as an OpenID provider? If not, you might remove 'django_mailman3.lib.auth.fedora', from INSTALLED_APPS in your Django settings. Otherwise, see https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdjango-al… -- 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… Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… This message sent to mmasoudf(a)aaas.org

2 years, 5 months

[MM3-users] Re: ***SPAM*** Re: How to hide sender completely

by Bill Oliver

Oops. Sorry for the digression. When I read the question, I thought the OP was asking about making the list itself anonymous -- difficult to find and resistant to subpoena -- not turning on anonymization inside of mailman. So... never mind On May 9, 2023 11:12:36 AM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 5/9/23 02:00, Roland Miyamoto via Mailman-users wrote: >> Could anyone tell me whether there is a way to hide >> the sender address of list mails completely from the recipients. >> >> Even for an anonymous list, the sender still occurs in two fields >> >> envelope-from <sender(a)sender-domain.tld> >> X-MailFrom: sender(a)sender-domain.tld >> >> of the mail header. >> Is there a way to suppress this information? > > >Anonymous lists should be removing any X-MailFrom: or X-Envelope-From: headers from delivered mail. The envelope-from in the outgoing mail should be the list-bounces address, not the original sender. > >If you are seeing this information in mail from an anonymous list, it is a bug and I would like to see a raw message as received from the list with this information. > >-- >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

2 years, 1 month

[MM3-users] Re: Post-installation documentation?

by David Newman

On 11/25/21 10:28 AM, Mark Sapiro wrote: > On 11/24/21 10:17 PM, David Newman wrote: >> On 11/24/21 2:36 PM, Mark Sapiro wrote: >>> >>> To import archives run the Django admin command with arguments >>> >>> hyperkitty_import -l alist(a)example.com >>> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox >> >> Good up to here, but ... hyperkitty_import not found. >> >> This wasn't covered in the venv docs: > > It is covered at > https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy > > Your issue is probably that the Django admin command you ran is not > accessing your `settings.py`. You may need to do > ``` > export DJANGO_SETTINGS_MODULE=settings > export PYTHONPATH=/path/to/directory/containing/settings.py > ``` > before running the Django admin command. These can also be given as > --settings and --pythonpath options to the Django admin command. Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced. On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain. Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file? Thanks dn

3 years, 6 months

Search results for query "sapiro"