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

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by Mark Sapiro

On 11/19/21 9:43 PM, David Newman wrote: > ((reposting with correct subject line -- sorry!)) Actually, the original Subject was probably closer to the problem. > Greetings. I am attempting a complete Mailman 3 installation on a Debian > 10 system that already runs Mailman 2, following this documentation: > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Even following this guide, I'd had a lot of issues with permissions, > where directories and files were owned by list rather than mailman. > After correcting those issues, I then got to the point of checking > mailman3's status, and systemctl shows this error: > > Nov 19 20:09:57 [REDACTED] mailman[1463]: Error in atexit._run_exitfuncs: > Nov 19 20:09:57 [REDACTED] mailman[1463]: Traceback (most recent call > last): > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/usr/lib/python3.7/logging/__init__.py", line 2038, in shutdown > Nov 19 20:09:57 [REDACTED] mailman[1463]: h.flush() > Nov 19 20:09:57 [REDACTED] mailman[1463]: File > "/opt/mailman/venv/lib/python3.7/site-packages/mailman/core/logging.py", > line 67, in flush > Nov 19 20:09:57 [REDACTED] mailman[1463]: if self._stream: > Nov 19 20:09:57 [REDACTED] mailman[1463]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream' These generally stem from permissions errors preventing opening the log file. > There is an October 2019 thread on this error [1] but I think it's in a > different context, where the OP already had mailman3 running, and was > trying to migrate Mailman 2 lists. > > Also, regarding those permissions issues above, it matters which > "layout" value is in /etc/mailman3/mailman.cfg. I'd tried "dev" because > I saw a post from Mark Sapiro recommending that, I don't know in what context I recommended that. In my installs I use `layout: here` and in [paths.here] I specify an absolute path for var_dir. > but then mailman3 > wanted me to create a bunch of directories under /etc, even though > $var_dir was set to /var/lib/mailman3. Things seem to go better, except > for the confusion between lists/mailman ownership, when I set layout to > "debian", which was the default. It seems you may be using the Debian packages as our source has no `debian` layout. I.e., if you are installing with pip in a virtualenv, there would be no `debian` layout. If you are using Debian packages the Mailman user is `list` not `mailman`. > Thanks in advance for clues on addressing the ReopenableFileHandler > error above. Fix the underlying permissions error. -- 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: exim4 + mailman3 lmtp failure

by Mark Sapiro

