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

[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

5 years, 4 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[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

3 years, 1 month

[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, 9 months

[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

4 years, 2 months

[MM3-users] Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Christian Stalberg

Main.cf had transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then changed local_recipient_maps to transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains I then restarted postfix & mailman. When sending a message to the list I am still getting the same error I had before <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) help please! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, June 10, 2022 4:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected On 6/9/22 18:12, Christian Stalberg via Mailman-users wrote: > > -Added lists.ccalternatives.org to the mydestination line in > /etc/postfix/main.cf and restarted Postfix -Now a new error message: > <Deepadaptation(a)lists.ccalternatives.org>: host > lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 > <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: > User > unknown in local recipient table (in reply to RCPT TO command) See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml#transport-maps - in particular local_recipient_maps. -- 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/

3 years, 8 months

[MM3-users] Re: Good choice of defaults for content filtering?

by Allan Hansen

Excellent. Thank you, Mark. Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Jul 30, 2020, at 18:00, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/30/20 5:00 PM, hansen(a)rc.org wrote: >> Hi all, >> >> I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: >> a. What were those MM2 defaults (My MM2 server is long gone now). > > > You will find the content filtering defaults beginning at > <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. > These have been the defaults for new lists since Mailman 2.1.21. Prior > th that, the the default for pass_mime_types was > > ['multipart/mixed', > 'multipart/alternative', > 'text/plain'] > > >> b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. > > > If you go with the current defaults, except of course for setting filter > content on, you can add text/html to pass_types and any html parts that > aren't collapsed out by collapse alternatives will be kept and converted > to plain text. > > -- > 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/

5 years, 6 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/14/2016 07:11 AM, Mark Sapiro wrote: > On 5/13/16 5:05 PM, Simon Hanna wrote: >> On 05/12/2016 09:26 PM, Barry Warsaw wrote: >>> On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >>> >>>> It is the intent that Postorius will eventually expose all these >>>> settings. We're not there yet. At present you could possibly do this by >>>> interacting with mailmanclient, although I'm not certain the settings are >>>> exposed there. >>> >>> I'm not sure if they're exposed in mailmanclient, but they are exposed in the >>> core's REST API, on the member resource. It's the `delivery_mode` attribute >>> and it takes as legal values one of 'regular', 'plaintext_digests', >>> 'mime_digests', and 'summary_digests' (IOW, the enum item names for the >>> DeliveryMode enum). > >> They are exposed in mailmanclient and are used in postorius. They can be >> found in the users personal subscription settings >> https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > > You are correct. When I checked this before my initial reply, I never > pulled down the Delivery Mode list to see all the options. My bad. > > However, please correct me if I'm wrong, but there does not appear to be > a way in Postorius to set a list's mime_is_default_digest attribute. > You've got that one right. But I don't think core is exposing this through rest. At least it's not exposed via mailmanclient.

9 years, 9 months

[MM3-users] Re: MTA setup

by Arte Chambers

The shunt queue is empty. I see a 400 error "Bad Request" in the mailman logs, not sure what my next troubleshooting steps should be. mailman log: Dec 23 16:58:51 2024 (684048) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> Dec 23 16:58:51 2024 (684058) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/urls: <!doctype html> <html lang="en"> <head> <title>Bad Request (400)</title> </head> <body> <h1>Bad Request (400)</h1><p></p> </body> </html> (400) Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Dec 23, 2024 at 1:29 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 09:03, Arte Chambers via Mailman-users wrote: > > Update: After changing the DMARC settings messages are now going through > to > > my inbox, however they are still not being archived. > > > Yes, that's always been a separate issue. > > -- > 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 paul.m.robey(a)gmail.com >

1 year, 2 months

[MM3-users] Re: Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Sapiro

On 04/20/2017 05:37 PM, Mark Lindsay wrote: > > I'm new to Mailman 3 and Mailman in general, but I've got it up and > running, and my external app is communicating quite well with the > administrative REST API. Cool. > Here's the only problem I haven't been able to figure out: > > Say I have a list called "potato." List members can post to the list by > emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail > for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to > the list too. The command email gets sent out to all members, as if the > user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. > This is also the case with the potato-request(a)lists.mydomain.org address. > > I am using exim4 on Ubuntu. I followed the instructions here: > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The > only change I had to make to the exim4 config files in the readthedocs > instructions was in this line: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > I had to change it to: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > > That is how the subdirectories are named in my lists directory. e.g. > potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from > readthedocs, I get 550 Unrouteable bounces. OK. That document needs updating. Also, the '-admin' local_part_suffix should not be there, but that's not related to your issue. '-admin' is from MM 2.1 and isn't used in MM 3. > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >> `? That's the key question. The transport is supposed to just relay the message to Mailman via LMTP to MM3_LMTP_PORT, but it appears to be rewriting the envelope recipient from potato-leave(a)lists.mydomain.org to potato(a)lists.mydomain.org. I suspect the router is somehow stripping local_part_suffix from the recipient address, but why, I don't know. > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through it. We want to make MM 3 work with Exim as an MTA. Unfortunately, I have not used Exim as an MTA in a long time and not with Mailman 3 at all, so I may not be much help. I think the person who set up Exim is on this list and may reply. If not, I'll try to research this further. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

Search results for query "sapiro"