On 5/6/20 12:52 PM, Thomas Drillich wrote: > lines from exim4/mainlog > 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu > 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT > 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) It's not clear to me from the log what is happening. It all happens within a fraction of a second, so there don't seem to be any time outs involved. It seems the first two entries are the delivery of the message from th(a)drillich.com to exim for seebruecke(a)listen.td3.eu. I'm guessing here because I don't know that much about exim, but it looks like exim is trying to connect to listen.td3.eu rather than localhost to deliver the message and most likely, port 8024 is not open to the outside which is correct. I think you need to add hosts_override = true to your transport definition to tell exim to use `hosts = localhost` rather than the host part of the email address. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/19/22 21:23, Stephen J. Turnbull wrote: > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > doesn't replicate that success. > > systemd doesn't know anything about venv. If it's possible to source > (not call as a command!) the venv bin/activate script via systemd, > that should fix it. If not, we'll have to figure out what it is that > the venv provides that the current systemd config does not. I would > guess that after sourcing the venv's bin/activate Our suggested systemd script at https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… has ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop /opt/mailman/venv/bin/mailman should work whether or not a venv is active. Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman is quite different from mine which is just ``` #!/opt/mailman/venv/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' __requires__ = 'mailman==3.3.5' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() ) ``` What is yours? and can you start mailman as the mailman user with ``` /opt/mailman/venv/bin/mailman start ``` without activating the venv? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: How to remove a message with an invalid Message-Id?

by Mark Sapiro

On 6/14/23 15:12, McGuire, Tommy M. (MSFC-IS61)[EAST2] via Mailman-users wrote: > I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? > > Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". This is https://gitlab.com/mailman/mailman/-/issues/1065 which is fixed for the next release by https://gitlab.com/mailman/mailman/-/merge_requests/1099 You will find the message queued at Mailman's var/archives/hyperkitty/spool/ directory. You can examine the pickled message object with `mailman qfile` and you can simply remove the file. If you want to "fix" it and archive it, A `mailman shell` interaction like this will do it ``` >>> import pickle >>> with open('/path/to/.pck/file', 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Message-ID', '<83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com>') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Moving mm3 -> mm3 to different host

by Mark Sapiro

On 10/19/23 02:38, Axel Rau wrote: > Hi all, > > There are lots of threads for mm2 -> mm3 moves, but only one > thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining > the steps, but I can't find it again. > > I have created a working mm3 installation on the new host with both > mailman and mail-web dbs imported. > hyperkitty archive seems to in the db. > > What are the next steps to complete the transfer? > > - rsyncing messages, lists and templates to new host You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db. > - Setting up DNS CNAMES to the new server > - Adapting exim to accept mails to the aliased domain > > - Can I keep the old listname, with the old domain name? As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery. > -What else has to be done ? I think that's it. -- 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: "Approved:" header from mailman2 times

by Mark Sapiro

On 04/09/2018 03:59 PM, Abhilash Raj wrote: > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: >> Hi, >> >> is there any equivalent to "Approved" header that was present in MM2 in >> MM3 land? Google is not very helpful in that. > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. I don't think it is broken, but it requires setting the moderator_password attribute for the list which can be set visa REST but I think not by mailmanclient. > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > Agreed. This is a shared password. and would be sent in plain text as a header or body line. It would be nice though to have some feature to enable, for example, spoof proof posting to a one-way (announce only) list. One thought on how to do this would be to have a list attribute that says posts from 'authenticated' owners and moderators can be auto approved and authentication could be by PGP signing the post. This would require Mailman to have the ability to verify a PGP signature from an owner or moderator which is not currently the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 12:42, ceo(a)sartrack.nz wrote: > I found the problem with Exim4. > The Exim4 config file should contain this: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > and NOT > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > Somewhere the documentation is wrong. The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} Where did you see MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > But I now have the next problem: > I send an email to a new mailing list called templist(a)sartrack.nz (I imported my old list members). > in /var/log/mailman3 I get an error regarding this; > The (final) error states: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/lists/templist.sartrack.nz/digest.mmdf' > > The file digest.mmdf does not exist there at all. Because Mailman was trying to create it and couldn't. I suspect you ran `mailman create` as root and the /var/lib/mailman3/lists/templist.sartrack.nz/ got created with user:group as root:root rather than the mailman user and group. Recent Mailman versions won't run the `mailman` command as root without a --run-as-root option for this reason. How are you installing Mailman? > The mailing server does not send out any emails for "templist" This is a separate issue from the above error, but it might also be a permissions error. What other errors do you see in /var/log/mailman3/mailman.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, 9 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/23/2017 08:16 AM, Rafael Mora wrote: > This is the content of my /var/log: > > > [root@localhost log]# pwd > /var/log > [root@localhost log]# ls > anaconda grubby messages-20170716 spooler-20170710 > audit grubby_prune_debug messages-20170723 spooler-20170716 > boot.log httpd mysqld.log spooler-20170723 > btmp lastlog php-fpm tallylog > btmp-20170701 letsencrypt ppp tuned > chrony maillog rhsm wtmp > cron maillog-20170702 samba xferlog > cron-20170702 maillog-20170710 secure xferlog-20170702 > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > cron-20170723 mailman secure-20170716 xferlog-20170723 > dmesg messages secure-20170723 yum.log > dmesg.old messages-20170702 spooler > firewalld messages-20170710 spooler-20170702 Your current postfix log is /var/log/maillog. The files like /var/log/maillog-20170702, etc are older versions rotated by logrotate. On 07/23/2017 08:14 AM, Rafael Mora wrote: > content of the file maillog-20170723 (I didn't find mail.log in /var/log): > > [root@localhost log]# cat maillog-20170723 You want to be looking at /var/log/maillog for current messages. ... > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Is this where these files are? You should have at least postfix_domains, postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the /var/lib/mailman/var/data/ directory. It this the case? > output command 'postconf -n': > ... > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp This is missing a / transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: configuring moderators per list

by Mark Sapiro

On 11/06/2017 02:33 PM, Dmitry Makovey wrote: > We're trying to configure moderator per list and so far we were only > able to add "superuser" accounts that can handle "Held messages", > "Members", "Banned addresses" etc. You can add ordinary users as Moderator or Owner of a list. I'm not sure what is and isn't currently working, but Moderators and Owners get notices of things like held messages and subscriptions and can approve or deny them. I think only Owners, not Moderators, should be able to change various list settings. Have you tried these things? Is it not working? > Is there a way to create special account per-list to manage some of the > aspects of particular ML without giving them all the permissions that > Superuser comes along with? An Owner of one list should not be able to do things to other lists. If you're looking for more granularity in permissions on a single list, Owners can do anything, and Moderators should only be able to deal with held requests, but there's no granularity beyond that. > In MM2 there was a ML password that moderator/list admin would use to > login to perform operations. > > Current setup allows list admins to add/delete existing lists which is > not desired. This was a site option in MM 2.1. I'm not sure about MM 3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:33 PM, Andrew Bernard wrote: > Hi Mark, > > Thanks for your great help. But despite decades of UNIX experience, my area > is not Django (yet). The nub of my question is that I thought you have to > have a manage.py file for Django to be able to set up the various affairs, > such as making the database migrations and so on. It is that that is > eluding me. Apologies for this hopelessly newbie question. The equivalent of manage.py in what I suggested is /opt/mailman/bin/django-admin. > I was impressed with your method of installation in the page referenced, > and I have foolwed that closely. But I am puzzled about the build script. > If I run as user mailman, not root, it wanted to install under /usr. which > of course results in permission denied. I had to modify the script to say > this: > > python setup.py install --prefix /opt/mailman/mm/venv If you want to install in the virtualenv, you should just activate the virtualenv and it should work. Perhaps the issue is that the build script at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> assumes the virtualenv is at /opt/mailman/mm/venv. You need to insure that the '. ../mm/venv/bin/activate' line is actually pointing to your 'venv/bin/activate' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Search results for query "sapiro"